Changes between Version 37 and Version 38 of HelloGENI
- Timestamp:
- 04/02/12 17:13:15 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HelloGENI
v37 v38 16 16 17 17 = Reserving necessary resources = 18 Tango GENI has diverse compute resources that are connected over multiple OpenFlow switches. In order to be able to reserve all the needed resources, we should first draw a detailed topology of our experiment. [wiki:TangoGENI Tango GENI] has two backbone VLANs (3715, 3716) each providing a different topology. For this example we are going to use VLAN 3715. 19 20 So using the topology maps of Tango GENI, along with diagrams from [http://groups.geni.net/geni/attachment/wiki/NetworkCore/OF-INT-BB%2025-May-2011.png NLR core], [http://groups.geni.net/geni/wiki/GeniAggregate/GpoLabOpenFlow GPO lab] and 21 [http://groups.geni.net/geni/wiki/GeniAggregate/ClemsonOpenFlow Clemson lab], we can draw this detailed topology for this simple example : 18 GENI Mesoscale deployment has diverse compute resources that are connected over multiple OpenFlow switches. In order to be able to reserve all the needed resources, we should first draw a detailed topology of our experiment. [wiki:TangoGENI The Mesoscale GENI deployment] has two backbone VLANs (3715, 3716) each providing a different topology. For this example we are going to use VLAN 3715. 19 20 So using the topology maps, along with diagrams from [wiki: NLR core], we can draw this detailed topology for this simple example : 22 21 23 22 [[Image(hellogeni-topo.jpg, 20%)]] … … 35 34 For the purpose of this example, using this [attachment:omni_config] file, created a slice named hellogenislice 36 35 {{{ 37 > src/omni.py createslice hellogenislice38 > src/omni.py renewslice hellogenislice 20110630T18:00:0036 > omni.py createslice hellogenislice 37 > omni.py renewslice hellogenislice 20120408T18:00:00 39 38 }}} 40 39 41 40 == Reserve an IP subnet == 42 In Tango GENI, if an experiment is a layer 3 experiment, it would need it's own separate IP subnet so that it is able to control all traffic for this subnet without interfering with traffic from other experiments. GPO has set aside 10.42.0.0/16 as a pool of IP subnets for this. These subnets aren't provided by an aggregate, and thus can't be reserved via the GENI AM API. Please DO NOT use an IP subnet that you have not reserved, just request for one toassigned to you.41 In Mesoscale, if an experiment is a layer 3 experiment, it would need it's own separate IP subnet so that it is able to control all traffic for this subnet without interfering with traffic from other experiments. GPO has set aside 10.42.0.0/16 as a pool of IP subnets for this. These subnets aren't provided by an aggregate, and thus can't be reserved via the GENI AM API. Please DO NOT use an IP subnet that you have not reserved, just request for one to be assigned to you. 43 42 44 43 === Email template for reserving IP subnet === … … 53 52 so that I can complete the tutorial. 54 53 user urn : URI:urn:publicid:IDN+pgeni.gpolab.bbn.com+user+inki, email:inki@pgeni.gpolab.bbn.com 55 duration : until June 30th 201154 duration : until April the 8th 2012 56 55 57 56 Thanks, … … 63 62 64 63 == Create slivers == 65 For each aggregate we would need to create a sliver that will contain the necessary resources. For all aggregates it is important to now the AM url for requesting the resources. The best place to get the information is at [wiki:GeniAggregate the Aggregate's wiki page]. At [wiki:TangoGENI] there is also a list of URLs of active aggregates. If there is an aggregate whose URL you can't find, please email [mailto:help@geni.net].64 For each aggregate we would need to create a sliver that will contain the necessary resources. For all aggregates it is important to know the AM url for requesting the resources. The best place to get the information is at [wiki:GeniAggregate the Aggregate's wiki page]. Also the example [source:trunk/wikifiles/hello-geni/omni_config] file has a list of all the AMs along with assigned nicknames. If you include a similar section in your omni_config file then you can refer to AMs using their nicknames. If there is an aggregate whose URL you can't find, please email [mailto:help@geni.net]. 66 65 67 66 === Clemson myPLC sliver === 68 From [wiki:GeniAggregate/ClemsonMyPlc this page], we get this aggregate's URL and using [source:trunk/wikifiles/hello-geni/rspecs/myplc-clemson-hellogeni.rspec this rspec file], we can reserve a sliver in planetlab5:69 {{{ 70 src/omni.py createsliver -n -a https://myplc.clemson.edu:12346 -n hellogenislice myplc-clemson-hellogeni.rspec67 From [wiki:GeniAggregate/ClemsonMyPlc this page], we get this aggregate's URL, and we find out what is its nickname from our [source:trunk/wikifiles/hello-geni/omni_config] file (in this case it is `plc-clemson`) and using [source:trunk/wikifiles/hello-geni/rspecs/myplc-clemson-hellogeni.rspec this rspec file], we can reserve a sliver in planetlab5: 68 {{{ 69 omni.py createsliver -a plc-clemson hellogenislice myplc-clemson-hellogeni.rspec 71 70 }}} 72 71 The output should look like [attachment:myplc-clemson-hellogeni.out this]. … … 74 73 Use sliverstatus to figure out the login name : 75 74 {{{ 76 > src/omni.py sliverstatus -n -a https://myplc.clemson.edu:12346 hellogenislice75 >omni.py sliverstatus -n -a https://myplc.clemson.edu:12346 hellogenislice 77 76 }}} 78 77 … … 85 84 Your sliver should be ready within 1 min. If after 5 min you are not able to login to the host, delete your sliver and recreate it. If the problem persists email to the support email given in the aggregate page. 86 85 {{{ 87 src/omni.py deletesliver -n -a https://myplc.clemson.edu:12346 hellogenislice86 omni.py deletesliver -n -a https://myplc.clemson.edu:12346 hellogenislice 88 87 }}} 89 88 … … 101 100 From [wiki:GeniAggregate/GpoLabProtoGeni this page], we get this aggregate's URL and using [source:rtrunk/wikifiles/hello-geni/rspecs/protogeni-bbn-hellogeni.rspec this rspec file], we can reserve one ProtoGENI node: 102 101 {{{ 103 src/omni.py createsliver -n -a http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am hellogenislice protogeni-bbn-hellogeni.rspec102 omni.py createsliver -n -a http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am hellogenislice protogeni-bbn-hellogeni.rspec 104 103 }}} 105 104 … … 108 107 Then we can do sliverstatus to find out the status of the sliver 109 108 {{{ 110 > src/omni.py sliverstatus -n -a http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am hellogenislice109 >omni.py sliverstatus -n -a http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am hellogenislice 111 110 }}} 112 111 … … 147 146 148 147 {{{ 149 src/omni.py listresources -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 -o148 omni.py listresources -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 -o 150 149 }}} 151 150 … … 154 153 Based 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. 155 154 {{{ 156 src/omni.py createsliver -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 -n hellogenislice openflow-bbn-hellogeni.rspec155 omni.py createsliver -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 -n hellogenislice openflow-bbn-hellogeni.rspec 157 156 }}} 158 157 … … 162 161 Based 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. 163 162 {{{ 164 src/omni.py createsliver -a https://expedient.clemson.edu:1443/openflow/gapi/ hellogenislice openflow-clemson-hellogeni.rspec163 omni.py createsliver -a https://expedient.clemson.edu:1443/openflow/gapi/ hellogenislice openflow-clemson-hellogeni.rspec 165 164 }}} 166 165 … … 170 169 Based 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. 171 170 {{{ 172 src/omni.py createsliver -n -a https://ofc-testlab.grnoc.iu.edu:1443/openflow/gapi/ hellogenislice openflow-nlr-hellogeni.rspec171 omni.py createsliver -n -a https://ofc-testlab.grnoc.iu.edu:1443/openflow/gapi/ hellogenislice openflow-nlr-hellogeni.rspec 173 172 }}} 174 173 … … 262 261 For each aggregate delete the OpenFlow sliver : 263 262 {{{ 264 src/omni.py deletesliver -a https://ofc-testlab.grnoc.iu.edu:1443/openflow/gapi/ hellogenislice265 src/omni.py deletesliver -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 hellogenislice266 src/omni.py deletesliver -a https://expedient.clemson.edu:1443/openflow/gapi/ hellogenislice263 omni.py deletesliver -a https://ofc-testlab.grnoc.iu.edu:1443/openflow/gapi/ hellogenislice 264 omni.py deletesliver -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 hellogenislice 265 omni.py deletesliver -a https://expedient.clemson.edu:1443/openflow/gapi/ hellogenislice 267 266 }}} 268 267 … … 289 288 Invoke the delete sliver command 290 289 {{{ 291 src/omni.py deletesliver -a http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am hellogenislice292 src/omni.py deletesliver -a https://myplc.clemson.edu:12346 hellogenislice290 omni.py deletesliver -a http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am hellogenislice 291 omni.py deletesliver -a https://myplc.clemson.edu:12346 hellogenislice 293 292 }}} 294 293