Changes between Version 6 and Version 7 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/HW/DesignSetup
- Timestamp:
- 03/01/17 14:27:58 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/HW/DesignSetup
v6 v7 7 7 == Step 1. Obtain Controller Resources == 8 8 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.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. 10 10 11 11 [[Image(GENIExperimenter/Graphics:SimpleHardwareOpenFlow.jpg,40%)]] 12 12 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.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. 14 14 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: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: 16 16 17 17 {{{ https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OVSFloodLight/ControllerCustom_request_rspec.xml}}} 18 18 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]. 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 20 [wiki:HowTo/LoginToNodes how to login]. 20 21 21 22 22 23 === 1.1 Find your Endpoint Hosts RSpecs === 23 24 25 Once we have the controller allocated, we can proceed to reserving the second slice that allocates the VMs used as endpoint hosts in the topology. 24 26 25 27 '''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.27 28 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 VMsto different physical hosts.29 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. 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. 29 30 30 The RSpecs for th is 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`.31 The 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`. 31 32 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: 33 In 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: 35 34 36 35 {{{https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OpenFlowHW/pvtVlan/ig-<AGGREGATE-NAME>.rspec}}}. 37 36 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:37 For example, if you are working with max-ig, then you can get the sample RSPec as follows: 39 38 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}}} 41 40 42 41 43 === 1.2 Edit your RSpecs ===42 === 1.2 Edit your Endpoint Hosts RSpecs === 44 43 45 44 Open 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: … … 49 48 50 49 50 === 1.3 Reserve Endpoint Hosts Resources === 51 51 52 === 1.3 Reserve Resources === 52 Use your favorite resource reservation tool (Omni, jFed, Portal) to reserve your resources. For example, if you are using Omni and the MAX IG aggregate: 53 53 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 }}} 56 55 57 56 … … 67 66 68 67 === 2a. Configure the Controller for the Hardware Switch: Useful Tips === 68 69 69 ==== Which port is connected to which host ==== 70 70