<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style='font-family: Verdana,Geneva,sans-serif'>
<p>On 2014-01-15 05:51, Victor Sergeyev wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px">
<div dir="ltr">
<div>Hello All.</div>
<div> </div>
<div>As for lockutils - a few days ago I wondered why we used custom oslo module instead of lockfile library [1]. AFAIK, it must be due to this bug [2] (please fix me, if I wrong).</div>
<div> </div>
<div>This library is available on github [3] and there is a pull-request fixing the bug [4], but unfortunately it hasn’t been merged yet. And seems that this project is not maintained anymore - author told, that he “haven't done anything with it in a few years” [5]. </div>
<div> </div>
<div>So my question is - can we start maintaining this library (put it on stackforge) and use it instead of oslo.lockutils? Or maybe we could include parts of oslo.lockutils into lockfile? Or vice versa, incorporate lockfile into oslo.lockutils?</div>
<div> </div>
<div>[1] <a href="https://pypi.python.org/pypi/lockfile">https://pypi.python.org/pypi/lockfile</a></div>
<div>[2] <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857</a></div>
<div>[3] <a href="https://github.com/smontanaro/pylockfile">https://github.com/smontanaro/pylockfile</a></div>
<div>[4] <a href="https://github.com/smontanaro/pylockfile/pull/3">https://github.com/smontanaro/pylockfile/pull/3</a></div>
<div>[5] <a href="https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554">https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554</a></div>
</div>
<div class="gmail_extra"> </div>
</blockquote>
<p>The problem is that lockfile doesn't really solve our current problem, which is where to put the lock files. Fortunately, it sounds like Julien is working on changes to lockutils to remove the file based locking, which should solve the issues we're having with it right now.</p>
<p>-Ben</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px">
<div class="gmail_extra"><br /><br />
<div class="gmail_quote">On Wed, Jan 15, 2014 at 1:00 AM, Michael Still <span><<a href="mailto:mikal@stillhq.com">mikal@stillhq.com</a>></span> wrote:<br />
<div class="im">On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec <<a href="mailto:openstack@nemebean.com">openstack@nemebean.com</a>> wrote:<br /><br /> > It would be nice to get lockutils graduated to solve some of the issues<br /> > mentioned in the oslo.db section, but I believe we do have an outstanding<br /> > question regarding its behavior without lock_path being set. I think Clint<br /> > was on board with Sean's proposed solution after quite a bit of discussion<br /> > (<a href="http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html">http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html</a>),<br /> > so it's possible we could just restore that patch and call it done, but it<br /> > should probably be addressed somehow before graduation.<br /><br /></div>
I committed a while ago (at the last summit IIRC) to working on<br /> getting lockutils released as a library, but I haven't managed to get<br /> that done yet. If it is blocking other people I can prioritise that<br /> work to being higher on my todo list.<br /><br /> Part of the problem here is that its my first oslo graduation, so I<br /> need to figure out what to do...<br />
<div class="HOEnZb">
<div class="h5"><br /> Michael<br /><br /> --<br /> Rackspace Australia<br /><br /> _______________________________________________<br /> OpenStack-dev mailing list<br /><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br /><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</div>
</div>
</div>
</blockquote>
<p> </p>
<div> </div>
</body></html>