Changes between Version 32 and Version 33 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Nov 9, 2012, 12:36:23 AM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -17 +17 @@
  [#w7 week7][[BR]]
  [#w8 week8][[BR]]
+ [#w9 week9][[BR]]
+ [#w10 week10][[BR]]
+ [#w11 week11][[BR]]
+ [#w12 week12][[BR]]
+ [#w13 week13][[BR]]
 
 == Overview. == #i
@@ -286 +291 @@
 To keep things simple, of the Message category of events, focus will be placed on the Packet_In type (0x10), which is practically a catch-all for network host related messages. If more fine-tuned filtering is requires, a OFMatch structure may probably be used to describe the constraints on the types of Packet_Ins a subscriber may wish to hear about. 
 
+[[BR]]      
+End of week7 :[#iv Back to Logs.]
 ==== (11/2) ==== #w8
 Concept work for the module front end to remote connections: [[BR]]
@@ -310 +317 @@
  * multiple remote controllers with conflicting requests - For the same event. Strongly implies diversion should /not/ drop a event after it passes through one. 
 
-For starters, the most basic structure would be a diverting module(work on one at a time, the default dispatcher behavior)        
+For starters, the most basic structure would be a diverting module(work on one at a time, the default dispatcher behavior)  
+
+==== (11/8) ====
+The current state of the implementation is as follows:
+ * central configuration file for the advertisements sent by the controller 
+ * single remote dispatch module that registers as a listener for devices, switches, and messages
+ * Vendor message-based control plane communication 
+
+Vendor message contents may be classified into initialization messages and service messages. The former are messages exchanged during an initial handshake between controllers, and the latter are messages used during normal operation e.g. for event messaging and returning processed results. In the interest of time, the controller-specific event contexts will probably be used for this purpose, as it can be used to directly manipulate the behavior of various modules. In the ideal case, a more general messaging format should work. 
 ----
 [#home Home.]