7 | | || '''OpenFlow Aggregate info page''' || '''Opt-in Mgr contact''' || |
8 | | || [wiki:GeniAggregate/GpoLabOpenFlow GPO Lab] || gpo-infra@geni.net || |
9 | | || [wiki:GeniAggregate/StanfordOpenFlow Stanford] || deployment-help@openflowswitch.org || |
10 | | || [wiki:GeniAggregate/WashingtonOpenFlow Washington] || balkan@cs.washington.edu || |
11 | | || [wiki:GeniAggregate/WisconsinOpenFlow Wisconsin] || agember@cs.wisc.edu || |
12 | | || [wiki:GeniAggregate/ClemsonOpenFlow Clemson] || arosen@clemson.edu || |
13 | | || [wiki:GeniAggregate/IndianaOpenFlow Indiana] || meylor@grnoc.iu.edu || |
14 | | || [wiki:GeniAggregate/RutgersOpenFlow Rutgers] || seskar@winlab.rutgers.edu || |
| 7 | == Opting in your traffic == |
| 8 | |
| 9 | If you allocate a shared resource that connects to an !OpenFlow aggregate (e.g. a MyPLC plnode or ProtoGENI host), you'll typically also need to reserve some !OpenFlow resources. When you do this, your reservation request goes to the Opt-In Manager, and a local Expedient OIM admin needs to approve your request before your sliver actually becomes live. The OIM admin isn't notified of your request, so you'll usually want to contact them to ask them to opt in your sliver. Here's a list of Expedient aggregates, and contact info for the OIM admins: |
| 10 | |
| 11 | || '''!OpenFlow Aggregate info page''' || '''Opt-In Manager admin''' || |
| 12 | || [wiki:GeniAggregate/ClemsonOpenFlow Clemson] || arosen@clemson.edu || |
| 14 | || [wiki:GeniAggregate/GpoLabOpenFlow GPO Lab] || gpo-infra@geni.net || |
| 15 | || [wiki:GeniAggregate/IndianaOpenFlow Indiana] || meylor@grnoc.iu.edu || |
| 16 | || [wiki:GeniAggregate/RutgersOpenFlow Rutgers] || seskar@winlab.rutgers.edu || |
| 17 | || [wiki:GeniAggregate/StanfordOpenFlow Stanford] || deployment-help@openflowswitch.org || |
| 18 | || [wiki:GeniAggregate/WashingtonOpenFlow Washington] || balkan@cs.washington.edu || |
| 19 | || [wiki:GeniAggregate/WisconsinOpenFlow Wisconsin] || agember@cs.wisc.edu || |
| 20 | |
| 21 | = Info for admins = |
| 22 | |
| 23 | The following sections are mostly of interest to Expedient admins. |
| 24 | |
| 25 | == Slice Authority trust configuration == |
| 26 | |
| 27 | You may want to configure your Expedient AM to trust user certificates signed by additional Slice Authorities. To do that, install the CA cert for the Slice Authority in /etc/expedient/gcf-x509-trusted.crt/<authority>.crt (note that the name has to end in ".crt"), and then do |
| 28 | |
| 29 | {{{ |
| 30 | cd /etc/expedient/apache/ca-certs |
| 31 | sudo make |
| 32 | }}} |
| 33 | |
| 34 | to create a symlink in /etc/expedient/apache/ca-certs pointing to it. |
| 35 | |
| 36 | In particular, campus mesoscale deployments may want to trust the pgeni.gpolab.bbn.com SA; you can get the cert from http://www.pgeni.gpolab.bbn.com/ca-cert/pgeni.gpolab.bbn.com.pem. |