Changes between Version 13 and Version 14 of GEC21Agenda/ChoiceNet/run_tests


Ignore:
Timestamp:
10/19/14 23:36:18 (5 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC21Agenda/ChoiceNet/run_tests

    v13 v14  
    33= A !ChoiceNet Source-Routed Forwarding Service and Marketplace =
    44
    5 The first !ChoiceNet service that we will use is the ''!ChoiceNet Source-Routed Forwarding Service'' described [wiki:  earlier].
     5The first !ChoiceNet service that we will use is the ''!ChoiceNet Source-Routed Forwarding Service'' described [wiki:GEC21Agenda/ChoiceNet/gt_tool  earlier].  We assume you have [wiki:GEC21Agenda/ChoiceNet/ already created two terminal windows], '''TERMINAL 1''' and '''TERMINAL 2''' that are logged into slice nodes '''H1''' and '''H2''' respectively.  You objective in this part of the tutorial is to run ''iperf'' between H1 and H2 several different ways:
     6 1. Without providing sufficient payment to the ''path service (PS)'' -- which should cause iperf to fail
     7 1. Requesting a higher cost but higher-bandwidth path (and providing the payment need to get back high bandwidth paths from the PS)
     8 1. Requesting a lower cost but lower-bandwidth path (and providing the reduced payment need to get back low bandwidth paths from the PS)
     9 1. Requesting a medium cost, high bandwidth but high latency path and providing the payment need to get back high bandwidth/high latency paths from the PS)
     10You will run your iperf server on H1 and the iperf client on H2.  For each test case, we will be able to see the throughput achieved by iperf, indicating that the PS found an appropriate path, and iperf received the requested performance characteristics.   If you are logged into the GENI Desktop, you will be able to visually see the traffic taking different paths across the topology.
    611
    7 At this point we have the Choicenet Framework setup. We now need to run some end to end services to demonstrate the usability of "choice" within a network. For this we will run an iperf test between the end host nodes H1 and H2.
     12=== Start the iperf server '''on TERMINAL 1''' ('''H1''') ===
    813
    9 So Open up two more ssh session terminals to the GNO Node and cd ~/choicenet/source/bin on each one
    10 
    11 
    12 '''On TERMINAL 1'''
    13 
    14 {{{
    15 #!sh
    16 cd ~/choicenet/source/bin
    17 }}}
    18 
    19 
    20 {{{
    21 #!sh
    22 ./getool -f <MANIFEST FILENAME> -l <GENI USERNAME> -i ~/.ssh/id_rsa ssh h1
    23 }}}
    24 
    25 this will take you to H1 node (You can also directly ssh into H1 Node from your laptop if you prefer that way)
    26 
    27 on H1 Node
     14Once you are logged into H1, copy the wrapper library into the bin directory, and then find the IP address of H1.  In particular, run the following commands on '''TERMINAL 1''' ('''H1'''):
    2815
    2916{{{
     
    3724}}}
    3825
    39 Form the last command (ifconfig), please note down the IPV6 Scope Site address of eth1. (This should begin with an fec0:: . This will be used the next terminal )
     26Look at the output from the /sbin/ifconfig, and write down the IPV6 Scope Site address of eth1. (This should begin with an fec0::).  You will need this address when starting the iperf client (in the '''TERMINAL 2''' window).
    4027
    41 Choicenet is all about choices in the network. For our iperf test run, we currently have a set the network to use the High Bandwidth path "HB". If you like to take an alternate route based on your network preference , you can use any editor (vim, pico , nano) that you prefer to edit the  ../config/config.txt and change HB to LB ( Low Bandwith) path or HBHL (High bandwidth High Latency) path as the last line.
    42 
    43 We then use a Choicenet wrapper app to convert an existing tcp application into a Choicenet application as shown below
    44 
    45 get ready to start the iperf Server here . Type the command and keep it ready . '''DO NOT RUN IT JUST YET'''
     28You will then use our !ChoiceNet wrapper to transform the iperf server (an existing TCP/IPv4 application) into a !ChoiceNet-enabled application.  To start the iperf server type (on H1):
    4629
    4730{{{
     
    5134
    5235
    53 '''On TERMINAL 2'''
     36=== Start the iperf client '''on TERMINAL 2''' ('''H2''') ===
    5437
    55 {{{
    56 #!sh
    57 cd ~/choicenet/source/bin
    58 }}}
    59 
    60 
    61 {{{
    62 #!sh
    63 ./getool -f <MANIFEST FILENAME> -l <GENI USERNAME> -i ~/.ssh/id_rsa ssh h2
    64 }}}
    65 
    66 this will take you to H2 node (You can also directly ssh into H2 Node from your laptop if you prefer that way)
    67 
    68 on H2 Node
     38After you have logged into H2, copy the wrapper library into the bin directory, and start the iperf client.  In particular, run the following commands on '''TERMINAL 2''' ('''H2''') to start the iperf client:
    6939
    7040{{{
     
    7444cp ../wrap .
    7545
     46sudo ./wrap /usr/bin/iperf -c <IPv6 address of H1 > -V
    7647}}}
     48
     49where ''IPv6 address of H1'' is the IPv6 address you found above (in TERMINAL 1).
    7750
    7851Choicenet is all about choices in the network. For our iperf test run, we currently have a set the network to use the High Bandwidth path "HB". If you like to take an alternate route based on your network preference , you can use any editor (vim, pico , nano) that you prefer to edit the  ../config/config.txt and change HB to LB ( Low Bandwidth) path or HBHL (High bandwidth High Latency) path as the last line.