Hi Sela, You might want to look into the Routed-RPC option for this if your performance requirements are not so severe.
To illustrate, in Openflowplugin, every switch in effect exposes a RPC and registers itself with the central routed-rpc registry. If a flow has to be provisioning from Node A but the switch is connected to Node B (or Node B is master of switch in OF high-availability lingo), RPC call from Node A gets routed by MD-SAL infrastructure to Node B's RPC-provider of given switch. I am not sure about your deployment model. But an important pre-requisite for above to work is that both RPC consumer(S) and RPC provider(s) must be on same Akka cluster Hope this helps Regards Muthu From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Sela, Guy Sent: Thursday, August 25, 2016 1:01 PM To: mdsal-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org Cc: Alfasi, Shlomi; Cohen, Elad Subject: [controller-dev] Invoking MD-SAL RPC's from outside the cluster Hi, Let's say I have a cluster of 3 ODLs, and I have another external ODL that is not part of the Cluster. Can this external ODL invoke RPCs on the ODLs in the cluster? The current MD-SAL RPC framework allows me to invoke RPCs on remote machines in an async way, giving me a Future. I want the same capability for a machine that doesn't live in the cluster. If the answer is no, what do you think will be the best way to do it? What we are trying to achieve is very similar to this library: https://github.com/barakb/asyncrmi/ Thanks, Guy Sela
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
