Changes between Version 50 and Version 51 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/13/12 13:57:52 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v50 v51  
    33= GENI !OpenFlow Experiment Example 2 =
    44
    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.
     5This page illustrates an !OpenFlow (OF) example for the [wiki:HowToUseOmni Omni How-to] page. 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
     7The 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.
    88
    99[[Image(OF-Experiment-example.jpg)]]
     
    1313    * Determine Resources Availability
    1414    * Define Compute Resources RSpecs
    15     * Define OpenFlow Network Resources Rspecs
     15    * Define !OpenFlow Network Resources Rspecs
    1616    * Create Slice and Request Resources
    1717    * Run Experiment
     
    161161
    162162Step 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.
    163 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.
     163Step 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.
    164164Step 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.
    165165
     
    189189=== Step 2: Determine site specific OpenFlow details ===
    190190
    191 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:
     191Define 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:
    192192
    193193{{{
     
    219219   * VLAN 1750 is mapped to the Core VLAN 3715 on ''poblano'' port 3.
    220220
    221 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. 
     221The 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. 
    222222
    223223Now we have all the information needed to define the BBN OF resource request RSpec. These are lines that define the ports on habanero:
     
    417417Note: If you do not have a controller, you may set one up as shown [http://groups.geni.net/geni/wiki/OpenFlow/GeniBackboneTest#SetupyourOpenFlowcontroller here]
    418418
    419 You can now combine the modified template with each of the Site specific openflow details from Step 2.
     419You can now combine the modified template with each of the Site specific !OpenFlow details from Step 2.
    420420
    421421This will result in the following final OF RSpecs: