Changes between Version 127 and Version 128 of GIMIv1.0Tutorial

Timestamp:

07/06/12 22:04:54 (12 years ago)

Author:

zink@cs.umass.edu

Comment:

--

GIMIv1.0Tutorial

@@ -176 +176 @@
   * The node names will be automatically set to the correct names by a post boot script (defined in Flukes). The code snippet below shows the section of the post boot script that performs this step (for the case of node A) :
 {{{
-hostname nodeA
+hostname gimiXX-tutorial-nodeA
 }}}
   * The experiment name has to be set to the unique slice name of your ExoGENI request. This is already done in the post boot for this tutorial.
 
  * If you want to perform a measurement on a different slice, we here outline the steps to adapt the post boot script for that scenario.
-  * Change the post boot script option to add ''slice name'' as the ''experiment name''. Therefore change the existing experiment name "gec14-gimi01" in line five to the experiment that includes your account name. E.g., if your account name is "gimi05" the experiment name has to be changed to "gimi05-gec14"!!
+  * Change the post boot script option to add ''slice name'' as the ''experiment name''. Therefore change the existing experiment name "gec14-gimi01" in line five to the experiment that includes your account name. E.g., if your account name is "gimi05" the experiment name has to be changed to "gimi05-tutorial"!!
 {{{
 curl http://emmy8.casa.umass.edu/omf-resctl.yaml -o
 /etc/omf-resctl-5.4/omf-resctl.yaml
 
-perl -i.bak -pe "s/\:slice\:/\:slice\: gimi01-gec14/g"
+perl -i.bak -pe "s/\:slice\:/\:slice\: gimi05-tutorial/g"
 /etc/omf-resctl-5.4/omf-resctl.yaml
 }}}
@@ -197 +197 @@
 omf_create_psnode-5.4 "XMPP Server" mkslice "slice_name" "list_of_nodenames"
 
-E.g., omf_create_psnode-5.4 emmy9.casa.umass.edu mkslice gimiXX-gec14 nodeA nodeB nodeC
+E.g., omf_create_psnode-5.4 emmy9.casa.umass.edu mkslice gimiXX-tutorial nodeA nodeB nodeC
 }}}
 If this succeeds you should see an output similar to the one below
@@ -218 +218 @@
 }}}
 
-And you should see the following lines towards the end of the log file:
+And you should see the following as the last two lines of the log file:
 {{{
 2012-06-30 23:49:10 DEBUG nodeAgent::OMFPubSubTransport: Listening on '/OMF/dilip-testing/resources/nodeA' at 'emmy9.casa.umass.edu'
@@ -233 +233 @@
 
 The latest version of OML offers the capability of executing a script after the measurement has finished. In OML terminology this is called a "hook". The following shows the hook script we execute on the OML server which pushes measurement results into iRODS.
-
 {{{
 }}}
@@ -245 +244 @@
    1.5.3 We start the experiment running the following command from the user workspace terminal:
 {{{
-
-omf-5.4 exec --no-cmc -S "slice_name" "ED file name" -- --source1 "hostname" --sink "hostname"
+cd ~/Tutorials/GIMI/common/tcp_iperf.rb
+omf-5.4 exec --no-cmc -S <slice_name> <ED file name> -- --source1 <hostname> --sink <hostname>
 
 Eg., omf-5.4 exec --no-cmc -S gimiXX-gec14 tcp_iperf.rb -- --source1 nodeA --sink nodeC