Changes between Version 26 and Version 27 of OpenFlow/Slicer/TestPlan

Timestamp:

11/20/14 11:49:56 (9 years ago)

Author:

tupty@bbn.com

Comment:

--

OpenFlow/Slicer/TestPlan

@@ -80 +80 @@
 
 
-=== Step 7: Test for any extra fucntionality ===
- a. Test that any documented control plane performance isoaltion solution works as expected.  Consider using the following modules from OFTest: PacketInLoad, FlowModLoad, PacketOutLoad, FlowRemovedLoad. ''(011)''
- b. Test that any documented data plane performance isoaltion solution works as expected.  This will involve appropriately setting up two slices, proactively installing flows, and starting UDP iperfs to make sure expected throughput is matched. ''(012)''
+=== Step 7: Test for any extra functionality ===
+ a. Test that any documented control plane performance isolation solution works as expected.  Consider using the following modules from OFTest: PacketInLoad, FlowModLoad, PacketOutLoad, FlowRemovedLoad. ''(011)''
+ b. Test that any documented data plane performance isolation solution works as expected.  This will involve appropriately setting up two slices, proactively installing flows, and starting UDP iperfs to make sure expected throughput is matched. ''(012)''
  c. Test that any per-slice flow limits work as expected.  Consider using the OFTest FlowModLoad test or Floodlight static flow pusher. ''(012)''
 
-=== Step 8: Test API ===
+=== Step 8: Test management API ===
  a. Call dump_slices and make sure it works as expected.  Ensure it returns which slices are active and which are disabled along with however the AM identifies the slices. ''(005-d)'' ''(008-b)'' ''(008-c)''
  b. Call change_controller and make sure it is reflected in the slicer state ''(005-c)''