mhorban wrote:
 > Excerpts from Josh's message:

 >> So a few 'event' like constructs/libraries that I know about:
 >>
 >>
http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier

 >>
 >>
 >> I'd be happy to extract that and move to somewhere else if needed, it
 >> provides basic event/pub/sub kind of activities for taskflow
(in-memory,
 >> not over rpc...)

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.

Very cool, will check more of that review out,

Although if we are going to go forward with this it's probably a good idea to split that notification class/code out of taskflow and into its own tiny library, so that taskflow and oslo.service can use it (this is how https://github.com/openstack/automaton and https://github.com/openstack/futurist came into being). That avoids having to bring in all of taskflow when you are using just *one* of its types/classes (and aren't really using the rest of taskflow).



 > Excerpts from Doug's message

 >> We probably want the ability to have multiple callbacks. There are
 >> already a lot of libraries available on PyPI for handling "events" like
 >> this, so maybe we can pick one of those that is well maintained and
 >> integrate it with oslo.service?

I've created raw review in oslo.service
https://review.openstack.org/#/c/228892/ .
I've used taskflow library(as Josh proposed).
By default I added one handler that reloads global configuration.
What do you think about such implementation?

Marian

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to