Changes between Version 18 and Version 19 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-7


Ignore:
Timestamp:
01/16/13 13:55:47 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-7

    v18 v19  
    22= EG-EXP-7:  Click Router Experiment Acceptance Test =
    33
    4 This page captures status for the test case EG-EXP-2, which verifies a click router scenario between two racks. For overall status see the [wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus InstaGENI Acceptance Test Status] page.
     4This page captures status for the test case EG-EXP-2, which verifies a click router scenario between two racks. This test has been executed in two topologies:
     5 - Scenario 1: All nodes in topology are in GPO InstaGENI rack.
     6 - Scenario 2: Resources hostA and 2 click routers in GPO rack;Resources hostB and 2 click routers are in Utah rack.
     7
     8For overall status see the [wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus InstaGENI Acceptance Test Status] page.
    59
    610''Last update: 2013/01/16''
     
    1014This section captures the status for each step in the acceptance test plan.
    1115
    12 || '''Step''' || '''State'''           || '''Date completed'''    ||''' Ticket ''' || '''Comments''' ||
     16|| '''Step''' ||'''State/Scenario 2:'''|| '''State/Scenario 1:''' ||'''Date completed '''||'''Ticket'''||
    1317|| Step 1     || [[Color(green,Pass)]] ||                         ||               ||                ||
    1418|| Step 2     || [[Color(green,Pass)]] ||                         ||               ||                ||
     
    4044
    4145
    42 
    4346= Test Plan Steps =
    44 The following aggregate manager nicknames are used:
     47
     48The following aggregate manager nicknames are used in this test case:
    4549{{{
    4650ig-utah=,https://utah.geniracks.net/protogeni/xmlrpc/am/2.0
    4751ig-gpo=,https://instageni.gpolab.bbn.com/protogeni/xmlrpc/am/2.0
    4852}}}
     53
     54= Scenario 1 - GPO Rack =
     55
     56== 1. As Experimenter1, request !ListResources from GPO InstaGENI ==
     57
     58As user lnevers@bbn.com requested listresources from GPO and Utah InstaGENI aggregates:
     59{{{
     60$ omni.py listresources -a ig-gpo -o
     61}}}
     62
     63== 2. Review !ListResources ==
     64
     65Reviews output file ''rspec-instageni-gpolab-bbn-com-protogeniv2.xml'' to determine available resources.
     66
     67== 3. Define a request RSpec for three VMs at GPO InstaGENI ==
     68
     69The RSpec generated is [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-7/IG-EXP-7.rspec IG-EXP-7.rspec]  requests a topology shown in here:
     70
     71
     72[[Image(IG-EXP-7-gpo.jpg)]]
     73
     74== 4. Define a request RSpec for GPO InstaGENI ==
     75
     76The RSpec generated is [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-7/IG-EXP-7-gpo.rspec IG-EXP-7-gpo.rspec].
     77
     78== 5. Create slice ==
     79
     80Created a slice:
     81{{{
     82$ omni.py createslice IG-EXP-7
     83}}}
     84
     85== 6. Create a sliver ==
     86
     87In the slice IG-EXP-7 create a slivers at the GPO InstaGENI AM using the RSpecs [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-7/IG-EXP-7-gpo.rspec IG-EXP-7-gpo.rspec].
     88{{{
     89$ omni.py createsliver -a ig-gpo IG-EXP-7 IG-EXP-7-gpo.rspec
     90}}}
     91
     92== 7. Install Click router ==
     93
     94The Rspec used defines the following services to install the click router:
     95{{{
     96      <services>
     97      <execute command="sudo /local/install-script.sh" shell="sh"/>
     98      <install install_path="/local" url="http://www.gpolab.bbn.com/experiment-support/ClickExampleExperiment/click-example.tar.gz"/>
     99    </services>
     100}}}
     101The above service will get the ''click-example.tar.gz'' place it on ''/local'' on the 4 router nodes,  unpack the tar.gz file which contains two files:
     102 * ''install-script.sh'' - installs click routes v.2.0.1 ran as part of the createsliver.
     103 *  ''extractClickConfig.py'' - determines MAC and IP settings for the configuration, ran manually after sliver is ready.
     104
     105== 8. Determine Click router settings ==
     106
     107The click router setting are determined by the ''extractClickConfig.py'' script.  To run this script, determin login for each of the nodes in the experiment at each resource aggregate:
     108{{{
     109$ readyToLogin.py -a ig-gpo IG-EXP-7
     110}}}
     111
     112First logged into hostA and hostB to verify connection are in place:
     113
     114Generated configuration on each click router:
     115
     116
     117== 9. Run the user-level Click router ==
     118
     119Login to each of the routers, and run the user-level Click router by providing the print pings configuration file name. Leave terminal connection open:
     120{{{
     121$ cd /local/click/userlevel
     122$ sudo ./click ~/click.conf
     123}}}
     124
     125== 10. Log in to Host1 and send traffic to host2 ==
     126
     127Log in to host1 and send traffic to host2 and leave traffic running.  Review the output on the terminal for each of the
     128
     129Log in to host2 and send traffic to host1
     130
     131== 11. Review Click logs on each Click router ==
     132
     133== 16. Delete slivers ==
     134
     135
     136= Scenario 2 - GPO and Utah IG Racks =
    49137
    50138== 1. As Experimenter1, request !ListResources from GPO and Utah InstaGENI ==
     
    458546
    459547== 16. Delete slivers ==
     548
     549
     550