Changes between Version 8 and Version 9 of GENIFlowSpaceFirewallTests

Timestamp:

05/06/14 17:11:01 (10 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIFlowSpaceFirewallTests

@@ -9 +9 @@
   * FSF ability to support multiple concurrent add/delete learning switch controller request. 
   * Verify ability to use different learning switch controller implementations (FloodLight, POX)
+  * Verify rate limiting
   * Ability to query statistics for switch, links, firewall rules with FloodLight rest API. 
 
@@ -24 +25 @@
  2. Delete VLANs and verify release of VLANs via AL2S router proxy. 
  3. Submit multiple concurrent requests to add and to delete flow spaces.
+ 4. Configure various rate limits and verify enforcement.  
  4. Query FSF status and rules via FloodLight rest API.
  5. Generate traffic outside of pre-defined flowspace and verify that it is handled properly.
@@ -83 +85 @@
 [[Image(fsfw-test-topology-step4.jpg)]]
 
+== 2.1 Test Methodology ==
+
+Test Characteristics:
+ - All test hosts are dedicate hosts (bare metal/raw-pc) unless otherwise stated
+ - All results are captured for default bandwidth allocation (100Mb/s shaped), unless otherwise stated. 
+ - All results collected between January 2014
+
+Iperf TCP measurements captured in this page have the following assumptions:
+ - All results are for a 60 second test run.
+ - For !OpenFlow scenarios, traffic is exchanged before each of the measurements below to establish data flows:
+    - iperf '1 client' scenario command: 'iperf -c dest_host -t 60'
+    - iperf '5 clients' scenario command: 'iperf -c dest_host -t 60 -P 5'
+    - iperf '10 clients' scenario command: 'iperf -c dest_host -t 60 -P 10'
+
+Iperf UDP measurements captured in this page have the following assumptions:
+ - Each test run is 60 seconds and traffic is exchanged before each of the measurements to establish a data flow.
+ - UDP measurements between racks requested a bandwidth of 100 Mbits/sec, if results showed that 100Mb/s was possible, then increased to 1Gb/s.
+