Changes between Version 38 and Version 39 of GENIExperimenter/Tutorials/OpenFlowOVS/Appendix

Timestamp:

07/22/14 10:52:54 (10 years ago)

Author:

Vic Thomas

Comment:

--

GENIExperimenter/Tutorials/OpenFlowOVS/Appendix

@@ -3 +3 @@
 = Appendix - Move to HW switches = 
 
-'''Notes about this tutorial:'''
+'''Notes about this tutorial'''
    * This is '''not''' a standalone tutorial.  Please refer to the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Intro to OpenFlow using OVS] for background.
    * The topology used in this experiment is the same as the one used in the  [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Intro to OpenFlow using OVS] tutorial: Three virtual machines (VMs) connected by an !OpenFLow switch. However this tutorial uses the hardware !OpenFlow switch on the rack instead of a software OVS switch.
    * You will use the same controller you developed in the previous tutorial.  Make sure it is still running.
 
-
+'''About GENI !OpenFlow switches''' [[BR]]
 GENI  offers 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.   
@@ -54 +54 @@
 {{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}}
 
-'''If you are using a shared VLAN:''' You will need to reserve your compute and flowspace resources separately using your favorite resource reservation tool (Omni, jFed, Portal).  For example, [[BR]]
+'''If you are using a shared VLAN:''' [[BR]]
+   * You will need to reserve your compute and flowspace resources separately using your favorite resource reservation tool (Omni, jFed, Portal).  For example, [[BR]]
 {{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve compute resources) [[BR]]
 {{{ omni -a max-ig-of createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve flowspace resources)