<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/taskflow.git/taskflow/utils, branch 0.7.1</title>
<subtitle>opendev.org: openstack/taskflow.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/'/>
<entry>
<title>Revert "Add retries to fetching the zookeeper server version"</title>
<updated>2015-02-16T18:13:31+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@gmail.com</email>
</author>
<published>2015-02-16T18:13:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=9f60336aad60648415cbe711f8813196704f813a'/>
<id>9f60336aad60648415cbe711f8813196704f813a</id>
<content type='text'>
This reverts commit a14adc3c62658228a12d45e0851ae443c8429b85.

Change-Id: Ib0d1dad15142b3b8650d343515ad4c61db65db1b
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit a14adc3c62658228a12d45e0851ae443c8429b85.

Change-Id: Ib0d1dad15142b3b8650d343515ad4c61db65db1b
</pre>
</div>
</content>
</entry>
<entry>
<title>Add retries to fetching the zookeeper server version</title>
<updated>2015-02-16T04:07:22+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@yahoo-inc.com</email>
</author>
<published>2015-02-14T01:34:27+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=a14adc3c62658228a12d45e0851ae443c8429b85'/>
<id>a14adc3c62658228a12d45e0851ae443c8429b85</id>
<content type='text'>
Apparently the execution of four-letter commands to
zookeeper is known to be flakey (and you may receive
partial results) so to avoid this use the retrying
library during fetching/parsing of the server version
and try up to 3 times to get a valid version from the
zookeeper server.

When the following merges (and is released) we can
likely remove this equivalent/similar code:

https://github.com/python-zk/kazoo/pull/280

Change-Id: I9191c463c7969df101541463a76fe20ff5ed06af
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Apparently the execution of four-letter commands to
zookeeper is known to be flakey (and you may receive
partial results) so to avoid this use the retrying
library during fetching/parsing of the server version
and try up to 3 times to get a valid version from the
zookeeper server.

When the following merges (and is released) we can
likely remove this equivalent/similar code:

https://github.com/python-zk/kazoo/pull/280

Change-Id: I9191c463c7969df101541463a76fe20ff5ed06af
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge "Let the multi-lock convert the provided value to a tuple"</title>
<updated>2015-02-12T07:08:23+00:00</updated>
<author>
<name>Jenkins</name>
<email>jenkins@review.openstack.org</email>
</author>
<published>2015-02-12T07:08:23+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=c15b95d15cfb0481f6646762cb70687227fa1028'/>
<id>c15b95d15cfb0481f6646762cb70687227fa1028</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Let the multi-lock convert the provided value to a tuple</title>
<updated>2015-02-11T06:57:24+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@gmail.com</email>
</author>
<published>2015-02-11T06:55:37+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=59771ddc6d16468c5e2010ea16f2be552f02a679'/>
<id>59771ddc6d16468c5e2010ea16f2be552f02a679</id>
<content type='text'>
Instead of forcing the locks (list or tuple) into a list
and then having the multi-lock code force that back into
a tuple just pass the value through to the multi-lock
class and let it handle the conversion in a more easy to
understand manner (and one that doesn't involve as many
copies).

Change-Id: Ib0e78bacb80aea73af465a91cb4f509904f47990
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Instead of forcing the locks (list or tuple) into a list
and then having the multi-lock code force that back into
a tuple just pass the value through to the multi-lock
class and let it handle the conversion in a more easy to
understand manner (and one that doesn't involve as many
copies).

Change-Id: Ib0e78bacb80aea73af465a91cb4f509904f47990
</pre>
</div>
</content>
</entry>
<entry>
<title>Modify stop and add wait on conductor to prevent lockups</title>
<updated>2015-02-09T23:30:27+00:00</updated>
<author>
<name>Min Pae</name>
<email>sputnik13@gmail.com</email>
</author>
<published>2015-02-09T22:50:41+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=e7df6c66f041218b204a8b0785da0ee1b728dbda'/>
<id>e7df6c66f041218b204a8b0785da0ee1b728dbda</id>
<content type='text'>
Removed _dead.wait from the stop method and added a wait method to
explicitly wait for graceful shutdown.  Implicitly waiting for
graceful shutdown in the stop method is leading to potential
deadlock situations when conductor is running in the main thread
and a signal handler is used to kick off stop/shutdown.

Also in larger systems, it is desirable to be able to initiate
shutdown on all running services then wait/join everything together
so as not to force a serial shutdown pattern.

Change-Id: Ic74dab22b09100c5b653d12c2518f83a1bf8e859
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Removed _dead.wait from the stop method and added a wait method to
explicitly wait for graceful shutdown.  Implicitly waiting for
graceful shutdown in the stop method is leading to potential
deadlock situations when conductor is running in the main thread
and a signal handler is used to kick off stop/shutdown.

