Changes between Version 3 and Version 4 of Internal/OpenFlow/FloodlightFVPort/Overview
- Timestamp:
- Aug 20, 2012, 6:36:52 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/FloodlightFVPort/Overview
v3 v4 10 10 Without 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. The re-writing of messages has the effect of controlled network resource allocation that enables multiple controllers to share a single physical network. 11 11 12 This project draws an analog between the individual modules and controllers, and attempts to implement a version of Floodlight applies !FlowVisor's resource allocation to its modules.12 This project draws an analog between the individual modules and controllers, and attempts to implement a version of Floodlight that applies !FlowVisor's resource allocation to its modules. 13 13 14 14 == Goals ==