<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
> Excerpts from Josh's message:<br>
<br>
>> So a few 'event' like constructs/libraries that I know
about:<br>
>> <br>
>>
<a class="moz-txt-link-freetext" href="http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier">http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier</a>
<br>
>> <br>
>> <br>
>> I'd be happy to extract that and move to somewhere else if
needed, it <br>
>> provides basic event/pub/sub kind of activities for
taskflow (in-memory, <br>
>> not over rpc...)<br>
<br>
I've investigated several event libraries...And chose taskflow
because first of all it fits all our requirements and it is already
used in openstack.<br>
<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
> Excerpts from
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Doug's message<br>
<br>
>> We probably want the ability to have multiple callbacks.
There are<br>
>> already a lot of libraries available on PyPI for handling
"events" like<br>
>> this, so maybe we can pick one of those that is well
maintained and<br>
>> integrate it with oslo.service?<br>
<br>
I've created raw review in oslo.service
<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/228892/">https://review.openstack.org/#/c/228892/</a> .<br>
I've used taskflow library(as Josh proposed).<br>
By default I added one handler that reloads global configuration.<br>
What do you think about such implementation?<br>
<br>
Marian<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</body>
</html>