Changes between Version 1 and Version 2 of Internal/OpenFlow/FloodlightFVPort/Overview


Ignore:
Timestamp:
Aug 20, 2012, 5:52:21 AM (12 years ago)
Author:
akoshibe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/OpenFlow/FloodlightFVPort/Overview

    v1 v2  
    66 2. Multiple functionalities to coexist as modules on the same controller.
    77
    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.   
     8Currently, 2) is only true for modules that depend on one another. Modules that have conflicting functions cannot be loaded together on one running Floodlight instance. For 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, since it had already sent the packet out.
    99
    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.
     10Without some form of management over control traffic, the same problem will still occur if two (or more) controllers on the same network are running conflicting modules. An entity such as !FlowVisor can resolve this situation by intercepting control traffic and ensuring that each controller's messages do not interfere with the others.   
    1111
    1212This 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.