Changes between Version 43 and Version 44 of HelloGENI


Ignore:
Timestamp:
04/10/12 17:02:29 (12 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • HelloGENI

    v43 v44  
    140140
    141141=== OpenFlow Slivers ===
    142 After we have reserved and configured all the compute resources we are ready to reserve the OpenFlow resources. This example spans three different OpenFlow aggregates, GPO, Clemson and NLR. The first thing we need to figure out, is where to run the OpenFlow controller. The OpenFlow controller is the software that decides how packets that belong to our sliver should be handled. The host running the !OpenFlow controller listening on a TCP port, should be reachable by the OpenFlow resources at the sites (i.e. any firewalls in front of your controller must permit your TCP port).For the purpose of this example the controller will run at nineveh.gpolab.bbn.com on tcp port 1718.
     142After we have reserved and configured all the compute resources we are ready to reserve the OpenFlow resources. This example spans three different OpenFlow aggregates, GPO, Clemson and NLR. The first thing we need to figure out, is where to run the OpenFlow controller. The OpenFlow controller is the software that decides how packets that belong to our sliver should be handled. The host running the !OpenFlow controller listening on a TCP port, should be reachable by the OpenFlow resources at the sites (i.e. any firewalls in front of your controller must permit your TCP port).For the purpose of this example the controller will run at example.geni.net on tcp port 9933.
    143143
    144144'''Note''' that for some switches, the OpenFlow number port is not the same as the physical port name. The best way to figure out what port number you need is through listresources.
    … …  
    153153Based on the topology diagram above, at the GPO aggregate we would like to reserve resources related to IP subnet 10.42.130.0/24 on the two GPO switches for ports 1, 47 of the first switch and ports 20 and 3 on the second. [source:trunk/wikifiles/hello-geni/rspecs:openflow-bbn-hellogeni.rspec This] is an rspec that requests these resources. From GPO's aggregate page we can also get the AM URL.
    154154{{{
    155 omni.py createsliver -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 -n hellogenislice openflow-bbn-hellogeni.rspec
     155omni.py createsliver -a of-gpo -n hellogenislice openflow-bbn-hellogeni.rspec
    156156}}}
    157157
    … …  
    161161Based on the topology diagram above, at the Clemson aggregate we would like to reserve resources related to IP subnet 10.42.130.0/24 on the two clemson switch for ports 43 and 36. [source:trunk/wikifiles/hello-geni/openflow-clemson-hellogeni.rspec This] is an rspec that requests these resources. From Clemson's aggregate page we can also get the AM URL.
    162162{{{
    163 omni.py createsliver  -a https://foam.clemson.edu:3626/foam/gapi/1 hellogenislice openflow-clemson-hellogeni.rspec
     163omni.py createsliver  -a of-clemson hellogenislice openflow-clemson-hellogeni.rspec
    164164}}}
    165165
    … …  
    169169Based on the topology diagram above, at the Clemson aggregate we would like to reserve resources related to IP subnet 10.42.130.0/24 on the two NLR switch for ports 25 and 26 on both. [source:trunk/wikifiles/hello-geni/rspecsopenflow-nlr-hellogeni.rspec This] is an rspec that requests these resources. From NLR's aggregate page we can also get the AM URL.
    170170{{{
    171 omni.py createsliver -n -a https://foam.nlr.net:3626/foam/gapi/1 hellogenislice openflow-nlr-hellogeni.rspec
     171omni.py createsliver -n -a of-nlr hellogenislice openflow-nlr-hellogeni.rspec
    172172}}}
    173173
    … …  
    231231For each aggregate delete the OpenFlow sliver :
    232232{{{
    233 omni.py deletesliver -a https://ofc-testlab.grnoc.iu.edu:1443/openflow/gapi/ hellogenislice
    234 omni.py deletesliver -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 hellogenislice
    235 omni.py deletesliver -a https://foam.clemson.edu:3626/foam/gapi/1 hellogenislice
     233omni.py deletesliver -a of-gpo hellogenislice
     234omni.py deletesliver -a of-clemson hellogenislice
     235omni.py deletesliver -a of-nlr hellogenislice
    236236}}}
    237237
    238238The output should look like [attachment:delete-openflow-nlr-hellogeni.out this].
    239239
    240 If your slice has already expired then only the Aggregate administrator can delete your OpenFlow sliver. In this case you would need to send an email :
    241 
    242 {{{
    243 To: <email@aggregate.geni>
    244 From: Geni User <geniuser@example.com>
    245 Subject: Delete OpenFlow slice <slice_name>
    246 
    247 Please delete the OpenFlow slice with the following information :
    248  * name : <slice_name>
    249  * project : <project_name>
    250  * email : <user_email>
    251 
    252 Thanks,
    253 
    254 }}}
    255 
    256240== Release GPO's ProtoGENI and Clemson's myPLC  ==
    257241
    258242Invoke the delete sliver command
    259243{{{
    260 omni.py deletesliver -a http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am hellogenislice
    261 omni.py deletesliver -a https://myplc.clemson.edu:12346 hellogenislice
     244omni.py deletesliver -a pg-gpo hellogenislice
     245omni.py deletesliver -a plc-clemson hellogenislice
    262246}}}
    263247