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


Ignore:
Timestamp:
Jan 14, 2013, 6:35:59 PM (12 years ago)
Author:
akoshibe
Comment:

Legend:

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

    v45 v46  
    435435 * Illustrate multi-service transaction : authentication + mobility path setup. (homebrew !OpenRoads)
    436436
     437==== 1/14 ====
     438Meeting 1 of this week. Discussion of possible demos combining several services into one and the testbed topology for running said topology.
     439 * two islands (admin domains, possibly - whose interconnection is an open logistics problem. One word: BGP) - and two layers of controllers. (demo horizontal interconnect, hierarchy)
     440 * service reachability - not all can reach eachother directly (demo control forwarding)
     441 * execution - two streaming hosts (client-server), with a mobile client. (demo usage in experimental setting)
     442  * steps: authentication, resolution, stream setup, host mobility, readjustment of stream.
     443  * traffic injection to data plane, active participation by controller (controller can send packets to end host, e.g. responses to resolution queries)
     444 * using a testbed - NetFPGA cubes with switches and lower tier, nodes 1-11/12 as higher-tier controller(s).
     445
     446The specifics of the execution of the demo mentioned above are:
     447 1. A client attaches and must authenticate with the network. The authentication result is stored locally at tier 1.
     448 1. This client is located in one admin domain, by default unable to communicate with admin domain 2, where the server lives. 
     449 1. The client wishes to contact a stream server at a known address. It initiates a request, which triggers an address resolution.
     450 1. The address is resolved by a service that maintains a global map of hosts to addresses, tier 2.   
     451 1. The resolution maps a location to the client, injecting a flow that permits traffic to cross domain boundaries. A reply from the server does likewise.
     452 1. The client moves to the same domain as server. The injected flows are torn down by some mechanism. We can name a few, though being proactive is hard: 
     453    * by active trigger by host departure and arrival. This is completely reactive.
     454    * flow timeout due to inactivity. This is a passive, autonomic approach.
     455    * consistency check service. If a client appears in two distinct locations, remove all but the flows to the most recent location. This is also reactive.
    437456
    438457----