Changes between Version 19 and Version 20 of OpenFlow/Slicer/TestPlan

Timestamp:

11/14/14 10:32:31 (9 years ago)

Author:

tupty@bbn.com

Comment:

--

OpenFlow/Slicer/TestPlan

@@ -55 +55 @@
  e. Send ICMP ping traffic between the 'diffvlans' hosts and make sure it gets exchanged properly. ''(014-d)''
 
-=== Step 4: Test for OF functionality ===
+=== Step 4: Check data plane throughput ===
+ a. If it is not in place already, start a floodlight instance with static flow pusher enabled for the 'samevlan' slice.  Make sure no flows are in place.
+ b. Push flows that match traffic from one of the ports and sends the traffic to the other port in each direction.
+ c. Run a tcp iperf between the two hosts and record the results compared to the known substrate bandwidth.
+ d. Run a 1 Mbps udp iperf between the two hosts and record the results compared to the known substrate bandwidth.
+ e. Run a 10 Mbps udp iperf between the two hosts and record the results compared to the known substrate bandwidth.
+
+=== Step 5: Test for OF functionality ===
  a. Start a packet capture on the slicer facing both the switch and the controller.
  b. Push a flow_stats request from the controller.
@@ -63 +70 @@
  f. Test that ''(007-a)'', ''(007-b)'', and ''(007-c)'' all generate error messages.
 
-=== Step 5: Test for stacked slicer support ===
+=== Step 6: Test for stacked slicer support ===
  a. For 'diffvlans' stop the pox forwarding.l2_learning controller.  In its place, stand up another instance of the slicer.  In this higher-level slicer, create an identical slice for 'diffvlans' (can be done manually), and point it at a new controller URL.  At that new controller URL, run an instance of floodlight forwarding with static flow pusher.  Push down a flow that matches on the slice's VLAN for the switch and forwards traffic to the controller.
  b. Send ICMP ping data plane traffic between the 'diffvlans' hosts. ''(010)''
 
 
-=== Step 6: Test for any extra fucntionality ===
+=== Step 7: Test for any extra fucntionality ===
  a. Test that any documented control plane performance isoaltion solution works as expected. ''(011)''
  b. Test that any documented data plane performance isoaltion solution works as expected. ''(012)''
  c. Test that any per-slice flow limits work as expected. ''(012)''
 
-=== Step 7: Test API ===
+=== Step 8: Test 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)''