Changes between Version 26 and Version 27 of GENIExperimenter/Tutorials/OpenFlowOVS/Appendix

Timestamp:

07/21/14 23:45:02 (10 years ago)

Author:

Vic Thomas

Comment:

--

GENIExperimenter/Tutorials/OpenFlowOVS/Appendix

@@ -1 +1 @@
 = Appendix - Move to HW switches = 
 
-'''Note:" This is not a standalone tutorial.  Please refer to the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Intro to OpenFlow using OVS] for background.
+'''Note:" This is not a standalone tutorial.  Please refer to the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Intro to !OpenFlow using OVS] for background.
+
+GENI and FIRE offer access to hardware !OpenFlow switches. Each !OpenFlow switch in most cases can support only one controller.  There are two ways of slicing the controller flowspace:
+   1. By VLAN id.  This is used when each slice has its own VLANs.   For instructions to use the !OpenFlow switches with private VLANs, see [].
+   2. By IP addresses.  This is used when multiple slices share the same VLAN.  For example, the GENI mesoscale VLAN.  For instructions, see [].
+
+== Using Hardware OpenFlow switches using Private VLANs ==
+
+=== Design/Setup ===
 
 
-GENI and FIRE offer access to hardware OpenFlow switches. Each OpenFlow switch in most cases can support only one controller. To enable sharing of the resources many times a slicer (FlowVIsor) and an OpenFlow specific AM (FOAM) is used. 
+
+
+
+
+
+To enable sharing of the resources many times a slicer (FlowVIsor) and an OpenFlow specific AM (FOAM) is used. 
+
+
+
+
+
+
+
+
 
 In GENI there is a common VLAN that has been setup for all the GENI racks and within this VLAN experimenters can reserve a flowspace based on IP or eth_type. Experimenter can also obtain a private VLAN only for their slice. For this tutorial we are going to use the common VLAN that has been setup.