Changes between Version 3 and Version 4 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-7


Ignore:
Timestamp:
01/09/13 13:20:15 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v3 v4  
    44This 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.
    55
     6''Last update: 2013/01/09''
    67
    78= Test Status =
     9
    810This section captures the status for each step in the acceptance test plan.
    911
    1012|| '''Step''' || '''State'''           || '''Date completed'''    ||''' Ticket ''' || '''Comments''' ||
    11 || Step 1     ||[[Color(orange,Blocked)]] ||                         ||               ||BBN rack is not yet available||
     13|| Step 1     ||                       ||                         ||               ||                ||
    1214|| Step 2     ||                       ||                         ||               ||                ||
    1315|| Step 3     ||                       ||                         ||               ||                ||
     
    4042
    4143= Test Plan Steps =
     44the following aggregate manager nicknames are used:
     45{{{
     46ig-utah=,https://utah.geniracks.net/protogeni/xmlrpc/am/2.0
     47ig-gpo=,https://instageni.gpolab.bbn.com/protogeni/xmlrpc/am/2.0
     48}}}
    4249
    43  1. As Experimenter1, request !ListResources from BBN InstaGENI, and Utah InstaGENI.
    44  2. Review !ListResources output from both rack AMs.
    45  3. Define a request RSpec for three VMs at the BBN InstaGENI.
    46  4. Define a request RSpec for three VMs at the Utah InstaGENI.
    47  5. Create the first slice.
    48  6. Create a sliver in the first slice at each AM, using the RSpecs defined above.
    49  7. Download the Click Router software on the 4 nodes that will be routers in the experiment.
    50  7. Build the user-level Click program in the 'userlevel' directory on each of the 4 router nodes.
    51  8. Determine the interface to MAC address mapping, and various settings required for the 4 router node and modify click configuration.
    52  9. Run the user-level Click router by providing the configuration file name as an argument on each node.
    53  10. Log in to Host1 and send traffic to host2, leave traffic running.
    54  11. Review Click logs on each Click router.
    55  12. Stop traffic on Host2.
    56  13. Log in to Host1 and send traffic to host2, leave traffic running.
    57  14. Review Click logs on each Click router.
    58  15. Stop traffic on Host2.
    59  16. Delete sliver.
     50== 1. As Experimenter1, request !ListResources from GPO and Utah InstaGENI ==
     51As user lnevers@bbn.com requested listresources from GPO and Utah InstaGENI aggregates:
     52{{{
     53$ omni.py listresources -a ig-gpo -o
     54$ omni.py listresources -a ig-utah -o
     55}}}
     56
     57== 2. Review !ListResources output from both AMs ==
     58Reviews output files "rspec-instageni-gpolab-bbn-com-protogeniv2.xml" and "spec-utah-geniracks-net-protogeniv2.xml" to determine available resources.
     59
     60== 3. Define a request RSpec for three VMs at BBN InstaGENI ==
     61
     62== 4. Define a request RSpec for three VMs at Utah InstaGENI ==
     63
     64== 5. Create slice ==
     65
     66== 6. Create a sliver ==
     67In the slice IG-EXP-7 create a slivers at each AM, using the RSpecs defined above.
     68{{{
     69
     70}}}
     71
     72== 7. Install Click router ==
     73
     74Download the Click Router software on the 4 nodes that will be routers in the experiment. Build the user-level Click program in the 'userlevel' directory on each of the 4 router nodes.
     75
     76== 8. Determine Click router settings ==
     77Determine the interface to MAC address mapping, and various settings required for the 4 router node and modify click configuration.
     78
     79== 9. Run the user-level Click router ==
     80Run the user-level Click router by providing the configuration file name as an argument on each node.
     81
     82== 10. Log in to Host1 and send traffic to host2 ==
     83
     84Log in to Host1 and send traffic to host2 and leave traffic running.
     85
     86== 11. Review Click logs on each Click router ==
     87
     88== 16. Delete slivers ==