Changes between Version 20 and Version 21 of GENIExperimenter/Tutorials/HelloOmni

Timestamp:

11/15/12 12:18:09 (11 years ago)

Author:

nriga@bbn.com

Comment:

--

GENIExperimenter/Tutorials/HelloOmni

@@ -60 +60 @@
    Another interesting section to look at is the `[aggregate-nicknames]` sections. Flack already knows the URL for all the AMs and present you a list of AMs to choose from using a short, descriptive name. In Omni a user is required to pass the URL for each call to the GENI AM API. In this section the user gets a chance to provide short descriptive names to the URLs that are easier to memorize and use. 
 
-= 2. Launch your experiment = 
+= 2. Setup your experiment = 
 In this step we are going to setup a simplet Layer 2 GENI experiment, in order to get familiarized with most of the Omni commands. 
 
@@ -127 +127 @@
 = 3. Run your experiment =
 Now that resources are ready we can start running our experiment. We will first start by logging in to our reserved nodes. 
+
+{{{
+#!html
+<table border="0">
+   
+      <tr>
+       <td> 
+
+<img border="0" src="http://groups.geni.net/geni/attachment/wiki/Tutorials/Graphics/readytologin_output.png" alt="readyToLogin snapshot"  height="120" title="readyToLogin snapshot" />  
+       </td>
+       <td >
+         <ol>
+            <li><b>'Login to your nodes - Omni Scripting</b>. Depending on the Aggregate the login information are either part of the <code>sliverstatus</code> call, or as part of the manifest rspec, i.e. returned from the <code>listresources</code> call. Omni comes with a script that makes it easy to gather all this information.  In the terminal run: <br>
+    <code>
+readyToLogin.py -a pg-utah <slicename>
+</code>
+            </li>
+          </ol>
+       </td>
+ 
+    </tr>
+ </table>
+}}}
 
   1. '''Login to your nodes - Omni Scripting'''. Depending on the Aggregate the login information are either part of the `sliverstatus` call, or as part of the manifest rspec, i.e. returned from the