There's a bug for it: https://bugs.opendaylight.org/show_bug.cgi?id=3128. There was a patch pushed but not sure where it stands as the author is no longer working on ODL.
On Tue, Oct 11, 2016 at 3:01 AM, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mire...@cisco.com> wrote: > Hi Robert, > unfortunately this is a case of global rpc. I can temporarily add a fake > routing context and try. But is there a plan on adding global rpc support > to clustered rpc broker? > > Regards, > Michal > ________________________________________ > From: Robert Varga <n...@hq.sk> > Sent: Monday, October 10, 2016 16:50 > To: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco); > controller-dev@lists.opendaylight.org; coretutorials-dev@lists. > opendaylight.org > Subject: Re: [controller-dev] register rpc at 1 node in cluster > > On 10/10/2016 04:00 PM, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES > at Cisco) wrote: > > Hi all, > > > > is there a way to register rpc service at 1 cluster node (which won > > election of SingletonClusterService in 3node-cluster). And have that rpc > > available via restconf from all cluster nodes? > > > > I end up using RpcProviderRegistry.addRpcImplementation(..) which > > results into locally available rpc. So if I point restconf call to wrong > > cluster node then I get: > > > > "No implementation of RPCservice .. available". Is there a different > > registry point or rpc interface which has to be used in order to achieve > > cluster-wide rpc? > > Global or routed RPC? Unfortunately the current clustered RPC broker > ignores the former... If it is a routed RPC, this looks like a bug ... > > Bye, > Robert > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
