89 | | 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 advertisements of available compute resources from the BBN, Clemson and Wisconsin MyPLC aggregates: |
| 89 | To write a MyPLC RSpec you must determine which nodes will be used for the experiment at each site. This section describes this process, which is comprised of the following steps: |
| 90 | |
| 91 | Step 1. Collect listresources from all MyPLC Aggregates. |
| 92 | Step 2. Determine the MyPLC host to be reserved. |
| 93 | Step 3. Generate the MyPLC Rspecs. |
| 94 | |
| 95 | === Step 1. Collect listresources from all MyPLC Aggregates === |
| 96 | |
| 97 | As a first step, the experimenter determines the available compute resources at each site. Following are the Omni commands issued to get the advertisements of available compute resources from the BBN, Clemson and Wisconsin MyPLC aggregates: |
101 | | The advertisement RSpecs are used to generate the request RSpecs to reserve the resources. Following are the compute resources request RSpec defined based on the output of the listresources commands above. |
| 109 | === Step 2. Determine the MyPLC hosts to be reserved === |
| 110 | From each site's advertisement RSpecs generated above, we choose one host: |
| 111 | |
| 112 | ==== BBN MyPLC Host ==== |
| 113 | At the BBN MyPLC, we choose the host ''navis'': |
| 114 | {{{ |
| 115 | <node component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+navis.gpolab.bbn.com" |
| 116 | component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" |
| 117 | component_name="navis.gpolab.bbn.com" client_id="mypc0" exclusive="false"> |
| 118 | <sliver_type name="plab-vnode"> |
| 119 | </sliver_type> |
| 120 | </node> |
| 121 | }}} |
| 122 | |
| 123 | ==== Clemson MyPLC Host ==== |
| 124 | At the Clemson MyPLC, we choose the host ''planetlab4'': |
| 125 | {{{ |
| 126 | <node component_id="urn:publicid:IDN+plc:cu+node+planetlab4.clemson.edu" |
| 127 | component_manager_id="urn:publicid:IDN+plc+authority+am" |
| 128 | component_name="planetlab4.clemson.edu" client_id="planetlab4" exclusive="false"> |
| 129 | <sliver_type name="plab-vnode"> |
| 130 | </sliver_type> |
| 131 | </node> |
| 132 | }}} |
| 133 | |
| 134 | ==== Wisconsin MyPLC Host ==== |
| 135 | At the Wisconsin MyPLC, we choose the host ''wings-openflow-1'': |
| 136 | {{{ |
| 137 | <node component_id="urn:publicid:IDN+plc:wisc+node+wings-openflow-1.wail.wisc.edu" |
| 138 | component_manager_id="urn:publicid:IDN+plc+authority+am" |
| 139 | component_name="wings-openflow-1.wail.wisc.edu" exclusive="false"> |
| 140 | <sliver_type name="plab-vnode"> |
| 141 | </sliver_type> |
| 142 | </node> |
| 143 | |
| 144 | }}} |
| 145 | |
| 146 | === Step 3. Generate the MyPLCs RSpecs === |
| 147 | |
| 148 | The advertisement RSpecs are used to generate the request RSpecs to reserve the resources. Following are the compute resources request RSpec defined based on the output of the listresources commands above. The request Rspec template looks as follows: |
| 149 | {{{ |
| 150 | <?xml version="1.0" ?> |
| 151 | <!-- Resources at AM: |
| 152 | URN: unspecified_AM_URN |
| 153 | URL: http://myplc.gpolab.bbn.com:12346/ |
| 154 | --> |
| 155 | |
| 156 | <rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/2" |
| 157 | xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" |
| 158 | xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" |
| 159 | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| 160 | xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 |
| 161 | http://www.protogeni.net/resources/rspec/2/request.xsd"> |
| 162 | |
| 163 | </rspec> |
| 164 | }}} |
| 165 | |