1 / 10

OpenFlow Tutorial

OpenFlow Tutorial. Theophilus Benson. Outline. Components in an OpenFlow testbed Setting up a testbed Writing a new component C++ components version Python components version. OpenFlow Components. Controller Openflow switches Traffic generators. OpenFlow Enabled Switches. End host1.

paul2
Download Presentation

OpenFlow Tutorial

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. OpenFlow Tutorial Theophilus Benson

  2. Outline • Components in an OpenFlow testbed • Setting up a testbed • Writing a new component • C++ components version • Python components version

  3. OpenFlow Components • Controller • Openflow switches • Traffic generators OpenFlow Enabled Switches End host1 End host3 End host2 OpenFlow Controller

  4. Virtual Testbed • Directions available online • http://noxrepo.org/manual/using.html#setting-up-a-noxnetwork • Requirements • Linux system • Qemu • Python • Nox code • Other linux libraries

  5. Testbed Setup • Compile Nox code • Set up virtual machines • Connect topology • Start controller • Use appropriate components • Connect switches to controller

  6. Writing Components • Two languages; c++ and python • More information found: http://noxrepo.org/manual/app.html • Components are stored in src/nox/apps • Separate each component into a distinct directory • Component Structure • You must inherit from class Component • You must include a call to the REGISTER_COMPONENT macro • You must include the following methods • Void configure(const Configuration *) • Void install()

  7. Component Paradigm • Register for events and specify handlers • register_handler<eventtype>(boost::bind(handling_method, this, _1)); • register_handler<Packet_in_event>(boost::bind(&Hub::handler, this, _1)); • All work done in handler • Return either CONTINUE or END • NOTE: you can start the controller with a list of components, event get passed from one to the other • Returning CONTINUE means the next component handles the packet • Returning END means no other components handle the packets

  8. Demo • Run component in openflow controller • Ping from endhost A • Should observe printouts in controller’s console

  9. Resources • Nox website • http://noxrepo.org • OpenFlow Site • http://www.openflowswitch.org/wp/documents

  10. Questions

More Related