| 74 | | 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 Aggregate Managers. Following are the omni commands issued to get the manifests for available resources: |
| 75 | | |
| 76 | | 1. Clemson FOAM and MyPLC aggregates: |
| 77 | | {{{ |
| 78 | | ./src/omni.py -a https://foam.clemson.edu:3626/foam/gapi/1 listresources -o # generates output file rspec-foam-clemson-edu-3626-foam-gapi-1.xml |
| | 80 | For complete list of available aggregates see the available [http://groups.geni.net/geni/wiki/GeniAggregate GENI Aggregates] page. |
| | 81 | |
| | 82 | == Define Compute Resources RSpecs == |
| | 83 | |
| | 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 | {{{ |
| 89 | | ./src/omni.py -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 listresources -o # generates rspec-foam-gpolab-bbn-com-3626-foam-gapi-1.xml |
| 90 | | }}} |
| 91 | | 4. NLR !OpenFlow Core FOAM server: |
| 92 | | {{{ |
| 93 | | $ ./src/omni.py -a https://foam.nlr.net:3626/foam/gapi/1 -o listresources # generates rspec-foam-nlr-net-3626-foam-gapi-1.xml |
| 94 | | }}} |
| 95 | | |
| 96 | | 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 Requests RSpecs to reserve the resources. Information in these files provides the switch and the port URN information to be used in making the OF flowspace reservation. |
| 97 | | |
| 98 | | The above results will give you some insight into what is available, but it is recommended that you coordinate with the site contact to ensure RSpec accuracy for each of the OF Aggregate Managers. |
| 99 | | |
| 100 | | |
| 101 | | == Define Compute Resources RSpecs == |
| 102 | | |
| 103 | | The section shows the compute resources RSpec defined based on the output of the listresources commands. |
| 104 | | |
| 105 | | '''BBN ProteGENI Compute Resource RSpec ''' |
| 106 | | {{{ |
| 107 | | #!xml |
| 108 | | <?xml version="1.0" ?> |
| 109 | | <!-- Resources at AM: |
| 110 | | URN: unspecified_AM_URN |
| 111 | | URL: http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am |
| 112 | | --> |
| 113 | | <rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/2" |
| 114 | | xmlns:emulab="http://www.protogeni.net/resources/rspec/ext/emulab/1" |
| 115 | | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| 116 | | xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 http://www.protogeni.net/resources/rspec/2/request.xsd |
| 117 | | http://www.protogeni.net/resources/rspec/ext/emulab/1 http://www.protogeni.net/resources/rspec/ext/emulab/1/ptop_extension.xsd "> |
| 118 | | <node component_id="urn:publicid:IDN+pgeni.gpolab.bbn.com+node+pc5" |
| 119 | | component_manager_id="urn:publicid:IDN+pgeni.gpolab.bbn.com+authority+cm" |
| 120 | | component_name="pc5" exclusive="true"> |
| 121 | | <sliver_type name="raw-pc"> |
| 122 | | </sliver_type> |
| 123 | | </node> |
| 124 | | </rspec> |
| | 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. |
| | 100 | |
| | 101 | '''BBN MyPLC Compute Resource RSpec ''' |
| | 102 | {{{ |
| | 103 | <?xml version="1.0"?> |
| | 104 | <!-- |
| | 105 | This rspec will create a container on each of the BBN production MyPLC plnodes. |
| | 106 | |
| | 107 | AM: https://myplc.gpolab.bbn.com:12346/ |
| | 108 | --> |
| | 109 | <RSpec type="SFA"> |
| | 110 | <network name="plc.gpolab"> |
| | 111 | <node component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+navis.gpolab.bbn.com" |
| | 112 | component_manager_id="urn:publicid:IDN+plc:gpolab+authority+sa" |
| | 113 | node_id="n1" site_id="urn:publicid:IDN+plc:gpolab:gpolab+authority+sa"> |
| | 114 | <hostname> navis.gpolab.bbn.com </hostname> |
| | 115 | </node> |
| | 116 | </network> |
| | 117 | </RSpec> |
| 170 | | The OF RSpecs used for this example assumes that the flowspace between the 3 sites is based on traffic type and port. This section has two parts which: |
| 171 | | * Walks through how to figure out the OF network path |
| 172 | | * Show RSpec defined as a result of the walkthrough |
| | 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: |
| | 164 | |
| | 165 | Step 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. |
| | 166 | Step 2. Review [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] to determine how each MyPLC host maps to the Site's OpenFlow switch. |
| | 167 | ports are |
| | 168 | Step 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. |
| | 169 | |
| | 170 | Each of the above is covered in detail below: |
| | 171 | |
| | 172 | '' ''' Step 1''' ''. Collect listresources from all FOAM Aggregate: |
| | 173 | |
| | 174 | 1. Clemson FOAM and MyPLC aggregates: |
| | 175 | {{{ |
| | 176 | ./src/omni.py -a https://foam.clemson.edu:3626/foam/gapi/1 listresources -o # generates output file rspec-foam-clemson-edu-3626-foam-gapi-1.xml |
| | 177 | }}} |
| | 178 | 2. Wisconsin FOAM and MyPLC aggregates: |
| | 179 | {{{ |
| | 180 | ./src/omni.py -a https://foam.wail.wisc.edu:3626/foam/gapi/1 listresources -o # generates rspec-foam-wail-wisc-edu-3626-foam-gapi-1.xml |
| | 181 | }}} |
| | 182 | 3. BBN FOAM and MyPLC aggregates: |
| | 183 | {{{ |
| | 184 | ./src/omni.py -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 listresources -o # generates rspec-foam-gpolab-bbn-com-3626-foam-gapi-1.xml |
| | 185 | }}} |
| | 186 | 4. NLR !OpenFlow Core FOAM server: |
| | 187 | {{{ |
| | 188 | $ ./src/omni.py -a https://foam.nlr.net:3626/foam/gapi/1 -o listresources # generates rspec-foam-nlr-net-3626-foam-gapi-1.xml |
| | 189 | }}} |
| | 190 | Information in these files provides the switch and the port information to be used in making the OF flowspace reservation. |
| | 191 | |
| | 192 | '' ''' Step 2''' ''. Review [http://groups.geni.net/geni/wiki/GeniAggregate GeniAggregate] to determine MyPLC hosts mapping to the Site's OpenFlow switch. |
| | 193 | |
| | 194 | |
| | 195 | '' '''Step 3''' ''. Merge Step 1 and 2 to generate request RSpecs. |
| | 196 | |
| 192 | | || dpid="0e:83:00:23:47:c8:bc:00" || |
| 193 | | || dpid="0e:83:00:23:47:ca:bc:40" || |
| 194 | | || dpid="0e:83:00:24:a8:d2:48:00" || |
| 195 | | || dpid="0e:83:00:24:a8:d2:b8:40" || |
| 196 | | || dpid="0e:83:00:26:f1:40:a8:00" || |
| 197 | | || dpid="0e:84:00:23:47:c8:bc:00" || |
| 198 | | || dpid="0e:84:00:23:47:ca:bc:40" || |
| 199 | | || dpid="0e:84:00:24:a8:d2:48:00" || |
| 200 | | || dpid="0e:84:00:24:a8:d2:b8:40" || |
| 201 | | || dpid="0e:84:00:26:f1:40:a8:00" || |
| 202 | | |
