Changes between Version 5 and Version 6 of Internal/OpenFlow/FloodlightFVPort/Architecture
- Timestamp:
- Aug 20, 2012, 3:49:25 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/FloodlightFVPort/Architecture
v5 v6 4 4 5 5 === Internal links === 6 [#goals Goals][[BR]]7 6 [#ov Overview][[BR]] 8 7 [#comp Components][[BR]] … … 11 10 [#iii FlowVisor service][[BR]] 12 11 [#iv Message Handlers][[BR]] 13 14 == Goals == #goals15 16 The main goals of this project's designs are the following:17 18 * Implement a slicing scheme that prevents unwanted interaction between modules19 * Allow control of slice behavior through a configuration file20 * Avoid modification of existing Floodlight source code21 * Provide an easy way to switch between normal Floodlight and "!FlowVisor" modes of operation22 23 In addition, the following assumptions were made as a consideration of the amount of time provided by GSoC :24 25 * All modules to be run are loaded at startup, and remain subscribed to events as long as Floodlight is running26 * Several modules such as link discovery and device manager need a global view of the network and so should not be restricted27 * modules that depend on one another must be in the same slice28 * The configurations are not persistent29 12 30 13 ---- … … 52 35 [[Image(FL-slicer.png)]] 53 36 54 * Upon receiving a FEATURE_REPLY from the switch, FVChannelHandler spawnsa FVClassifier.37 * Each switch is associated with a FVClassifier. 55 38 * For each slice that the switch belongs to FVClassifier initializes an FVSlicer. 56 39 * Each slice specifies a module that it is able to isolate. Some slices may not be associated with any modules (and vice versa)