Changes between Version 5 and Version 6 of sol4/IDMS/ExpTutorial

06/20/14 15:21:46 (9 years ago)



  • sol4/IDMS/ExpTutorial

    v5 v6  
    3 == IDMS Experiment in GENI ==
     3= IDMS Experiment in GENI =
    55The persistent IDMS experiment allows other users to attach at shared VLAN sites, granting
    2323== Prerequisite  ==
    25 In order to go through this tutorial you will need to use a tool for reserving resources. You can use either [ Flack] or [ Omni]. If you haven't used any of these tools before, please go through the introductory tutorials first.
     25In order to attach external user to base experiment. You need to reserve resources. You can use either [ Flack] or [ Omni] to do that. If you haven't used any of these tools before, please go through the introductory tutorials first.
    2626  * [wiki:GENIExperimenter/Tutorials/RunHelloGENI Flack tutorial.] Flack is graphical web tool.
    2727  * [wiki:GENIExperimenter/Tutorials/HelloOmni Omni tutorial.] Omni is a command line tool.
    29 = 1. Create your experiment =
     31== Step 1: Create Slice ==
     33Create the slice in the project. Name the slice something like xxxxIdmsUser.
    31 #!html
    32 <table border="0">
    34       <tr>
    35        <td>
    36 <img border="0" src="" alt="Layer2 example topology"  width="300" title="Layer2 example topology" />  </a>
    37        </td>
    38        <td >
    39          <ol>
    40             <li><b> Create a slice </b>. Name your slice something like <b>xxxomni</b> (where xxx are your initials). </li>
    41             <li> <b> Reserve resources </b>. In this step we are going to reserve resources using the <a href=""> rspec file </a> from this URL: <a href=""></a>. The topology that this rspec describes looks like the diagram on the left. </li>
    42              <li> <b> Wait until your resources are ready </b> </li>
    43           </ol>
    44        </td>
    46     </tr>
    47  </table>
     35     omni createslice <slice_name> -r <project_name>
     39== Step 2: Reserve Resources ==
    52 = 2. Run your experiment =
    53 Now that resources are ready we can start running our experiment.
    54   1. '''Login to all the reserved hosts.''' We will first start by logging in to both of our reserved nodes. If you don't know how to login to your nodes please follow [wiki:HowTo/LoginToNodes these instructions].
     411. Download the  [ rspec ]. For more information on rspec refer [ Inside rspec][[BR]]
     432. Base experiment can only be joined at shared VLAN nodes. Currently shared VLAN nodes are at
     44    * stanford-ig
     45    * utah-ig
     46    * illinois-ig
     47    * ig-bbn
     493. Select aggregate manager from list above.
     51   omni createsliver -a <aggregate_manager> <slice_name> <path_to_rspec_file> -r <project_name>
     544. Poll the resource status to make sure overall 'geni_status' is 'ready'
     56   omni sliverstatus -a <aggregate_manager> <slice_name> -r <project_name>
     595. If 'geni_status' is not 'ready' try using another aggregate manager
    57   2. '''Send IP traffic''' The first simple experiment that we will run is to verify the IP connectivity between our hosts.
    58     i. Check the interfaces of your nodes. In the terminal type:
    59     {{{
    60    /sbin/ifconfig
    61   }}}
    62     You should see at least two interfaces:
    63       * 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.
    64       * 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.
    65     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.
    66     i. From the client ping the server. From the xterm that is logged in to the client type :
    67     {{{
    68     ping server -c 5
    69   }}}
    70     '''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 :
    71     {{{
    72 [[inki@r2 ~]$ ping server -c 5
    73 PING ( 56(84) bytes of data.
    74 64 bytes from icmp_seq=1 ttl=64 time=1.95 ms
    75 64 bytes from icmp_seq=2 ttl=64 time=2.27 ms
    76 64 bytes from icmp_seq=3 ttl=64 time=2.04 ms
    77 64 bytes from icmp_seq=4 ttl=64 time=1.95 ms
    78 64 bytes from icmp_seq=5 ttl=64 time=1.72 ms
     62== Step 3: login to Reserved Host ==     
    80 --- ping statistics ---
    81 5 packets transmitted, 5 received, 0% packet loss, time 4005ms
    82 rtt min/avg/max/mdev = 1.728/1.992/2.278/0.179 ms
     641. To download / upload data on the storage node login to reserved resource. If you are unaware of this, please follow instruction [ here][[BR]]
     652. '''Test configuration''' : DHCP server allocate ip to each resource connected to base experiment. To ensure your reserved resource is connected to idms base experiment data plane, ping the DHCP server.
     67    ping
    85   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.
    86     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:
    87     {{{
    88   sudo /sbin/ifconfig <data i/f name>
    89   }}}
    90     '''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.
    91     i. Try again to ping from the client to the server. In the xterm of the client type:
    92     {{{
    93   ping server -c 5
    94   }}}
    95     This time the ping should timeout.
    96     i. Start the Layer 2 ping server: In the server xterm, type:
    97     {{{
    98   sudo /usr/local/bin/pingPlusListener 12345
    99   }}}
    100     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:
    101     {{{
    102   sudo /usr/local/bin/pingPlus <server data mac addr> <client data i/f name> 12345
    103   }}}
    104     The result should look like :
    105     {{{
    106 [uncusr20@client ~]$ sudo /usr/local/bin/pingPlus 02:00:9B:48:3E:20 mv1.1 12345
    107 RQ:'5582+2067' to 2:0:9b:48:3e:20.
    108 RQ:5582+2067 from 2:0:3e:15:6c:ab.
    109 }}}
    111 Congratulations you have run a Layer 2 experiment in GENI!
     71== Inside rspec ==
    113 = 3. Cleanup  =
    114 Although all your reservations, have expiration times, you should always release
    115 your resources once you have completed your experiment to make them available
    116 to other experimenters.