Changes between Version 23 and Version 24 of OpenFlow/Slicer/TestPlan

Timestamp:

11/14/14 11:04:56 (9 years ago)

Author:

tupty@bbn.com

Comment:

--

OpenFlow/Slicer/TestPlan

@@ -95 +95 @@
 === 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.  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 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)''
 
 === Step 2: Collect monitoring data ===
@@ -103 +103 @@
  a. Create a new slice 'testslice', use the modified pox forwarding.l2_learning controller, and ensure that pings in the other slices continue to flow.  Ensure that this slice is added with no operator intervention. ''(004)'' ''(001-a)''
  b. Change the controller URL for 'testslice'.  Ensure that the change takes place with no operator intervention. ''(001-c)''
- c. If a slicer is capable of disabling a slice, trigger 'testslice' to get disabled.  Ensure that the slicer owner either gets notified, or that at the very least, 'dump_slices' shows that the slice is disabled.  Re-enable the slice if it was disabled. ''(001-d)''
- d. Disconnect the controller.  Wait for about a minute, and try sending traffic.  Ensure that it doesn't get through. ''(008)''
+ c. If a slicer is capable of disabling a slice, trigger 'testslice' to get disabled.  Ensure that either the slicer owner either gets notified, or that 'dump_slices' shows that the slice is disabled.  Administratively re-enable the slice if it was disabled. ''(001-d)''
+ d. Disconnect the 'testslice' controller.  Wait for about a minute, and try sending ICMP ping traffic in the data plane.  Ensure that it doesn't get through. ''(008)''
  e. Delete the slice and make sure that doing so does not require operator intervention.  Check right away and make sure all flows for that slice have been removed. ''(001-b)'' ''(009)''
 
@@ -116 +116 @@
  c. Look at the entries for the log.  Any entries that exist in the default case should be reasonable.  At this point, the size of the log should also be reasonable. ''(006-a)''
  d. Try changing the log level while the slicer is running to the most verbose level.  Verify that the logs are showing more data. ''(006-b)''
- e. Set the logging back to a standard level.  Leave the setup running overnight.  In the morning, verify that the logs have been rotated, and that logging is still working. ''(006-c)''
+ e. Set the logging back to a standard level.  Leave the setup running overnight.  In the morning, verify that the logs have been rotated, the logs are of reasonable size, and that logging is still working. ''(006-c)''
 
 == OF-OPR-SLCR-SW Testing ==
@@ -126 +126 @@
  e. Work with the development team to make sure they can satisfy remaining software requirements. ''(005)'' ''(006)'' ''(008)''
 
-== Wishlist Testing ==
+== Wishlist Testing (on request) ==
 === Step 1: Check documentation ===
  * Does the software come in a package?  If so, are there instructions for installing the software as a package?
@@ -143 +143 @@
  * Remove the higher-priority flows and make sure that traffic flows again.
 
-= Test Methodology =
-Describe how testing is to be conducted, how issues are to be tracked, how status will be made available.
-Describe how test cases are named.
-