5 | | This page illustrates an !OpenFlow (OF) example for the [wiki:HowToUseOmni Omni How-to] page. [http://www.openflow.org/ OpenFlow] is used for the control of the network resources in the GENI backbone and at meso-scale campus locations. Experimenters can use these GENI resources without learning !OpenFlow. The GPO [mailto:help@geni.net] can help arrange connectivity across your GENI slice, including IP connectivity and/or layer 2 VLANs. |
6 | | |
7 | | For experimenters who desire control over the network switching fabric in their slices, !OpenFlow provides increased flexibility. Your experiment will incorporate an !OpenFlow controller. Many experimenters use existing controller code as-is, some use controllers with relatively simple modifications, and some experimenters have written their own controller. The GPO is available to help design your controller and plan your experiment configuration. Feel free to contact us at [mailto:help@geni.net]. |
8 | | |
9 | | This experiment uses credentials from the GPO ProtoGENI Clearinghouse (pgeni.gpolab.bbn.com) to set up a 3 Meso-scale sites !OpenFlow experiment. The sites are includes BBN, Wisconsin and Clemson each with a MyPLC compute resource. If you are interested in using PG resources, see the [http://groups.geni.net/geni/wiki/HelloGENI HelloGENI] experiment page. |
| 5 | This page illustrates an !OpenFlow (OF) example for the [wiki:HowToUseOmni Omni How-to] page. [http://www.openflow.org/ OpenFlow] is used for the control of the network resources in the GENI backbone and at meso-scale campus locations. Experimenters can use GENI resources without learning !OpenFlow. Experimenters can choose to control the network switching fabric in their slices by running an !OpenFlow controller. Many experimenters use existing !OpenFlow controller code as-is, some use controllers with relatively simple modifications, and some experimenters have written their own controller. The GPO is available to help design your controller and plan your experiment configuration. Feel free to contact us at [mailto:help@geni.net]. |
| 6 | |
| 7 | The experiment in this page uses credentials from the GPO ProtoGENI Clearinghouse (pgeni.gpolab.bbn.com) to set up a 3 Meso-scale sites !OpenFlow experiment. The sites are BBN, Wisconsin and Clemson each with a MyPLC compute resource. If you are interested in using PG resources, see the [http://groups.geni.net/geni/wiki/HelloGENI HelloGENI] experiment page for an OpenFlow experiment using PG nodes. |
66 | | Each of the 3 sites will requires an !OpenFlow RSpec and a compute resource RSpec. Also an !OpenFlow RSpec will be required for the GENI Core (NLR in this example). |
67 | | To find out what resources are available use Omni tools to get a list of available resources. Following is a list of MyPLC and FOAM aggregates available in the meso-scale network: |
68 | | |
69 | | ||'''Site'''|| '''MyPLC Aggregate URL''' || ''' FOAM Aggregate URL ''' || |
70 | | || BBN || http://myplc.gpolab.bbn.com:12346/ ||https://foam.gpolab.bbn.com:3626/foam/gapi/1 |
71 | | || Clemson || http://myplc.clemson.edu:12346/ ||https://foam.clemson.edu:3626/foam/gapi/1 |
72 | | || GA Tech || https://myplc.cip.gatech.edu:12346/ ||https://nox.orbit-lab.org:3626/foam/gapi/1 |
73 | | ||Indiana || https://myplc.grnoc.iu.edu:12346/ ||https://foam.noc.iu.edu:3626/foam/gapi/1 |
74 | | || Intenet2 || ||https://foam.net.internet2.edu:3626/foam/gapi/1 |
75 | | || NLR || ||https://foam.nlr.net:3626/foam/gapi/1 |
76 | | || Rutgers ||https://plc.orbit-lab.org:12346/ ||https://foam.oflow.cip.gatech.edu:3626/foam/gapi/1 |
77 | | || Stanford ||https://myplc.stanford.edu:12346/ ||https://openflow4.stanford.edu:3626/foam/gapi/1 |
78 | | ||Washington||https://of.cs.washington.edu:12346/ ||https://of.cs.washington.edu:3626/foam/gapi/1 |
79 | | ||Wisconsin ||https://wings-openflow-1.wail.wisc.edu:12346/||https://foam.wail.wisc.edu:3626/foam/gapi/1 |
| 63 | Each of the 3 sites requires an !OpenFlow RSpec and a compute resource RSpec. Also, an !OpenFlow RSpec is required for the GENI Core (NLR in this example). |
| 64 | To find out what resources are available use Omni tools to get a list of available resources from the available aggregates. Following is a list of MyPLC and FOAM aggregates available in the meso-scale network: |
| 65 | |
| 66 | ||'''Site'''|| '''MyPLC Aggregate URL''' || ''' FOAM Aggregate URL ''' || |
| 67 | || BBN || http://myplc.gpolab.bbn.com:12346/ ||https://foam.gpolab.bbn.com:3626/foam/gapi/1 || |
| 68 | || Clemson || http://myplc.clemson.edu:12346/ ||https://foam.clemson.edu:3626/foam/gapi/1 || |
| 69 | || GA Tech || https://myplc.cip.gatech.edu:12346/ ||https://nox.orbit-lab.org:3626/foam/gapi/1 || |
| 70 | ||Indiana || https://myplc.grnoc.iu.edu:12346/ ||https://foam.noc.iu.edu:3626/foam/gapi/1 || |
| 71 | || Intenet2 || ||https://foam.net.internet2.edu:3626/foam/gapi/1 || |
| 72 | || NLR || ||https://foam.nlr.net:3626/foam/gapi/1 || |
| 73 | || Rutgers ||https://plc.orbit-lab.org:12346/ ||https://foam.oflow.cip.gatech.edu:3626/foam/gapi/1 || |
| 74 | || Stanford ||https://myplc.stanford.edu:12346/ ||https://openflow4.stanford.edu:3626/foam/gapi/1 || |
| 75 | ||Washington||https://of.cs.washington.edu:12346/ ||https://of.cs.washington.edu:3626/foam/gapi/1 || |
| 76 | ||Wisconsin ||https://wings-openflow-1.wail.wisc.edu:12346/||https://foam.wail.wisc.edu:3626/foam/gapi/1 || |
194 | | |
| 191 | Let map the 3 nodes from the Site's compute resources RSpec. |
| 192 | |
| 193 | == BBN OF AGGREGATE == |
| 194 | To define the OF RSpec for the BBN site we need to consider the compute resource used for the site which is the node navis.gpolab.bbn.com. To determine the ports and Data Path IDentifier (DPID) see the [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow BBN OF Aggregate] diagram and locate where the node is connected. |
| 195 | |
| 196 | From the [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow BBN OF Aggregate] diagram you will find that navis.bbn.com is connected to the OF switch named ''habanero'' which has a DPID of ''06:d6:00:24:a8:c4:b9:00'' for VLAN 1750. VLAN 1750 uses the switch ''poblano'' which has a DPID of ''06:d6:00:12:e2:b8:a5:d0'' for VLAN 1750. The VLAN 1750 is used at every meso-scale site for MyPLC resources to access the back bone OpenFLow VLANs, in our case the backbone OpenFlow VLAN is 3715. This DPID information maps to the following line in the BBN OpenFlow advertisement Rspec: |
| 197 | {{{ |
| 198 | #habanero |
| 199 | <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:24:a8:c4:b9:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" dpid="06:d6:00:24:a8:c4:b9:00"> |
| 200 | #poblano |
| 201 | <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:12:e2:b8:a5:d0" component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" dpid="06:d6:00:12:e2:b8:a5:d0"> |
| 202 | }}} |
| 203 | |
| 204 | Now we have to add ports to the above definition. The host navis.bbn.com is on port 32, for the BBN habanero switch only, you must add 24 to the physical port number to determine the port to use in the rspec, which means you are looking for the OpenFlow port named ''56'' in the listresources associated to the DPID. Also you will see that port 47 (+24=71) is used to get to poblano. So these are the lines that define the ports on habanero: |
| 205 | {{{ |
| 206 | <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:24:a8:c4:b9:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" dpid="06:d6:00:24:a8:c4:b9:00"> |
| 207 | <openflow:port name="32" num="56"/> |
| 208 | <openflow:port name="47" num="71"/> |
| 209 | }}} |
| 210 | Habanero Connects to port 20 on poblano where port 3 and 4 are used to map VLAN 1750 to VLAN 3715 and traffic goes out to backbone via port 1. This maps to: |
| 211 | {{{ |
| 212 | <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:12:e2:b8:a5:d0" component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" dpid="06:d6:00:12:e2:b8:a5:d0"> |
| 213 | |
| 214 | |
| 215 | |
| 216 | * CLemson site Rspec includes node planetlab4.clemson.edu map to ports and DPID in [http://groups.geni.net/geni/wiki/GeniAggregate/ClemsonOpenFlow Clemson OF Aggregate] diagram. |
| 217 | * Wisconsin site Rspec include node wings-openflow-2.wail.wisc.edu map to ports and DPID in [http://groups.geni.net/geni/wiki/GeniAggregate/WisconsinOpenFlow Winsconsin OF Aggregate]. |