Changes between Version 14 and Version 15 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-6

Timestamp:

08/07/12 10:20:10 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-6

@@ -105 +105 @@
 == 3. Define a request RSpec for a VM at the BBN ExoGENI. ==
 
-Defined an RSpec for one VM on the shared VLAN 1750: [EG-EXP-6-exp1-exobbn.rspec]
+Defined an RSpec for one VM on the shared VLAN 1750 in the BBN ExoGENI rack: [EG-EXP-6-exp1-exobbn.rspec]
 
 == 4. Define a request RSpec for a VM at the RENCI ExoGENI. ==
 
-Define an RSpec for one VM on the shared VLAN 1750: [EG-EXP-6-exp1-exorci.rspec]
+Define an RSpec for one VM on the shared VLAN 1750 in the RENCI ExoGENI rack: [EG-EXP-6-exp1-exorci.rspec]
 
 == 5. Define request RSpecs for !OpenFlow resources from BBN FOAM to access GENI !OpenFlow core resources. ==
@@ -131 +131 @@
 == 8. Create a sliver in the first slice at each AM, using the RSpecs defined above. ==
 {{{
-$omni.py -a exobbn createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-exobbn.rspec
-$omni.py -a of-bbn createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-openflow-bbn.rspec
-$omni.py -a of-nlr createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-openflow-nlr.rspec
-$omni.py -a exorci createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-exorci.rspec
+ $omni.py -a exobbn createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-exobbn.rspec
+ $omni.py -a of-bbn createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-openflow-bbn.rspec
+ $omni.py -a of-nlr createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-openflow-nlr.rspec
+ $omni.py -a exorci createsliver EG-EXP-6-exp1 EG-EXP-6-exp1-exorci.rspec
 }}}
 
@@ -142 +142 @@
 
 == 9. Log in to each of the systems, verify IP address assignment. Send traffic to the other system, leave traffic running. ==
+Determine the status of the OpenFlow slivers, check the sliverstatus for each to make sure that they have been approved. Note that 'geni_status' is 'ready' when the sliver is approved.  If the OpenFlow sliver is waiting for approval the 'geni_status' will be 'configuring:
+{{{
+ $ omni.py -a of-bbn sliverstatus EG-EXP-6-exp1
+ $ omni.py -a of-nlr sliverstatus EG-EXP-6-exp1
+}}}
+
+Determine compute resources allocated to each sliver in the ExoGENI racks. First make sure the sliverstatus is ready:
+{{{
+ $ omni.py -a exobbn sliverstatus EG-EXP-6-exp1
+ $ omni.py -a exorci sliverstatus EG-EXP-6-exp1
+}}}
+Once the slivers are ready get the list of hosts allocated with Omni:
+{{{
+ $ omni.py -a exobbn listresources EG-EXP-6-exp1 -o
+ $ omni.py -a exorci listresources EG-EXP-6-exp1 -o 
+ $ egep hostname EG-EXP-6-exp1-rspec-bbn-hn-exogeni-net-11443-orca.xml 
+   <login authentication="ssh-keys" hostname="192.1.242.6" port="22" username="root"/> 
+ $ egrep hostname EG-EXP-6-exp1-rspec-rci-hn-exogeni-net-11443-orca.xml 
+   <login authentication="ssh-keys" hostname="152.54.14.18" port="22" username="root"/>   
+}}}
 
 == 10. As Experimenter2, define a request RSpec for one VM and one bare metal node at BBN ExoGENI. ==
@@ -172 +192 @@
 {{{
 $ omni.py -a exorci createsliver EG-EXP-6-exp2 ./exorspec/EG-EXP-6/EG-EXP-6-exp2-exorci.rspec 
-
 }}}
 
 == 16. Log in to each of the systems in the slice, and send traffic to each other systems; leave traffic running
 
+Determine compute resources allocated to each sliver in the ExoGENI racks. First make sure the sliverstatus is ready:
+{{{
+ $ omni.py -a exobbn sliverstatus EG-EXP-6-exp2
+ $ omni.py -a exorci sliverstatus EG-EXP-6-exp2
+}}}
+Once the slivers are ready get the list of hosts allocated with Omni:
+{{{
+ $ omni.py -a exobbn listresources EG-EXP-6-exp2 -o
+ $ omni.py -a exorci listresources EG-EXP-6-exp2 -o 
+ $ egep hostname EG-EXP-6-exp2-rspec-bbn-hn-exogeni-net-11443-orca.xml 
+   < 
+ $ egrep hostname EG-EXP-6-exp2-rspec-rci-hn-exogeni-net-11443-orca.xml 
+   <   
+}}}
+
+
 == 17. As Experimenter3, request !ListResources from BBN ExoGENI, GPO FOAM, and FOAM at Meso-scale Site ==
 
+For the initial run only had 2 user account available, so the Experimenter3 steps are executed with the same credentials as experiment 1.
+Also the WAPG resource at Rutgers is available via the Emulab PG aggregate.  Executed the following to get resources for each aggregate:
+{{{
+$ omni.py listresources -a exobbn -o
+$ omni.py listresources -a of-bbn -o
+$ omni.py listresources -a of-i2 -o
+$ omni.py listresources -a of-rutgers -o   
+$ omni.py listresources -a pg2 --api-version 2 -t GENI 3 -o   
+}}}
+
 == 18. Review !ListResources output from all AMs ==
+Reviewed content of advertisement RSpecs for each of the aggregates polled in the previous step.
+
 == 19. Define a request RSpec for a VM at the BBN ExoGENI ==
+
+Defined RSpec for one VM on the shared VLAN 1750 in the BBN ExoGENI rack: [EG-EXP-6-exp3-exobbn.rspec]
+
 == 20. Define a request RSpec for a compute resource at the GPO Meso-scale site ==
+
+Defined RSpec for one PG Resource at the GPO PG site: [EG-EXP-6-exp3-bbn-pgeni.rspec]
+
 == 21. Define a request RSpec for a compute resource at a Meso-scale site ==
+
+Defined RSpec for one WAPG Resource at the Rutgers site [EG-EXP-6-exp3-rutgers-wapg.rspec]
+
 == 22. Define request RSpecs for !OpenFlow resources to allow connection from OF BBN ExoGENI to Meso-scale OF sites  
 GPO (NLR) and Rutgers Sites (I2) ==
 
+Defined the !OpenFlow RSpecs for the sites below, note that the BBN OF RSpec overlaps with the one in experiment 1 and is being used here:
+  - Rutgers [EG-EXP-6-exp3-openflow-rutgers.rspec]
+  - BBN [EG-EXP-6-exp1-openflow-bbn.rspec] 
+  - Internet2 [EG-EXP-6-exp3-openflow-i2.rspec]
+
 == 23. Create a third slice ==
 {{{
@@ -191 +252 @@
 }}}
 == 24. Create a sliver that connects the Internet2 Meso-scale !OpenFlow site to the BBN ExoGENI Site, and the GPO Meso-scale site ==
-{{{
-$omni.py -a of-i2 createsliver EG-EXP-6-exp3 EG-EXP-6-expX-openflow-i2.rspec
-}}}
+As stated in step 22, the BBN OpenFlow flows were requested as part of experiment1 and are not re-executed here.  The remaining requests are as follows:
+{{{
+ $ omni.py -a exobbn createsliver EG-EXP-6-exp3 EG-EXP-6-exp3-exobbn.rspec
+ $ omni.py -a pgeni createsliver EG-EXP-6-exp3 EG-EXP-6-exp3-bbn-pgeni.rspec 
+ $ omni.py -a of-i2 createsliver EG-EXP-6-exp3 EG-EXP-6-exp3-openflow-i2.rspec
+ $ omni.py -a pg2 createsliver EG-EXP-6-exp3 --api-version 2 -t GENI 3 EG-EXP-6-exp3-rutgers-wapg.rspec 
+ $ omni.py -a of-rutgers createsliver EG-EXP-6-exp3 EG-EXP-6-exp3-openflow-rutgers.rspec 
+}}}
+
 == 25. Log in to each of the compute resources in the slice, and configure data plane network interfaces on any non-ExoGENI resources as necessary, and send traffic to each other systems; leave traffic running.
 
+Determine compute resources allocated to the sliver in the BBN ExoGENI rack. First make sure the sliverstatus is ready and once the sliver is ready get the host allocated with Omni:
+{{{
+ $ omni.py -a exobbn sliverstatus EG-EXP-6-exp3
+ $ omni.py -a exobbn listresources EG-EXP-6-exp3 -o
+ $ egep hostname EG-EXP-6-exp3-rspec-bbn-hn-exogeni-net-11443-orca.xml 
+   < 
+}}}
+
+Determine the resources allocated to the WAPG Rutgers node:
+{{{
+ $ omni.py -a pg2 sliverstatus EG-EXP-6-exp3 --api-version 2 -t GENI 3 
+
+}}}
+
+Determine the resources allocated to the GPO PG node:
+{{{
+ $ omni.py -a pgeni sliverstatus EG-EXP-6-exp3
+ $ omni.py -a pgeni listresources EG-EXP-6-exp3 -o  
+ $ egrep "hostname" EG-EXP-6-exp3-rspec-pgeni-gpolab-bbn-com.xml
+    <login authentication="ssh-keys" hostname="pc9.pgeni.gpolab.bbn.com" port="22" username="lnevers"/>  
+
+
 == 26. Verify that all three experiments continue to run without impacting each other's traffic and verify that data is exchanged over the path along which data is supposed to flow ==