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

Timestamp:

10/20/12 18:08:38 (12 years ago)

Author:

Jeanne Ohren

Comment:

--

GIMIv1.1Tutorial/Slice

@@ -158 +158 @@
 
 === B.2.2 Omni ===
-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:
+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 (replace gimiXX with your username):
 
   ''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.
 This script will be installed and executed on the nodes by an execute service defined in the rspec as follows:
 {{{
-<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"/>
-}}}
-
-  ''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.
+<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"/>
+}}}
+
+  ''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.
+
+You can download an example rspec using the following command:
+{{{
+    wget -P ~/Tutorials/GIMI/gimiXX http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/gimi-tutorial.rspec
+}}}
+
+Change the slice name in the rspec using the following command (replace gimiXXslice with your slice name).
+{{{
+    sed -i -e 's/SLICENAME/gimiXXslice' ~/Tutorials/GIMI/gimiXX/gimi-tutorial.rspec
+}}}
 
   ''B.2.2.3'' Then the following commands have to be executed to set up and manage the slice with Omni:
   * Create the slice:
 {{{
-omni.py createslice johGimi09-tutorial
+omni.py createslice gimiXXslice
 }}}
   * Create the sliver:
 {{{
-omni.py -a eg-sm createsliver johGimi09-tutorial ~/Tutorials/GIMI/gimi09/gec15-tutorial-gimi09-nospec.rspec
-}}}
-  * Check the status of the sliver:
-{{{
-omni.py -a eg-sm sliverstatus johGimi09-tutorial 2>&1 | grep geni_status
-}}}
-  * Get the manifest of the sliver (to get the login information):
-{{{
-omni.py -a eg-sm listresources johGimi09-tutorial -o
+omni.py -a eg-sm createsliver gimiXXslice ~/Tutorials/GIMI/gimiXX/gimi-tutorial.rspec
+}}}
+  * Check the status of the sliver (you are waiting for all geni_status to show ''ready''):
+{{{
+omni.py -a eg-sm sliverstatus gimiXXslice 2>&1 | grep geni_status
+}}}
+  * Get the manifest of the sliver to get the login information (manifest will be saved to a file specified in the output):
+{{{
+omni.py -a eg-sm listresources gimiXXslice -o
 }}}
   * Delete the sliver:
 {{{
-omni.py -a eg-sm deletesliver johGimi09-tutorial
+omni.py -a eg-sm deletesliver gimiXXslice
 }}}