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


Ignore:
Timestamp:
Jan 11, 2013, 11:28:51 PM (12 years ago)
Author:
akoshibe
Comment:

Legend:

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

    v44 v45  
    2323 [#w13 week13][[BR]]
    2424 [#w15 week 15][[BR]]
     25 [#w17 week 17][[BR]]
    2526== Overview. == #i
    2627The 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.
     
    420421[[Image(controller_arch_rev-3.png)]]
    421422
    422 ==== 1/11 (week 17) ==== #w15 
     423==== 1/11 (week 17) ==== #w17 
    423424The weeks are going by faster, I swear.
    424425Need 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.
     
    426427meeting scheduled Mon, 11am for details on the demo.
    427428
     429Things to do:
     430 * think of method for sanity-checking forward dispatch
     431 * control plane routing table - for allowing servers to determine if they can handle things on spot, or be client to higher-ups
     432  * make use of CPLUpdate messages, their filters.
     433  * tether each filter to a UID, 0 if `this` (as in, a filter the server itself had asked for).
     434   * concept of a "localhost" (oi vay)
     435 * Illustrate multi-service transaction : authentication + mobility path setup. (homebrew !OpenRoads)
     436
     437
    428438----
    429439[#home Home.]