Force use of ExoSM if RSpec has >1 ExoGENI AMs

[ahelsing]

If an RSpec has >1 ExoGENI AMs, then ExoGENI requires that you use the ExoSM and not the local rack.

Enforce this in stitcher.

Imported from trac ticket #689, created by ahelsing on 09-09-2014 at 14:15, last modified: 09-10-2014 at 17:02

[ahelsing]

Heidi suggests that she heard this restriction may get lifted by GEC21. I wrote to Ilya to find out if I should be fixing this now, or wait for the restriction to be lifted.

Trac comment by ahelsing on 09-09-2014 at 14:31

[ahelsing]

To make this work

• must combine dependencies lists (_dependsOn and isDependencyFor) and hops lists (_hops) and path lists (_paths)
• reconcile userRequested
• what do we do with the now multiple alt_url values?
• Ensure there is only a single Aggregate object in the cls.aggs list. That list is by URN.

Where do we do this check / reconciliation?

• Do once early in mainStitch loop around line 697 before looking at the URNs back from the SCS?
• In add_am_info?
• After the call to add_am_info?

Trac comment by ahelsing on 09-09-2014 at 14:53

[ahelsing]

Ilya says ExoGENI sites will continue to refuse requests that include resources from more than 1 EG site. He suggests that ExoGENI stitching and the ExoSM will work with multiple ExoGENI sites, but it's unclear so far exactly what he is saying. My testing says the ExoSM can't handle a request for 1 UH node plus 1 GPO-EG node stitched to 1 GPO-EG node (I get "Invalid slice urn")

I worry I'm going to have to instead have multiple request RSpecs that are submitted to the individual sites somehow.

Trac comment by ahelsing on 09-09-2014 at 14:56

[ahelsing]

See #692 for limitations

Trac comment by ahelsing on 09-10-2014 at 17:02