Context Navigation

Execute

Timestamp:: 07/19/13 22:37:57 (11 years ago)
Author:: nriga@bbn.com
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

GEC17Agenda/AdvancedOpenFlow/Procedure/Execute

-                      v2
+                      v3
 == 2.1 Run an example Load Balancing OpenFlow Controller ==
   An example OpenFlow Controller that assigns incoming TCP connections to alternating paths '''based on total number of flows''' is already downloaded for you. You can find it (load-balancer.rb) in the home directory on node "Switch". [[BR]]
   - 2.1.1 Log on to node "Switch", wait until all interfaces are up and running by issuing "ifconfig", make sure eth1, eth2, eth3 are up and assigned with valid IP addresses. [[BR]]
+  - 2.1.1 Log on to node "Switch", wait until all interfaces are up and running. To check that all interfaces are configured issue "ifconfig", make sure eth1, eth2, eth3 are up and assigned with valid IP addresses. [[BR]]
   Start the example Load Balancer by executing the following:
   {{{
 …
 == 2.2 Use GIMI Portal to run the experiment and monitor the load balancer ==
    - 2.2.1 Log on to your !LabWiki Account on http://emmy9.casa.umass.edu:3005 , on the `Prepare` Column, type "OpenFlow", it will pop up with a list of .rb choices. Choose any one, and replace the whole content with the ruby script [http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/loadbalancer_monitor.rb HERE].
+   - 2.2.1 Log on to !LabWiki on http://emmy9.casa.umass.edu:3005 , on the `Prepare` Column, type "OpenFlow", it will pop up with a list of .rb choices. Choose any one, and replace the whole content with the ruby script [http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/loadbalancer_monitor.rb HERE].
    - 2.2.2 Log on to node "Switch" and do "ifconfig" to see the IP addresses on each interfaces.
     - '''Note''': You may not be able to see all interfaces up immediately when node "Switch" is ready; wait for some more time (about 1 min) then try "ifconfig" again.
     - Identify the two interfaces that you want to monitor: the interfaces with IP address 192.168.2.1 and 192.168.3.1 respectively. On the !LabWiki page, in your ruby script, find the following line:
+    - Identify the two interfaces that you want to monitor: the interfaces with IP addresses 192.168.2.1(left) and 192.168.3.1(right) respectively. On the !LabWiki page, in your ruby script, find the following lines:
 {{{
 ###### Change the following to the correct interfaces ######
 …
 ###### Change the above to the correct interfaces ######
 }}}
    - 2.2.3 Change eth1 and eth3 to the corresponding two interfaces you found with IP address 192.168.2.1 (the interface that connects to the left path) and 192.168.3.1 (the interface that connects to the right path) and press the "save" icon on your !LabWiki page.
    - 2.2.4 Drag the `file Icon` at the left-top corner on your !LabWiki page from `Prepare` column and drop it to `Execute` column. Fill in the name of your !LabWiki experiment (this can be anything), the name of your slice (this has to be your slice name), and type "true" in the graph box to enable graphs. And then press "Start Experiment" button.
    - 2.2.5 When your experiment is finished, turn off your controller and disconnect switch from your controller:
+   - 2.2.3 Change eth1 and eth3 to the corresponding two interfaces you found with IP addresses 192.168.2.1 (the interface that connects to the left path) and 192.168.3.1 (the interface that connects to the right path) and press the "save" icon on your !LabWiki page.
+   - 2.2.4 Drag the `file Icon` at the left-top corner on your !LabWiki page from `Prepare` column and drop it to `Execute` column. Fill in the name of your !LabWiki experiment (this can be anything, it is just to help you track the experiments you run), the name of your slice (this has to be your slice name), and type "true" in the graph box to enable graphs. Then press the "Start Experiment" button.
+   - 2.2.5 When your experiment is finished, turn off your controller and disconnect the switch from your controller:
       - On node "Switch", press "Ctrl" and "c" key to kill your Load Balancer process on node "Switch"
       - On node "Switch", use the following command to disconnect the OpenFlow Switch from the controller:
 …
    - '''Note''': Do not start another experiment (i.e., drag and drop the file icon in !LabWiki and press "Start Experiment") before your current experiment is finished.
+== (Optional) 2.3 Fetch experimental results from your iRods account ==
+ - 2.3.1 Log in your iRods account on https://www.irods.org/web/index.php, use "emmy9.casa.umass.edu" as Host/IP, "1247" as Port.
+ - 2.3.2 Download your experimental results from your user directory under /geniRenci/home/
+== 2.4 Change link parameters of left path using "ovs-vsctl" and repeat the experiment ==
+ - 2.4.1 Log on to node "left" and change the link capacity for the interface with IP address "192.168.2.2" (use "ifconfig" to find the correct interface, here we assume eth1 is the interface connecting to node "Switch"):
+== 2.3 Run the experiment in paths with different bandwidth ==
+ - 2.3.1 Log on to node "left" and change the link capacity for the interface with IP address "192.168.2.2" (use "ifconfig" to find the correct interface, here we assume eth1 is the interface connecting to node "Switch"):
 {{{
 ovs-vsctl set Interface eth1 ingress_policing_rate=10000
 …
  - Other ways to e.g., change link delay and lossrate using "tc qdisc netem" can be found in Section 4.
+== 2.5 Repeat Experiment with limited bandwidth on Left path ==
+ - 2.5.1 On node "Switch", start your Load Balancer using the following command:
+ - 2.3.2 On node "Switch", start your Load Balancer using the following command:
  {{{
  /opt/trema-trema-f995284/trema run /root/load-balancer.rb
  }}}
  - 2.5.2 Start a new command line window, log onto node "Switch", use the following command to connect the OpenFlow Switch to the controller (the console window that runs your controller should display "Switch is Ready!" when the switch is connected):
+ - 2.3.3 Start a new terminal, log onto node "Switch", use the following command to connect the OpenFlow Switch to the controller (the console window that runs your controller should display "Switch is Ready!" when the switch is connected):
  {{{
  ovs-vsctl set-controller br0 tcp:127.0.0.1 ptcp:6634:127.0.0.1
  }}}
  - 2.5.3 Go back to your !LabWiki web page, drag and drop the `file icon` and repeat the experiment, as described in section 2.2.4, using a different experiment name (the slice name should stay the same).
  - 2.5.4 When your experiment is finished, turn off your controller and disconnect switch from your controller:
+ - 2.3.4 Go back to your !LabWiki web page, drag and drop the `file icon` and repeat the experiment, as described in section 2.2.4, using a different experiment name (the slice name should stay the same).
+ - 2.3.5 When your experiment is finished, turn off your controller and disconnect switch from your controller:
       - On node "Switch", press "Ctrl" and "c" key to kill your Load Balancer process on node "Switch"
       - On node "Switch", use the following command to disconnect the OpenFlow Switch from the controller:
 …
  - To answer the above question, you need to understand the Load Balancing controller. Check out the "load-balancer.rb" file in your home directory on node "Switch". Check Section 3.1 for hints/explanations about this OpenFlow Controller.
 == 2.6 Modify the OpenFlow Controller to balance throughput among all the TCP flows ==
  - You need to calculate the average per-flow throughput observed from both left and right path in function "stats_reply" in your load-balancer.rb
+== 2.4 Modify the OpenFlow Controller to balance throughput among all the TCP flows ==
+ - You need to calculate the average per-flow throughput observed from both left and right paths. The modifications need to happen in the function "stats_reply" in load-balancer.rb
  - In function "decide_path", change the path decision based on the calculated average per-flow throughput: forward the flow onto the path with more average per-flow throughput. (Why? TCP tries its best to consume the whole bandwidth so more throughput means network is not congested)
  - If you do not know where to start, check the hints in Section 3.1.
   - If you really do not know where to start after reading the hints, the answer can be found on node "Switch", at /tmp/load-balancer/load-balancer-solution.rb
+  - Copy the above solution into your home directory then re-do the experiment on !LabWiki. '''Note:''' you need to change your script to use the correct Load Balancing controller (e.g., if your controller is "load-balancer-solution.rb", you should run "/opt/trema-trema-f995284/trema run /root/load-balancer-solution.rb")
+ - Redo the experiment using your new OpenFlow Controller following steps in Section 2.5, check the graphs plotted on !LabWiki as well as the controller's log on node "Switch" and see the difference.
+  - Copy the above solution into your home directory then re-do the experiment on !LabWiki.
+    '''Note:''' you need to change your script to use the correct Load Balancing controller (e.g., if your controller is "load-balancer-solution.rb", you should run "/opt/trema-trema-f995284/trema run /root/load-balancer-solution.rb")
+ - Reren the experiment using your new OpenFlow Controller following steps in Section 2.5, check the graphs plotted on !LabWiki as well as the controller's log on node "Switch" and see the difference.
  - When your experiment is done, you need to stop the Load Balancer:
   - On node "Switch", use the following command to disconnect the OpenFlow Switch from the controller:
 …
   - On node "Switch", press "Ctrl" and "c" key to kill your Load Balancer process on node "Switch"
 == 2.7 Automate your experiment using !LabWiki ==
  - 2.7.1 Add code in your !LabWiki script to automate starting and stoping your OpenFlow Controller:
   - Go back to your !LabWiki page, un-comment the script from line 184 to line 189 to start your OpenFlow Controller automatically on !LabWiki
+== 2.5 Automate your experiment using !LabWiki ==
+ - 2.5.1 Add code in your !LabWiki script to automate starting and stoping your OpenFlow Controller:
+  - 2.5.1.1 Go back to your !LabWiki page, un-comment the script from line 184 to line 189 to start your OpenFlow Controller automatically on !LabWiki
    - Note: You might need to change line 185 to use the correct load balancer controller
   - Uncomment the script from line 205 to line 209 to stop your OpenFlow Controller automatically on !LabWiki
+  - 2.5.1.2 In your script, uncomment lines 205 to line 209 to stop your OpenFlow Controller automatically on !LabWiki
  - 2.7.2 On your !LabWiki web page, drag and drop the `file icon` and repeat the experiment, as described in section 2.3, using a different experiment name (the slice name should stay the same).
  - If you have more time or are interested in trying out things, go ahead and try section 1.9. The tutorial is over now and feel free to ask questions :-)
 == 2.8 Try more experiments using different kinds of OpenFlow Load Balancers ==
+ - If you have more time or are interested in trying out things, go ahead and try section 2.6. The tutorial is over now and feel free to ask questions :-)
+== 2.6 Try more experiments using different kinds of OpenFlow Load Balancers ==
  - You can find more load balancers under /tmp/load-balancer/ on node "Switch"
  - To try out any one of them, follow the steps: