Changes between Version 80 and Version 81 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/20/12 10:19:32 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/ExperimentExample-OF-FOAM

    v80 v81  
    204204==== BBN !OpenFlow Aggregate ====
    205205
    206 To define the !OpenFlow request RSpec for the BBN site we need to consider the compute resource selected, which is the MyPLC node navis.gpolab.bbn.com.  We then determine how the node is connected to the !OpenFlow switch, the Data Path IDentifier (DPID) for the switch, and then we determine the path required to connects to the network core OF VLAN 3715. All this information can be found in the [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow BBN OF Aggregate] diagram, which is shown below with the relevant BBN !OpenFlow request RSpec details highlighted:
     206To define the !OpenFlow request RSpec for the BBN site we need to consider the compute resource we selected, which is the MyPLC node navis.gpolab.bbn.com.  We then determine how the node navis is connected to the !OpenFlow switch, then we find the Data Path IDentifier (DPID) for the switch VLAN 1750 which is used at every meso-scale site for MyPLC resources to access the backbone !OpenFlow VLANs, and finally we determine the path required to connects to the network core OF VLAN 3715.  All this information can be found in the [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow BBN OF Aggregate] diagram, which is shown below with the relevant BBN !OpenFlow request RSpec details highlighted:
    207207
    208208[[Image(BBNOFAggregateResources.jpg)]]
    … …  
    215215   * VLAN 1750 is mapped to the Core VLAN 3715 on ''poblano'' port 3.
    216216
    217 Note: The VLAN 1750 is used at every meso-scale site for MyPLC resources to access the back bone !OpenFlow VLANs. [[BR]]
    218217Note: 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. 
    219218
    220 Now we have all the information needed to define the BBN OF resource request RSpec. These are lines that define the ports on habanero:
     219Now we have all the site specific information needed to define the BBN OF resource request RSpec. These are the RSpec lines that define the ports on habanero:
    221220{{{
    222221
    … …  
    233232}}}
    234233
    235 These are the RSpec lines that define the ports on habanero:
    236 
    237 {{{
    238 
     234These are the RSpec lines that define the ports on poblano:
     235
     236{{{
    239237 <openflow:group name="bbn-1750-3715">
    240238     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:12:e2:b8:a5:d0"
    … …  
    244242        <openflow:port num="20"/>
    245243      </openflow:datapath>
    246     </openflow:group>
    247 
    248 }}}
    249 In addition each of the groups must be allowed to share traffic:
     244 </openflow:group>
     245
     246}}}
     247In addition each of the groups must be allowed to share traffic for the IP subnet range reserved for the experiment:
    250248{{{
    251249   <openflow:match>
    … …  
    253251      <openflow:use-group name="bbn-1750-nodes" />
    254252      <openflow:use-group name="bbn-1750-3715" />
    255 
    256253      <openflow:packet>
    257254        <openflow:dl_type value="0x800,0x806"/>
    … …  
    263260}}}
    264261
    265 To complete the BBN OF RSpec see ''Step 3''
     262The BBN !OpenFlow request RSpec will be completed in ''Step 3''.
    266263
    267264==== Clemson !OpenFlow Aggregate ====
    268265
    269 To define the OF RSpec for the Clemson site 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.
    270 The following diagram show the information required from the Clemson OF Aggregate that is needed for the Clemson !OpenFlow request RSpec:
     266To define the OF RSpec for the Clemson site review the information in the [http://groups.geni.net/geni/wiki/GeniAggregate/ClemsonOpenFlow Clemson OF Aggregate] diagram.  The compute resource used is the MyPLC node  planetlab4.clemson.edu. The following image highlights the the information required from the Clemson !OpenFlow Aggregate site diagram:
    271267
    272268[[Image(ClemsonOFAggregateResources.jpg)]]
    273269
    274 These are the lines from the Advertisement that should be used in the request RSpec:
     270These are the lines from the Advertisement that should be used in the !OpenFlow request RSpec:
    275271{{{
    276272
    … …  
    283279      </openflow:datapath>
    284280  </openflow:group>
    285 
    286 }}}
    287 
    288 In addition each of the groups must be allowed to share traffic:
     281}}}
     282
     283In addition each of the groups must be allowed to share traffic for the IP subnet range reserved for the experiment:
    289284{{{
    290285   <openflow:match>
    … …  
    299294
    300295    </openflow:match>
    301 
    302 }}}
    303 
    304 To complete the Clemson OF RSpec see ''Step 3''
     296}}}
     297
     298The Clemson !OpenFlow request RSpec will be completed in ''Step 3''.
    305299
    306300==== Wisconsin !OpenFlow Aggregate ====
    307301
    308 To define the OF RSpec for the Wisconsin site review the [http://groups.geni.net/geni/wiki/GeniAggregate/WisconsinOpenFlow Winsconsin OF Aggregate] diagram.  The compute resource used at the Wisconsin site is the node wings-openflow-2.wail.wisc.edu.  The Wisconsin OF aggregate diagram only shows the MAC address for the OF switch to determine the DPID simply combine the hexadecimal value for 1750 (06d6) and the MAC address (00:23:47:CC:44:00) to create the DPID (06:d6:00:23:47:CC:44:00).
     302To define the !OpenFlow RSpec for the Wisconsin site review the [http://groups.geni.net/geni/wiki/GeniAggregate/WisconsinOpenFlow Winsconsin OF Aggregate] diagram.  The compute resource used is the MyPLC node wings-openflow-2.wail.wisc.edu.  The [http://groups.geni.net/geni/wiki/GeniAggregate/WisconsinOpenFlow Winsconsin OF Aggregate] diagram only shows the MAC address for the !OpenFlow switch, to determine the DPID simply combine the hexadecimal value for 1750 (06d6) and the MAC address of the switch (00:23:47:CC:44:00) to create the DPID (06:d6:00:23:47:CC:44:00).  The following image highlights the the information required from the Wisconsin !OpenFlow Aggregate site diagram:
    309303
    310304[[Image(WisconsinOFAggregateResources.jpg)]]
    311305
    312306
    313 These are the lines from the Wisconsin OF Advertisement that should be used in the OF request RSpec:
    314 {{{
    315 
     307These are the lines from the Wisconsin OF Advertisement that should be used in the !OpenFlow request RSpec:
     308{{{
    316309    <openflow:group name="wisconsin-nodes-1750">
    317310      <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+datapath+06:d6:00:23:47:cc:44:00"
    … …  
    329322      </openflow:datapath>
    330323    </openflow:group>
    331 
    332 }}}
    333 
    334 
    335 In addition each of the groups must be allowed to share traffic:
     324}}}
     325
     326
     327In addition each of the groups must be allowed to share traffic for the IP subnet range reserved for the experiment:
    336328{{{
    337329    <openflow:match>
    … …  
    348340    </openflow:match>
    349341
    350 
    351 }}}
    352 
    353 To complete the Wisconsin OF RSpec see ''Step 3''
    354 
     342}}}
     343
     344The Wisconsin !OpenFlow request RSpec will be completed in ''Step 3''.
    355345
    356346
    357347==== NLR !OpenFlow Aggregate ====
    358348
    359 
    360 To define the NLR OF RSpec review the [http://groups.geni.net/geni/wiki/SiteNlr#OpenFlow OpenFlow DPIDs] table for the core in the [http://groups.geni.net/geni/wiki/SiteNlr National LambaRail] GENI page. From the table you can see the DPIDs for OF VLAN 3715 for NLR. You may choose to use only the two core sites (Chicago and Atlanta) associated with the three sites in this experiment, but for simplicity you may choose to define all DPIDs in the NLR Core for VLAN 3715, which is how this example is shown:
     349To define the NLR OF RSpec review the [http://groups.geni.net/geni/wiki/SiteNlr#OpenFlow OpenFlow DPIDs] table for the core in the [http://groups.geni.net/geni/wiki/SiteNlr National LambaRail] GENI page. From the table you can see the DPIDs for NLR !OpenFlow VLAN 3715. You may choose to use only the two core sites (Chicago and Atlanta) associated with the three experiment sites, but you can also choose to define all DPIDs in the NLR Core for VLAN 3715, which is how this example is shown:
    361350{{{
    362351   <openflow:group name="nlr-3715">
    … …  
    379368
    380369
    381 To complete the NLR OF RSpec see ''Step 3''
     370The NLR !OpenFlow request RSpec will be completed in ''Step 3''.
    382371
    383372=== Step 3: Generate OpenFlow V3 RSpec ===