Changes between Version 39 and Version 40 of Internal/OpenFlow/Controllers/MultiCtl


Ignore:
Timestamp:
Dec 31, 2012, 10:39:57 PM (12 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/Controllers/MultiCtl

    v39 v40  
    2222 [#w12 week12][[BR]]
    2323 [#w13 week13][[BR]]
    24 
     24 [#w15 week 15][[BR]]
    2525== Overview. == #i
    2626The 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.
     
    404404Thought was also put into the notion of autoconfiguration, in which the controllers discover other controllers by themselves, as opposed to being preconfigured through a file. References for this process included UPnP, although this becomes potentially very complicated. Using broadcast as the default behavior also compromises a good bit of the initial design, as the hierarchy had used the point-to-point TCP connections in order to maintain context as messages were passed between controllers (albeit poorly).
    405405
    406  
    407 
    408 
    409 
     406==== (week 14) ==== 
     407An informal break due to holidays.
     408
     409==== 12/31 (week 15) ==== #w15 
     410The architecture was revised yet again for what is hoped to be the final time:
     411
     412[[Image(arch_rev3.png)]]
    410413
    411414----