In Helium plugin, this is how it goes 1) Openflowplugin receives the switch connection 2) plugin register that controller as a candidate for device ownership with EOS 3) Plugin fetch the current ownership state of the device, if it does not get the ownership it doesn't do anything, if it gets the ownership state and EOS give ownership to that controller, 4) It's sends the master role to the switch else it will send slave role to the switch 5) Once master role is set, it will send nodeAdded() yang notification to the application 6) If master role setting fails,it de-register the candidate for device ownership, so that anyone else can get EOS ownership and it can try for the master role setting.
On Mon, Feb 22, 2016 at 10:11 AM, Shuva Jyoti Kar < [email protected]> wrote: > Hi Anil/Kamal, > > > > What are the exact sequence of events between EOS receiving a switch > connection and the switch data being populated in the Oper DS ? > > > > Thanks > > Shuva > -- Thanks Anil
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
