Changes between Version 49 and Version 50 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Jan 29, 2013, 10:36:01 PM (11 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -24 +24 @@
  [#w15 week 15][[BR]]
  [#w17 week 17][[BR]]
+ [#w19 week 19][[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. 
@@ -469 +470 @@
  * Tracking TID - hopefully possible through the context, though not under all cases to IOFSwitch.write(). A quick glance shows that as long as write() is called through receive(), the context can be preserved. 
  
+==== w/o 1/27-2/2 ==== #w19
+A mild hiatus during the week-long Juniper hackathon. On the meanwhile:
+
+ 1. reworked routing table + forwarding table for the control plane implementing a very simplified RIP/split horizon -like service info dissipation mechanism. Hop count is used as the preferred reachability mechanism, and is encoded in the CPLVendorData header. 
+ 1. transparency mechanism for topology information. A higher-tier controller seeking switch info is assumed to be seeking topology transparency. This implies:
+  * transmission of all collected feature replies from the lower tiers (no two low-tier controllers connect to the same switch)
+  * escalation of topology data (!PacketIn and !PortStats, required by topology and link discovery modules)
+ 
 ----
 [#home Home.]