Hi Robert Yes, supporting large number of routes for (large number of) VPN(s) service is another interesting usecase..
However, from what I know, processing for VPN routes also follows single-producer-single-consumer pattern. If so, we should be able to leverage external datastore for such usecase in clustered ODL environment. With regards Ashutosh -----Original Message----- From: Robert Varga [mailto:n...@hq.sk] Sent: Friday, October 07, 2016 3:15 PM To: Ashutosh Bisht <ashutosh.bi...@ericsson.com>; mdsal-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org Subject: Re: [mdsal-dev] Use of external datastore in ODL On 10/07/2016 11:04 AM, Ashutosh Bisht wrote: > This is because, single-producer-single-consumer scenario can be implemented > in many ways.. > Notifications truly shine when there are multiple listener (many times > unknown consumers) for a notification.. > Based on your response, I believe BGP scenario is > single-producer-single-consumer pattern (even with the new request). In this particular case yes, but both the AdjRIBIn and EffRIBIn are interesting to users, too. Furthermore having the ability to listen on LocRIB is important to route the data to other users (such as VPN service). Kind regards, Robert _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
