Changes between Version 6 and Version 7 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/HW/DesignSetup


Ignore:
Timestamp:
03/01/17 14:27:58 (3 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/HW/DesignSetup

    v6 v7  
    77== Step 1.  Obtain Controller 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 with Floodlight] tutorial: Three Virtual Machines (VMs) connected by an !OpenFlow switch. However this tutorial uses A hardware !OpenFlow switch instead of a software OVS switch.
     9The 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] tutorial: Three Virtual Machines (VMs) connected by an !OpenFlow switch. However this tutorial uses A hardware !OpenFlow switch instead of a software OVS switch.
    1010
    1111[[Image(GENIExperimenter/Graphics:SimpleHardwareOpenFlow.jpg,40%)]]
    1212
    13 * This experiment requires two slices; one slice for the OpenFlow Controller reservation and a second slice for the network topology that includes the compute resource for the endpoint hosts.
     13This experiment requires two slices; one slice for the OpenFlow Controller reservation and a second slice for the network topology that includes the compute resource for the endpoint hosts.
    1414
    15 * 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:
     15If 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:
    1616
    1717{{{ https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OVSFloodLight/ControllerCustom_request_rspec.xml}}}
    1818
    19 * Once the controller has been reserved, login to the allocated VM and get the routable IP Address that has been allocated to the controller node. This address will be used in the next step when the hosts topology is requested. If needed, see help on [wiki:HowTo/LoginToNodes how to login].
     19Once the controller has been reserved, login to the allocated VM and get the routable IP Address that has been allocated to the controller node. This address will be used in the next step when the hosts topology is requested. If needed, see help on
     20[wiki:HowTo/LoginToNodes how to login].
    2021
    2122
    2223=== 1.1 Find your Endpoint Hosts RSpecs ===
    2324
     25Once we have the controller allocated, we can proceed to reserving the second slice that allocates the VMs used as endpoint hosts in the topology.
    2426
    2527'''About GENI !OpenFlow switches''' [[BR]]
    26 GENI 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.
    2728
    28 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 '''bind''' each of the Xen VMs to different physical hosts.
     29GENI 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. To force the  links between the endpoint host VMs to go through the rack !OpenFlow switch, we must request that each be on separate physical hosts on the rack.  Our experiment will '''bind''' each endpoint hosts to a separate Xen VM server, i.e. to different physical hosts.
    2930
    30 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,  kansas, uky, max, stanford or wisconsin`.
     31The RSpecs for the second slice are site specific and are used to reserves the compute resources and to specify the location of your controller. 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`.
    3132
    32 ''In the URLs below, replace <AGGREGATE-NAME> with the name of the site you are using (clemson, cornell,  kansas, uky, max, stanford or wisconsin). ''
    33 
    34 The RSpec you need is at:
     33In the URLs below, replace the <AGGREGATE-NAME> with the name of the site you are using (clemson, cornell,  kansas, uky, max, stanford or wisconsin). The RSpec for the second slice is available at:
    3534
    3635{{{https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-<AGGREGATE-NAME>.rspec}}}.
    3736
    38 These 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:
     37For example, if you are working with max-ig, then you can get the sample RSPec as follows:
    3938
    40 {{{$ wget https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-max.rspec}}}
     39{{{wget https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-max.rspec}}}
    4140
    4241
    43 === 1.2 Edit your RSpecs ===
     42=== 1.2 Edit your Endpoint Hosts RSpecs ===
    4443
    4544Open 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:
     
    4948
    5049
     50=== 1.3 Reserve Endpoint Hosts Resources ===
    5151
    52 === 1.3 Reserve Resources ===
     52Use your favorite resource reservation tool (Omni, jFed, Portal) to reserve your resources.  For example, if you are using Omni and the MAX IG aggregate:
    5353
    54   * Use your favorite resource reservation tool (Omni, jFed, Portal) to reserve your resources.  For example, if you are using Omni and the MAX aggregate:
    55 {{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}}
     54{{{omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}}
    5655
    5756
     
    6766
    6867=== 2a. Configure the Controller for the Hardware Switch: Useful Tips ===
     68
    6969==== Which port is connected to which host ====
    7070