Changes between Version 30 and Version 31 of GENIFlowSpaceFirewallTests


Ignore:
Timestamp:
02/02/15 13:55:55 (5 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIFlowSpaceFirewallTests

    v30 v31  
    33= Internet2 !FlowSpace Firewall Tests =
    44
    5 This page outlines testing planned for the  Advanced Layer 2 Services (AL2S) !FlowSpace Firewall (FSF) feature. 
     5This page outlines testing planned for the Advanced Layer 2 Services (AL2S) !FlowSpace Firewall (FSF) feature. 
    66
    7 The tests will verify the ability of FSF to provide advertised features for various scenarios that will use both ION and AL2S GENI endpoints.  GENI slices will be set up to validate this functionality.
     7The tests will verify the ability of FSF to provide advertised features for various scenarios that will use AL2S GENI endpoints.  GENI slices will be set up to validate this functionality and using the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller], which is a GPO-developed controller based on POX.
    88
    9 The initial test plan will use a very basic Floodlight Controller as a GENI learning switch controller.  After finishing the testplan once successfully to evaluate FSFW, we may re-execute with other controllers that experimenters may want to use (e.g. POX)
     9The initial test plan will be executed with the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller] as the switch controller.  After successful completion, the GPO may re-execute test scenarios with other controllers that experimenters may want to use (e.g. FloodLight).
    1010
    1111__Test Goals__
    12   * Confirm FSF ability to support a simple GENI learning switch controller for various topologies.
    13   * Confirm FSF ability to support multiple concurrent add/delete learning switch controller requests.
     12  * Confirm FSF ability to support the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller] for various topologies.
     13  * Confirm FSF ability to support multiple concurrent add/delete requests with [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller].
    1414  * Verify rate limiting,if any, on the control plane.  (No rate limiting enforced on the AL2S data plane with FSFW)
    1515  * 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.
     
    1919
    2020    * Functional testing starts with a simple 2 node topology connected to AL2S.
    21     * All topologies are run without an active GENI !OpenFlow Controller first to verify connectivity (i.e. endpoints are connected using GENI stitching and test data is exchanged to verify end-to-end connectivity. If GENI OESS stitching is not available, we will use a combination of GENI Stitching and OESS tools to set up and verify end-to-end connectivity.)
     21    * All topologies are run without an active [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller]   first to verify connectivity (i.e. endpoints are connected using GENI stitching and test data is exchanged to verify end-to-end connectivity. If GENI AL2S stitching is not available, we will use a combination of GENI Stitching and AL2S tools to set up and verify end-to-end connectivity.)
    2222    * Once connectivity is verified, experiments are re-run with an experimenter Learning Switch !OpenFlow Controller in AL2S.
    23     * All ION to AL2S cross-connects are used to verify ability to support !OpenFlow connections to endpoints that are not on AL2S.
     23    * ~~All ION to AL2S cross-connects are used to verify ability to support !OpenFlow connections to endpoints that are not on AL2S.~~
    2424    * Each topology is verified with stitching only as a first step. Once verified, we add the experimenter !OpenFlow controller in AL2S and other relevant !OpenFlow controllers outside AL2S to the experiment.
    2525    * End-point traffic types generated include UDP, TCP, and ICMP.
     
    4444 3. Delete slices and and verify release of VLANs via AL2S router proxy.
    4545 4. Submit multiple concurrent requests to add and to delete flow spaces.
    46  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._
     46 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.
    4747 6. Query FSF status and rules via SNAPP.
    4848 7. Generate traffic outside of pre-defined flowspace and verify that it is handled properly.
     
    8686== FSF-T3 Linear Topologies tests ==
    8787
    88 Multiple concurrent linear topologies will be set up by multiple experimenters.  Topologies are run without an experimenter controller first, to verify connectivity.  Once verified, the topologies will be run with an experimenter Learning Switch !OpenFlow controller.
     88Multiple concurrent linear topologies will be set up by multiple experimenters.  Topologies are run without the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller] first, to verify connectivity.  Once verified, the topologies will be run [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller].
    8989
    9090[[Image(fsfw-test-topology-step3.jpg)]]
    9191
    92 Review of available statistics will take place to ensure that resource allocation and usage is properly captured in the available tools in AL2S Router Proxy, SNAPP, and GENI local data stores for I2 AL2S and ION.
     92Review of available statistics will take place to ensure that resource allocation and usage is properly captured in the available tools in AL2S Router Proxy, SNAPP, and GENI local data stores for I2 AL2S.
    9393
    9494
     
    106106=== Experimenter Controllers ===
    107107
    108 Each experiment will be run without the !OpenFlow Controller to verify connectivity.  Following that, we will use the GENI !OpenFlow Learning Switch controller in AL2S to enable traffic for all slices.   
     108Each experiment will be run without the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller] to verify connectivity.  Following that, we will enable the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller]to enable traffic for all AL2S slices.   
    109109
    110110
    111111=== Test Characteristics ===
     112
    112113 - Both raw-pc and Xen VMs will be used at IG end-points. 
    113114 - All experiments will request the default bandwidth allocation (100Mb/s), unless otherwise stated.