Changes between Version 1 and Version 2 of GENIExperimenter/Tutorials/PortalOmniExample/ExecuteExperiment

Timestamp:

07/02/13 12:37:55 (11 years ago)

Author:

Gary Wong

Comment:

Add text to the execution page.

GENIExperimenter/Tutorials/PortalOmniExample/ExecuteExperiment

@@ -13 +13 @@
              <ul>
                  <li><a href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/PortalOmniExample/SetupAccount">Step 1: Establish Management Environment: Setup your GENI account and join a GENI Project</a></li>
-                 <li><b><a href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources">Step 2: Obtain Resources: Create a slice and reserve resources</a></b></li>
+                 <li><a href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources">Step 2: Obtain Resources: Create a slice and reserve resources</a></li>
              </ul></ul>
                </td>
@@ -25 +25 @@
 <li>Part II: Execute</li>
              <ul> 
-                 <li><a href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ExecuteExperiment">Execute Experiment: Log in to nodes and monitor the experiment execution</a> </li>
+                 <li><b><a href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ExecuteExperiment">Execute Experiment: Log in to nodes and monitor the experiment execution</a></b></li>
              </ul></ul>
                 </td>
@@ -50 +50 @@
 = Instructions =
 
-FIXME
+Although the Omni {{{createsliver}}} client request has finished, the
+aggregate manager may still be busy in the background booting the
+requested nodes and bringing up network connections.  It is possible
+to use Omni manually to follow the AM's progress (with the
+"{{{omni sliverstatus}}}" command, which in turn uses the {{{SliverStatus}}}
+AM call), but instead we will demonstrate a higher-level tool which
+illustrates how custom scripts can make use of Omni to simplify
+common sequences of tasks into a single convenient command.
+
+The {{{readyToLogin.py}}} script will contact an AM, determine whether
+all requested resources at that AM are ready, and if so, display a summary
+of the hosts including their addresses and the proper SSH keys to use to
+access them.
+
+To run this script, please use the command:
 
 {{{
@@ -56 +70 @@
 }}}
 
-When it is ready, it will give login info in terminal.  Log in to client,
-look in
+If it reports that the sliver is not yet ready, then please wait a minute
+or two and try again.  Once everything is complete, {{{readyToLogin.py}}}
+will give output that should look something like this:
 
 {{{
-/tmp/iperf-logs/
+...
+server's geni_status is: ready (am_status:ready) 
+User example logs in to server using:
+        ssh -p 32768 -i /home/geni/.ssh/geni_key_portal example@pc1.utah.geniracks.net
+User example logs in to client using:
+        ssh -p 32769 -i /home/geni/.ssh/geni_key_portal example@pc1.utah.geniracks.net
+...
 }}}
+
+You can copy and paste the {{{ssh}}} command lines directly into your terminal
+to log in to either of your hosts.  While you're welcome to inspect either
+one, for the purpose of this experiment, the {{{client}}} host is the one
+running the {{{iperf}}} tests and collecting all the logs, so please use
+the {{{client}}} ssh command now.
+
+You may get a warning from {{{ssh}}} complaining that the authenticity of the
+host cannot be established.  This is just because your {{{ssh}}} client has
+never accessed this VM before, and so does not yet recognise its key.  Say
+"yes", you do want to continue connecting, and you should see a shell prompt
+from the remote end:
+{{{
+[example@client ~]$
+}}}
+
+The {{{install}}} and {{{execute}}} services requested in our rspec have
+already started, and measurements are now being collected.  (You can
+verify that things are working by inspecting the {{{/local}}} directory
+on each host, and looking for the approriate processes with a command like
+{{{ps ax}}}.  If you do not see the proper files and processes, please
+double-check the {{{rspec}}} you used in the previous step.)
+
+The client machine is saving all the test results in the {{{/tmp/iperf-logs}}}
+directory.  Files with timestamps in the names will gradually appear
+there (there are 100 tests overall, and it may take 20 minutes for all
+of them to complete if you want to wait for them).  
+
+Each log file corresponds to one test with some number of simultaneous
+TCP connections over the VLAN link you requested between the two hosts.
+Later tests gradually include more concurrent connections, so the
+throughput of each individual connection will decrease, but the
+aggregate throughput (the {{{[SUM]}}} line at the end of each file)
+should remain approximately consistent.
+
+For a real experiment, of course, this step would be the most imporant
+and collection, analysis and archival of the results would be critical,
+but for now, play around as necessary to satisfy your curiosity and
+then continue.
+
+= [wiki:GENIExperimenter/Tutorials/PortalOmniExample/TeardownExperiment Next: Finish] =