Changes between Version 75 and Version 76 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/20/12 09:16:24 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/ExperimentExample-OF-FOAM

    v75 v76  
    33= GENI !OpenFlow Experiment Example 2 =
    44
    5 This 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].
     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].
    66
    77The 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.
    … …  
    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
    … …  
    5656== Reserve GENI IP subnet ==
    5757
    58 In the Meso-scale network a layer 3 experiment requires its own separate IP subnet in order to control all traffic without interfering with traffic from other experiments. Before you start this experiment, you need to request an IP subnet from the gpo-infra@geni.net mail list along with a duration for the subnet reservation. To view the current list of subnets and their current allocation see the [http://groups.geni.net/geni/wiki/NetworkCore/SubnetReservations GENI Network Core Subnet] page.
     58In the Meso-scale network a layer 3 experiment requires its own separate IP subnet in order to control all traffic without interfering with traffic from other experiments. Before you start this experiment, you need to request an IP subnet from the gpo-infra@geni.net mail list along with a duration for the subnet reservation. To view the current list of subnets and their current allocation see the [http://groups.geni.net/geni/wiki/NetworkCore/SubnetReservations GENI Network Core Subnet] page. 
    5959
    6060
    … …  
    6262
    6363Each of the 3 sites requires an !OpenFlow RSpec and a compute resource RSpec. Also, an !OpenFlow RSpec is required for the GENI Core (NLR in this example).
    64 To find out what resources are available use Omni tools to get a list of available resources from the available aggregates.  Following is a list of MyPLC and FOAM aggregates available in the meso-scale network:
     64To find out what resources are available use Omni tools to get a list of available resources from the available aggregates.  Following is a list of MyPLC and FOAM aggregates available in the Meso-scale network:
    6565
    6666||'''Site'''|| '''MyPLC Aggregate URL'''                   || ''' FOAM Aggregate URL '''                        ||
    … …  
    7777||Wisconsin ||https://wings-openflow-1.wail.wisc.edu:12346/||https://foam.wail.wisc.edu:3626/foam/gapi/1        ||
    7878
    79 The experiment in this page uses the BBN, Clemson, Wisconsin and NLR Aggregates.  For complete list of available aggregates see the available [http://groups.geni.net/geni/wiki/GeniAggregate GENI Aggregates] page. 
     79The experiment captured in this page uses the BBN, Clemson, Wisconsin and NLR Aggregates.  For a complete list of available aggregates see the [http://groups.geni.net/geni/wiki/GeniAggregate GENI Aggregates] page. 
    8080
    8181== Define Compute Resources RSpecs ==
    8282
    83 This experiment uses Omni V1.6.1 to set up the experiment. As a first step, the experimenter determines the available compute resources at each site. Following are the omni commands issued to get the manifests for available compute resources from the BBN, Clemson and Wisconsin MyPLC aggregates:
    84 
    85 {{{
    86   ./src/omni.py -a http://myplc.gpolab.bbn.com:12346/ listresources -o             # generates rspec-myplc-gpolab-bbn-com-12346-.xml
    87   ./src/omni.py -a  http://myplc.clemson.edu:12346/ listresources -o               # generates rspec-myplc-clemson-edu-12346-.xml
    88   ./src/omni.py -a https://wings-openflow-1.wail.wisc.edu:12346/ listresources -o  # generates rspec-wings-openflow-1-wail-wisc-edu-12346-.xml
    89 
    90 }}}
    91 
    92 Each of the omni command above used the -o argument to get the listresources output to a file, all output advertisement RSpec files are attached to this page as a reference.  The advertisement RSpecs are used to generate the request RSpecs to reserve the resources.  Following are the compute resources RSpec defined based on the output of the listresources commands above.
     83This experiment uses Omni V1.6.1 to set up the experiment. As a first step, the experimenter determines the available compute resources at each site. Following are the omni commands issued to get the manifests of available compute resources from the BBN, Clemson and Wisconsin MyPLC aggregates:
     84
     85{{{
     86 $ ./src/omni.py -a http://myplc.gpolab.bbn.com:12346/ listresources -o             # generates rspec-myplc-gpolab-bbn-com-12346-.xml
     87 $ ./src/omni.py -a  http://myplc.clemson.edu:12346/ listresources -o               # generates rspec-myplc-clemson-edu-12346-.xml
     88 $ ./src/omni.py -a https://wings-openflow-1.wail.wisc.edu:12346/ listresources -o  # generates rspec-wings-openflow-1-wail-wisc-edu-12346-.xml
     89}}}
     90
     91The Omni commands above used the ''-o'' argument to get the listresources output into advertisement RSpec files, which are all attached to this page as a reference.  The advertisement RSpecs are used to generate the request RSpecs to reserve the resources.  Following are the compute resources RSpec defined based on the output of the listresources commands above.
    9392
    9493'''BBN MyPLC Compute Resource RSpec '''
    … …  
    9796<!--
    9897This rspec will create a container on each of the BBN production MyPLC plnodes.
    99 
    10098AM: https://myplc.gpolab.bbn.com:12346/
    10199-->
    … …  
    116114<?xml version="1.0" ?>
    117115<!-- Resources at AM:
    118         URN: unspecified_AM_URN
    119116        URL: http://myplc.clemson.edu:12346/
    120  -->
     117-->
    121118<RSpec type="SFA"> 
    122119    <network name="plc">   
    123120        <node component_id="urn:publicid:IDN+plc:cu+node+planetlab4.clemson.edu"
    124121             component_manager_id="urn:publicid:IDN+plc+authority+sa"
    125                 node_id="n1" site_id="urn:publicid:IDN+plc:cu+authority+sa">   
    126  
     122                node_id="n1" site_id="urn:publicid:IDN+plc:cu+authority+sa">     
    127123            <hostname>        planetlab4.clemson.edu      </hostname>     
    128124        </node>