Changes between Version 5 and Version 6 of GENIExperimenter/Tutorials/RunHelloOmni


Ignore:
Timestamp:
02/02/15 11:16:43 (5 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/RunHelloOmni

    v5 v6  
    107107  <li><b>Create a slice</b>. The first thing to do when preparing to run a GENI experiment is to create a slice. Name your slice something like <b>xxxomni</b> (where xxx are your initials). Your slicename in general should be something memorable but <b>not</b> your username. Type:<br>
    108108  <code>
    109   omni.py createslice &lt slicename &gt
     109  omni createslice &lt slicename &gt
    110110  </code><br>
    111111  </li>
    112112  <li><b>Verify that your slice was created</b>. Use the <code>listmyslices</code> command, of omni: <br>
    113113  <code>
    114   omni.py listmyslices &lt username &gt
     114  omni listmyslices &lt username &gt
    115115  </code> </li>
    116116   <li><b>Renew your slice</b>. To extend the lifetime of your slice. Type:<br>
    117117   <code>
    118   omni.py renewslice &lt slicename &gt &lt YYYYMMDD &gt
     118  omni renewslice &lt slicename &gt &lt YYYYMMDD &gt
    119119    </code> <br>
    120120  The slice lifetime is typically short and when your slice expires, all reserved resources at the time are also released. <b>Note</b>: your resources might have a shorter lifetime than your slice.
     
    123123  <li><b> See available resources.</b> For this experiment we are going to use the Aggregate manager of Nysernet.  In order to see what each AM offers you can use the <code>listresources</code> command. Type:<br>
    124124   <code>
    125  omni.py listresources -a nysernet-ig -o
     125 omni listresources -a nysernet-ig -o
    126126 </code><br>
    127127   The <code>-o</code> 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 : <br>
    128128   <code>
    129 geni@geni-VirtualBox:~$ omni.py listresources -a nysernet-ig -o<br>
     129geni@geni-VirtualBox:~$ omni listresources -a nysernet-ig -o<br>
    13013020:13:35 INFO    : Loading agg_nick_cache file '/home/rrhain/.gcf/agg_nick_cache'<br>
    13113120:13:35 INFO    : Loading config file '/home/rrhain/.gcf/omni_config'<br>
     
    158158  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 <code>rspec-instageni-nysernet-org.xml</code>. This file is a <a href="http://groups.geni.net/geni/wiki/GENIExperimenter/RSpecs" target="_blank">  SPECification document(RSpec) </a>, 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:<br>
    159159  <code>
    160   omni.py listresources -a nysernet-ig --available -o
    161   </code></li>
    162   <li><b>Reserve resources</b> To be able to reserve resources you will need to craft a <a href="http://groups.geni.net/geni/wiki/GENIExperimenter/RSpecs" target="_blank">  request rspec</a>. For this example we have created the rspec and posted it on the web for you to use. If you want you can  view this Rspec at <a href;"http://www.gpolab.bbn.com/experiment-support/HelloGENI/hellogeni.rspec" this URL>. Type:<br>
    163   <code>
    164     omni.py createsliver -a nysernet-ig &lt slicename &gt http://www.gpolab.bbn.com/experiment-support/HelloGENI/hellogeni.rspec
     160  omni listresources -a nysernet-ig --available -o
     161  </code></li>
     162  <li><b>Reserve resources</b> To be able to reserve resources you will need to craft a <a href="http://groups.geni.net/geni/wiki/GENIExperimenter/RSpecs" target="_blank">  request rspec</a>. For this example we have created the rspec and posted it on the web for you to use. If you want you can  view this Rspec <a href="http://www.gpolab.bbn.com/experiment-support/HelloGENI/hellogeni.rspec" target="_blank"> here </a>. Type:<br>
     163  <code>
     164    omni createsliver -a nysernet-ig &lt slicename &gt http://www.gpolab.bbn.com/experiment-support/HelloGENI/hellogeni.rspec
    165165  </code></li>
    166166  <li><b>See the reserved resources</b>. You can use the <code>listresources</code> command, to see what resources are reserved at an Aggregate. <br>
    167167  <code>
    168    omni.py listresources -a nysernet-ig &lt slicename &gt
     168   omni listresources -a nysernet-ig &lt slicename &gt
    169169  </code></li>
    170170  <li><b>Optional- Extend the lifetime of your reservation</b>.  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. <b>Note</b> After reserving your resources, renewing your slice <b>will not</b> 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:<br>
    171171   <code>
    172 omni.py renewsliver -a nysernet-ig &lt slicename &gt  &lt YYYYMMDD &gt
     172omni renewsliver -a nysernet-ig &lt slicename &gt  &lt YYYYMMDD &gt
    173173  </code></li>
    174174<li><b>Check the status of your resources</b>. Type:<br>
    175175
    176176   <code>
    177   omni.py sliverstatus -a nysernet-ig  &lt slicename &gt
     177  omni sliverstatus -a nysernet-ig  &lt slicename &gt
    178178  </code><br>
    179179  The <code>sliverstatus</code> 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 <code>ready</code> means that the host is booted and ready, i.e. you can login to it. When the status is <code>ready</code> for the whole sliver, in the summary of the output there will be something like: