Changes between Version 28 and Version 29 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-6

Timestamp:

08/14/12 10:30:55 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-6

@@ -1 +1 @@
 
-= EG-EXP-6: ExoGENI and Meso-scale Multi-site OpenFlow Acceptance Test =
+= EG-EXP-6: ExoGENI and Meso-scale Multi-site !OpenFlow Acceptance Test =
 
 This page captures status for the test case EG-EXP-6, which verifies ExoGENI rack interoperability with other meso-scale GENI sites. For overall status see the [wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus ExoGENI Acceptance Test Status] page.
@@ -116 +116 @@
  - RENCI Rack RSpec: [http://groups.geni.net/geni/browser/trunk/GENIRacks/ExoGENI/Spiral4/Rspecs/AcceptanceTests/EG-EXP-6/EG-EXP-6-exp1-openflow-exorci.rspec EG-EXP-6-exp1-openflow-exorci.rspec]
 
-The BBN ExoGENI rack connects to the GENI backbone via the BBN GPO Lab OpenFlow switch named poblano. In order for this scenario to work OpenFlow must be configured also on the poblano switch to allow the BBN ExoGENI rack OF traffic to get to the OF GENI core. The following OpenFlow RSpec was defined for the BBN site switch poblano: [http://groups.geni.net/geni/browser/trunk/GENIRacks/ExoGENI/Spiral4/Rspecs/AcceptanceTests/EG-EXP-6/EG-EXP-6-exp1-openflow-bbn.rspec EG-EXP-6-exp1-openflow-bbn.rspec]
+The BBN ExoGENI rack connects to the GENI backbone via the BBN GPO Lab !OpenFlow switch named poblano. In order for this scenario to work !OpenFlow must be configured also on the poblano switch to allow the BBN ExoGENI rack OF traffic to get to the OF GENI core. The following !OpenFlow RSpec was defined for the BBN site switch poblano: [http://groups.geni.net/geni/browser/trunk/GENIRacks/ExoGENI/Spiral4/Rspecs/AcceptanceTests/EG-EXP-6/EG-EXP-6-exp1-openflow-bbn.rspec EG-EXP-6-exp1-openflow-bbn.rspec]
 
 == 6. Define request RSpecs for !OpenFlow core resources at NLR FOAM. ==
@@ -144 +144 @@
 
 == 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:
+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
@@ -274 +274 @@
 == 24. Create a sliver that connects the Internet2 Meso-scale !OpenFlow site to the BBN ExoGENI Site, and the GPO Meso-scale site ==
 
-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:
+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
@@ -318 +318 @@
 == 28. As site administrator, identify all controllers that the BBN ExoGENI !OpenFlow switch is connected to ==
 
-Do not have site administrator privileges to identify all controllers that have access to the BBN ExoGENI OpenFlow Switch. Verified that the
-appropriate switches for the experiment on this page are connected to the OpenFlow Controller. 
+Do not have site administrator privileges to identify all controllers that have access to the BBN ExoGENI !OpenFlow Switch. Verified that the
+appropriate switches for the experiment on this page are connected to the !OpenFlow Controller. 
 Based on the RSpecs the following is requested:
 {{{