Handle fake path in SCS workflow

GENI-NSF / geni-tools

Omni, stitcher, GCF sample aggregate manager, and other GENI tools.

Other

11 stars 15 forks source link

Handle fake path in SCS workflow #511

Open ahelsing opened 9 years ago

ahelsing commented 9 years ago

The SCS is adding a fake path in the workflow_data structure. This 'path' represents a merge of all the requested paths, with the cumulative dependencies across all AMs and hops.

How should stitcher handle this?

compare with our own calculation of AM dependencies?
ignore?
stop doing our own calculation?

For now, don't break.

Imported from trac ticket #511, created by ahelsing on 02-17-2014 at 13:39, last modified: 10-15-2014 at 13:23

ahelsing commented 9 years ago

the loop over paths in the workflow now skips a path by that name. Still need to do something with that data

Trac comment by ahelsing on 02-17-2014 at 13:53