Changes between Version 23 and Version 24 of Internal/OpenFlow/FloodlightFVModule

Timestamp:

Jul 8, 2012, 3:43:42 AM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -263 +263 @@
 For now, a sane goal is probably to have the proxy identify which slice a message belongs to based on the contents of the configuration file.  
    
+==== (7/7) ====
+To tie back to the proxy module:
+ * receive() gets all IO Events.
+ * Added/!RemovedSwitch() gets all switch joinleave events. 
+The actions that must occur at reception of an IO event include, as per Flowvisor documentations:
+ * identification of origin - switch or a slice?
+ * if from a switch, which slice(s) it belongs to 
+ * if from a slice, which switch(es) they apply to 
+As of now, we assume that there is one module per slice (forwarding, switch, hub...). 
+
+The flow of event handling for messages, compared to the components of Flowvisor, looks like the following in the modified version of Floodlight:
+{{{
+OFSwitchAcceptor             FVClassifier                                     FVSlicer
+                   _______________/\_______________  ____________________________/\____________________________
+                  /                                \/                                                          \
+   FVAcceptor        FVController        Modules        OFSwitchImpl         FVController               Modules    
+   receive()  ->   handleMesssage() ->  receive()  ->     write()    ->  handleOutgoingMessage()  ->   receive() 
+}}}
+receive() in the modules may be called twice, but since message handling varies with OFType, this does not loop as one may think. 
+We can then use these functions to handle the functionalities of the Slicers and Classifiers in Flowvisor. 
 
 == . ==#end