Changes between Initial Version and Version 1 of GeniTmixCalibTutorial


Ignore:
Timestamp:
06/19/14 12:24:33 (10 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixCalibTutorial

    v1 v1  
     1[[PageOutline(2-3, Table of Contents)]]
     2
     3= Using Tmix on GENI =
     4
     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 a machine from which you can execute ssh commands and login to external machines.  If you wish to reserve resources using omni, some version of Linux or Unix running on a PC or virtual machine is required.  The tutorial also assumes basic familiarity with Linux or Unix.
     6
     7
     8== 1 Reserve Resources in Omni or GENI Portal ==
     9Determine whether you wish to use Omni or GENI Portal to reserve GENI resources for this Tutorial.  We recommend you use GENI Portal, unless you are experienced with, or wish to gain experience with Omni.  Click one of the links below that matches your choice.
     10
     11[wiki:GeniTmixTutorialPortal Reserve Resources using GENI Portal]
     12
     13[wiki:GeniTmixTutorialOmni Reserve Resources using Omni]
     14
     15== 2 Login to nodes ==
     16We suggest you now open two new terminal windows, one for each node. 
     17To log into the nodes reserved in the previous step issue the following command for each node in one of the new windows. 
     18{{{
     19ssh -i ~/.ssh/id_geni_ssh_rsa <username>@<hostname> -p <port>
     20}}}
     21As expected, <username> should be replaced with your GENI username, and <hostname> and <port> are replaced with the hostname and port of the reserved Geni resource noted in the previous step. 
     22
     23== 3 Run Tmix ==
     24The image loaded on the nodes has the tmix tools already installed and in your path.  Also, while booting the first time, a script has generated a set of tmix configuration files for these nodes.  Each time the system boots, a kernel module is automatically inserted to assist in simulating the packet delays.  List the contents of your home directory.
     25{{{
     26ls
     27}}}
     28You should see a tmix.conf file, which contains the configuration for the tmix experiment.  Feel free to open the file and browse its contents. 
     29
     30Tmix relies upon a pre-determined start time to synchronize tmix on the two nodes.  On both nodes run the following command to determine the time and date:
     31{{{
     32date
     33}}}
     34Note that the time may be in a different time zone. 
     35Decide on a start time about 2-3 minutes in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes with 30 seconds to spare before that start time.
     36
     37Finally, execute the following command on both nodes:
     38{{{
     39tmix -s HH:MM:SS tmix.conf &
     40}}}
     41where HH:MM:SS is the chosen start time in hours minutes and seconds. 
     42
     43Tmix on both hosts will load the data files and then wait until the designated start time. 
     44You will see "Running for ???? seconds" once tmix is ready to go. 
     45
     46To verify when tmix has started run
     47{{{
     48top
     49}}}
     50You should see tmix at the top of the list once it starts.  To exit top type 'q'.
     51
     52After about 12 minutes, the experiment will complete, and a list of statistics will be output to the console.  Also a set of log files with extentions .ert, .trt, .unc, .rt, and .ts will be created in the directory. 
     53
     54== 4 Delete Resources ==
     55Once your experiment is complete and you have collected your results, you should return the reserved resources.  To do so, follow the step below which matches your choice to use GENI Portal or Omni.
     56=== 4.1 Using GENI Portal ===
     571.  '''Click on slices''' in the upper right-hand corner. 
     58
     592.  Find your slice in the list, and click on the corresponding '''Delete Resources''' button.
     60
     613.  Click "Delete Resources" again to confirm that you want to delete all reserved resources. 
     62
     63=== 4.2 Using Omni ===
     64 In the terminal execute the following command:
     65{{{
     66omni.py -a pg-utah deletesliver <sliceName>
     67}}}
     68where <sliceName> is once again replaced with your chosen unique slice name.