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

Timestamp:

01/09/13 13:20:15 (11 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-7

@@ -4 +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.
 
+''Last update: 2013/01/09''
 
 = Test Status =
+
 This section captures the status for each step in the acceptance test plan.
 
 || '''Step''' || '''State'''           || '''Date completed'''    ||''' Ticket ''' || '''Comments''' ||
-|| Step 1     ||[[Color(orange,Blocked)]] ||                         ||               ||BBN rack is not yet available||
+|| Step 1     ||                       ||                         ||               ||                ||
 || Step 2     ||                       ||                         ||               ||                ||
 || Step 3     ||                       ||                         ||               ||                ||
@@ -40 +42 @@
 
 = Test Plan Steps =
+the following aggregate manager nicknames are used:
+{{{
+ig-utah=,https://utah.geniracks.net/protogeni/xmlrpc/am/2.0
+ig-gpo=,https://instageni.gpolab.bbn.com/protogeni/xmlrpc/am/2.0
+}}}
 
- 1. As Experimenter1, request !ListResources from BBN InstaGENI, and Utah InstaGENI.
- 2. Review !ListResources output from both rack AMs.
- 3. Define a request RSpec for three VMs at the BBN InstaGENI.
- 4. Define a request RSpec for three VMs at the Utah InstaGENI.
- 5. Create the first slice.
- 6. Create a sliver in the first slice at each AM, using the RSpecs defined above. 
- 7. Download the Click Router software on the 4 nodes that will be routers in the experiment.
- 7. Build the user-level Click program in the 'userlevel' directory on each of the 4 router nodes.
- 8. Determine the interface to MAC address mapping, and various settings required for the 4 router node and modify click configuration.
- 9. Run the user-level Click router by providing the configuration file name as an argument on each node.
- 10. Log in to Host1 and send traffic to host2, leave traffic running.
- 11. Review Click logs on each Click router.
- 12. Stop traffic on Host2.
- 13. Log in to Host1 and send traffic to host2, leave traffic running.
- 14. Review Click logs on each Click router.
- 15. Stop traffic on Host2.
- 16. Delete sliver.
+== 1. As Experimenter1, request !ListResources from GPO and Utah InstaGENI ==
+As user lnevers@bbn.com requested listresources from GPO and Utah InstaGENI aggregates:
+{{{
+$ omni.py listresources -a ig-gpo -o
+$ omni.py listresources -a ig-utah -o
+}}}
+
+== 2. Review !ListResources output from both AMs ==
+Reviews output files "rspec-instageni-gpolab-bbn-com-protogeniv2.xml" and "spec-utah-geniracks-net-protogeniv2.xml" to determine available resources.
+
+== 3. Define a request RSpec for three VMs at BBN InstaGENI ==
+
+== 4. Define a request RSpec for three VMs at Utah InstaGENI ==
+
+== 5. Create slice ==
+
+== 6. Create a sliver == 
+In the slice IG-EXP-7 create a slivers at each AM, using the RSpecs defined above. 
+{{{
+
+}}}
+
+== 7. Install Click router ==
+
+Download 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.
+
+== 8. Determine Click router settings ==
+Determine the interface to MAC address mapping, and various settings required for the 4 router node and modify click configuration.
+
+== 9. Run the user-level Click router ==
+Run the user-level Click router by providing the configuration file name as an argument on each node.
+
+== 10. Log in to Host1 and send traffic to host2 ==
+
+Log in to Host1 and send traffic to host2 and leave traffic running.
+
+== 11. Review Click logs on each Click router ==
+
+== 16. Delete slivers ==