Opened 9 years ago
Closed 9 years ago
#1359 closed (fixed)
Allow requesting GENI stitching on ExoGENI only links
| Reported by: | Aaron Helsinger | Owned by: | xyang@maxgigapop.net |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | MAXSCS | Version: | SPIRAL7 |
| Keywords: | Cc: | tlehman@maxgigapop.net, lnevers@bbn.com | |
| Dependencies: |
Description
By default, the SCS does not provide a path for links between ExoGENI resources.
Add new options to allow optionally getting GENI stitched paths between ExoGENI resources.
The default would be that you get no GENI stitching path for a link between 2 EG sites, but with a particular option specifying a path by name, the SCS would attempt to generate a GENI path for that connection and return an error if that is not possible. This would be passed under options -> geni_routing_profile -> path_id, where we'd add a new optional argument: attempt_path_finding: True (default False).
In addition, also support:
- A different top level option (not per path, so parallel to geni_routing_profile) that gives this behavior for all EG only links in the request. Call this new option "always_attempt_path_finding (a boolean, default False).
Again, any link in the request for which the SCS cannot find a path causes an error when this option is supplied.
Support attempt_path_finding option both at global level and in per-path routing profile.
Patched code on Test server.