Changes between Version 78 and Version 79 of GENIExperimenter/ExperimentExample-OF-FOAM

Timestamp:

04/20/12 09:57:22 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIExperimenter/ExperimentExample-OF-FOAM

@@ -152 +152 @@
 == Define !OpenFlow Network Resources Rspecs ==
 
-To write an OF RSpec you must determine the end-to-end OF path that will be used for the experiment. This section defines how to define the OF RSpecs by following the process outlined below to determine the content of the OF RSpec:
-
-Step 1. Collect listresources from all FOAM Aggregate.  The manifest RSpec details all resources at the aggregate, but does not provide any insight into whether they are available.
-Step 2. Review [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] to determine how each MyPLC host maps to the Site's !OpenFlow switch. Determine addresses and ports, and define site specific OF Group rules.
+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:
+
+Step 1. Collect listresources from all FOAM Aggregate.  Note that these !OpenFlow advertisment RSpec provide insight into all resources at the aggregate, but does not provide any insight into whether they are available.
+Step 2. Review [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] to determine how each experiment MyPLC host maps to the Site's !OpenFlow switch. Determine addresses and ports, and define site specific OF Group rules.
 Step 3. Using guidelines from the [http://groups.geni.net/geni/wiki/HowTo/WriteOFv3Rspecs#WritingOpenFlowv3requestrspecs Writing OF V3 RSpec] page merge the information from step 1 and 2 to generate the request RSpecs. 
 
@@ -165 +165 @@
  1. Clemson FOAM and MyPLC aggregates:
 {{{
- ./src/omni.py -a https://foam.clemson.edu:3626/foam/gapi/1 listresources -o   # generates output file rspec-foam-clemson-edu-3626-foam-gapi-1.xml
+ $ ./src/omni.py -a https://foam.clemson.edu:3626/foam/gapi/1 listresources -o   # generates output file rspec-foam-clemson-edu-3626-foam-gapi-1.xml
 }}}
  2. Wisconsin FOAM and MyPLC aggregates:
 {{{
- ./src/omni.py -a https://foam.wail.wisc.edu:3626/foam/gapi/1 listresources -o    # generates rspec-foam-wail-wisc-edu-3626-foam-gapi-1.xml
+ $ ./src/omni.py -a https://foam.wail.wisc.edu:3626/foam/gapi/1 listresources -o    # generates rspec-foam-wail-wisc-edu-3626-foam-gapi-1.xml
 }}}
  3. BBN FOAM and MyPLC aggregates:
 {{{
- ./src/omni.py -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 listresources -o         # generates rspec-foam-gpolab-bbn-com-3626-foam-gapi-1.xml
+ $ ./src/omni.py -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 listresources -o         # generates rspec-foam-gpolab-bbn-com-3626-foam-gapi-1.xml
 }}}
  4. NLR !OpenFlow Core FOAM server:
 {{{
-$ ./src/omni.py -a https://foam.nlr.net:3626/foam/gapi/1 -o listresources           # generates rspec-foam-nlr-net-3626-foam-gapi-1.xml
-}}}
-Information in the output manifest files provides the switch and the port information to be used in making the OF flowspace reservation.  
-
-=== Step 2: Determine site specific OpenFlow details ===
-
-Define the site specific !OpenFlow details based on [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] and MyPLC hosts mapping to the Site's !OpenFlow switch.  This step walk through how the site details are defined. In the [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] page, select the !OpenFlow Aggregate link for BBN, Clemson and Wisconsin and use the OF site diagrams to determine which ports and DPID should be used in the OF RSpec.  In addition OF groups rules will be defined for each of the site to handle traffic for the hosts.  Each site Rspec will include a group definition that looks as follows:
+ $ ./src/omni.py -a https://foam.nlr.net:3626/foam/gapi/1 listresources -o           # generates rspec-foam-nlr-net-3626-foam-gapi-1.xml
+}}}
+
+Information in the output Advertisement RSpec files provides the switch and the port information to be used in making the !OpenFlow flowspace reservation.  
+
+
+=== Step 2: Determine site specific !OpenFlow details ===
+
+This sections shows you how to determine the site specific !OpenFlow RSpec details by walking through the information gathering process. To determine which !OpenFlow resources to use, go to the [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] page and select the !OpenFlow Aggregate links for BBN, Clemson and Wisconsin. Each of these !OpenFlow Aggregate pages contain a site diagram. The !OpenFlow site diagrams show ports, DPIDs, and hosts mapping for the site's !OpenFlow switch.  In addition to the information from the !OpenFlow site diagram, !OpenFlow groups rules must defined for each site to handle traffic for the hosts.  Each site Rspec will include a group definition that looks as follows:
 
 {{{
@@ -196 +198 @@
 }}}
  ''Note:''' The ''group-name'' above will be replace by the actual group name values defined in flowspec. [[BR]]
- ''Note: The address "10.42.11.0/24" was assigned as described in the section XXXX above.
-
-Now, let map the 3 nodes from the Site's Compute Resource RSpecs to the appropriate OF Switch port and determine how they connect to the GENI CORE network VLAN 3715.
+ ''Note: The address "10.42.11.0/24" was assigned as described in the section [wiki:GENIExperimenter/ExperimentExample-OF-FOAM#ReserveGENIIPsubnet above].
+
+Now, let's map the 3 nodes we chose in the compute resource RSpecs to the appropriate !OpenFlow switch ports and determine how they connect to the GENI CORE network VLAN 3715. 
 
 ==== BBN !OpenFlow Aggregate ====
 
-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 and determine how it is connected on the OF switch at the site, and then determine how that connection connects to the network core OF VLAN 3715. To determine the ports and Data Path IDentifier (DPID) review 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:
+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:
 
 [[Image(BBNOFAggregateResources.jpg)]]
 
-The [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow BBN OF Aggregate] diagran shows the information required for the !OpenFlow RSpec. The image shows:
+The BBN !OpenFlow Aggregate image above shows the information required for the !OpenFlow RSpec:
    * Host navis.bbn.com is connected to port 32 of the OF switch named ''habanero''
    * OF switch ''habanero'' has a DPID of ''06:d6:00:24:a8:c4:b9:00'' for VLAN 1750.
@@ -213 +215 @@
    * VLAN 1750 is mapped to the Core VLAN 3715 on ''poblano'' port 3.
 
-The 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.  
+Note: The VLAN 1750 is used at every meso-scale site for MyPLC resources to access the back bone !OpenFlow VLANs. [[BR]]
+Note: 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.  
 
 Now we have all the information needed to define the BBN OF resource request RSpec. These are lines that define the ports on habanero:
@@ -227 +230 @@
    </openflow:datapath>
  </openflow:group>
-
 
 }}}