Changes between Version 4 and Version 5 of GENIEducation/SampleAssignments/OpenFlowLoadBalancerAssignment/ExerciseLayout/Execute
- Timestamp:
- 05/31/13 10:11:56 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIEducation/SampleAssignments/OpenFlowLoadBalancerAssignment/ExerciseLayout/Execute
v4 v5 212 212 213 213 '''Process: ''' Upon the arrival of a new TCP flow, the OpenFlow controller should send out a `FlowStatsRequest` message to the OpenFlow switch. The OpenFlow switch will reply with statistics information about all flows in its flow table. 214 This flow statistics message will be fetched by the `stats_reply` function in Trema. Based on the statistics, experimenters can apply their own policy on which path to choose in different situations.215 The !FlowStatsReply message is in the following format:214 This flow statistics message will be fetched by the `stats_reply` function in the openflow controller implemented by the user on node `switch`. Based on the statistics, experimenters can apply their own policy on which path to choose in different situations. 215 The !FlowStatsReply message is in the following format: 216 216 {{{ 217 217 FlowStatsReply.new( … … 237 237 238 238 '''Question: Try modify the downloaded load balancer so that it decides path based on the average per-flow throughput observed on each path''' 239 239 240 '''Note: ''' since Trema does not yet support multi-thread mode, this simple implementation runs in one thread. As a result, users will experience some delay in fetching the flow statistics (i.e., `stats_reply` will not be called right after a !FlowStatsRequest message has been sent in `packet_in` handler). 240 241 241 242 = [wiki:GENIEducation/SampleAssignments/OpenFlowLoadBalancerAssignment/ExerciseLayout/Finish Next: Teardown Experiment] =