[openflowplugin-dev] Deprecated EntityOwnershipService APIs


Sam Hague
 

Anil,

are you saying ovsdb and ofp cannot deprecate EOS until the two bugs are fixed in CSS?

Beyond that issue, is CSS stable enough to use? Are the changes to bring it in small and straight-forward? Genius and NetVirt will need to make the changes also so trying to scope that effort.

Thanks, Sam

On Thu, Jul 13, 2017 at 1:14 PM, Anil Vishnoi <vishnoianil@...> wrote:
Hi mdsal-dev,

EntityOwnershipService APIs are deprecated in Nitrogen release, but we have following two open bug that needs to be resolved for singleton clustering service API, otherwise project like Openflowplugin/Ovsdb can't support stable clustering solution. Currently both of these projects are using the both EOS and singleton clustering service to resolve these issues.


Is there any plan to fix these bugs in nitrogen cycle ?

--
Thanks
Anil

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev



Anil Vishnoi
 

Hi Sam

inline ..

On Mon, Jul 17, 2017 at 7:10 AM, Sam Hague <shague@...> wrote:
Anil,

are you saying ovsdb and ofp cannot deprecate EOS until the two bugs are fixed in CSS?
​Yes, that's pretty much the case.​
 

Beyond that issue, is CSS stable enough to use? Are the changes to bring it in small and straight-forward? Genius and NetVirt will need to make the changes also so trying to scope that effort.
​I believe CSS is pretty stable, I have not seen any issues as such, it's just that the API limitations is making things hard to totally rely on CSS. In openflowplugin we have to use both CSS + EOS to resolve few issues and for that reason i didn't move OVSDB to CSS. ​
 

​As far as applications are not handling with device connections (like most of the southbound plugin) and your application instance don't want to take any action as being Slave instance, things should be fine. The main issue is that slave instance don't get a notification that it's slave instance, so you either have to assume (but that doesn't really mean that leader is selected) that it's slave and start your operations and  meanwhile if you being elected as  a master instance, you should abort all your slave operation and switch to master operations OR wait for sometime and hope that election will be done in that time and assume the slave ownership if you don't get callback to initialize the service. First option is more deterministic, but it's not really optimal for application in some scenario. Bug 7820 is clean-up related bug that is something more related to southbound plugins handling device connections and should not have any impact on the application if they don't deal with connection. 


Thanks, Sam

On Thu, Jul 13, 2017 at 1:14 PM, Anil Vishnoi <vishnoianil@...> wrote:
Hi mdsal-dev,

EntityOwnershipService APIs are deprecated in Nitrogen release, but we have following two open bug that needs to be resolved for singleton clustering service API, otherwise project like Openflowplugin/Ovsdb can't support stable clustering solution. Currently both of these projects are using the both EOS and singleton clustering service to resolve these issues.


Is there any plan to fix these bugs in nitrogen cycle ?

--
Thanks
Anil

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...aylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev





--
Thanks
Anil


Anil Vishnoi
 

Hi Mdsal-devs,

Any thoughts on the it?

Thanks
Anil

On Thu, Jul 20, 2017 at 10:10 AM, Anil Vishnoi <vishnoianil@...> wrote:
Hi Sam

inline ..

On Mon, Jul 17, 2017 at 7:10 AM, Sam Hague <shague@...> wrote:
Anil,

are you saying ovsdb and ofp cannot deprecate EOS until the two bugs are fixed in CSS?
​Yes, that's pretty much the case.​
 

Beyond that issue, is CSS stable enough to use? Are the changes to bring it in small and straight-forward? Genius and NetVirt will need to make the changes also so trying to scope that effort.
​I believe CSS is pretty stable, I have not seen any issues as such, it's just that the API limitations is making things hard to totally rely on CSS. In openflowplugin we have to use both CSS + EOS to resolve few issues and for that reason i didn't move OVSDB to CSS. ​
 

​As far as applications are not handling with device connections (like most of the southbound plugin) and your application instance don't want to take any action as being Slave instance, things should be fine. The main issue is that slave instance don't get a notification that it's slave instance, so you either have to assume (but that doesn't really mean that leader is selected) that it's slave and start your operations and  meanwhile if you being elected as  a master instance, you should abort all your slave operation and switch to master operations OR wait for sometime and hope that election will be done in that time and assume the slave ownership if you don't get callback to initialize the service. First option is more deterministic, but it's not really optimal for application in some scenario. Bug 7820 is clean-up related bug that is something more related to southbound plugins handling device connections and should not have any impact on the application if they don't deal with connection. 


Thanks, Sam

On Thu, Jul 13, 2017 at 1:14 PM, Anil Vishnoi <vishnoianil@...> wrote:
Hi mdsal-dev,

EntityOwnershipService APIs are deprecated in Nitrogen release, but we have following two open bug that needs to be resolved for singleton clustering service API, otherwise project like Openflowplugin/Ovsdb can't support stable clustering solution. Currently both of these projects are using the both EOS and singleton clustering service to resolve these issues.


Is there any plan to fix these bugs in nitrogen cycle ?

--
Thanks
Anil

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...aylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev





--
Thanks
Anil



--
Thanks
Anil