Clustering : Provide a mechanism for consumers to specify how they would like to receive notifications in a cluster

When an application is deployed on every node in a cluster it may have different requirements as to which instance of the application should receive the notification. In Helium the default was to deliver the notification to a local listener.

The enhancement that is needed is to do the following types of notifications,

• NotifyAll
• NotifyLocal
• NotifyAtleastOne
• NotifyAtMostOne
• And anything else I cannot think of today

A rough consensus on design is that this could be achieved by creating a subclass per listener where the listener provides additional information about how the notification should happen. This subclassed listener should be available on both the Binding Aware and Binding Independent interfaces of MD-SAL and should be available for both YANG and DataChange notifications.