workflow: add ping-mesh workflow #1640
Conversation
|
please squash your commits |
dvandra
force-pushed
the
workflows_pingmesh
branch
2 times, most recently
from
3ce5113 to
15c8d08
Compare
dvandra
force-pushed
the
workflows_pingmesh
branch
4 times, most recently
from
506df31 to
eb31dd0
Compare
nplanel
force-pushed
the
workflows_pingmesh
branch
from
eb31dd0 to
54bf4af
Compare
dvandra
force-pushed
the
workflows_pingmesh
branch
from
54bf4af to
afbb4cc
Compare
|
You need to rebase and change the parameter names according to the new yaml tags |
dvandra
force-pushed
the
workflows_pingmesh
branch
from
afbb4cc to
9cde40d
Compare
| }); | ||
| }).then(function () { | ||
| return result | ||
| }).finally(function () { |
There was a problem hiding this comment.
the order should be catch and finally
|
Hi @dvandra & @masco-enovance I was looking on this today, trying to make this work. It look os ok, but not working so well. I was able to get
Also ... if you have any future plans to enhance and you can share it will be good ... we would like to enhance this workflow with the help of some students if possible so we want to sync on plans forward. |
|
run tests |
|
@eranra I did a review, and packets are not injected correctly, that's why you having random behaviour |
|
@eranra We have a doc with somes workflows/use cases ideas. I can share and we can discuss about that tomorrow during the weekly |
dvandra
force-pushed
the
workflows_pingmesh
branch
from
9cde40d to
f7aa075
Compare
May be now it is working.
|
dvandra
force-pushed
the
workflows_pingmesh
branch
2 times, most recently
from
dd8ba4a to
f74f52a
Compare
| var pktform = {}; | ||
| client.gremlin.query(src).then(function(nodes) { | ||
| nodes.forEach(function(node) { | ||
| sources.push(node.Metadata.TID); |
There was a problem hiding this comment.
you can just avoid to add the node in sources when dst == node.Metadata.T
dvandra
force-pushed
the
workflows_pingmesh
branch
from
f74f52a to
04e727a
Compare
Check connectivity from/to multiple points at once