Changes between Version 11 and Version 12 of Internal/OpenFlow/Controllers/FloodLight

Timestamp:

Jun 3, 2012, 5:26:35 AM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/FloodLight

@@ -124 +124 @@
 3. Run the REST API and core controller. 
 
-At this point, Floodlight is up and running. 
+At this point, Floodlight is up and running. The TCP server functions are implemented with [http://netty.io/ Netty]. The controller's ''run'' routine does two things:
+ 1. create a server-side channel on port 6633 (or where specified)  
+ 1. handle updates. 
+Updates include switches joining and departing, controller role change, and controller IP change. 
 
 === IFloodlightProviderService ===
-This interface lies at the core of Floodlight's functions (literally in net.floodlightcontroller.core). The class `Controller` implements this interface.   
+This interface lies at the core of Floodlight's functions (literally in net.floodlightcontroller.core). The class `Controller` implements this interface and defines Floodlight's corre controller functionalities. 
 
+==== !OpenFlow message processing chain ====   
+The manner in which a control message is processed is defined in the modules themselves through the `IOFMessageListener` interface's ''receive'' function. 
+
+In `Controller`:   
+ 
+ 1. injectOfMessage(sw, msg) calls overloaded injectOfMessage with null context
+ 2. injectOfMessage (sw, msg, context) calls handleMessage(sw, msg, context)
+ 3. handleMessage(...) calls ''receive'' for each listener subscribed to the particular type of message received from a switch (types are defined in `OFType`) 
+  * messageListener maintains mappings between control message type and listeners. 
+  * This is also where `IListener`'s ''Command'' enumeration (return value for `IOFMessageListener`::receive) is used to decide if a message continues down the processing chain.
 
 = The Floodlight VM = #vm