On Tue, Jul 10, 2018 at 11:38 AM, Jaime Caamaño Ruiz <jcaam...@suse.de> wrote:
> Hello Faseela > > Thinking a bit more into this... > > Even if we properly augment the genius RPC nodes and then convert to > these new augmentations, then user apps will need to convert these new > augmentations back to the original ones before writing to MDSAL. > > Seems really cumbersome, and since serveral apps will be impacted, not > really something that can be done right away; if we were to do it, I > would say we even need a weather item for this. > > The most feasible way to get out of this in the time being, seeing > latest Robert answer, is to not use the RpcRegistry. But using > blueprint is also not an option for SFC, we need weak coupling on these > RPC services, so probably need to implement our own ServiceTracker. I > am working on this. > The serialization bypass will be restored relatively shortly. In the meantime, you can convert to use the mdsal org.opendaylight.mdsal.binding.api.RpcConsumerRegistry interface as was done in the BP ext. We want to convert to the mdsal APIs anyway long term. > > BR > Jaime. > >
_______________________________________________ sfc-dev mailing list sfc-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/sfc-dev
