| | 1 | [[PageOutline]] |
| | 2 | '''Note: These instructions are for a prior Omni, V1.2. See [wiki:GENIExperimenter/ExperimentExample ExperimentExample].''' |
| | 3 | |
| | 4 | = GENI Experiment Example 1 = |
| | 5 | |
| | 6 | This page illustrates an operational example for the [wiki:GENIExperimenterOmniV1.2 GENI Experimenter How-to] page capturing the actions required to run an experiment using multiple resource aggregates and with user credentials from the GPO ProtoGENI Clearinghouse pgeni.gpolab.bbn.com. Details on how credentials are set up can be found in the [wiki:GENIExperimenterOmniV1.2#a1.GetGENICredentials GENI Credentials] section of the main GENI Experimenter page. In this experiment, a total of 5 nodes are requested, with 2 nodes from the Emulab(PG) aggregate and 3 nodes from the !PlanetLab (PL) aggregate. |
| | 7 | |
| | 8 | This page does not cover the installation of the OMNI client, as it is well documented, please see the following pages to get the [http://trac.gpolab.bbn.com/gcf/wiki/GettingGcf GCF package] and to [http://trac.gpolab.bbn.com/gcf/wiki/QuickStart install] it. |
| | 9 | |
| | 10 | == Omni Configuration == |
| | 11 | |
| | 12 | For GENI Experiment Example defined above, the following omni_config settings were used: |
| | 13 | |
| | 14 | {{{ |
| | 15 | [omni] |
| | 16 | default_cf = pgeni |
| | 17 | users = lnevers |
| | 18 | |
| | 19 | # ---------- Users ---------- |
| | 20 | [lnevers] |
| | 21 | urn = urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers |
| | 22 | keys = ~/.ssh/id_rsa.pub |
| | 23 | |
| | 24 | # ---------- Frameworks ---------- |
| | 25 | [pgeni] |
| | 26 | type = pg |
| | 27 | ch = https://www.emulab.net:443/protogeni/xmlrpc/ch |
| | 28 | sa = https://www.pgeni.gpolab.bbn.com:443/protogeni/xmlrpc/sa |
| | 29 | cert = ~/.ssl/encrypted-cleartext.pem |
| | 30 | key = ~/.ssl/encrypted-cleartext.pem |
| | 31 | verbose=false |
| | 32 | |
| | 33 | [emulab] |
| | 34 | type = pg |
| | 35 | ch = https://www.emulab.net:443/protogeni/xmlrpc/ch |
| | 36 | sa = https://www.emulab.net:443/protogeni/xmlrpc/sa |
| | 37 | cert = ~/.ssl/encrypted-cleartext.pem |
| | 38 | key = ~/.ssl/encrypted-cleartext.pem |
| | 39 | |
| | 40 | [plc] |
| | 41 | type=sfa |
| | 42 | authority=plc.bbn |
| | 43 | user=plc.bbn.lnevers |
| | 44 | cert=~/.gcf/plc.bbn.lnevers.gid |
| | 45 | key=~/.gcf/lnevers.pkey |
| | 46 | registry=http://www.planet-lab.org:12345 |
| | 47 | slicemgr=http://www.planet-lab.org:12347 |
| | 48 | }}} |
| | 49 | |
| | 50 | The above configuration is specific to the experiment captured in this page. Note, the pgeni framework definition includes the Utah Emulab clearinghouse, which is the only clearing house for ProtoGENI aggregates. For additional configuration details please see the [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] page for more details. The omni_configuration parameters shown define the following: [[BR]] |
| | 51 | || '''Parameter''' || ''' Use''' || |
| | 52 | || default_cf|| Default aggregate used if not specified on the command line. || |
| | 53 | || users|| users setting used when reserving slices. || |
| | 54 | || urn|| The username URN, see how to determing [wiki:GENIExperimenter/ExperimentCredentials#DetermineyourURN your URN] || |
| | 55 | || keys|| A comma separated list of public ssh key files to be uploaded to the Clearinghouse || |
| | 56 | || type|| Resource aggregate "pg" indicates ProtoGENI, sse the [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] page. || |
| | 57 | || ch|| ProtoGENI Clearinghouse URL. || |
| | 58 | || sa|| Slice Authority URL. || |
| | 59 | || cert|| Location of the SSL encrypted certificate (contains both a certificate and a key). || |
| | 60 | || key|| Location of your SSL encrypted certificate (contains both a certificate and a key). || |
| | 61 | |
| | 62 | |
| | 63 | == List available resources == |
| | 64 | |
| | 65 | With the GPO Protogeni setting defined as shown in the omni_config above, you can get a list of available resources from each of the other 2 aggregates. |
| | 66 | |
| | 67 | Getting a list of resources from Emulab Protogeni aggregate in native format: |
| | 68 | {{{ |
| | 69 | $ src/omni.py -n -a https://www.emulab.net/protogeni/xmlrpc/am listresources >resources-PG-emulab.xml |
| | 70 | INFO:omni:Loading config file omni_config |
| | 71 | INFO:omni:Using control framework pgeni |
| | 72 | INFO:omni:Resources at https://www.emulab.net/protogeni/xmlrpc/am: |
| | 73 | }}} |
| | 74 | Getting a list of resources from !PlanetLab aggregate: |
| | 75 | {{{ |
| | 76 | $ src/omni.py listresources -n -a http://www.planet-lab.org:12346 >resources-PL.xml |
| | 77 | INFO:omni:Loading config file omni_config |
| | 78 | INFO:omni:Using control framework pgeni |
| | 79 | INFO:omni:Resources at http://www.planet-lab.org:12346: |
| | 80 | }}} |
| | 81 | |
| | 82 | You may use the output of two ''listresources'' commands to generate rspecs to request resources. The above ''listresources'' commands use the ''-n'' flag to request output in native rspec format rather than the default omnispec format. Note, the ''-n'' flag requires the ''-a'' flag also be used to specify an aggregate manager. |
| | 83 | |
| | 84 | If you are planning to use MyPLC resources, you may query a MyPLC installation to get a list of available resources as follows: |
| | 85 | {{{ |
| | 86 | $ ./src/omni.py -n -a http://myplc.gpolab.bbn.com:12346 listresources >resources-MyPLC.xml |
| | 87 | INFO:omni:Loading config file omni_config |
| | 88 | INFO:omni:Using control framework pgeni |
| | 89 | INFO:omni:Resources at http://myplc.gpolab.bbn.com:12346: |
| | 90 | |
| | 91 | }}} |
| | 92 | If you are planning to use Univerity of Kentucky Emulab resources, you can query this installation to get a list of available resources, note the example below was collected with GPO pgeni.gpolab.com credentials: |
| | 93 | {{{ |
| | 94 | $ src/omni.py -n -a https://www.uky.emulab.net/protogeni/xmlrpc/am listresources >resources-uky-emulab.xml |
| | 95 | INFO:omni:Loading config file omni_config |
| | 96 | INFO:omni:Using control framework pgeni |
| | 97 | INFO:omni:Resources at https://www.uky.emulab.net/protogeni/xmlrpc/am: |
| | 98 | }}} |
| | 99 | |
| | 100 | == Create a slice == |
| | 101 | |
| | 102 | Since the [wiki:GENIExperimenterOmniV1.2/ExperimentExample#OmniConfiguration omni_config] defines the credentials and the Clearinghouse for the GPO Protogeni, your slice will be created in pgeni.gpolab.bbn.com aggregate. For this example a slice named ''lnevers_slice'' is created, you should choose a slice name that is meaningful to you: |
| | 103 | |
| | 104 | {{{ |
| | 105 | $ ./src/omni.py createslice lnevers_slice |
| | 106 | INFO:omni:Loading config file omni_config |
| | 107 | INFO:omni:Using control framework pgeni |
| | 108 | Created slice with Name lnevers_slice, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers_slice |
| | 109 | }}} |
| | 110 | |
| | 111 | == Add Emulab PG resources to GPO PG slice == |
| | 112 | |
| | 113 | To request two Emulab ProtoGENI nodes, the following rspec named emulab.rspec was used for this example, your rspec will be specific to your experiment requirements: |
| | 114 | {{{ |
| | 115 | <?xml version="1.0" encoding="UTF-8"?> |
| | 116 | <rspec xmlns="http://protogeni.net/resources/rspec/0.2"> |
| | 117 | <node virtual_id="geni1" |
| | 118 | virtualization_type="emulab-vnode"> |
| | 119 | </node> |
| | 120 | <node virtual_id="geni2" |
| | 121 | virtualization_type="emulab-vnode"> |
| | 122 | </node> |
| | 123 | </rspec> |
| | 124 | }}} |
| | 125 | |
| | 126 | To request two Protogeni nodes, a sliver was created within the Emulab Protogeni with the rpec above using the following command: |
| | 127 | {{{ |
| | 128 | $ ./src/omni.py -a https://www.emulab.net/protogeni/xmlrpc/am -n createsliver lnevers_slice emulab.rspec |
| | 129 | INFO:omni:Loading config file omni_config |
| | 130 | INFO:omni:Using control framework pgeni |
| | 131 | Asked https://www.emulab.net/protogeni/xmlrpc/am to reserve resources. Result: |
| | 132 | <?xml version="1.0" ?> |
| | 133 | <rspec xmlns="http://protogeni.net/resources/rspec/0.2"> |
| | 134 | <node component_manager_urn="urn:publicid:IDN+emulab.net+authority+cm" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" component_urn="urn:publicid:IDN+emulab.net+node+pc303" component_uuid="de9e6e61-773e-102b-8eb4-001143e453fe" exclusive="1" hostname="pc303.emulab.net" sliver_urn="urn:publicid:IDN+emulab.net+sliver+36084" sliver_uuid="a8e9898e-48df-11e0-b35d-001143e453fe" sshdport="22" virtual_id="geni1" virtualization_type="raw"> |
| | 135 | <services> <login authentication="ssh-keys" hostname="pc303.emulab.net" port="22"/> </services> </node> |
| | 136 | <node component_manager_urn="urn:publicid:IDN+emulab.net+authority+cm" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" component_urn="urn:publicid:IDN+emulab.net+node+pc203" component_uuid="de9e66fd-773e-102b-8eb4-001143e453fe" exclusive="1" hostname="pc203.emulab.net" sliver_urn="urn:publicid:IDN+emulab.net+sliver+36085" sliver_uuid="a95e6eef-48df-11e0-b35d-001143e453fe" sshdport="22" virtual_id="geni2" virtualization_type="raw"> |
| | 137 | <services> <login authentication="ssh-keys" hostname="pc203.emulab.net" port="22"/> </services> </node> |
| | 138 | </rspec> |
| | 139 | |
| | 140 | }}} |
| | 141 | |
| | 142 | == Add PlanetLab resources to GPO PG slice == |
| | 143 | |
| | 144 | To request three Planetlab nodes, the following rspec named planet.rspec was used for this example, your rspec will be specific to your experiment requirements: |
| | 145 | |
| | 146 | {{{ |
| | 147 | <?xml version="1.0"?> |
| | 148 | <RSpec type="SFA"> |
| | 149 | <network name="plc"> |
| | 150 | <site id="rit"> |
| | 151 | <name>RIT</name> |
| | 152 | <node id="n11503"> |
| | 153 | <hostname>planet2.cs.rit.edu</hostname> |
| | 154 | <sliver /> |
| | 155 | </node> |
| | 156 | </site> |
| | 157 | <site id="williams"> |
| | 158 | <name>Williams College</name> |
| | 159 | <node id="n10860"> |
| | 160 | <hostname>planetlab3.williams.edu</hostname> |
| | 161 | <sliver /> |
| | 162 | </node> |
| | 163 | </site> |
| | 164 | <site id="bbn"> |
| | 165 | <name>BBN Technologies</name> |
| | 166 | <node id="n13627"> |
| | 167 | <hostname>plnode-03.gpolab.bbn.com</hostname> |
| | 168 | <sliver /> |
| | 169 | </node> |
| | 170 | </site> |
| | 171 | </network> |
| | 172 | </RSpec> |
| | 173 | }}} |
| | 174 | |
| | 175 | To request the three Planetlab nodes, a sliver was created within Planetlab with the rpec above using the following command: |
| | 176 | |
| | 177 | {{{ |
| | 178 | $ ./src/omni.py -a http://www.planet-lab.org:12346 -n createsliver lnevers_slice planet.rspec |
| | 179 | INFO:omni:Loading config file omni_config |
| | 180 | INFO:omni:Using control framework pgeni |
| | 181 | Asked http://www.planet-lab.org:12346 to reserve resources. Result: <?xml version="1.0"?> |
| | 182 | <RSpec type="SFA"> |
| | 183 | <network name="plc"> |
| | 184 | <site id="rit"> |
| | 185 | <name>RIT</name> |
| | 186 | <node id="n11503"> |
| | 187 | <hostname>"planet2.cs.rit.edu</hostname> |
| | 188 | <sliver /> |
| | 189 | </node> |
| | 190 | </site> |
| | 191 | <site id="williams"> |
| | 192 | <name>Williams College</name> |
| | 193 | <node id="n10860"> |
| | 194 | <hostname>planetlab3.williams.edu</hostname> |
| | 195 | <sliver /> |
| | 196 | </node> |
| | 197 | </site> |
| | 198 | <site id="bbn"> |
| | 199 | <name>BBN Technologies</name> |
| | 200 | <node id="n13627"> |
| | 201 | <hostname>plnode-03.gpolab.bbn.com</hostname> |
| | 202 | <sliver /> |
| | 203 | </node> |
| | 204 | </site> |
| | 205 | </network> |
| | 206 | </RSpec> |
| | 207 | |
| | 208 | |
| | 209 | INFO:omni:Please run the omni sliverstatus call on your slice to determine your login name to PL resources |
| | 210 | }}} |
| | 211 | |
| | 212 | As part of the ''createsliver'' operation for PL nodes, Omni tools upload the user SSH keys based on the [users] section of the omni_config. If you have problems in setting up your slice, contact us at [mailto:help@geni.net]. |
| | 213 | |
| | 214 | == Checking sliver resource status == |
| | 215 | |
| | 216 | Once you have requested the resources you may check the sliver status for PG and PL nodes. As you review the results, note the expiration time to make sure that it meets your experiment running time requirement. To get ''sliverstatus'' for the example experiment on this page the following command was issued for the PG resources: |
| | 217 | |
| | 218 | {{{ |
| | 219 | $ ./src/omni.py sliverstatus -a https://www.emulab.net/protogeni/xmlrpc/am lnevers_slice |
| | 220 | INFO:omni:Loading config file omni_config |
| | 221 | INFO:omni:Using control framework pgeni |
| | 222 | Status of Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers_slice: |
| | 223 | Sliver at https://www.emulab.net/protogeni/xmlrpc/am: |
| | 224 | {'geni_resources': [{'geni_error': '', |
| | 225 | 'geni_status': 'ready', |
| | 226 | 'geni_urn': 'urn:publicid:IDN+emulab.net+sliver+36085', |
| | 227 | 'pg_manifest': {'attributes': {'component_manager_urn': 'urn:publicid:IDN+emulab.net+authority+cm', |
| | 228 | 'component_manager_uuid': '28a10955-aa00-11dd-ad1f-001143e453fe', |
| | 229 | 'component_urn': 'urn:publicid:IDN+emulab.net+node+pc203', |
| | 230 | 'component_uuid': 'de9e66fd-773e-102b-8eb4-001143e453fe', |
| | 231 | 'exclusive': 1, |
| | 232 | 'hostname': 'pc203.emulab.net', |
| | 233 | 'sliver_urn': 'urn:publicid:IDN+emulab.net+sliver+36085', |
| | 234 | 'sliver_uuid': 'a95e6eef-48df-11e0-b35d-001143e453fe', |
| | 235 | 'sshdport': 22, |
| | 236 | 'virtual_id': 'geni2', |
| | 237 | 'virtualization_type': 'raw', |
| | 238 | 'xmlns': 'http://protogeni.net/resources/rspec/0.2'}, |
| | 239 | 'children': [{'attributes': {}, |
| | 240 | 'children': [{'attributes': {'authentication': 'ssh-keys', |
| | 241 | 'hostname': 'pc203.emulab.net', |
| | 242 | 'port': 22}, |
| | 243 | 'children': [], |
| | 244 | 'name': 'login'}], |
| | 245 | 'name': 'services'}], |
| | 246 | 'name': 'node'}, |
| | 247 | 'pg_status': 'ready'}, |
| | 248 | {'geni_error': '', |
| | 249 | 'geni_status': 'ready', |
| | 250 | 'geni_urn': 'urn:publicid:IDN+emulab.net+sliver+36084', |
| | 251 | 'pg_manifest': {'attributes': {'component_manager_urn': 'urn:publicid:IDN+emulab.net+authority+cm', |
| | 252 | 'component_manager_uuid': '28a10955-aa00-11dd-ad1f-001143e453fe', |
| | 253 | 'component_urn': 'urn:publicid:IDN+emulab.net+node+pc303', |
| | 254 | 'component_uuid': 'de9e6e61-773e-102b-8eb4-001143e453fe', |
| | 255 | 'exclusive': 1, |
| | 256 | 'hostname': 'pc303.emulab.net', |
| | 257 | 'sliver_urn': 'urn:publicid:IDN+emulab.net+sliver+36084', |
| | 258 | 'sliver_uuid': 'a8e9898e-48df-11e0-b35d-001143e453fe', |
| | 259 | 'sshdport': 22, |
| | 260 | 'virtual_id': 'geni1', |
| | 261 | 'virtualization_type': 'raw', |
| | 262 | 'xmlns': 'http://protogeni.net/resources/rspec/0.2'}, |
| | 263 | 'children': [{'attributes': {}, |
| | 264 | 'children': [{'attributes': {'authentication': 'ssh-keys', |
| | 265 | 'hostname': 'pc303.emulab.net', |
| | 266 | 'port': 22}, |
| | 267 | 'children': [], |
| | 268 | 'name': 'login'}], |
| | 269 | 'name': 'services'}], |
| | 270 | 'name': 'node'}, |
| | 271 | 'pg_status': 'ready'}], |
| | 272 | 'geni_status': 'ready', |
| | 273 | 'geni_urn': 'urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers_slice', |
| | 274 | 'pg_expires': '2011-03-07 16:23:05', |
| | 275 | 'pg_status': 'ready'} |
| | 276 | }}} |
| | 277 | |
| | 278 | To Check the ''sliverstatus'' for PL resources, the following command was issued: |
| | 279 | |
| | 280 | {{{ |
| | 281 | $ ./src/omni.py sliverstatus -a http://www.planet-lab.org:12346 lnevers_slice |
| | 282 | INFO:omni:Loading config file omni_config |
| | 283 | INFO:omni:Using control framework pgeni |
| | 284 | Status of Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers_slice: |
| | 285 | Sliver at http://www.planet-lab.org:12346: |
| | 286 | {'geni_resources': [{'geni_error': '', |
| | 287 | 'geni_status': 'ready', |
| | 288 | 'geni_urn': 'urn:publicid:IDN+plc:bbn+node+plnode-03.gpolab.bbn.com', |
| | 289 | 'pl_boot_state': 'boot', |
| | 290 | 'pl_hostname': 'plnode-03.gpolab.bbn.com', |
| | 291 | 'pl_last_contact': 'Mon Mar 7 12:17:51 2011'}, |
| | 292 | {'geni_error': '', |
| | 293 | 'geni_status': 'ready', |
| | 294 | 'geni_urn': 'urn:publicid:IDN+plc:williams+node+planetlab3.williams.edu', |
| | 295 | 'pl_boot_state': 'boot', |
| | 296 | 'pl_hostname': 'planetlab3.williams.edu', |
| | 297 | 'pl_last_contact': 'Mon Mar 7 12:23:21 2011'}, |
| | 298 | {'geni_error': '', |
| | 299 | 'geni_status': 'ready', |
| | 300 | 'geni_urn': 'urn:publicid:IDN+plc:rit+node+planet2.cs.rit.edu', |
| | 301 | 'pl_boot_state': 'boot', |
| | 302 | 'pl_hostname': 'planet2.cs.rit.edu', |
| | 303 | 'pl_last_contact': 'Tue Mar 1 05:49:20 2011'}], |
| | 304 | 'geni_status': 'ready', |
| | 305 | 'geni_urn': 'urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers_slice', |
| | 306 | 'pl_expires': 'Mon Mar 21 13:24:29 2011', |
| | 307 | 'pl_login': 'pgenigpolabbbncom_lneversslice'} |
| | 308 | |
| | 309 | }}} |
| | 310 | |
| | 311 | A lot of very useful information is reported for the ''sliverstatus'' output including which hosts are assigned to you and for how long. For PlanetLab, notice the value in the 'pl_login' field, which is the login to be used to access the nodes. For a slice across multiple aggregates, you should pay close attention to the expiration time for each aggregate sliver (pg_expires & pl_expires). For this example the pg_expires is ''2011-03-07 16:23:05'' while the pl_expires is ''Mon Mar 21 13:24:29 2011'', make sure that each expiration time meets your requirements for the experiment duration. If you need to extend the expiration, you can use the Omni ''renewsliver'' to expand the time for each sliver and for the slice. The following command is issued to modify the expiration time for the ProtoGENI resources: |
| | 312 | |
| | 313 | {{{ |
| | 314 | $ ./src/omni.py -a https://www.emulab.net/protogeni/xmlrpc/am renewslice lnevers_slice "03/21/11 13:00:00" |
| | 315 | INFO:omni:Loading config file omni_config |
| | 316 | INFO:omni:Using control framework pgeni |
| | 317 | INFO:omni.protogeni:requesting new expiration '2011-03-21T13:00:00' |
| | 318 | Slice lnevers_slice now expires at 2011-03-21 13:00:00 |
| | 319 | |
| | 320 | }}} |
| | 321 | |
| | 322 | Check status again and you will notice that the ''pg_expires'' has been modified and is more in line with the ''pg_expires'': |
| | 323 | |
| | 324 | {{{ |
| | 325 | $ ./src/omni.py sliverstatus -a https://www.emulab.net/protogeni/xmlrpc/am lnevers_slice |
| | 326 | INFO:omni:Loading config file omni_config |
| | 327 | INFO:omni:Using control framework pgeni |
| | 328 | Status of Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers_slice: |
| | 329 | Sliver at https://www.emulab.net/protogeni/xmlrpc/am: |
| | 330 | {'geni_resources': [{'geni_error': '', |
| | 331 | 'geni_status': 'ready', |
| | 332 | 'geni_urn': 'urn:publicid:IDN+emulab.net+sliver+36085', |
| | 333 | 'pg_manifest': {'attributes': {'component_manager_urn': 'urn:publicid:IDN+emulab.net+authority+cm', |
| | 334 | 'component_manager_uuid': '28a10955-aa00-11dd-ad1f-001143e453fe', |
| | 335 | 'component_urn': 'urn:publicid:IDN+emulab.net+node+pc203', |
| | 336 | 'component_uuid': 'de9e66fd-773e-102b-8eb4-001143e453fe', |
| | 337 | 'exclusive': 1, |
| | 338 | 'hostname': 'pc203.emulab.net', |
| | 339 | 'sliver_urn': 'urn:publicid:IDN+emulab.net+sliver+36085', |
| | 340 | 'sliver_uuid': 'a95e6eef-48df-11e0-b35d-001143e453fe', |
| | 341 | 'sshdport': 22, |
| | 342 | 'virtual_id': 'geni2', |
| | 343 | 'virtualization_type': 'raw', |
| | 344 | 'xmlns': 'http://protogeni.net/resources/rspec/0.2'}, |
| | 345 | 'children': [{'attributes': {}, |
| | 346 | 'children': [{'attributes': {'authentication': 'ssh-keys', |
| | 347 | 'hostname': 'pc203.emulab.net', |
| | 348 | 'port': 22}, |
| | 349 | 'children': [], |
| | 350 | 'name': 'login'}], |
| | 351 | 'name': 'services'}], |
| | 352 | 'name': 'node'}, |
| | 353 | 'pg_status': 'ready'}, |
| | 354 | {'geni_error': '', |
| | 355 | 'geni_status': 'ready', |
| | 356 | 'geni_urn': 'urn:publicid:IDN+emulab.net+sliver+36084', |
| | 357 | 'pg_manifest': {'attributes': {'component_manager_urn': 'urn:publicid:IDN+emulab.net+authority+cm', |
| | 358 | 'component_manager_uuid': '28a10955-aa00-11dd-ad1f-001143e453fe', |
| | 359 | 'component_urn': 'urn:publicid:IDN+emulab.net+node+pc303', |
| | 360 | 'component_uuid': 'de9e6e61-773e-102b-8eb4-001143e453fe', |
| | 361 | 'exclusive': 1, |
| | 362 | 'hostname': 'pc303.emulab.net', |
| | 363 | 'sliver_urn': 'urn:publicid:IDN+emulab.net+sliver+36084', |
| | 364 | 'sliver_uuid': 'a8e9898e-48df-11e0-b35d-001143e453fe', |
| | 365 | 'sshdport': 22, |
| | 366 | 'virtual_id': 'geni1', |
| | 367 | 'virtualization_type': 'raw', |
| | 368 | 'xmlns': 'http://protogeni.net/resources/rspec/0.2'}, |
| | 369 | 'children': [{'attributes': {}, |
| | 370 | 'children': [{'attributes': {'authentication': 'ssh-keys', |
| | 371 | 'hostname': 'pc303.emulab.net', |
| | 372 | 'port': 22}, |
| | 373 | 'children': [], |
| | 374 | 'name': 'login'}], |
| | 375 | 'name': 'services'}], |
| | 376 | 'name': 'node'}, |
| | 377 | 'pg_status': 'ready'}], |
| | 378 | 'geni_status': 'ready', |
| | 379 | 'geni_urn': 'urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers_slice', |
| | 380 | 'pg_expires': '2011-03-21 07:00:00', |
| | 381 | 'pg_status': 'ready'} |
| | 382 | }}} |
| | 383 | |
| | 384 | Both sliver now have similar expiration time and resources are available for the same timeframe. |
| | 385 | |
| | 386 | == Verify Resources and run your Experiment == |
| | 387 | |
| | 388 | Once you have the ''sliverstatus'', you have enough information to access the hosts allocated for you experiment. Simply SSH into one of the hosts and ping any of the other hosts in your experiment. Notice that the ''pl_login'' is being used to get access. Now verify that there is connectivity between to allocated resource. In this example experiment, one of the !PlanetLab resources allocated is used to ping a !ProtoGENI resource also part of the experiment: |
| | 389 | |
| | 390 | {{{ |
| | 391 | $ ssh pgenigpolabbbncom_lneversslice@plnode-03.gpolab.bbn.com |
| | 392 | Last login: Mon Mar 7 18:20:48 2011 from sendaria.gpolab.bbn.com |
| | 393 | [pgenigpolabbbncom_lneversslice@plnode-03 ~]$ ping pc203.emulab.net -c 3 |
| | 394 | PING pc203.emulab.net (155.98.39.3) 56(84) bytes of data. |
| | 395 | 64 bytes from pc203.emulab.net (155.98.39.3): icmp_seq=1 ttl=44 time=116 ms |
| | 396 | 64 bytes from pc203.emulab.net (155.98.39.3): icmp_seq=2 ttl=44 time=116 ms |
| | 397 | 64 bytes from pc203.emulab.net (155.98.39.3): icmp_seq=3 ttl=44 time=116 ms |
| | 398 | |
| | 399 | --- pc203.emulab.net ping statistics --- |
| | 400 | 3 packets transmitted, 3 received, 0% packet loss, time 2001ms |
| | 401 | rtt min/avg/max/mdev = 116.385/116.595/116.997/0.398 ms |
| | 402 | [pgenigpolabbbncom_lneversslice@plnode-03 ~]$ |
| | 403 | }}} |
| | 404 | |
| | 405 | Once you have verified connectivity between these hosts that have been allocated, you may start your experiment. |
| | 406 | |
| | 407 | == Delete sliver resources == |
| | 408 | |
| | 409 | When the experiment is completed you should release the resources by deleting the resource sliver for each the Resource Aggregates used in the Experiment. In the example experiment used in this page, the ProtoGENI sliver was deleted as follows: |
| | 410 | {{{ |
| | 411 | $ ./src/omni.py -a https://www.emulab.net/protogeni/xmlrpc/am deletesliver lnevers_slice |
| | 412 | INFO:omni:Loading config file omni_config |
| | 413 | INFO:omni:Using control framework pgeni |
| | 414 | Deleted sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lneversslice on unspecified_AM_URN at https://www.emulab.net/protogeni/xmlrpc/am |
| | 415 | }}} |
| | 416 | |
| | 417 | Also the Planetlab sliver was deleted as follows: |
| | 418 | {{{ |
| | 419 | $ ./src/omni.py -a http://www.planet-lab.org:12346 deletesliver lnevers_slice |
| | 420 | INFO:omni:Loading config file omni_config |
| | 421 | INFO:omni:Using control framework pgeni |
| | 422 | Deleted sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lneversslice on unspecified_AM_URN at http://www.planet-lab.org:12346 |
| | 423 | |
| | 424 | }}} |
| | 425 | |
| | 426 | |
| | 427 | ---- |
| | 428 | {{{ |
| | 429 | #!html |
| | 430 | <a href="mailto: help@geni.net">Email us</a> with any questions and feedback on this page! |
| | 431 | }}} |
