Changes between Version 3 and Version 4 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/HW/DesignSetup


Ignore:
Timestamp:
03/01/17 13:24:29 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/HW/DesignSetup

    v3 v4  
    11= OpenFlow using a Hardware Switch =
    22
    3 This page provides a guide on how to do the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight OpenFlowOVS tutorial] using the Hardware OpenFlow switches present at the IG racks. This can serve as a general guide on how to use the OpenFlow Hardware switches.
     3This page provides a guide on how to do the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight OpenFlowOVS with Floodlight tutorial] using the Hardware OpenFlow switches available in the InstaGENI (IG) racks. This can serve as a general guide on how to use the OpenFlow Hardware switches.
    44
    55[[PageOutline]]
    … …  
    77== Step 1.  Obtain resources ==
    88
    9    * The topology used in this experiment is the same as the one used in the  [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/DesignSetup OpenFlow using OVS] part of this 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.
    10    * If you have not reserved a controller yet, make sure to create a slice that will run the !OpenFlow controller by reserving a VM running the controller using the request RSpec [https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OVSFloodLight/ControllerCustom_request_rspec.xml] .
     9   * The topology used in this experiment is the same as the one used in the  [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/DesignSetup OpenFlow using OVS with Floodlight] part of this 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.
     10
     11   * If you have not reserved a controller yet, make sure to create a slice that will run the !OpenFlow controller by reserving a VM running the controller using the request RSpec:
     12{{{ [https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OVSFloodLight/ControllerCustom_request_rspec.xml]}}}
     13
    1114
    1215[[Image(GENIExperimenter/Graphics:SimpleHardwareOpenFlow.jpg,40%)]]
    … …  
    1417
    1518'''About GENI !OpenFlow switches''' [[BR]]
    16 GENI  offers access to hardware !OpenFlow switches. Each !OpenFlow switch, in most cases, can support only one controller.  On the IG racks the switch is sliced based on VLANs, so each VLAN is its own virtual datapath.
     19GENI offers access to hardware !OpenFlow switches, which in most cases can support only one controller.  On the InstaGENI racks the switch is sliced based on VLANs, so each VLAN is its own virtual datapath.
    1720
    18 To force the  links between the VMs to go through the rack !OpenFlow switch, the three VMs must be on separate physical hosts on the rack.  Our experiment will:
    19    * Bind the Xen VMs to different physical hosts.
     21To force the  links between the VMs to go through the rack !OpenFlow switch, the three VMs must be on separate physical hosts on the rack.  Our experiment will '''bind''' each of the Xen VMs to different physical hosts.
    2022
    21 === 1.1 Find your RSPecs ===
     23=== 1.1 Find your RSpecs ===
    2224
    23 The RSpecs for this tutorial are site specific. If you are attending a tutorial, use the site and IP network that was given to you on your worksheet. If you are doing this at home, choose a site from : `clemson, cornell, gatech, gpo, illinois, kansas, uky, kettering, max, missouri, northwestern, nysernet, nyu, sox, stanford, wisconsin`.
     25The RSpecs for this tutorial are site specific. If you are attending a tutorial, use the site and IP network that was given to you on your worksheet. If you are doing this at home, choose a site from : `clemson, cornell,  kansas, uky, max, stanford or wisconsin`.
    2426
    2527''In the URLs below, replace <AGGREGATE-NAME> with the name of the site you are using (clemson, cornell,  kansas, uky, max, stanford or wisconsin). ''
    2628
    2729The RSpec you need is at:
    28     * {{{https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-<AGGREGATE-NAME>.rspec}}}. (Reserves compute resources and specifies location of your controller). For example, if you are working with max-ig, then you can get the sample RSPec as follows:
    2930
    30  {{{$ wget https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-max.rspec}}}
     31{{{https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-<AGGREGATE-NAME>.rspec}}}.
     32
     33These RSpecs can be used to reserves compute resources and to specify the location of your controller. For example, if you are working with max-ig, then you can get the sample RSPec as follows:
     34
     35{{{$ wget https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-max.rspec}}}
    3136
    3237
    3338=== 1.2 Edit your RSpecs ===
    3439
    35 Open your RSpec in a text editor to make the following changes:
     40Open your RSpec in a text editor to insert the IP address of your controller. Done by replacing the string <CONTROLLER_IP> at the bottom of the RSpec with the IP address of your controller.  The controller line looks as follows:
     41 
     42{{{<emulab:openflow_controller url="tcp:CONTROLLER_IP:6633"/>}}}
    3643
    37     * Replace the string <CONTROLLER_IP> (at the bottom of the RSpec) with the IP address of your controller.
    3844
    3945