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

Timestamp:

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

Author:

tupty@bbn.com

Comment:

--

OpenFlow/Slicer/TestPlan

@@ -128 +128 @@
 == 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?
- * Is untagged traffic supported in the slicer?  If so, does the documentation show how to reserve the untagged space on a port?
- * Is data plane isolation supported (unlikely until future OpenFlow versions are supported)?
+ a. Does the software come in a package?  If so, are there instructions for installing the software as a package?
+ b. Is untagged traffic supported in the slicer?  If so, does the documentation show how to reserve the untagged space on a port?
+ c. Is data plane isolation supported (unlikely until future OpenFlow versions are supported)?
  
 === Step 2: Set up the environment ===
- * Create a slice that uses two ports that connect two hosts in a slice.  Use untagged space on those ports if possible.
- * Run Floodlight static flow pusher, and push down a set of flows that will forward traffic between the two ports.
- * Make sure that you can exchange traffic between the hosts.
+ a. Create a slice that uses two ports that connect two hosts in a slice.  Use untagged space on those ports if possible.
+ b. Run Floodlight static flow pusher, and push down a set of flows that will forward traffic between the two ports.
+ c. Make sure that you can exchange traffic between the hosts.
 
 === Step 3: Test that priority setting works ===
- * Install an identical set of flows with a higher priority and no actions.  When doing this, do not remove the old rules.
- * If possible, check the flow table and ensure that all four of the flows are in the flow table.
- * Ensure that traffic is not exchanged between the hosts.
- * Remove the higher-priority flows and make sure that traffic flows again.
+ a. Install an identical set of flows with a higher priority and no actions.  When doing this, do not remove the old rules.
+ b. If possible, check the flow table and ensure that all four of the flows are in the flow table.
+ c. Ensure that traffic is not exchanged between the hosts.
+ d. Remove the higher-priority flows and make sure that traffic flows again.