openstack/taskflow
Code Issues Proposed changes
7a1a467a7a
taskflow/doc/source/index.rst
Joshua Harlow addc286409 Use explicit WBE object arguments (instead of kwargs) 
Instead of passing around kwargs to root WBE classes and to
contained classes prefer to use explicitnamed arguments that are
passed around. This makes the code more obvious as to what
the intended arguments are and makes it easier for error validation
when other unknown arguments are passed (as well as for docs).

Also moves the docs for the worker engine to be a sub-TOC under
the main engine document so that it can be more easily explored
and managed/found...

Change-Id: I9413fad187c330fee494f0d4536cc27d9a90f0fb
2015-01-22 12:13:17 -08:00

2.7 KiB
Raw Blame History

TaskFlow

TaskFlow is a Python library that helps to make task execution easy, consistent and reliable.1

Note

If you are just getting started or looking for an overview please visit: http://wiki.openstack.org/wiki/TaskFlow which provides better introductory material, description of high level goals and related content.

Contents

atoms arguments_and_results inputs_and_outputs

patterns engines notifications persistence resumption

jobs conductors

Examples

While developing TaskFlow the team has worked hard to make sure the various concepts are explained by relevant examples. Here are a few selected examples to get started (ordered by perceived complexity):

examples

To explore more of these examples please check out the examples directory in the TaskFlow source tree.

Note

If the examples provided are not satisfactory (or up to your standards) contributions are welcome and very much appreciated to help improve them. The higher the quality and the clearer the examples are the better and more useful they are for everyone.

Considerations

Things to consider before (and during) development and integration with TaskFlow into your project:

  • Read over the paradigm shifts and engage the team in IRC (or via the openstack-dev mailing list) if these need more explanation (prefix [TaskFlow] to your emails subject to get an even faster response).
  • Follow (or at least attempt to follow) some of the established best practices (feel free to add your own suggested best practices).
  • Keep in touch with the team (see above); we are all friendly and enjoy knowing your use cases and learning how we can help make your lives easier by adding or adjusting functionality in this library.

Miscellaneous

exceptions states types utils

Indices and tables

  • genindex
  • modindex
  • search

  1. It should be noted that even though it is designed with OpenStack integration in mind, and that is where most of its current integration is it aims to be generally usable and useful in any project.↩︎