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


Ignore:
Timestamp:
07/22/14 10:52:54 (5 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/OpenFlowOVS/Appendix

    v38 v39  
    33= Appendix - Move to HW switches =
    44
    5 '''Notes about this tutorial:'''
     5'''Notes about this tutorial'''
    66   * This is '''not''' a standalone tutorial.  Please refer to the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Intro to OpenFlow using OVS] for background.
    77   * 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.
    88   * You will use the same controller you developed in the previous tutorial.  Make sure it is still running.
    99
    10 
     10'''About GENI !OpenFlow switches''' [[BR]]
    1111GENI  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:
    1212   1. By VLAN id.  This is used when each slice has its own VLANs.   
     
    5454{{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}}
    5555
    56 '''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]]
     56'''If you are using a shared VLAN:''' [[BR]]
     57   * You will need to reserve your compute and flowspace resources separately using your favorite resource reservation tool (Omni, jFed, Portal).  For example, [[BR]]
    5758{{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve compute resources) [[BR]]
    5859{{{ omni -a max-ig-of createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve flowspace resources)