Changes between Version 34 and Version 35 of GENIFlowSpaceFirewallTests

Timestamp:

02/02/15 14:02:05 (9 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIFlowSpaceFirewallTests

@@ -13 +13 @@
   * Confirm FSF ability to support multiple concurrent add/delete requests with [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller]. 
   * Verify rate limiting,if any, on the control plane.  (No rate limiting enforced on the AL2S data plane with FSFW)
-  * Confirm ability to collect AL2S and FSFW usage statistics relevant to these test scenarios via SNAPP and GENI local datastore monitoring interfaces. Example statistics include total flows, flowmods/sec, VLANs throughput on switches and links, active GENI slices/slivers.  See the GENI monitoring use cases for more detail on statistics not specifically realted to FSFW.
+  * Confirm ability to collect AL2S and FSFW usage statistics relevant to these test scenarios via SNAPP and GENI local datastore monitoring interfaces. Example statistics include total flows, flowmods/sec, VLANs throughput on switches and links, active GENI slices/slivers.  See the GENI monitoring use cases for more detail on statistics not specifically related to FSF.
   * Run through Internet2 procedures for qualifying and running an experimenter controller in AL2S and provide feedback to I2 to streamline the procedures as much as possible, and ensure experimenters can get complete and accurate documentation to help guide them through procedures.
 
@@ -27 +27 @@
     * Tests are described in this plan with the assumption that GENI network stitching is available from OESS AM. 
     * OESS AM may not be available, so sliver creation may be done in 2 steps:
-       - AL2S circuits will be set up to connect the edge ports.  (This may require manual setup by I2, because of the VLAN range restrictions for FSFW)
+       - AL2S circuits will be set up to connect the edge ports.  (This may require manual setup by I2, because of the VLAN range restrictions for FSF)
        - Stitched slivers with fixed AL2S endpoints are created for IG sites.
     * Each test lists rack endpoints we intend to use for those tests.  Other racks may be substituted if necessary due to outages or scheduled events such as tutorials, although all racks were unscheduled as of May 2.
@@ -44 +44 @@
  3. Delete slices and and verify release of VLANs via AL2S router proxy. 
  4. Submit multiple concurrent requests to add and to delete flow spaces.
- 5. Test limits configured in FSFW for control plane rate limits, and  verify enforcement.  (This step likely requires cooperation from I2, since GPO may not have the ability to directly affect controller to attempt to exceed control plane rate limits.
+ 5. Test limits configured in FSF for control plane rate limits, and  verify enforcement.  (This step likely requires cooperation from I2, since GPO may not have the ability to directly affect controller to attempt to exceed control plane rate limits.
  6. Query FSF status and rules via SNAPP.
  7. Generate traffic outside of pre-defined flowspace and verify that it is handled properly.
- 8. Create slice requesting specific VLAN outside of FSFW range, verify rejection.
+ 8. Create slice requesting specific VLAN outside of FSF range, verify rejection.
  9. Request network capacity beyond configured FSF capacity, verify that request fails.
 
@@ -72 +72 @@
 [[Image(fsfw-test-topology-step2.jpg)]]
 
+''' This test may only be executed if ION sites still remain when this plan is executed'''
+
 __ION to AL2S cross-connects__ [[BR]]
+
 The following cross-connects will be verified in the !OpenFlow topologies shown above:
  1. sdn-sw.losa e1/1 <-> rtr.losa:port=et-10/0/0