| 1 | = Execute Experiment: Log in to nodes and monitor the experiment execution = |
| 2 | Introduction: [wiki:GENIExperimenter/Tutorials/PortalOmniExample Getting Started with GENI and the GENI Portal] |
| 3 | {{{ |
| 4 | #!html |
| 5 | <table id="Table_01" height="205" border="0" cellpadding="0" cellspacing="0"> |
| 6 | <tr> |
| 7 | <td> |
| 8 | <a href="http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_II/SetupAccount"><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/design.png?format=raw" width="76" height="76" alt="Design/Setup"></a> |
| 9 | </td> |
| 10 | <td> |
| 11 | <ul> |
| 12 | <li><b>Part I: Design/Setup</b></li> |
| 13 | <ul> |
| 14 | <li><a href="http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_II/SetupAccount">Step 1: Establish Management Environment: Setup your GENI account and join a GENI Project</a></li> |
| 15 | <li><a href="http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_II/ObtainResources">Step 2: Obtain Resources: Create a slice and reserve resources</a></li> |
| 16 | </ul></ul> |
| 17 | </td> |
| 18 | </tr> |
| 19 | <tr> |
| 20 | <td> |
| 21 | <a href="http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_II/ExecuteExperiment"><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/execute_on.png?format=raw" width="76" height="72" alt="Execute"></a> |
| 22 | </td> |
| 23 | <td> |
| 24 | <ul> |
| 25 | <li>Part II: Execute</li> |
| 26 | <ul> |
| 27 | <li><b><a href="http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_II/ExecuteExperiment">Execute Experiment: Log in to nodes and monitor the experiment execution</a></b></li> |
| 28 | </ul></ul> |
| 29 | </td> |
| 30 | </tr> |
| 31 | <tr> |
| 32 | <td> |
| 33 | <a href="http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_II/TeardownExperiment"><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/finish.png?format=raw" width="76" height="57" alt="Finish"></a> |
| 34 | </td> |
| 35 | |
| 36 | <td> |
| 37 | <ul> |
| 38 | <li>Part III: Finish</li> |
| 39 | <ul> |
| 40 | <li><a href="http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_II/TeardownExperiment">Teardown Experiment: Delete Resources</a></li> |
| 41 | </ul></ul> |
| 42 | </td> |
| 43 | |
| 44 | </tr> |
| 45 | </table> |
| 46 | |
| 47 | }}} |
| 48 | |
| 49 | |
| 50 | == 6.1 Wait for experiment setup == |
| 51 | |
| 52 | 1. Please use the command: |
| 53 | {{{ |
| 54 | readyToLogin.py --no-keys -a AM_NICKNAME SLICENAME |
| 55 | }}} |
| 56 | where (as before) {{{AM_NICKNAME}}} and {{{SLICENAME}}} are your aggregate |
| 57 | manager nickname and your slice name (both found on your worksheet). |
| 58 | |
| 59 | 2. 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 |
| 60 | or two and try again. Once everything is complete, {{{readyToLogin.py}}} |
| 61 | will give output that should look something like this: |
| 62 | |
| 63 | {{{ |
| 64 | ... |
| 65 | server's geni_status is: ready (am_status:ready) |
| 66 | User example logs in to server using: |
| 67 | ssh -p 32768 example@pc1.utah.geniracks.net |
| 68 | User example logs in to client using: |
| 69 | ssh -p 32769 example@pc1.utah.geniracks.net |
| 70 | ... |
| 71 | }}} |
| 72 | |
| 73 | {{{ |
| 74 | #!html |
| 75 | <table border="0" cellpadding="0" cellspacing="0"><tr><td><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/warning-icon-hi.png?format=raw" /></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 |
| 76 | not be set up to log in with above commands. Try re-running <tt>readyToLogin.py</tt> without the <tt>--no-keys</tt> option, and it will give you one or |
| 77 | more <tt>ssh</tt> commands to choose from (which should work, although might require the key passphrase).</td></tr></table> |
| 78 | }}} |
| 79 | |
| 80 | == 6.2 Log in to client node == |
| 81 | |
| 82 | 1. Copy and paste the {{{ssh}}} command lines directly into your terminal |
| 83 | to log in to either of your hosts. While you're welcome to inspect either |
| 84 | one, for the purpose of this experiment, the {{{client}}} host is the one |
| 85 | running the {{{iperf}}} tests and collecting all the logs, so please use |
| 86 | the {{{client}}} ssh command now. |
| 87 | |
| 88 | You may get a warning from {{{ssh}}} complaining that the authenticity of the |
| 89 | host cannot be established. This is just because your {{{ssh}}} client has |
| 90 | never accessed this VM before, and so does not yet recognise its key. Say |
| 91 | "yes", you do want to continue connecting, and you should see a shell prompt |
| 92 | from the remote end: |
| 93 | {{{ |
| 94 | [example@client ~]$ |
| 95 | }}} |
| 96 | |
| 97 | The {{{install}}} and {{{execute}}} services requested in our rspec have |
| 98 | already started, and measurements are now being collected. (You can |
| 99 | verify that things are working by inspecting the {{{/local}}} directory |
| 100 | on each host, and looking for the approriate processes with a command like |
| 101 | {{{ps ax}}}. If you do not see the proper files and processes, please |
| 102 | double-check the {{{rspec}}} you used in the previous step.) |
| 103 | |
| 104 | 2. The client machine is saving all the test results in the {{{/tmp/iperf-logs}}} |
| 105 | directory. Files with timestamps in the names will gradually appear |
| 106 | there (there are 100 tests overall, and it may take 20 minutes for all |
| 107 | of them to complete if you want to wait for them). |
| 108 | |
| 109 | Each log file corresponds to one test with some number of simultaneous |
| 110 | TCP connections over the VLAN link you requested between the two hosts. |
| 111 | Later tests gradually include more concurrent connections, so the |
| 112 | throughput of each individual connection will decrease, but the |
| 113 | aggregate throughput (the {{{[SUM]}}} line at the end of each file) |
| 114 | should remain approximately consistent. |
| 115 | |
| 116 | For a real experiment, of course, this step would be the most imporant |
| 117 | and collection, analysis and archival of the results would be critical, |
| 118 | but for now, play around as necessary to satisfy your curiosity and |
| 119 | then continue. |
| 120 | |
| 121 | = [wiki:GEC17Agenda/GettingStartedWithGENI_II/TeardownExperiment Next: Finish] = |