Changes between Initial Version and Version 1 of GeniTmixTutorialOmni

03/01/13 13:41:56 (9 years ago)
Ben Newton



  • GeniTmixTutorialOmni

    v1 v1  
     1[[PageOutline(2-3, Table of Contents)]]
     3= Using Tmix on GENI =
     5This page describes how to run experiments with [wiki:GeniTmix Tmix] on GENI nodes.  This tutorial assumes that you are already familiar with basic experimentation with GENI, and that you have access to some version of Linux/Unix running on a PC or virtual machine.  We also assume basic familiarity with Linux/Unix.
     8== 1 Install Omni ==
     9This tutorial will use Omni, which is a command line interface tool for reserving GENI resources.  If you do not already have Omni installed and set up, please follow Step 1 (Configuring Omni with your GENI Account) [wiki:GENIExperimenter/Tutorials/HelloOmni here].  Please note, it may take 30-45 minutes to get Omni installed and configured.  Also note when installing Omni, the ./ script may need to be run from your gcf/src directory, and you may need to create the .ssl subdirectory in your home directory. 
     11== 2 Extra Omni Configuration ==
     12=== 2.1 Add gcf/src to path (optional but recommended) ===
     13Although optional, it will be helpful to add the gcf/src directory to your path and python path.  To do this, replace "/path/to/gcf" in the lines below with the path to your copy of gcf, and add the lines to the end of your .profile file or equivalent.   
     16export PYTHONPATH="/path/to/gcf/src:$PATH"
     19Once you have added the lines and saved the file, run
     21source .profile
     23to setup the path environment variables for this session. This will be done automatically from now on.   
     25If you don't make this change, you may need to add python in front of all the omni commands, and call them from within the gcf/src directory.
     27=== 2.2 Clear Passphrases (optional but recommended) ===
     28We recommend that you clear the passphrase from your SSL certificate and/or your SSH key that you will use to login to your nodes.  This step is also optional, however, if you don't clear your passphrases some commands will require you to enter your it several times, which can become burdensome.  To clear the passphrases from your certificate and key run this script:
     35== 3 A Simple Tmix Experiment ==
     37=== 3.1 Reserve Resources ===
     38The following is the request rspec for a simple two node network.  It requests two raw nodes named left and right, each with a single interface named left:if0 and right:if0 respectively. A link named left-right-lan connects these interfaces.
     40<rspec type="request"
     41    xmlns=""
     42    xmlns:flack=""
     43    xmlns:xsi=""
     44    xmlns:client=""
     45    xsi:schemaLocation="
     47  <node client_id="left" component_manager_id="" exclusive="true">
     48    <sliver_type name="raw-pc">
     49      <disk_image name=""/> 
     50    </sliver_type>
     51    <services>
     52        <execute command="/local/" shell="sh"/>     
     53        <install install_path="/local" url=""/>
     54    </services>
     55    <interface client_id="left:if0">
     56      <ip address="" netmask="" type=""/>
     57    </interface>
     58  </node>
     59  <node client_id="right" component_manager_id="" exclusive="true">
     60    <sliver_type name="raw-pc">
     61      <disk_image name=""/>
     62    </sliver_type>
     63    <services>
     65        <execute command="/local/" shell="sh"/>     
     66        <install install_path="/local" url=""/>
     67    </services>
     68    <interface client_id="right:if0">
     69      <ip address="" netmask="" type=""/>
     70    </interface>
     71  </node>
     72  <link client_id="left-right-lan">
     73    <component_manager name=""/>
     74    <interface_ref client_id="left:if0"/>
     75    <interface_ref client_id="right:if0"/>
     76    <property source_id="left:if0" dest_id="right:if0"/>
     77    <property source_id="right:if0" dest_id="left:if0"/>
     78    <link_type name="lan"/>
     79  </link>
     83Think of a unique name for your slice.  We recommend the slice name begin with your GENI username. 
     84Create a new slice by issuing the following command with your unique slice name in place of <sliceName>.
     85{{{ createslice <sliceName>
     88Next, create a sliver with the resources requested in the rspec by issuing the following command where <sliceName> is again replaced with the unique slice name you have chosen. 
     89{{{ -a pg-utah <sliceName> two-nodes-tmix.rspec
     92Note: this and future steps assume your ~/.gcf/omni_config includes a mapping from nickname pg-utah to If pg-utah causes issues, you can use the full url in the -a option.
     94If the resources were successfully reserved the {{{Result Summary}}} from Omni should say: Got Reserved resources ...
     95If there was an error you will see something like "Failed CreateSliver".
     97Look back further in the output and you should see two lines which include "hostname=pc???".  These are the hostnames of the machines reserved for your experiment.  Make note of these hostnames for later use.   
     99In addition to listing desired resources, the rspec also specifies a script to be run at boot time on the host.  This script configures the host for Tmix.