Changes between Version 27 and Version 28 of GENIFlowSpaceFirewallTests
- Timestamp:
- 05/08/14 18:14:02 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIFlowSpaceFirewallTests
v27 v28 82 82 83 83 ---- 84 Conduct 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. 84 85 85 86 == FSF-T3 Linear Topologies tests == 86 87 87 Multiple concurrent linear topologies will be set up by multiple experimenters. Topologies are run without an experimenter controller first, to verify setup. Once verified, the topologies will be run with an experimenter Learning Switch !OpenFlow controller.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. 88 89 89 90 [[Image(fsfw-test-topology-step3.jpg)]] 90 91 91 Review of available statistics will take place to ensure that resource allocation and usage is properly captured in the available tools AL2S Router Proxy.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. 92 93 93 94 … … 96 97 == FSF-T4 Star Topology tests == 97 98 98 A version of this topology will be set up by multiple users:99 A version of this topology will be set up to support multiple simultaneous experiments: 99 100 100 101 [[Image(fsfw-test-topology-step4.jpg)]] … … 105 106 === Experimenter Controllers === 106 107 107 Each experiment will be run without and experimenter defined !OpenFlow Controller. Once shown to work, the experiment will add a user defined !OpenFlow Learning Switch controller.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. 108 109 109 Majority of !OpenFlow test cases will be executed with !FloodLight 0.90 Learning Switch !OpenFlow Controller, although other experimenter controllers will be tries, such as POX 0.1.0.110 110 111 111 === Test Characteristics === 112 - Both raw-pc and Xen VM will be used asIG end-points.113 - All experiment will request the default bandwidth allocation (100Mb/s), unless otherwise stated.112 - Both raw-pc and Xen VM swill be used at IG end-points. 113 - All experiments will request the default bandwidth allocation (100Mb/s), unless otherwise stated. 114 114 - All 10 ION to AL2S cross-connects will be verified, but the majority of testing will use LOSA, KANS, and ATLA cross-connects. 115 115 … … 117 117 === Experimenter Generated traffic === 118 118 119 Iperf will be used to generate TCP and UDP traffic for 60 seconds test runs. For iperf TCP traffics, results will be collected for 1, 5 and 10 clients. Commands used:119 Iperf will be used to generate TCP and UDP traffic for short (60 second test) runs. For iperf TCP traffic, results will be collected for 1, 5 and 10 clients. Commands used: 120 120 - iperf '1 client' scenario command: 'iperf -c dest_host -t 60' 121 121 - iperf '5 clients' scenario command: 'iperf -c dest_host -t 60 -P 5' 122 122 - iperf '10 clients' scenario command: 'iperf -c dest_host -t 60 -P 10' 123 123 124 Iperf UDP measurements will request 100 Mbits/sec , based on results will increasedor decrease bandwidth requests.124 Iperf UDP measurements will request 100 Mbits/sec. Based on results, we will increase or decrease bandwidth requests. 125 125 126 126 Ping statistics will run for 60 seconds to capture network delay.
