Changes between Version 71 and Version 72 of GENIExperimenter/Tutorials/HelloOmni


Ignore:
Timestamp:
05/16/14 13:50:36 (10 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/Tutorials/HelloOmni

    v71 v72  
    6363  1. '''Create a slice'''. The first thing to do when preparing to run a GENI experiment is to create a slice. Name your slice something like '''xxxomni''' (where xxx are your initials). Your slicename in general should be something memorable but '''not''' your username. Type:
    6464  {{{
    65   omni.py createslice <slicename>
     65  omni createslice <slicename>
    6666  }}}
    6767  2. '''Verify that your slice was created'''. Use the `listmyslices` command, of omni:
    6868  {{{
    69   omni.py listmyslices <username>
     69  omni listmyslices <username>
    7070  }}}
    7171  3. '''Renew your slice'''. To extend the lifetime of your slice. Type:
    7272  {{{
    73   omni.py renewslice <slicename> <YYYYMMDD>
     73  omni renewslice <slicename> <YYYYMMDD>
    7474  }}}
    7575  The slice lifetime is typically short and when your slice expires, all reserved resources at the time are also released. '''Note''': your resources might have a shorter lifetime than your slice.
    7676  4. '''See available resources'''.  For this experiment we are going to use the Aggregate manager at NYSERNet.  In order to see what each AM offers you can use the `listresources` command. Type:
    7777   {{{
    78  omni.py listresources -a nysernet-ig -o
     78 omni listresources -a nysernet-ig -o
    7979}}}
    8080   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 :
    8181   {{{
    82 geni@geni-VirtualBox:~$ omni.py listresources -a nysernet-ig -o
     82geni@geni-VirtualBox:~$ omni listresources -a nysernet-ig -o
    8383INFO:omni:Loading config file /home/geni/.gcf/omni_config
    8484INFO:omni:Using control framework pg
    … …  
    104104  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:
    105105  {{{
    106   omni.py listresources -a nysernet-ig --available -o
     106  omni listresources -a nysernet-ig --available -o
    107107  }}}
    108108  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:
    109109  {{{
    110     omni.py createsliver -a nysernet-ig <slicename> http://www.gpolab.bbn.com/exp/HelloGENI/hellogeni.rspec
     110    omni createsliver -a nysernet-ig <slicename> http://www.gpolab.bbn.com/exp/HelloGENI/hellogeni.rspec
    111111  }}}
    112112  6. '''See the reserved resources'''. You can use the `listresources` command, to see what resources are reserved at an Aggregate.
    113113  {{{
    114    omni.py listresources -a nysernet-ig <slicename>
     114   omni listresources -a nysernet-ig <slicename>
    115115  }}}
    116116  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:
    117117   {{{
    118 omni.py renewsliver -a nysernet-ig <slicename> <YYYYMMDD>
     118omni renewsliver -a nysernet-ig <slicename> <YYYYMMDD>
    119119  }}}
    120120  8. '''Check the status of your resources'''. Type:
    121121   {{{
    122   omni.py sliverstatus -a nysernet-ig <slicename>
     122  omni sliverstatus -a nysernet-ig <slicename>
    123123  }}}
    124124  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:
    … …  
    139139              <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>
    140140    <center><code>
    141 readyToLogin.py -a nysernet-ig &lt;slicename&gt
     141readyToLogin -a nysernet-ig &lt;slicename&gt
    142142</code> </center>
    143143            </li>
    … …  
    184184  1. In the terminal, where you have been running your omni commands do:
    185185  {{{
    186 omni.py deletesliver -a  nysernet-ig <slicename>
     186omni deletesliver -a  nysernet-ig <slicename>
    187187}}}