Changes between Version 35 and Version 36 of OpenFlow/Slicer/TestPlan

Timestamp:

04/28/15 09:41:33 (9 years ago)

Author:

tupty@bbn.com

Comment:

--

OpenFlow/Slicer/TestPlan

@@ -103 +103 @@
 === Step 1: Setup ===
  a. Clear any existing log files that the slicer may have created.
- b. Create 10 slices named slice{1-10}.  Each slice should have a single unique VLAN ID spanning across 10 switches between two hosts.  For each of these slices, install static flows for passing traffic between the hosts.  Generate ping traffic from a host at the end of each of the slices and make sure it is working.  Leave this traffic running for the duration of this scenario. ''(003)''
+ b. Create 10 slices named slice{1-10}.  Each slice should have a single unique VLAN ID spanning across one switch between two hosts.  For each of these slices, install static flows for passing traffic between the hosts.  Generate ping traffic from a host at the end of slice1 make sure it is working.  Leave this traffic running for the duration of this scenario. ''(003)''
+ c. Attach another host which is in a VLAN that doesn't correspond to any slice.
 
 === Step 2: Collect monitoring data ===
@@ -116 +117 @@
 
 === Step 4: Substrate-generated traffic ===
- a. Connect a host to the substrate that is not part of a slice, and that does not share a data plane port with the other slices.  Send a high rate of traffic out of its data plane interface and ensure that the other slices remain stable. ''(007)''
+ a. From the attached host which is not in a VLAN that has a corresponding slice, send a high rate of traffic out of its data plane interface and ensure that the other slices remain stable. ''(007)''
  b. Try sending traffic that the slicer cannot process (e.g. non-OpenFlow traffic or an OpenFlow version that the slicer doesn't currently understand) directly to the southbound interface of the slicer.  Make sure the slicer remains stable. ''(011)''