Changes between Version 28 and Version 29 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Oct 24, 2012, 12:20:58 AM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -243 +243 @@
  * Some more discussion on use case was had, in the context of different management domains with multiple controllers owned by separate groups, but on the same network. In the traditional network setup, each group would have to actively collaborate in order to prevent controllers from trampling each others' policies. For example, a central controller orchestrator, when allowing a user to administrate the network, would only permit the user to configure their own controller. The orchestrator would have to "know" which users can access which controller, and how that controller may influence the network.  
 
-==== (10/16) ====
+[[BR]]      
+End of week5 :[#iv Back to Logs.]
+==== (10/16) ==== #w6
 The process chain was fleshed out further.
  * remote connections appear like modules that subscribe to the events that they need for their service. For example, the authenticator would listen for any new device connections and departures, and not let packet_ins from the device to pass through further down the OFMessage chain if the host is not allowed (or inject drop messages for the denied host).
@@ -250 +252 @@
 ==== (10/19) ====
  * Added parser for controller service descriptions/requirements to the topology file. The configs for the controller are parsed, then pushed out as part of the service info exchange that controllers do with each other when establishing a connection. The aim is to be able to describe services in terms of the resources that it needs. The resources are in the form of events that the controller is capable of detecting and dispatching (messages, switches, and hosts/devices).
+
+[[BR]]      
+End of week6 :[#iv Back to Logs.]
+==== (10/22) ====#w7
+
 ----
 [#home Home.]