Changes between Version 27 and Version 28 of GENIExperimenter/Tutorials/HelloOmni

11/15/12 14:21:26 (10 years ago)



  • GENIExperimenter/Tutorials/HelloOmni

    v27 v28  
    6262= 2. Launch your experiment =
    63 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.
     63Now that you have configured Omni we are ready to design our experiment, which going over most of the Omni commands.
    6565  1. '''Create a slice'''. The first thing to do when preparing to run a GENI experiment is to create a slice. Name your slice something like '''xxxomni''' (where xxx are your initials). Type
    109109  5. '''Reserve resources'''. To be able to reserve resources you will need to craft a [wiki:GENIExperimenter/RSpecs request rspec]. For this example we have created the rspec and made it available for you to use. Type:
    110110  {{{
    111 createsliver -a pg-utah <slicename>
     111 createsliver -a pg-utah <slicename>
    112112  }}}
    113113  6. '''See the reserved resources'''. You can use the `listresources` command, to see what resources are reserved at an Aggregate.
    125125  The `sliverstatus` command reports the status of your overall GENI slice. When the status is ready we are ready to continue to the next step.
    127 = 3. View results =
    128 Now that resources are ready we can start running our experiment. We will first start by logging in to our reserved nodes.
     127= 3. View your results =
     128For this example experiment we used the install script facility to automatically install the necessary software and kick-off the experiment. In this very simple setup, we have installed and launched a [ web server] as well as an [ iperf server], on the server host. On the client, we have started some processes to test both of these
     129services. To view the results of this experiment:
    134135      <tr>
    135        <td>
    136 <img border="0" src="" alt="readyToLogin snapshot"  height="120" title="readyToLogin snapshot" /> 
     136         <td>
     137         <img border="0" src="" alt="Hello GENI index"  height="90" title="Hello GENI Web server" /> 
    137138       </td>
    138139       <td >
    139140         <ol>
    140             <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>
    141     <code>
    142 -a pg-utah &lt;slicename&gt
    143 </code>   <br> The script will return the actual command that you would need to use for logging in. Login to both nodes by copy-paste the commands from the output of the script.
    144             </li>
    145           </ol>
     141            <li> After the background of your slice turns green, press the (i) button that is on the server node icon.</li>
     142            <li> In the information tab that came up, <b>press the Visit</b> button. A new tab should come up that looks like the picture on the side. </li>
     143            <li> Click the <b>webserver statistics</b> link to look at statistics. Refresh the page a couple of times to see how the statistics change as the client requests documents.</li>
     144            <li> Click the <b>iperf logs</b> link to see the statistics from the iperf transfers.</li>
     145           </ol>
    146147       </td>
    147148    </tr>
    148149 </table>
    152   2. '''Send IP traffic''' The first simple experiment that we will run is to verify the IP connectivity between our hosts.
    153     i. Check the interfaces of your nodes. In the terminal type:
    154     {{{
    155    /sbin/ifconfig
    156   }}}
    157     You should see at least two interfaces:
    158       * The '''control interface'''. This is the interface from where you access the node, e.g. ssh into your host. The control interface is mainly used for control traffic, i.e. traffic for controlling the node and the experiment. The control interface usually has a publicly routable IP.
    159       * The '''data interface'''. This is the interface that is used for sending experimental traffic. This is the interface that connects to the other hosts of your experiment through GENI. The links between these interfaces are the ones that allow you to run non-IP experiments.
    160     i. Note the name and the MAC address of the control and of the data interface for each node. The data interface is the one that has an IP that starts with 10.
    161     i. From the client ping the server. From the xterm that is logged in to the client type :
    162     {{{
    163     ping server -c 5
    164   }}}
    165     '''Note''': You can use the name that is assigned to the host to directly ping the host, you can also ping using the IP of the data interface of the node.  An example output should look like :
    166     {{{
    167 [[inki@r2 ~]$ ping server -c 5
    168 PING ( 56(84) bytes of data.
    169 64 bytes from icmp_seq=1 ttl=64 time=1.95 ms
    170 64 bytes from icmp_seq=2 ttl=64 time=2.27 ms
    171 64 bytes from icmp_seq=3 ttl=64 time=2.04 ms
    172 64 bytes from icmp_seq=4 ttl=64 time=1.95 ms
    173 64 bytes from icmp_seq=5 ttl=64 time=1.72 ms
    175 --- ping statistics ---
    176 5 packets transmitted, 5 received, 0% packet loss, time 4005ms
    177 rtt min/avg/max/mdev = 1.728/1.992/2.278/0.179 ms
    178 }}}
    180   3. '''Send non-IP traffic'''. GENI provides the capability of running non-IP experiments, since you can connect your hosts at Layer 2. For the purpose of this tutorial we have installed in all the hosts a very simple Layer 2 ping program that sends packets using a custom ethernet type.
    181     i. Disable the IP in your nodes. First of all we are going to completely disable IP on our nodes. In each of the terminals type:
    182     {{{
    183   sudo /sbin/ifconfig <data i/f name>
    184   }}}
    185     '''Note''': Be extra careful to bring down the IP on the data interface, bringing down the IP on the control interface means that you will lose connectivity to your host.
    186     i. Try again to ping from the client to the server. In the xterm of the client type:
    187     {{{
    188   ping server -c 5
    189   }}}
    190     This time the ping should timeout.
    191     i. Start the Layer 2 ping server: In the server xterm, type:
    192     {{{
    193   sudo /usr/local/bin/pingPlusListener 12345
    194   }}}
    195     i. From the client try to ping the server at layer 2. You will need the mac address of the data interface of the server and the name of the data interface of the client. In the xterm of the client, type:
    196     {{{
    197   sudo /usr/local/bin/pingPlus <server data mac addr> <client data i/f name> 12345
    198   }}}
    199     The result should look like :
    200     {{{
    201 [uncusr20@client ~]$ sudo /usr/local/bin/pingPlus 02:00:9B:48:3E:20 mv1.1 12345
    202 RQ:'5582+2067' to 2:0:9b:48:3e:20.
    203 RQ:5582+2067 from 2:0:3e:15:6c:ab.
    204 }}}
    206 Congratulations you have run a Layer 2 experiment in GENI!
    208152= 4. Cleanup  =