Changes between Version 25 and Version 26 of GENIFlowSpaceFirewallTests


Ignore:
Timestamp:
05/08/14 16:57:51 (6 years ago)
Author:
hdempsey@bbn.com
Comment:

minor rewording

Legend:

Unmodified
Added
Removed
Modified
  • GENIFlowSpaceFirewallTests

    v25 v26  
    55This 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 setup to validate the functionality.
     7The 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.
     8
     9The 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)
    810
    911__Test Goals__
    10   * FSF ability to support a simple learning switch controller for various topologies.
    11   * FSF ability to support multiple concurrent add/delete learning switch controller request.
    12   * Verify ability to use different learning switch controller implementations (FloodLight, POX)
     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.
    1314  * Verify rate limiting
    14   * Ability to query statistics for switch, links, firewall rules with !FloodLight rest API.
     15  * Confirm ability to query statistics for switch, links, firewall rules with !FloodLight rest API.
     16  * 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.
    1517
    1618__Assumptions__
    1719
    18     * Functional testing will start with simple 2 node topology connected to AL2s.
    19     * All topologies are run without an experimenter !OpenFlow Controller first to verify connectivity. 
    20     * Once connectivity is verified, experiments are re-run with an experimenter Learning Switch !OpenFlow Controller.
    21     * All ION to AL2S cross-connects will be used to verify ability to support !OpenFlow connections.
    22     * Each topology is verify with stitching only as a first step. Once verified !OpenFlow is added to the experiment.
    23     * End-point traffic types generated will include UDP, TCP, ICMP using various tools.
    24     * Layer 2 hardware matching is validated, there is no Layer 3 matching at this time.
    25     * Tests are described in this plan with the assumption that GENI networks stitching is available from OESS.
     20    * 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.)
     22    * 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.
     24    * 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.
     25    * End-point traffic types generated include UDP, TCP, and ICMP.
     26    * Layer 2 hardware matching is validated.  There is no Layer 3 matching at this time.  (Layer 3 matching tests will be done when AL2S makes that capability available.)
     27    * Tests are described in this plan with the assumption that GENI network stitching is available from OESS.
    2628    * OESS may not be available, so sliver creation may be done in 2 steps:
    2729       - AL2S circuits will be set up to connect the edge ports.
    28        - Stitched slivers fixed AL2S endpoint are created for IG sites.
     30       - Stitched slivers with fixed AL2S endpoints are created for IG sites.
    2931
    3032== FSF-T1 Two Sites Functional tests ==