On 05/24/2016 01:54 AM, Gary Kotton wrote:
Hi,
We have used tooz to enable concurrency. Zookeeper and Redis worked
well. I think that it is certainly something that we need to consider.
The challenge becomes a deployment.
I'm not following. What does tooz, ZK or Redis have to do with
concurrency of NeutronDbObject and oslo.versionedobject interfaces?
Best,
-jay
*From: *Damon Wang <damon.dev...@gmail.com>
*Reply-To: *OpenStack List <openstack-dev@lists.openstack.org>
*Date: *Tuesday, May 24, 2016 at 5:58 AM
*To: *OpenStack List <openstack-dev@lists.openstack.org>
*Subject: *Re: [openstack-dev] [neutron][ovo] NeutronDbObject
concurrency issues
Hi,
I want to add an option which handle by another project Tooz.
https://github.com/openstack/tooz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_tooz&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=BlFY_Ge8eQsKWmvzFjG8WDvC_476YtRBCancu5pAbt8&s=eX2MSKfmcWhBdoSfE7czdazEibklQWO9Z2bSdGtluOo&e=>
with redis or some other drivers, it seems pretty a good choice.
Any comments?
Wei Wang
2016-05-17 6:53 GMT+08:00 Ilya Chukhnakov <ichukhna...@mirantis.com
<mailto:ichukhna...@mirantis.com>>:
On 16 May 2016, at 20:01, Michał Dulko <michal.du...@intel.com
<mailto:michal.du...@intel.com>> wrote:
It's not directly related, but this reminds me of tests done by
geguileo
[1] some time ago that were comparing different methods of
preventing DB
race conditions in concurrent environment. Maybe you'll also
find them
useful as you'll probably need to do something like conditional
update
to increment a revision number.
[1] https://github.com/Akrog/test-cinder-atomic-states
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Akrog_test-2Dcinder-2Datomic-2Dstates&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=BlFY_Ge8eQsKWmvzFjG8WDvC_476YtRBCancu5pAbt8&s=NcW1-muP9ymke4gz9blqXQ1mbrfpmfLHZHjQspx6jMY&e=>
Thanks for the link. The SQLA revisions are similar to the
'solutions/update_with_where',
but they use the dedicated column for that [2]. And as long as it is
properly configured,
it happens 'automagically' (SQLA will take care of adding proper
'where' to 'update').
[2] http://docs.sqlalchemy.org/en/latest/orm/versioning.html
<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.sqlalchemy.org_en_latest_orm_versioning.html&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=BlFY_Ge8eQsKWmvzFjG8WDvC_476YtRBCancu5pAbt8&s=-WhOlX8NTukfXp5q3ud1TpLWsGMqRa4SlHYYYMGGTqs&e=>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
