Changes between Version 49 and Version 50 of GENIEducation/SampleAssignments/OpenFlowLoadBalancerTutorial/ExerciseLayout/Execute

Timestamp:

07/15/13 15:13:45 (11 years ago)

Author:

shuang@bbn.com

Comment:

--

GENIEducation/SampleAssignments/OpenFlowLoadBalancerTutorial/ExerciseLayout/Execute

@@ -79 +79 @@
  /opt/trema-trema-f995284/trema run /root/load-balancer.rb
  }}}
- - On node "Switch", use the following command to connect the OpenFlow Switch to the controller:
+ - Start a new command line window, log onto node "Switch", use the following command to connect the OpenFlow Switch to the controller:
  {{{
  ovs-vsctl set-controller br0 tcp:127.0.0.1 ptcp:6634:127.0.0.1
  }}}
  - Go back to 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). 
+ - 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:
+  {{{
+  ovs-vsctl del-controller br0
+  }}}
+  - On node "Switch", press "Ctrl" and "c" key to kill your Load Balancer process on node "Switch"
 
  Questions:
@@ -91 +97 @@
 
 == 1.7 Automate your experiment using !LabWiki ==
- - Stop the Load Balancer: 
-  - On node "Switch", use the following command to disconnect the OpenFlow Switch from the controller:
-  {{{
-  ovs-vsctl del-controller br0
-  }}}
-  - On node "Switch", press "Ctrl" and "c" key to kill your Load Balancer process on node "Switch"
  - 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
@@ -104 +104 @@
 ==  1.8 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
- - In function "packet_in", 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 2. 
+ - 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 2.1. 
   - If you really do not know where to start after reading the hints, download the answer directly from [http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/load-balancer-solution.rb load-balancer-solution.rb].
   - Save the above solution in your home directory then re-do the experiment on !LabWiki. '''Note:''' you need to change your !LabWiki script at line 185 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 > /tmp/lb.tmp")
@@ -130 +130 @@
 
 = 2. Hints / Explanation =
-== 3.2 About the OpenFlow controller [http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/load-balancer.rb load-balancer.rb] ==
+== 2.1 About the OpenFlow controller [http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/load-balancer.rb load-balancer.rb] ==
   - Trema web site: http://trema.github.io/trema/
   - Treme ruby API document: http://rubydoc.info/github/trema/trema/master/frames