Changes between Version 13 and Version 14 of GENIFlowSpaceFirewallTests


Ignore:
Timestamp:
05/07/14 09:28:53 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIFlowSpaceFirewallTests

    v13 v14  
    2020    * End-point traffic types generated will include UDP, TCP, ICMP using various tools.
    2121
    22 == FSF-T1 Functional Tests ==
     22== FSF-T1 Two Sites Functional tests ==
    2323
    24  1. Create slice which results in VLANs allocation between AL2S InstaGENI end-point
    25  2. Delete VLANs and verify release of VLANs via AL2S router proxy.
    26  3. Submit multiple concurrent requests to add and to delete flow spaces.
    27  4. Configure various rate limits and verify enforcement. 
    28  4. Query FSF status and rules via !FloodLight rest API.
    29  5. Generate traffic outside of pre-defined flowspace and verify that it is handled properly.
    30 
    31 = Topology Scenarios =
    32 
    33 == FSF-T2 Two Site tests ==
    34 
    35 Initial testing will take place with two sites that are already connected to AL2S.  Multiple slivers will be created by multiple experimenters.  Functional testing will be executed in this topology.
     24Initial testing will take place with two sites that are already connected to AL2S.  Multiple slivers will be created by multiple experimenters.
    3625
    3726[[Image(fsfw-test-topology-step1.jpg)]]
     27
     28
     29Functional testing is executed within these simple node experiments:
     30
     31 1. Create slice which results in VLANs allocation between AL2S InstaGENI end-point and exchange traffic. Verify AL2S router proxy statistics.
     32 2. Create slices to use configured number of VLANs, verify configuration is enforced and reflected in AL2S router proxy statistics.
     33 3. Delete slices and and verify release of VLANs via AL2S router proxy.
     34 4. Submit multiple concurrent requests to add and to delete flow spaces.
     35 5. Configure various rate limits and verify enforcement. 
     36 6. Query FSF status and rules via !FloodLight rest API.
     37 7. Generate traffic outside of pre-defined flowspace and verify that it is handled properly.
     38 8. Create slice requesting specific VLAN outside of FSFW range, verify rejection.
     39 9. Request network capacity beyond configured FSFW capacity, verify enforcement.
    3840
    3941Network Connection details for this 2 node topology:
    4042
    4143__Missouri InstaGENI:__[[BR]]
    42 VLANs: 1150-1160   [[BR]]
    43 AL2S end-point: KANS  [[BR]]
     44VLANs: 1150-1160      AL2S end-point: KANS  [[BR]]
    4445ION cross connect: urn:publicid:IDN+ion.internet2.edu+interface+rtr.kans:xe-0/0/3:missouri-ig  [[BR]]
    4546
    4647__Stanford InstaGENI:__ [[BR]]
    47 VLANs: 1630-1639  [[BR]]
    48 AL2S end-point: SUNN  [[BR]]
     48VLANs: 1630-1639      AL2S end-point: SUNN  [[BR]]
    4949ION cross connect: urn:publicid:IDN+ion.internet2.edu+interface+rtr.salt:xe-0/1/1:stanford-ig
    5050