Changes between Version 27 and Version 28 of GENIFlowSpaceFirewallTests


Ignore:
Timestamp:
05/08/14 18:14:02 (5 years ago)
Author:
hdempsey@bbn.com
Comment:

minor wording changes

Legend:

Unmodified
Added
Removed
Modified
  • GENIFlowSpaceFirewallTests

    v27 v28  
    8282
    8383----
     84Conduct 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.
    8485
    8586== FSF-T3 Linear Topologies tests ==
    8687
    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.
     88Multiple 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.
    8889
    8990[[Image(fsfw-test-topology-step3.jpg)]]
    9091
    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.
     92Review 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.
    9293
    9394
     
    9697== FSF-T4 Star Topology tests ==
    9798
    98 A version of this topology will be set up by multiple users:
     99A version of this topology will be set up to support multiple simultaneous experiments:
    99100
    100101[[Image(fsfw-test-topology-step4.jpg)]]
     
    105106=== Experimenter Controllers ===
    106107
    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. 
     108Each 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.  
    108109
    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.
    110110
    111111=== Test Characteristics ===
    112  - Both raw-pc and Xen VM will be used as IG 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.
    114114 - All 10 ION to AL2S cross-connects will be verified, but the majority of testing will use LOSA, KANS, and ATLA cross-connects.
    115115 
     
    117117=== Experimenter Generated traffic ===
    118118
    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:
     119Iperf 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:
    120120    - iperf '1 client' scenario command: 'iperf -c dest_host -t 60'
    121121    - iperf '5 clients' scenario command: 'iperf -c dest_host -t 60 -P 5'
    122122    - iperf '10 clients' scenario command: 'iperf -c dest_host -t 60 -P 10'
    123123
    124 Iperf UDP measurements will request 100 Mbits/sec, based on results will increased or decrease bandwidth requests.
     124Iperf UDP measurements will request 100 Mbits/sec.  Based on results, we will  increase or decrease bandwidth requests.
    125125
    126126Ping statistics will run for 60 seconds to capture network delay.