Changes between Version 147 and Version 148 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/27/12 09:49:26 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/ExperimentExample-OF-FOAM

    v147 v148  
    244244== 5. Define OpenFlow Network Resources RSpecs ==
    245245
    246 To write an OF RSpec you must determine the end-to-end OF path that will be used for the experiment. This section describes this process, which is comprised of the following steps:
     246To write an !OpenFlow RSpec you must determine the end-to-end path that will be used for the experiment. This section describes this process, which is comprised of the following steps:
    247247
    248248 Step 1. Collect listresources from all FOAM Aggregates.  Note that these !OpenFlow advertisement RSpecs provide insight into all resources at the aggregate, but do not provide any insight into whether they are available. [[BR]]
    … …  
    283283==== BBN !OpenFlow Aggregate ====
    284284
    285 To 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:
     285To 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 !OpenFlow 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:
    286286
    287287[[Image(BBNOFAggregateResources.jpg)]]
    288288
    289289The BBN !OpenFlow Aggregate image above shows the information required for the !OpenFlow RSpec:
    290    * Host navis.bbn.com is connected to port 32 of the OF switch named ''habanero''
    291    * OF switch ''habanero'' has a DPID of ''06:d6:00:24:a8:c4:b9:00'' for VLAN 1750.
    292    * OF switch ''habanero'' uses port 47 to connect to port 20 on the OF switch ''poblano''.
    293    * OF switch ''poblano'' has a DPID of ''06:d6:00:12:e2:b8:a5:d0'' for VLAN 1750.
     290   * Host navis.bbn.com is connected to port 32 of the !OpenFlow switch named ''habanero''
     291   * !OpenFlow switch ''habanero'' has a DPID of ''06:d6:00:24:a8:c4:b9:00'' for VLAN 1750.
     292   * !OpenFlow switch ''habanero'' uses port 47 to connect to port 20 on the !OpenFlow switch ''poblano''.
     293   * !OpenFlow switch ''poblano'' has a DPID of ''06:d6:00:12:e2:b8:a5:d0'' for VLAN 1750.
    294294   * VLAN 1750 is mapped to the Core VLAN 3715 on ''poblano'' port 3.
    295295
    296 As described in the diagram, 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, which has the following implications:
     296As described in the diagram, for the BBN ''habanero'' !OpenFlow switch *only*, you must add 24 to the physical port number to determine the port to use in the RSpec, which has the following implications:
    297297 * The host ''navis.bbn.com'' is on port 32 to which you add the required 24 (32+24=56),  which means your RSpec will use  port ''56''.
    298298 * The switch ''habanero'' is connected to poblano via port 47 to which you add the required 24 (47+24=71), which means your RSpec will use port ''71''. 
    299299
    300 Now we have all the site specific information needed to define the BBN OF resource request RSpec. The syntax for each of these RSpec items can be "borrowed" from the listresources associated to each DPID. 
     300Now we have all the site specific information needed to define the BBN !OpenFlow resource request RSpec. The syntax for each of these RSpec items can be "borrowed" from the listresources associated to each DPID. 
    301301
    302302These are the RSpec lines that define the ports on habanero:
    … …  
    364364==== Clemson !OpenFlow Aggregate ====
    365365
    366 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 is the MyPLC node  planetlab4.clemson.edu. The following image highlights the the information required from the Clemson !OpenFlow Aggregate site diagram:
     366To define the !OpenFlow 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:
    367367
    368368[[Image(ClemsonOFAggregateResources.jpg)]]
    … …  
    370370The Clemson !OpenFlow Aggregate image above shows the information required for the !OpenFlow RSpec:
    371371 * Host ''planetlab4.clemosn.edu'' is connected to port ''39''
    372  * The OF switch had a DPID of ''06:d6:00:26:f1:3f:e4:80''
    373  * The site OF VLAN 1750 is connected to backbone VLAN 3715 on port ''43''
     372 * The !OpenFlow switch had a DPID of ''06:d6:00:26:f1:3f:e4:80''
     373 * The site !OpenFlow VLAN 1750 is connected to backbone VLAN 3715 on port ''43''
    374374
    375375These are the lines from the Advertisement that should be used in the !OpenFlow request RSpec:
    … …  
    412412The Wisonsin !OpenFlow Aggregate image above shows the information required for the !OpenFlow RSpec:
    413413 * Host ''wings-openflow-2.wail.wisc.edu'' is connected to port ''22''.
    414  * The OF switch with the host has a DPID of ''06:d6:00:23:47:cc:44:00''
    415  * The OF switch with the hosts uses port ''1'' to connect to a second switch where VLAN 1750 is mapped to 3715.
    416  * The second OF switch has a DPID os ''06:d6:00:21:f7:be:8d:00''.
    417  * The second OF switch uses port ''C3'' to map VLAN 1750 to 3715. Following instruction on diagram, you must add 48 to the C port number to determine the !OpenFlow port number to use in the RSpec. The !OpenFlow port number to use is ''51'' (48+3).
    418 
    419 
    420 These are the lines from the Wisconsin OF Advertisement that should be used in the !OpenFlow request RSpec:
     414 * The !OpenFlow switch with the hosts has a DPID of ''06:d6:00:23:47:cc:44:00''
     415 * The !OpenFlow switch with the hosts uses port ''1'' to connect to a second switch where VLAN 1750 is mapped to 3715.
     416 * The second !OpenFlow switch has a DPID os ''06:d6:00:21:f7:be:8d:00''.
     417 * The second !OpenFlow switch uses port ''C3'' to map VLAN 1750 to 3715. Following instruction on diagram, you must add 48 to the C port number to determine the !OpenFlow port number to use in the RSpec. The !OpenFlow port number to use is ''51'' (48+3).
     418
     419
     420These are the lines from the Wisconsin !OpenFlow Advertisement that should be used in the !OpenFlow request RSpec:
    421421{{{
    422422    <openflow:group name="wisconsin-nodes-1750">
    … …  
    460460==== NLR !OpenFlow Aggregate ====
    461461
    462 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 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. This example  uses all sites and does not define any port to simplify the experiment workflow. So if you add a site, there is no need to delete, re-create, and re-approved the sliver.  Here are the NLR definitions:
     462To define the NLR !OpenFlow 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. This example  uses all sites and does not define any port to simplify the experiment workflow. So if you add a site, there is no need to delete, re-create, and re-approved the sliver.  Here are the NLR definitions:
    463463{{{
    464464   <openflow:group name="nlr-3715">