Changes between Version 37 and Version 38 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Dec 1, 2012, 5:24:14 AM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -379 +379 @@
 For bypass, device identity is specified by MAC for now, which we assume doesn't change. The important part is that there is some unique identifier that can be used to specify a device. 
 We also assume that each Packet_in is not sensitive to the handling of others, so they do not have to be processed in the order that they arrive. This is a simplifying assumption for the replay aspect of the bypass. Bypass is on a per-server basis, since some servers may still want the event even if another forgoes it.     
+
+==== (12/1) ====
+Mostly garbled self-notes. 
+
+ * "context-switching" - would be ideal for running a packet through a process chain after a delay. this involves saving the !FloodlightContext and running the queue from where it's left off. The queue can be pulled from Controller.java, and truncated at after the remote dispatcher. 
+ * "context-switching" would be handy for if our higher-tier module sends back out original message. This can happen when there is a bypass, or for some other reason. A check for it would be a Packet_in, since that's the only thing we'd ever send up. For now. 
+
+Flow of events:
+{{{
+client -> ClientChannelHandler +   (us as [server])
+                               | 
+                               V
+switch -> OFChannelHandler -> controller -> !RemoteDispatchBase -> OFUStreamImpl -> [remote server] -> OFUstreamImpl -> OFDStreamImpl -> switch/client    (us as [client])
+                                    |
+                                    +-----> [other internal modules] -> switch/client                                              
+}}}
 ----
 [#home Home.]