Changes between Version 67 and Version 68 of GENIExperimenter/Tutorials/HelloOmni

04/22/14 17:43:03 (10 years ago)



  • GENIExperimenter/Tutorials/HelloOmni

    v67 v68  
    7676  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:
    7777   {{{
    78 listresources -a pg-utah -o
     78 listresources -a nysernet-ig -o
    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:~$ listresources -a pg-utah -o
     82geni@geni-VirtualBox:~$ listresources -a nysernet-ig -o
    8383INFO:omni:Loading config file /home/geni/.gcf/omni_config
    8484INFO:omni:Using control framework pg
    8585INFO:omni:Saving output to a file.
    86 INFO:omni:Substituting AM nickname pg-utah with URL, URN unspecified_AM_URN
     86INFO:omni:Substituting AM nickname nysernet-ig with URL, URN unspecified_AM_URN
    8787INFO:omni:Listed resources on 1 out of 1 possible aggregates.
    8888INFO:omni:Writing to 'rspec-www-emulab-net-protogeniv2.xml'
    9292  Options as run:
    93                 aggregate: ['pg-utah']
     93                aggregate: ['nysernet-ig']
    9494                framework: pg
    9595                output: True
    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 listresources -a pg-utah --available -o
     106 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 createsliver -a pg-utah <slicename>
     110 createsliver -a nysernet-ig <slicename>
    111111  }}}
    112112  6. '''See the reserved resources'''. You can use the `listresources` command, to see what resources are reserved at an Aggregate.
    113113  {{{
    114 listresources -a pg-utah <slicename>
     114 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 renewsliver -a pg-utah <slicename> <YYYYMMDD> renewsliver -a nysernet-ig <slicename> <YYYYMMDD>
    119119  }}}
    120120  8. '''Check the status of your resources'''. Type:
    121121   {{{
    122 sliverstatus -a pg-utah <slicename>
     122 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 -a pg-utah &lt;slicename&gt -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 deletesliver -a  pg-utah <slicename> deletesliver -a  nysernet-ig <slicename>