On Mon, Jul 9, 2018 at 6:29 AM, Deepthi V V <deepthi....@ericsson.com> wrote:
> Hi Robert, Faseela, > > That does explain our situation. > But doesn't the blueprint extensions odl:rpc-implementation and > odl:rpc-service supposed to register and fetch the service through > RPC-registry? > These were recently changed to use the mdsal APIs. > > Thanks, > Deepthi > > -----Original Message----- > From: Robert Varga <n...@hq.sk> > Sent: Monday, July 09, 2018 3:36 PM > To: Faseela K <faseel...@ericsson.com>; Deepthi V V < > deepthi....@ericsson.com>; Vishal Thapar <vtha...@redhat.com> > Cc: sfc-...@lists.opendaylight.org; mdsal-...@lists.opendaylight.org; > genius-...@lists.opendaylight.org; Tom Pantelis <tompante...@gmail.com>; > openflowplugin-dev@lists.opendaylight.org > Subject: Re: [openflowplugin-dev] [mdsal-dev] IncorrectNestingException on > SFC when sing OFP model > > On 09/07/18 11:55, Faseela K wrote: > > Netvirt uses blueprint wiring and injects the odlInterfaceRpcService, > > where as sfc uses interfaceManagerRpcService = > > rpcProviderRegistry.getRpcService(OdlInterfaceRpcService.class); > > > > Robert indicated that so netvirt is bypassing MD-SAL, as it is taking > the service implementation from OSGi Service Registry, and that explains > why the failure is happening only for sfc. > > Correct. > > Note that netvirt approach requires the service to be local, whereas the > SFC approach is location agnostic (the service can be located anywhere in > the cluster). > > Regards, > Robert > >
_______________________________________________ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
