Changes between Version 37 and Version 38 of GENIFlowSpaceFirewallTests


Ignore:
Timestamp:
02/02/15 14:24:31 (9 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIFlowSpaceFirewallTests

    v37 v38  
    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 related to FSF.
    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.
     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.~~ The [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller] was run through the Internet2 qualification process and will be used for testing scenarios in this test plan.
    1717
    1818__Assumptions__
    1919
    2020    * Functional testing starts with a simple 2 node topology connected to AL2S.
    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.)
    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.
     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.)
     22    * Once connectivity is verified, experiments are re-run with the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller].
     23    * Some scenarios will be used to verify ability to support !OpenFlow connections to endpoints that are not on AL2S. This may be necessary for sites such as University of Utah, which may not migrate to AL2S initially.
     24    * Each topology is verified with stitching only as a first step. Once verified, we add the [http://trac.gpolab.bbn.com/al2sofctrl GeniSiteMon Controller] in AL2S and any other relevant !OpenFlow controllers outside AL2S to the experiment.
    2525    * End-point traffic types generated include UDP, TCP, and ICMP.
    2626    * 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.)
    … …  
    3333== FSF-T1 Two Sites Functional tests ==
    3434
    35 Initial testing will take place with two sites that are already connected to AL2S.  Multiple slivers will be created by multiple "experimenters."  (All experimenters will actually be GPO staff.)
     35Initial testing will take place with two sites that are already connected to AL2S.  Multiple slivers will be created by multiple "experimenters".  (All experimenters ids are for GPO staff.)
    3636
    3737[[Image(fsfw-test-topology-step1.jpg)]]
    38 
    3938
    4039Functional testing is executed within these simple node experiments:
    … …  
    5049 9. Request network capacity beyond configured FSF capacity, verify that request fails.
    5150
    52 {{{
    53 #!comment
    54 Network Connection details for this 2 node topology:
     51== FSF-T2 AL2S interconnects tests ==
    5552
    56 __Missouri InstaGENI:__[[BR]]
    57 Site VLANs: 1150-1160      -    AL2S end-point: KANS  [[BR]]
    58 ION cross connect: urn:publicid:IDN+ion.internet2.edu+interface+rtr.kans:xe-0/0/3:missouri-ig  [[BR]]
    59 
    60 __Stanford InstaGENI:__ [[BR]]
    61 Site VLANs: 1630-1639      -   AL2S end-point: SUNN  [[BR]]
    62 ION cross connect: urn:publicid:IDN+ion.internet2.edu+interface+rtr.salt:xe-0/1/1:stanford-ig
    63 }}}
    64 
    65 
    66 == FSF-T2 ION to AL2S interconnects tests ==
    67 
    68 ''' This test may only be executed if ION sites still remain when this plan is executed'''
    69 
    70 Both slices shown will be setup using each of the 10 interconnects between ION and AL2s:
     53This test may be executed for sites the may not transition to ION in the time frame of this plan.   Both slices shown will be setup using each of the 10 interconnects between ION and AL2s:
    7154
    7255[[Image(fsfw-test-topology-step2.jpg)]]
    7356
    74 ''' This test may only be executed if ION sites still remain when this plan is executed'''
     57'' This test may only be executed if a GENI site remains on ION and has not transitioned to AL2S when this plan is executed.''
    7558
    7659__ION to AL2S cross-connects__ [[BR]]
    … …  
    8871 10. sdn-sw.wash e5/2 <-> rtr.wash:port=et-9/0/0
    8972
    90 ----
     73
    9174Conduct functional testing similar to that specified in FSF-T1 for these slices.  Control plane limits and out-of-range VLAN tests from FSF-T1 will only be conducted for two simultaneously active slices, because the topology changes should not affect those tests.
    9275
    … …  
    118101=== Test Characteristics ===
    119102
    120  - Both raw-pc and Xen VMs will be used at IG end-points. 
     103 - Both raw-pc and Xen VMs will be used at InstaGENI end-points. 
    121104 - All experiments will request the default bandwidth allocation (100Mb/s), unless otherwise stated.
    122  - ~~All 10 ION to AL2S cross-connects will be verified, but the majority of testing will use LOSA, KANS, and ATLA cross-connects.~~
    123  
     105
    124106
    125107=== Experimenter Generated traffic ===