If a single EG AM is involved in 2 EG only links, you cannot make only 1 be EG only.
The problem is that the SCS will create a path for the one you request, but the ExoSM will also create a path for that link: there is no way to tell the ExoSM to not create a circuit for that path.
I think currently this may not really be an issue
because there aren't that many EG sites
because EG is limited to a single link at the moment.
Can we edit the request to the ExoSM to tell it to set up the link out the GENI stitching interface for a link, and not create an ExoGENI link for that path?
Or must we insist that any link for which both endpoints are (going to be) the ExoSM must be EG stitching?
Check out the ensureOneExoSM method.
Imported from trac ticket #765, created by ahelsing on 01-12-2015 at 08:54, last modified: 01-30-2015 at 13:42
If a single EG AM is involved in 2 EG only links, you cannot make only 1 be EG only. The problem is that the SCS will create a path for the one you request, but the ExoSM will also create a path for that link: there is no way to tell the ExoSM to not create a circuit for that path.
I think currently this may not really be an issue
Can we edit the request to the ExoSM to tell it to set up the link out the GENI stitching interface for a link, and not create an ExoGENI link for that path?
Or must we insist that any link for which both endpoints are (going to be) the ExoSM must be EG stitching?
Check out the ensureOneExoSM method.
Imported from trac ticket #765, created by ahelsing on 01-12-2015 at 08:54, last modified: 01-30-2015 at 13:42