Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Jon Castro's profile - activity

2015-09-12 05:42:55 -0700 received badge  Famous Question (source)
2015-09-09 12:07:24 -0700 received badge  Notable Question (source)
2015-09-02 09:31:25 -0700 received badge  Popular Question (source)
2015-08-30 23:25:21 -0700 answered a question Not able to ping between hosts from Mininet and ODL Helium

If you want hosts being reachable by ping, then you must ensure ARP Handler is enabled in proactive flood mode.

Go to /opt/bvc/controller/etc/opendaylight/karaf/54-arphandler.xml file and ensure proactive flood mode is enabled. This will require to restart the controller in case of change.

<is-proactive-flood-mode>true</is-proactive-flood-mode>

2015-08-23 20:25:45 -0700 received badge  Enthusiast
2015-08-10 21:34:31 -0700 asked a question Data Change Listeners and Cluster

My application requires all instances being notified when there is a data change in a Opendaylight cluster environment. Currently, only one instance (or member) of the cluster is being notified when there is a data change in the model.

Is it possible to register the listeners to be notified all of them? I did not found anything in the API to force this behaviour.

I'm using following configuration and code to register the listeners

In the Module create instance method

        final ListenerRegistration<DataChangeListener> dataChangeDevicesListenerRegistration =
            dataBrokerService.registerDataChangeListener(LogicalDatastoreType.CONFIGURATION,
                    CliconfProvider.DEVICES_IID, appProvider, DataChangeScope.SUBTREE);

In the application provider-impl.yang file

container data-broker {
            uses config:service-ref {
                refine type {
                    mandatory false;
                    config:required-identity mdsal:binding-async-data-broker;
                }
            }
        }