Changes between Version 25 and Version 26 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/03/12 14:03:19 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v25 v26  
    5858== Reserve GENI IP subnet ==
    5959
    60 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. At this point you need to request an IP subnet  from the gpo-infra@geni.net mail list. The request should also specify a duration.
     60In 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. At this point you need to request an IP subnet  from the gpo-infra@geni.net mail list. The request should also specify a duration. To view the current list of subnets and their allocation see the [http://groups.geni.net/geni/wiki/NetworkCore/SubnetReservations GENI Network Core Subnet] page.
     61
    6162
    6263
     
    8283== Define Compute Resources RSpecs ==
    8384
    84 This experiment uses Omni V1.6.1 to set up the experiment. As a first step, the experimenter determines the available resources at each of the MyPLC Aggregate Managers.  Following are the omni commands issued to get the manifests for available compute resources:
    85 
    86  1. Clemson MyPLC aggregate:
    87 {{{
    88  ./src/omni.py -a  http://myplc.clemson.edu:12346/ listresources -o            # generates rspec-myplc-clemson-edu-12346-.xml
    89 }}}
    90  2. Wisconsin MyPLC aggregate:
    91 {{{
    92  ./src/omni.py -a https://wings-openflow-1.wail.wisc.edu:12346/  listresources -o # rspec-wings-openflow-1-wail-wisc-edu-12346-.xml
    93 }}}
    94  3. BBN MyPLC aggregates:
    95 {{{
    96  ./src/omni.py -a http://myplc.gpolab.bbn.com:12346/ listresources -o            # generates rspec-myplc-gpolab-bbn-com-12346-.xml
    97 }}}
    98 
    99 Each of the omni command above used the -o argument to get the listresources output to a file, all output files are attached to this page as a reference.  The Advertisement RSpec generated by the listresources are then reviewed 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.
     85This experiment uses Omni V1.6.1 to set up the experiment. As a first step, the experimenter determines the available resources. Following are the omni commands issued to get the manifests for available compute resources from the BBN, Clemson and Wisconsin MyPLC aggregates:
     86
     87{{{
     88  ./src/omni.py -a http://myplc.gpolab.bbn.com:12346/ listresources -o             # generates rspec-myplc-gpolab-bbn-com-12346-.xml
     89  ./src/omni.py -a  http://myplc.clemson.edu:12346/ listresources -o               # generates rspec-myplc-clemson-edu-12346-.xml
     90  ./src/omni.py -a https://wings-openflow-1.wail.wisc.edu:12346/ listresources -o  # generates rspec-wings-openflow-1-wail-wisc-edu-12346-.xml
     91
     92}}}
     93
     94Each 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.
    10095
    10196'''BBN MyPLC Compute Resource RSpec '''
     
    159154}}}
    160155
     156The MyPLC plnodes are pre-configured to use pre-defined addresses and MyPLC doesn't allow experimenters to change that configuration. When the experiment is running you will need to choose the appropriate interface for your experiment traffic.
     157 
     158
    161159== Define !OpenFlow Network Resources Rspecs ==
    162160
    163 This section defines how to figure out the OF network path for youre rspec. To write an OF RSpec you must determine the end-to-end OF path that will be used for the experiment. Following is an outline of the process to determine the content of your OF RSpec:
     161To 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:
    164162
    165163Step 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.
     
    191189
    192190'' ''' Step 2''' ''. Review [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] to determine MyPLC hosts mapping to the Site's OpenFlow switch.
     191In the [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] page, select the OF Aggregate link for BBN, Clemson and Wisconsin and use the
     192OF site diagrams to determine which ports and DPID should be used in the OF RSpec. 
     193
    193194
    194195
    195196'' '''Step 3''' ''. Merge Step 1 and 2 to generate request RSpecs.
     197Use the request template in the [http://groups.geni.net/geni/wiki/HowTo/WriteOFv3Rspecs#WritingOpenFlowv3requestrspecs Writing OF V3 Request RSpecs]
    196198
    197199