Changes between Version 9 and Version 10 of GENIOESSTopologiesTestStatus/OESS-TC2
- Timestamp:
- 09/19/14 12:30:27 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIOESSTopologiesTestStatus/OESS-TC2
v9 v10 34 34 = Test Details = 35 35 36 Each test case exchanges describe traffic types (TCP, UDP, ICMP) for 60 seconds, tools used are iperf and ping.37 38 36 The RSpec [http://groups.geni.net/geni/browser/trunk/OESSRSpecs/stitch-ig-gpo-ig-stan.rspec stitch-ig-gpo-ig-stan.rspec] is used for all of the 10 test cases captured in this page. Each of the potential stitching paths are requested by using the stitcher option --excludeHop. The available cross-connects are: 39 37 … … 51 49 The Stitching Computation Service suggests the cross connect to be used used for stitching paths in the alphabetical order with Atlanta being the default. If the --excludeHop specifies the Atlanta urn then the Chicago hop will be used. If Atlanta and Chicago URNs are excluded then the next hop Houston in the list is used, and so on. 52 50 53 All VM end-point hosts used in these test cases are Xen hosts. All traffic results are over 60 seconds periods. 54 51 All VM end-point hosts used in these test cases are Xen hosts. Each test case exchanges describe traffic types (TCP, UDP, ICMP) for 60 seconds, tools used are iperf and ping. 55 52 56 53 == ION Site to AL2S site via Atlanta Cross Connect (default) ==