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


Ignore:
Timestamp:
11/14/14 11:11:11 (5 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/Slicer/TestPlan

    v24 v25  
    128128== Wishlist Testing (on request) ==
    129129=== Step 1: Check documentation ===
    130  * Does the software come in a package?  If so, are there instructions for installing the software as a package?
    131  * Is untagged traffic supported in the slicer?  If so, does the documentation show how to reserve the untagged space on a port?
    132  * Is data plane isolation supported (unlikely until future OpenFlow versions are supported)?
     130 a. Does the software come in a package?  If so, are there instructions for installing the software as a package?
     131 b. Is untagged traffic supported in the slicer?  If so, does the documentation show how to reserve the untagged space on a port?
     132 c. Is data plane isolation supported (unlikely until future OpenFlow versions are supported)?
    133133 
    134134=== Step 2: Set up the environment ===
    135  * Create a slice that uses two ports that connect two hosts in a slice.  Use untagged space on those ports if possible.
    136  * Run Floodlight static flow pusher, and push down a set of flows that will forward traffic between the two ports.
    137  * Make sure that you can exchange traffic between the hosts.
     135 a. Create a slice that uses two ports that connect two hosts in a slice.  Use untagged space on those ports if possible.
     136 b. Run Floodlight static flow pusher, and push down a set of flows that will forward traffic between the two ports.
     137 c. Make sure that you can exchange traffic between the hosts.
    138138
    139139=== Step 3: Test that priority setting works ===
    140  * Install an identical set of flows with a higher priority and no actions.  When doing this, do not remove the old rules.
    141  * If possible, check the flow table and ensure that all four of the flows are in the flow table.
    142  * Ensure that traffic is not exchanged between the hosts.
    143  * Remove the higher-priority flows and make sure that traffic flows again.
     140 a. Install an identical set of flows with a higher priority and no actions.  When doing this, do not remove the old rules.
     141 b. If possible, check the flow table and ensure that all four of the flows are in the flow table.
     142 c. Ensure that traffic is not exchanged between the hosts.
     143 d. Remove the higher-priority flows and make sure that traffic flows again.
    144144