Changes between Version 9 and Version 10 of Internal/OpenFlow/FloodlightFVModule

Timestamp:

Jun 18, 2012, 7:15:47 AM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -135 +135 @@
 
 This process forces the forwarding component to register with FVController, as opposed to the core module. The core module still takes care of !OpenFlow signaling e.g. echo keepalives and the initial handshake, so any switches will still connect properly and keep the connection alive. 
+
+==== (6/15): ====
+After much tweaking and code-tracing with log.debug outputs, a (seemingly) working proxy was implemented.
+
+ * FVController: implements its own bare-bones versions of:
+  * updateSwitch: track list of active switches
+  * add/removeOFMessageListener
+  * add/removeOFSwitchListener
+  * getSwitches: return immutable list of active switches
+  * handleOutgoingMessage
+  * injectOfMessage
+  * handleMessage
+  * init: initialize class variables
+
+ * OFSwitchImpl: 
+   *modified write() functions that call either FVController or Controller's handleOutgoingMessage() depending on OFType:
+{{{
+switch (m.getType()) {
+    case PACKET_OUT:
+    case FLOW_MOD:
+    case PORT_MOD:      
+        this.floodlightProxy.handleOutgoingMessage(this, m, bc);
+        break;
+    default:    
+        this.floodlightProvider.handleOutgoingMessage(this, m, bc);
+}
+}}} 
+  * a setFloodlightProxy setter function
+ * Controller: add functions to set the floodlightProxy in OFSwitchImpl
+ * !FloodlightProvider: fetch and set Controller's FVProxy in init()
+{{{
+controller.setFVProxy(
+    context.getServiceImpl(IFloodlightProxy.class));
+}}}
 == . ==#end