Changes between Version 67 and Version 68 of GENIExperimenter/Tutorials/HelloOmni
- Timestamp:
- 04/22/14 17:43:03 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/HelloOmni
v67 v68 76 76 4. '''See available resources'''. For this experiment we are going to use the Aggregate manager of ProtoGENI in Utah. In order to see what each AM offers you can use the `listresources` command. Type: 77 77 {{{ 78 omni.py listresources -a pg-utah-o78 omni.py listresources -a nysernet-ig -o 79 79 }}} 80 80 The `-o` option will save the output to a file. The filename is chosen by Omni and printed as part of the output. The output will look like : 81 81 {{{ 82 geni@geni-VirtualBox:~$ omni.py listresources -a pg-utah-o82 geni@geni-VirtualBox:~$ omni.py listresources -a nysernet-ig -o 83 83 INFO:omni:Loading config file /home/geni/.gcf/omni_config 84 84 INFO:omni:Using control framework pg 85 85 INFO:omni:Saving output to a file. 86 INFO:omni:Substituting AM nickname pg-utahwith URL https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0, URN unspecified_AM_URN86 INFO:omni:Substituting AM nickname nysernet-ig with URL https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0, URN unspecified_AM_URN 87 87 INFO:omni:Listed resources on 1 out of 1 possible aggregates. 88 88 INFO:omni:Writing to 'rspec-www-emulab-net-protogeniv2.xml' … … 91 91 92 92 Options as run: 93 aggregate: [' pg-utah']93 aggregate: ['nysernet-ig'] 94 94 framework: pg 95 95 output: True … … 104 104 In the last line of the output Omni will tell you the name of the file that output is saved at. In the example above this would be `rspec-www-emulab-net-protogeniv2.xml`. This file is a [wiki:GENIExperimenter/RSpecs Resource SPECification document(RSpec)], and in particular an advertisement rspec. Open the file that Omni saved and just take a look to see how an advertisement RSpec looks like. In order to see only available resources type: 105 105 {{{ 106 omni.py listresources -a pg-utah--available -o106 omni.py listresources -a nysernet-ig --available -o 107 107 }}} 108 108 5. '''Reserve resources'''. To be able to reserve resources you will need to craft a [wiki:GENIExperimenter/RSpecs request rspec]. For this example we have created the rspec and post it on the web for you to use. If you want to take a look to the rspec itself, you can directly visit the rspec URL. Type: 109 109 {{{ 110 omni.py createsliver -a pg-utah <slicename> http://www.gpolab.bbn.com/experiment-support/HelloGENI/hellogeni.rspec110 omni.py createsliver -a nysernet-ig <slicename> http://www.gpolab.bbn.com/exp/HelloGENI/hellogeni.rspec 111 111 }}} 112 112 6. '''See the reserved resources'''. You can use the `listresources` command, to see what resources are reserved at an Aggregate. 113 113 {{{ 114 omni.py listresources -a pg-utah<slicename>114 omni.py listresources -a nysernet-ig <slicename> 115 115 }}} 116 116 7. '''Optional- Extend the lifetime of your reservation'''. The lifetime of your reservation can never exceed the lifetime of your slice and is usually set to a default value. For the purpose of this exercise you don't need to renew your reservation. '''Note''' After reserving your resources, renewing your slice '''will not''' automatically renew your slivers, so you will have to manually renew them if you decide you need them longer. If you wanted to do this, the command would look like: 117 117 {{{ 118 omni.py renewsliver -a pg-utah<slicename> <YYYYMMDD>118 omni.py renewsliver -a nysernet-ig <slicename> <YYYYMMDD> 119 119 }}} 120 120 8. '''Check the status of your resources'''. Type: 121 121 {{{ 122 omni.py sliverstatus -a pg-utah<slicename>122 omni.py sliverstatus -a nysernet-ig <slicename> 123 123 }}} 124 124 The `sliverstatus` command reports the status of each individual resource that you reserved as well as the status of your overall GENI sliver. The status reported usually reflects the status of your resource, for example if you hav reserved a host, then status `ready` means that the host is booted and ready, i.e. you can login to it. When the status is `ready` for the whole sliver, in the summary of the output there will be something like: … … 139 139 <li> After the <code>sliverstatus</code> command tells you that your resources are ready, we should <b> visit the running webserver </b>. In order to do that we need to know which machine was assigned to be our <code>server</code> host. This information is part of the <code> sliverstatus </code> command but it is hard to locate. Omni comes with a script that makes it easy to gather all the information for accessing your hosts. In the terminal run: <br><br> 140 140 <center><code> 141 readyToLogin.py -a pg-utah<slicename>141 readyToLogin.py -a nysernet-ig <slicename> 142 142 </code> </center> 143 143 </li> … … 184 184 1. In the terminal, where you have been running your omni commands do: 185 185 {{{ 186 omni.py deletesliver -a pg-utah<slicename>186 omni.py deletesliver -a nysernet-ig <slicename> 187 187 }}}