Changes between Initial Version and Version 1 of GENIExperimenter/Tutorials/GettingStarted_PartII_ccn/Procedure/Execute

06/18/14 18:12:54 (7 years ago)
Vic Thomas



  • GENIExperimenter/Tutorials/GettingStarted_PartII_ccn/Procedure/Execute

    v1 v1  
     1= [  Understanding the AM API using Content Centric Networking] =
     5<div style="text-align:center; width:495px; margin-left:auto; margin-right:auto;">
     6<img id="Image-Maps_5201305222028436" src="" usemap="#Image-Maps_5201305222028436" border="0" width="495" height="138" alt="" />
     7<map id="_Image-Maps_5201305222028436" name="Image-Maps_5201305222028436">
     8<area shape="rect" coords="18,18,135,110" href="./DesignSetup" alt="" title=""    />
     9<area shape="rect" coords="180,18,297,111" href="./Execute" alt="" title=""    />
     10<area shape="rect" coords="344,17,460,110" href="./Finish" alt="" title=""    />
     11<area shape="rect" coords="493,136,495,138" href="" alt="Image Map" title="Image Map" />
     13<!-- Image map text links - End - -->
     18== 4 Wait for experiment setup ==
     20You can tell whether your nodes are ''ready'' by using a script built on `omni` called `readyToLogin`.
     24<ol type='a'>
     25  <li>
     26    Please use the command:
     28readyToLogin --no-keys -a AM_NICKNAME SLICENAME
     30where (as before) <tt>AM_NICKNAME</tt> and <tt>SLICENAME</tt> are your aggregate
     31manager nickname and your slice name (both found on your worksheet).
     32  </li>
     33  <li>If it reports that the sliver is not yet ready (for example, it might say that the status is "changing"), then please wait a minute
     34or two and try again.  Once everything is complete, <tt>readyToLogin</tt>
     35will give output that should look something like this:
     38server's geni_status is: ready (am_status:ready)
     39User example logs in to server using:
     40        ssh -p 32768
     41User example logs in to client using:
     42        ssh -p 32769
     46<table border="0" cellpadding="0" cellspacing="0"><tr><td><img src="" width='50' height='50' /></td><td>If you didn't previously complete the Flack tutorial (or are not running an <tt>ssh</tt> agent), then your <tt>ssh</tt> client might
     47not be set up to log in with above commands.  Try re-running <tt>readyToLogin</tt> without the <tt>--no-keys</tt> option, and it will give you one or
     48more <tt>ssh</tt> commands to choose from (which should work, although might require the key passphrase).</td></tr></table>
     50  </li>
     54== 5 Browse server webpage and log in to client node ==
     56The `install` and `execute` services requested in our RSpec have
     57already started, and the apache webserver has started on the server and measurements are now being collected.
     63<ol type='a'>
     65Enter the hostname of the server node in your browser.  It should bring up a webpage of statistics from your experiment similar to that shown in the figure.
     69        <td>
     70        <img
     71      src=""
     72      alt="Enter the hostname in your browser to see statistics"  width="300"
     73      title="Enter the hostname in your browser to see statistics" /> </a>
     74         <br/>
     75         <b>Figure 5-1</b> Enter the hostname of the <i>server</i> node in your browser to see statistics</i>
     76       </td>
     82<ol type='a' start='2'>
     83  <li>Find the <code>ssh</code> commands for your client in your <code>readyToLogin</code> output.  Copy and paste those <code>ssh</code> commands directly into your terminal
     84to log in.  You should see a shell prompt
     85from the remote end:
     87     [example@client ~]$
     90<table id="Table_01" border="0" cellpadding="5" cellspacing="0">
     91        <tr>
     92                <td>
     93                        <img src="" width="50" height="50" alt="Note">
     94               </td>
     96While you're welcome to inspect either
     97the client or server, for the purpose of this experiment the <tt>client</tt> host is the one
     98running the <tt>iperf</tt> tests and collecting all the logs.
     100        </tr>
     105Look in the <code>/local</code> directory to see the install scripts and other files from the Archive you specified in your RSpec:
     107cd /local
     112Look for the <code>iperf</code> and <code>wget</code> processes started by your install scripts:
     114ps ax
     117<table id="Table_03" border="0" cellpadding="5" cellspacing="0">
     118        <tr>
     119                <td>
     120                        <img src="" width="50" height="50" alt="Tip">
     121               </td>
     122               <td>
     123If you do not see the proper files and processes, please double-check the <code>RSpec</code> you used in the previous step.
     124        </tr>
     129       </td>
     131      </tr>
     139The client machine is saving all the test results in the `/tmp/iperf-logs`
     140directory.  Files with timestamps in the names will gradually appear
     141there (there are 100 tests overall, and it may take 20 minutes for all
     142of them to complete if you want to wait for them). 
     144Each log file corresponds to one test with some number of simultaneous
     145TCP connections over the VLAN link you requested between the two hosts.
     146Later tests gradually include more concurrent connections, so the
     147throughput of each individual connection will decrease, but the
     148aggregate throughput (the `[SUM]` line at the end of each file)
     149should remain approximately consistent.
     153== 6.  Analyze Experiment ==
     155For a real experiment, of course, this step would be the most important
     156and collection, analysis and archival of the results would be critical,
     157but for now, play around as necessary to satisfy your curiosity and
     158then continue.
     162= [wiki:GENIEducation/SampleAssignments/UnderstandAMAPI/Procedure Introduction] =
     163= [wiki:GENIEducation/SampleAssignments/UnderstandAMAPI/Procedure/Finish Next:  Finish] =