Changes between Version 5 and Version 6 of Internal/OpenFlow/FloodlightFVPort/Architecture


Ignore:
Timestamp:
Aug 20, 2012, 3:49:25 AM (12 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/FloodlightFVPort/Architecture

    v5 v6  
    44
    55=== Internal links ===
    6 [#goals Goals][[BR]]
    76[#ov Overview][[BR]]
    87[#comp Components][[BR]]
     
    1110 [#iii  FlowVisor service][[BR]]
    1211 [#iv  Message Handlers][[BR]]
    13 
    14 == Goals == #goals
    15 
    16 The main goals of this project's designs are the following:
    17 
    18  * Implement a slicing scheme that prevents unwanted interaction between modules
    19  * Allow control of slice behavior through a configuration file
    20  * Avoid modification of existing Floodlight source code
    21  * Provide an easy way to switch between normal Floodlight and "!FlowVisor" modes of operation
    22  
    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 running
    26  * Several modules such as link discovery and device manager need a global view of the network and so should not be restricted
    27  * modules that depend on one another must be in the same slice
    28  * The configurations are not persistent
    2912
    3013----
     
    5235[[Image(FL-slicer.png)]]
    5336
    54  * Upon receiving a FEATURE_REPLY from the switch, FVChannelHandler spawns a FVClassifier.
     37 * Each switch is associated with a FVClassifier.
    5538 * For each slice that the switch belongs to FVClassifier initializes an FVSlicer.
    5639 * Each slice specifies a module that it is able to isolate. Some slices may not be associated with any modules (and vice versa)