Joshua Harlow 19f9674877 Abstract out the worker finding from the WBE engine

To be able to easily plug-in future types of ways to get
which topics (and tasks) workers exist on (and can perform)
and to identify and keep this information up-to date refactor
the functionality that currently does this using periodic messages
into a finder type and a periodic function that exists on
it (that will be periodically activated by an updated and
improved periodic worker).

Part of blueprint wbe-worker-info

Change-Id: Ib3ae29758af3d244b4ac4624ac380caf88b159fd

2015-01-31 23:03:25 -08:00

1.3 KiB

Raw Blame History

Types

Note

Even though these types are made for public consumption and usage should be encouraged/easily possible it should be noted that these may be moved out to new libraries at various points in the future (for example the FSM code may move to its own oslo supported automaton library at some point in the future¹). If you are using these types without using the rest of this library it is strongly encouraged that you be a vocal proponent of getting these made into isolated libraries (as using these types in this manner is not the expected and/or desired usage).

Cache

taskflow.types.cache

Failure

taskflow.types.failure

FSM

taskflow.types.fsm

Futures

taskflow.types.futures

Graph

taskflow.types.graph

Notifier

taskflow.types.notifier

Periodic

taskflow.types.periodic

Table

taskflow.types.table

Timing

taskflow.types.timing

Tree

taskflow.types.tree

See: https://review.openstack.org/#/c/141961 for a proposal to do this.↩︎

1.3 KiB Raw Blame History