Changes between Version 2 and Version 3 of Internal/OpenFlow/FloodlightFVPort

Timestamp:

Aug 19, 2012, 8:40:28 AM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVPort

@@ -25 +25 @@
  * Provide an easy way to switch between normal Floodlight and "!FlowVisor" modes of operation
  
-=== Assumptions ===
-
-The following assumptions are made as a consideration of the amount of time provided by GSoC :  
+In addition, the following assumptions were made as a consideration of the amount of time provided by GSoC :  
 
  * All modules to be run are loaded at startup, and remain subscribed to events as long as Floodlight is running
  * Several modules such as link discovery and device manager need a global view of the network and so should not be restricted
- * Each slice can isolate one module
+ * modules that depend on one another must be in the same slice
  * The configurations are not persistent 
+
+=== How it works ===
+The logical structure is heavily inspired by !FlowVisor.
+
+ * ''Incoming connections'' - each new connection from a switch is allocated a FVClassifier, which, in turn, initializes one FVSlicer per slice that the DPID is associated with. 
+ * ''Module Isolation'' - each message that must be processed by a module is associated with a slice. This association is made according to the source DPID if controller-bound, and source module, if switch-bound. An FVClassifier will determine the destination slice with the aid of the !FlowMap, and send the message to the appropriate FVSlicer.     
 
 
 == Internal Links ==
  * [wiki:Documentation/OpenFlow/FloodlightFVPort/InstallUsage Installation and Usage]
+ * [wiki:Documentation/OpenFlow/FloodlightFVPort/Architecture Architecture]
 
 == External Links ==