Changes between Version 30 and Version 31 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/06/12 15:03:56 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample-OF-FOAM

    v30 v31  
    192192
    193193To 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.
    194 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. The following diagram show the information from the  [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow BBN OF Aggregate] diagram that will be needed for the !OpenFlow request RSpec:
     194To 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. The following diagram show the information from the BBN OF Aggregate diagram that is needed for the BBN !OpenFlow request RSpec:
    195195
    196196[[Image(BBNOFAggregateResources.jpg)]]
    197197
    198 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:
    199 {{{
    200 #habanero
    201   <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">
    202 #poblano
    203 <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">
    204 }}}
    205 
    206 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:
     198The [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow BBN OF Aggregate] diagran shows the information required for the !OpenFlow RSpec. The image shows:
     199   * Host navis.bbn.com is connected to port 32 of the OF switch named ''habanero''
     200   * OF switch ''habanero'' has a DPID of ''06:d6:00:24:a8:c4:b9:00'' for VLAN 1750.
     201   * OF switch ''habanero'' uses port 47 to connect to port 20 on the OF switch ''poblano''.
     202   * OF switch ''poblano'' has a DPID of ''06:d6:00:12:e2:b8:a5:d0'' for VLAN 1750.
     203   * VLAN 1750 is mapped to the Core VLAN 3715 on ''poblano'' port 3.
     204
     205The VLAN 1750 is used at every meso-scale site for MyPLC resources to access the back bone OpenFLow VLANs. Also, for the BBN ''habanero'' OF switch *only*, you must add 24 to the physical port number to determine the port to use in the rspec. The host navis.bbn.com is on port 32 (+24=56),  which means your rspec will use  port ''56''  and port 47 (+24=71) maps to ''71'' to get to poblano.  The syntax for each of these can be "borrowed" from the listresources associated to each DPID. 
     206
     207Now we have all the information needed to define the OF resource details. These are the RSpec lines that define the ports on habanero:
    207208{{{
    208209 <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">
     
    211212}}}
    212213
    213 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:
     214These are the RSpec lines that define the ports on habanero:
    214215
    215216{{{
     
    219220
    220221}}}
    221 
    222  * 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.
     222To complete the RSpec see ''Step 3''
     223
     224__Clemson Aggregate__ [[BR]]
     225
     226To define the OF RSpec for the Clemson site we need to  review the information in the [http://groups.geni.net/geni/wiki/GeniAggregate/ClemsonOpenFlow Clemson OF Aggregate] diagram.  The compute resource used for the site which is the node for planetlab4.clemson.edu.
     227The following diagram show the information required from the Clemson OF Aggregate that is needed for the Clemson !OpenFlow request RSpec:
     228
     229[[Image(XXXX)]]
     230
     231To complete the RSpec see ''Step 3''
     232
    223233 * 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].
     234
     235
     236To complete the RSpec see ''Step 3''
    224237
    225238'' '''Step 3''' ''. Merge Step 1 and 2 to generate request RSpecs.