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

07/02/13 12:37:55 (6 years ago)
Gary Wong

Add text to the execution page.


  • GENIExperimenter/Tutorials/PortalOmniExample/ExecuteExperiment

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