| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = OpenFlow !LoadBalancer Tutorial = |
| | 4 | In this tutorial, we will show how do Network Load Balancing using OpenFlow on GENI. Network Load Balancing is the division of traffic of multiple path to improve performance. |
| | 5 | |
| | 6 | == Overview == |
| | 7 | This tutorial leverages resources on the GENI aggregate in order to experiment with OpenFlow. For this tutorial, you will design a load-balancing OpenFlow controller capable of collecting flow status data from OpenFlow switches and using it to divide traffic between dissimilar network paths so as to achieve full bandwidth utilization. We are going to use OpenFlow Virtual Switches (OVS) and implement a Load Balancer OpenFlow Controller using Trema. [[BR]] |
| | 8 | Please remember to '''release the resources''' you when you are done with them. The following is the topology that you will be creating: [[BR]] |
| | 9 | [[Image(OpenFlowLB-topo.png, 20%, nolink)]] |
| | 10 | |
| | 11 | == Prerequisites == |
| | 12 | - A GENI account, if you don't have one [wiki:SignMeUp sign up!] |
| | 13 | - Familiarity with how to reserve GENI resources with any of the GENI Tools (GENI Experimenter Portal, Omni, Flack). If you don't know you can take any of the tutorials: |
| | 14 | * Reserving resources using Flack [wiki:GENIExperimenter/Tutorials/RunHelloGENI tutorial] |
| | 15 | * Reserving resources using Omni [wiki:GENIExperimenter/Tutorials/HelloOmni tutorial] |
| | 16 | - Familiarity with [wiki:HowTo/LoginToNodes logging in to GENI compute resources]. |
| | 17 | - Basic understanding of OpenFlow. If you are going over this tutorial at home, flip through the [http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/AdvancedOpenFlowTutorial/AdvancedOpenFlow-GEC17.pptx tutorial's slides] |
| | 18 | - Introduction to !LabWiki [http://groups.geni.net/geni/wiki/GEC18Agenda/GettingStartedWithGENI_III_GIMI tutorial] |
| | 19 | - Familiarity with Unix Command line - See "Tools" section |
| | 20 | - A moderately deep understanding of the [http://www.openflow.org OpenFlow controller model] and API is required. |
| | 21 | - The OpenFlow specification, [http://www.openflow.org/documents/openflow-spec-v1.1.0.pdf version 1.0] is a valuable reference for OpenFlow and the controller model. |
| | 22 | |
| | 23 | == Tools == |
| | 24 | '''1. Trema''' [[BR]] |
| | 25 | Each exercise in this assignment will require you to design and implement an OpenFlow controller. |
| | 26 | Numerous libraries and controller frameworks are available for this task. The guidelines in this assignment assume that you are using the [http://trema.github.com/trema/ Trema] controller framework. |
| | 27 | The Trema project web site, http://trema.github.com/trema/, contains documentation, a number of helpful examples, and some tutorial material for learning to use Trema. |
| | 28 | |
| | 29 | '''2. Traffic Control (tc)'''[[BR]] |
| | 30 | The tc command is available in the GNU Linux distributions on GENI nodes, found in the ''/sbin'' directory. |
| | 31 | This command manipulates the Linux network forwarding tables, allowing for configuration of queuing disciplines, |
| | 32 | which change the policies controlling which packets are forwarded in what order and which are dropped; and network |
| | 33 | emulation, which allows the Linux kernel to emulate various network conditions such as delay or loss. |
| | 34 | These two effects are provided by the qdisc and netem subcommands, respectively. |
| | 35 | In these exercises, tc will be used to modify network conditions and enable different scheduling policies. |
| | 36 | Example command lines will be provided. |
| | 37 | |
| | 38 | '''3. [http://iperf.sourceforge.net/ Iperf]'''[[BR]] |
| | 39 | Iperf is available on the GENI nodes, located at ''/usr/local/etc/emulab/emulab-iperf''. |
| | 40 | Iperf is used to measure the bandwidth performance of Internet links. In these exercises, |
| | 41 | it is used to study the behavior of TCP in the face of changing link characteristics. |
| | 42 | Iperf runs as both a server and a client. The server is started with the -s command line option, |
| | 43 | and listens for connections from the client. The client is started with the ''-c <server>'' command line option, |
| | 44 | and connects to the server and sends data at either the fastest possible rate (given the underlying network) |
| | 45 | or a user-specified rate. The -u option causes the sender or receiver to use UDP instead of TCP. |
| | 46 | Various other options will be required for these exercises, and provided in the appropriate sections. |
| | 47 | All Iperf measurement data should be recorded from the TCP receiver (server) side. |
| | 48 | |
| | 49 | == How to get Help == |
| | 50 | * Always ask your tutors (tutorial helper/presenter/TA) first. They are the fastest way to solve the problem. |
| | 51 | * If you are using a specific aggregate or tool, you should consider registering in their [wiki:NikySandbox/GENIExperimenter/GENICommunity#Joinusermailinglists mailing list]. It is a great way to get connected with other GENI users and it is an excellent source of wisdom. |
| | 52 | * Send mail to the GENI help list: [mailto:help@geni.net]. |
| | 53 | * If you want to chat real-time with other GENI users and ask questions, [wiki:HowTo/ConnectToGENIChatRoom join us] in a GENI chatroom. |
| | 54 | |
| | 55 | == Tutorial Instructions == |
| | 56 | {{{ |
| | 57 | #!html |
| | 58 | |
| | 59 | |
| | 60 | <table id="Table_01" height="409" border="0" cellpadding="0" cellspacing="0"> |
| | 61 | <tr> |
| | 62 | <td> |
| | 63 | <a href="http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/WinterCamp14/GIMITutorial/Procedure/DesignSetup"><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/design.png?format=raw" width="152" height="152" alt="Design/Setup"></a> |
| | 64 | </td> |
| | 65 | <td> |
| | 66 | <ul> |
| | 67 | <li><a href="http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/WinterCamp14/GIMITutorial/Procedure/DesignSetup">Part I: Design/Setup</a></li> |
| | 68 | <ul> |
| | 69 | <li> 1. Obtain Resources </li> |
| | 70 | </ul></ul> |
| | 71 | </td> |
| | 72 | </tr> |
| | 73 | <tr> |
| | 74 | <td> |
| | 75 | <a href="http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/WinterCamp14/GIMITutorial/Procedure/Execute"><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/execute.png?format=raw" width="152" height="143" alt="Execute"></a> |
| | 76 | </td> |
| | 77 | <td> |
| | 78 | <ul> |
| | 79 | <li><a href="http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/WinterCamp14/GIMITutorial/Procedure/Execute">Part II: Execute</a></li> |
| | 80 | <ul> |
| | 81 | <li> 2. Configure and Initialize services</li> |
| | 82 | <li> 3. Run your experiment </li> |
| | 83 | <li> Appendix: Hints and Explanations </li> |
| | 84 | </ul></ul> |
| | 85 | </td> |
| | 86 | </tr> |
| | 87 | <tr> |
| | 88 | <td> |
| | 89 | <a href="http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/WinterCamp14/GIMITutorial/Procedure/Finish"><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/finish.png?format=raw" width="152" height="114" alt="Finish"></a> |
| | 90 | </td> |
| | 91 | |
| | 92 | <td> |
| | 93 | <ul> |
| | 94 | <li><a href="http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/WinterCamp14/GIMITutorial/Procedure/Finish">Part III: Finish</a></li> |
| | 95 | <ul> |
| | 96 | <li> 4. Release Resources </li> |
| | 97 | </ul></ul> |
| | 98 | </td> |
| | 99 | |
| | 100 | </tr> |
| | 101 | </table> |
| | 102 | |
| | 103 | }}} |
