[openstack-dev] [oslo] instance lock and class lock
Zang MingJie
zealot0630 at gmail.com
Fri Sep 5 05:29:24 UTC 2014
does it require bp or bug report to submit oslo.concurrency patch ?
On Wed, Sep 3, 2014 at 7:15 PM, Davanum Srinivas <davanum at gmail.com> wrote:
> Zang MingJie,
>
> Can you please consider submitting a review against oslo.concurrency?
>
>
> http://git.openstack.org/cgit/openstack/oslo.concurrency/tree/oslo/concurrency
>
> That will help everyone who will adopt/use that library.
>
> thanks,
> dims
>
> On Wed, Sep 3, 2014 at 1:45 AM, Zang MingJie <zealot0630 at gmail.com> wrote:
> > Hi all:
> >
> > currently oslo provides lock utility, but unlike other languages, it is
> > class lock, which prevent all instances call the function. IMO, oslo
> should
> > provide an instance lock, only lock current instance to gain better
> > concurrency.
> >
> > I have written a lock in a patch[1], please consider pick it into oslo
> >
> > [1]
> >
> https://review.openstack.org/#/c/114154/4/neutron/openstack/common/lockutils.py
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140905/9da14ab0/attachment.html>
More information about the OpenStack-dev
mailing list