Not sure if it is relevant, we are using Beryllium SR3 as of now. My problem at hand is to generate yang notifications for topology data and I think data change event is the best way to go with. Only problem is with duplicate DCE resulting in unwanted notifications north bound when cluster role changes or on warm restart etc.
If I have cluster of 3 nodes (A, B,C) and if A is master, it is going to send yang notifications based on DCE (Data change event), if B becomes master, then B is going to get DCE events for all data that exists which will force B to send another set of notifications to north bound consumers (repeat of what A has done already). This duplicate stuff doesn't make sense from business perspective. so looking for right thing to do. Please advice. Thanks Hari On Wed, Feb 1, 2017 at 2:01 PM, Harinath Mallepally <h...@harinath.in> wrote: > > Hi All, > > As I understand, every warm restart and cluster node role change triggers > data change events for all data. > > We would like to build a notification mechanism for changes in data > through yang notifications but are worried that we keep sending duplicate > notifications. > > Is there a way to identify the data change events in a smart way so that I > can skip the duplicate events for the purpose of generating yang > notification. > > > Please advice me if there is an option or any ideas towards the same? > > > Please let me know if my question is not clear. > > Thanks > Hari > > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
