195 | | Expedient, the OpenFlow aggregate manager, requires a two-step process to reserve resources: First, the experimenter creates their sliver to request the resources, but then an OpenFlow admin at each aggregate uses the Expedient Opt-In Manager to approve the request. We didn't want to have to do this live, times six aggregates, at the demo itself, so we pre-provisioned the OpenFlow resources for each network into a separate slice, and just left those in place the whole time. Each OpenFlow sliver points to one of two ports on an OpenFlow server at GPO Lab, so when the demo users log in and start their controllers, the switches re-connect to the appropriate controller, and voila. |
196 | | |
197 | | Also, NLR and Internet2 didn't actually have Expedient set up yet at the time of the demo, so we provisioned those OpenFlow resources by hand in their respective FlowVisors. |
| 195 | FOAM, the OpenFlow aggregate manager, requires a two-step process to reserve resources: |
| 196 | 1. The experimenter creates their sliver to request the resources, |
| 197 | 2. An OpenFlow admin at each aggregate needs to approve the request. |
| 198 | |
| 199 | We didn't want to have to do this live, times six aggregates, at the demo itself, so we pre-provisioned the OpenFlow resources for each network into a separate slice, and just left those in place the whole time. Each OpenFlow sliver points to one of two ports on an OpenFlow server at GPO Lab, so when the demo users log in and start their controllers, the switches re-connect to the appropriate controller, and voila. |
| 200 | |
| 201 | Also, NLR and Internet2 didn't actually have an OpenFlow AM set up yet at the time of the demo, so we provisioned those OpenFlow resources by hand in their respective FlowVisors. |