Changes between Version 44 and Version 45 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Jan 11, 2013, 11:28:51 PM (11 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -23 +23 @@
  [#w13 week13][[BR]]
  [#w15 week 15][[BR]]
+ [#w17 week 17][[BR]]
 == Overview. == #i
 The basic architecture for an !OpenFlow network is a client - server (switch - controller) model involving a single controller and one or more switches. Networks can host multiple controllers. !FlowVisor virtualizes a single network into slices so that it can be shared amongst various controllers, and the newest !OpenFlow standard (v1.3.0) defines ''equal'', ''master'' and ''slave'' controllers to coexist as part of a redundancy scheme in what would be a single slice. A multi-controller scheme that isn't really explored yet is one where each controller has a different function, and cooperate. 
@@ -420 +421 @@
 [[Image(controller_arch_rev-3.png)]]
 
-==== 1/11 (week 17) ==== #w15  
+==== 1/11 (week 17) ==== #w17  
 The weeks are going by faster, I swear. 
 Need some ideas for demos. Focus should shift to describing this project in a top-down manner, e.g. how functionalities fit back into the architecture. 
@@ -426 +427 @@
 meeting scheduled Mon, 11am for details on the demo. 
 
+Things to do:
+ * think of method for sanity-checking forward dispatch
+ * control plane routing table - for allowing servers to determine if they can handle things on spot, or be client to higher-ups
+  * make use of CPLUpdate messages, their filters. 
+  * tether each filter to a UID, 0 if `this` (as in, a filter the server itself had asked for). 
+   * concept of a "localhost" (oi vay) 
+ * Illustrate multi-service transaction : authentication + mobility path setup. (homebrew !OpenRoads)
+
+
 ----
 [#home Home.]