Changes between Version 2 and Version 3 of Internal/OpenFlow/FloodlightFVPort/Architecture
- Timestamp:
- Aug 20, 2012, 3:39:21 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/FloodlightFVPort/Architecture
v2 v3 5 5 === Internal links === 6 6 [#goals Goals][[BR]] 7 [#ov Overview][[BR]] 7 8 [#comp Components][[BR]] 8 9 [#i Containers][[BR]] … … 27 28 * The configurations are not persistent 28 29 30 ---- 29 31 == Components == #comp 30 32 … … 44 46 * the FVSlicer, which handles messages to/from modules 45 47 48 ---- 49 == Overview == #ov 50 The following figure illustrates the high-level view of the implementation as it applies to a connection from one switch (s1): 51 [[Image(FV-slicer.png)]] 52 53 * Upon receiving a FEATURE_REPLY from the switch, FVChannelHandler spawns a FVClassifier. 54 * For each slice that the switch belongs to FVClassifier initializes an FVSlicer. 55 * Each slice specifies a module that it is able to isolate. Some slices may not be associated with any modules (and vice versa) 56 ---- 46 57 === Containers === #i 47 58 … … 51 62 * FVConfUtil : !FlowSpace contents, !FlowMap 52 63 64 ---- 53 65 === FVProxyProvider === #ii 54 66 … … 65 77 '''Initializes :''' The !FlowVisor service 66 78 79 ---- 67 80 === !FlowVisor service === #iii 68 81 … … 80 93 Because of their same logical purpose the !FlowVisor/FVProxyProvider pair are interchangeable with the Controller/!FloodlightProvider pair, allowing this version of Floodlight to be easily switched between "!FlowVisor" and "normal" modes of operation through the module loading system's configuration file. 81 94 95 ---- 82 96 === Message handlers === #iv 83 97 … … 114 128 * FVMessageConverter : translation of messages between OFMessage and !FlowVisor equivalents in org.flowvisor.message* 115 129 130 ----