Also in larger systems, it is desirable to be able to initiate
shutdown on all running services then wait/join everything together
so as not to force a serial shutdown pattern.

Change-Id: Ic74dab22b09100c5b653d12c2518f83a1bf8e859
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge "Default to using a thread-safe storage unit"</title>
<updated>2015-02-07T19:11:21+00:00</updated>
<author>
<name>Jenkins</name>
<email>jenkins@review.openstack.org</email>
</author>
<published>2015-02-07T19:11:20+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=a2bb00c68ae8f8ba681558970ac6f97ad282a7ff'/>
<id>a2bb00c68ae8f8ba681558970ac6f97ad282a7ff</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Default to using a thread-safe storage unit</title>
<updated>2015-02-06T07:19:08+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@yahoo-inc.com</email>
</author>
<published>2015-02-06T00:31:33+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=08a184639635c57735c5ce0ca60aa727777c9e69'/>
<id>08a184639635c57735c5ce0ca60aa727777c9e69</id>
<content type='text'>
Instead of having a nominally useful single-threaded storage
unit that uses a dummy r/w lock and a multi-threaded storage
unit just have the storage unit by default protect itself from
multi-threading calls being used on it (with the appropriate
reader/writer locks being activated to make this work
correctly).

Change-Id: Ib6879edb465156a8e54fd5b4002550d1cec49137
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Instead of having a nominally useful single-threaded storage
unit that uses a dummy r/w lock and a multi-threaded storage
unit just have the storage unit by default protect itself from
multi-threading calls being used on it (with the appropriate
reader/writer locks being activated to make this work
correctly).

Change-Id: Ib6879edb465156a8e54fd5b4002550d1cec49137
</pre>
</div>
</content>
</entry>
<entry>
<title>Use a thread-identifier that can't easily be recycled</title>
<updated>2015-02-05T06:30:59+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@gmail.com</email>
</author>
<published>2015-02-05T06:23:45+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=2f4bd6897dbdf0081b00fa359baf221b11cb5db2'/>
<id>2f4bd6897dbdf0081b00fa359baf221b11cb5db2</id>
<content type='text'>
Since it is possible for a thread-id from get_ident() to
potentially be recycled at some point in the future it is
safer to use a object that will only be recycled when there
are no more references to it (including the references held
in the reader-writer lock internals).

This avoids any type of thread-identifier recycling issues
that could be possible since it is now assured that said
recycling will not happen until the reader-writer lock itself
is cleaned up by the garbage collector.

Change-Id: I2ea693fe8fc129943648edef8ed6c3596772ebc0
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since it is possible for a thread-id from get_ident() to
potentially be recycled at some point in the future it is
safer to use a object that will only be recycled when there
are no more references to it (including the references held
in the reader-writer lock internals).

This avoids any type of thread-identifier recycling issues
that could be possible since it is now assured that said
recycling will not happen until the reader-writer lock itself
is cleaned up by the garbage collector.

Change-Id: I2ea693fe8fc129943648edef8ed6c3596772ebc0
</pre>
</div>
</content>
</entry>
<entry>
<title>Add and use a nicer kombu message formatter</title>
<updated>2015-01-30T06:59:54+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@yahoo-inc.com</email>
</author>
<published>2015-01-26T21:56:34+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=99b92aed5de1d0868266ce63dec4f3b0e4a636d1'/>
<id>99b92aed5de1d0868266ce63dec4f3b0e4a636d1</id>
<content type='text'>
Since the kombu message object that is recieved has
no useful __str__ or __repr__ and on reception and processing
we should the message (and the delivery tag) it is nice to have
a more useful formatting of that message for debugging and
such (where more detail about the messages are quite useful
to see).

Change-Id: I6730b10122a5de1a0a074525931f312fbd97b8c0
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since the kombu message object that is recieved has
no useful __str__ or __repr__ and on reception and processing
we should the message (and the delivery tag) it is nice to have
a more useful formatting of that message for debugging and
such (where more detail about the messages are quite useful
to see).

Change-Id: I6730b10122a5de1a0a074525931f312fbd97b8c0
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge "Use importutils.try_import for optional eventlet imports"</title>
<updated>2015-01-29T08:37:19+00:00</updated>
<author>
<name>Jenkins</name>
<email>jenkins@review.openstack.org</email>
</author>
<published>2015-01-29T08:37:19+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/taskflow.git/commit/?id=708b01ec1240b5d28c19e4a8bf99f1a3d7c4912f'/>
<id>708b01ec1240b5d28c19e4a8bf99f1a3d7c4912f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
