| | 1 | == Overview == |
| | 2 | |
| | 3 | Floodlight is a modularized !OpenFlow controller, in that its functional components can be split into two major parts, a core event dispatcher and the various event handlers, or modules, that process these events. The key point here is that Floodlight's modular structure allows for: |
| | 4 | |
| | 5 | 1. Extensibility, in that new functionalities can be added as new modules, and |
| | 6 | 2. Multiple functionalities to coexist as modules on the same controller. |
| | 7 | |
| | 8 | Currently, 2) is only partially true, as modules that have conflicting functions may not coexist on a running Floodlight instance. As an example, the learning switch and forwarding modules will conflict, as they both send a PACKET_OUT to a switch - The switch will respond with a buffer error when it receives the second PACKET_OUT, as it had already sent the packet out. |
| | 9 | |
| | 10 | In the case that the conflicting modules are running on separate instances of Floodlight on the same network, this situation can be averted by network slicing. A slice can be thought of as an !OpenFlow controller and the network resources allocated to it by a hypervisor-like entity such as !FlowVisor. With proper resource allocation, which guarantees isolation, multiple controllers can coexist on the network without interfering with each other. |
| | 11 | |
| | 12 | This project draws an analog between the individual modules and controllers, and attempts to implement an isolation scheme within Floodlight to isolate conflicting modules, allowing them to run properly on the same controller. |
| | 13 | |
| | 14 | == Goals == |
| | 15 | The main goals of this project are the following: |
| | 16 | |
| | 17 | * Implement a slicing scheme that prevents unwanted interaction between modules |
| | 18 | * Allow control of slice behavior through a configuration file |
| | 19 | * Avoid modification of existing Floodlight source code |
| | 20 | * Provide an easy way to switch between normal Floodlight and "!FlowVisor" modes of operation |
| | 21 | |
| | 22 | In addition, the following assumptions were made as a consideration of the amount of time provided by GSoC : |
| | 23 | |
| | 24 | * All modules to be run are loaded at startup, and remain subscribed to events as long as Floodlight is running |
| | 25 | * Several modules such as link discovery and device manager need a global view of the network and so should not be restricted |
| | 26 | * modules that depend on one another must be in the same slice |
| | 27 | * The configurations are not persistent |
