Changes between Version 56 and Version 57 of GIMIv1.1Tutorial/Slice


Ignore:
Timestamp:
10/20/12 18:08:38 (7 years ago)
Author:
Jeanne Ohren
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GIMIv1.1Tutorial/Slice

    v56 v57  
    158158
    159159=== B.2.2 Omni ===
    160 In this section, we present an alternative approach to setup a slice by using the Omni command line tools to reserve resources. To perform this task the following steps have to be executed:
     160In this section, we present an alternative approach to setup a slice by using the Omni command line tools to reserve resources. To perform this task the following steps have to be executed (replace gimiXX with your username):
    161161
    162162  ''B.2.2.1'' The post boot script that is used in the case of slice reservation via Flukes has to be converted from an RDF file into a single bash script that takes slice name and node ID as arguments.
    163163This script will be installed and executed on the nodes by an execute service defined in the rspec as follows:
    164164{{{
    165 <execute command="wget -q -P /tmp http://pc205.emulab.net/gimi/gec15-postboot.sh ;chmod +x /tmp/gec15-postboot.sh;/tmp/gec15-postboot.sh johGimi09-both nodeA > /tmp/gec15-postboot.log" shell="/bin/sh"/>
    166 }}}
    167 
    168   ''B.2.2.2'' The rdf file has to be converted into an rspec (see attached gec15-tutorial-gimi09-nospec.rspec). You will notice that the rspec has to be slice-specific because it needs to pass the slice name into the post boot script.
     165<execute command="wget -q -P /tmp http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/gec15-postboot.sh ;chmod +x /tmp/gec15-postboot.sh;/tmp/gec15-postboot.sh <slicename> nodeA > /tmp/gec15-postboot.log" shell="/bin/sh"/>
     166}}}
     167
     168  ''B.2.2.2'' The rdf file has to be converted into an rspec. You will notice that the rspec has to be slice-specific because it needs to pass the slice name into the post boot script.
     169
     170You can download an example rspec using the following command:
     171{{{
     172    wget -P ~/Tutorials/GIMI/gimiXX http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/gimi-tutorial.rspec
     173}}}
     174
     175Change the slice name in the rspec using the following command (replace gimiXXslice with your slice name).
     176{{{
     177    sed -i -e 's/SLICENAME/gimiXXslice' ~/Tutorials/GIMI/gimiXX/gimi-tutorial.rspec
     178}}}
    169179
    170180  ''B.2.2.3'' Then the following commands have to be executed to set up and manage the slice with Omni:
    171181  * Create the slice:
    172182{{{
    173 omni.py createslice johGimi09-tutorial
     183omni.py createslice gimiXXslice
    174184}}}
    175185  * Create the sliver:
    176186{{{
    177 omni.py -a eg-sm createsliver johGimi09-tutorial ~/Tutorials/GIMI/gimi09/gec15-tutorial-gimi09-nospec.rspec
    178 }}}
    179   * Check the status of the sliver:
    180 {{{
    181 omni.py -a eg-sm sliverstatus johGimi09-tutorial 2>&1 | grep geni_status
    182 }}}
    183   * Get the manifest of the sliver (to get the login information):
    184 {{{
    185 omni.py -a eg-sm listresources johGimi09-tutorial -o
     187omni.py -a eg-sm createsliver gimiXXslice ~/Tutorials/GIMI/gimiXX/gimi-tutorial.rspec
     188}}}
     189  * Check the status of the sliver (you are waiting for all geni_status to show ''ready''):
     190{{{
     191omni.py -a eg-sm sliverstatus gimiXXslice 2>&1 | grep geni_status
     192}}}
     193  * Get the manifest of the sliver to get the login information (manifest will be saved to a file specified in the output):
     194{{{
     195omni.py -a eg-sm listresources gimiXXslice -o
    186196}}}
    187197  * Delete the sliver:
    188198{{{
    189 omni.py -a eg-sm deletesliver johGimi09-tutorial
     199omni.py -a eg-sm deletesliver gimiXXslice
    190200}}}
    191201