delta/openstack/taskflow.git/taskflow/patterns, branch 2.5.0

Fix some misspellings in the function name and descriptions

2016-06-30T15:44:49+00:00

Change-Id: I7e3451feb94b1f25b00c5e7b197bb6b527548306

Allow for alterations in decider 'area of influence'

2016-01-10T06:42:17+00:00

Christmas came early.

Closes-Bug: #1479466

Change-Id: I931d826690c925f022dbfffe9afb7bf41345b1d0

Use graphs as the underlying structure of patterns

2015-09-18T17:39:04+00:00

This unifies all the patterns to be graph based so
that they are more uniform and there underlying constraints
are more easy to understand (taskflow basically processes
graphs).

Change-Id: Ib2ab07c1c87165cf40a06508128010887f658391

iter_nodes method added to flows

2015-08-28T14:54:25+00:00

New method allows to iterate over flow node and
get access to node metadata during iteration.

Change-Id: Ib0fc77f0597961602fbc3b49ba09e4df815d8230

Improve docstrings in graph flow to denote exceptions raised

2015-08-06T00:36:44+00:00

Link the existing exceptions mentioned to there sphinx doc about
them and also adds a section about when the 'DependencyFailure'
exception is raised.

Also tweaks the class docstring a little, to make it easier to
understand.

Change-Id: Ie4b989444c5ad73660cc61c0c3b2b1702b669087

Add docs for u, v, decider on graph flow link method

2015-07-10T21:18:25+00:00

The docstring is now quite important to know what the
params are (they are no longer as obvious due to the
decider addition) so add a useful docstring to that
method.

This also fixes how the targeted flow add was not passing
allow **kwargs as it should have been and removes the
duplicated docstrings that are in the child class (the
parent class docstrings are just fine).

Change-Id: Idacb7ee9f652fab4bdc762c1b49d7523e46e9a7b

Add support for conditional execution

2015-07-01T06:04:31+00:00

To make it possible to alter the runtime flow via a simple
conditional like structure make it possible to have the graph
flow link function take a decider that is expected to be some
callable that will decide (via a boolean return) whether the
edge should actually be traversed when running. When a decider
returns false; the affected + successors will be set into the
IGNORE state and they will be exempt from future runtime and
scheduling decisions.

Part of blueprint taskflow-conditional-execution

Change-Id: Iab0ee46f86d6b8e747911174d54a7295b3fa404d

Use 'node' terminology instead of 'item' terminology

2015-03-30T20:05:43+00:00

Since graphs are composed of 'nodes' it seems more
appropriate to use that terminology (which is known
to people with graph experience) instead of the non
descriptive and/or standard 'item' terminology.

Change-Id: I04a4521386d3cdf7e58fb9fa8cf26c00443c2cf6

Make the graph '_unsatisfied_requires' be a staticmethod

2015-03-26T00:47:16+00:00

To make it possible for users to subclass this flow and
replace this method (if they so choose to) make it a static
method that is directed to the current module level function
and call into the staticmethod when used (users can override
staticmethods and change them in subclasses).

Change-Id: I747c45636596ca5a8ad81dabcbba12ab55ce77d7

Use ordered[set/dict] to retain ordering

2015-03-11T18:12:06+00:00

Instead of using always using a set/dict which do not retain
use a ordered set and a ordered dict for requires, optional,
and provides and rebind mappings types so that the ordering
of these containers is maintained later when they are used.

These ordering can be useful depending on the atom type (such
as in a map and reduce tasks).

Partial-Bug: 1357117

Change-Id: I365d11bbba4aa221bc36ca15441acecf199b4d56