delta/openstack/taskflow.git/taskflow/retry.py, branch 2.5.0

Refactor Atom/BaseTask/Task/Retry class hierarchy

2016-02-19T03:58:59+00:00

* Moved common argument mapping logic to Atom
* Removed BaseTask
* Removed duplicated logic from subclasses

Change-Id: I275745adb80cecb0c35c1230eac76436bf3b0157

Add optional 'defer_reverts' behavior

2015-11-18T01:03:41+00:00

This makes it possible to REVERT a subflow
and have it also revert the parent flow if
the parent flow doesn't have its own retry
strategy. We will probably want to make this
new behavior the default or only behavior
in a future release.

Change-Id: Iea5ac366380ba7396a87d0185703549fb0c2f825

Document more of the retry subclasses special keyword arguments

2015-06-16T00:16:47+00:00

Change-Id: Iaa3949da61c95ffe697fd80cef3ee8a6febd2a8c

Adding a revert_all option to retry controllers

2015-06-12T00:31:54+00:00

When a retry controller is added to a nested flow, with the exception of
AlwaysRetryAll, existing retry controllers do not cause a revert of
predecessor tasks in the surrounding flow.  This is due to the fact that
these retry controllers always return RETRY.

The revert_all option, when set True, will result in the retry
controller returning REVERT_ALL rather than REVERT, which will cause
predecessor tasks in the surrounding flow to also be REVERTed.

Change-Id: I2d867b2d05e8559121ec48fd7249f15078450532

Use the enum library for the retry strategy enumerations

2015-02-20T01:07:03+00:00

Instead of having a set of string constants that are the
retry strategy/decision result have it instead be an enumerator
that can be more clearly associated in docs and in code that
these values are explicitly the strategies that the retry
code can use (making it more obvious to users of these constants
what they are for).

This also updates the retry docs to use this new linkable
class when describing the various strategies that can be
used/returned.

Change-Id: I944e521562be26f5315d7553da8d5820fc284c49

Merge "Add a history retry object, makes retry histories easier to use"

2014-12-18T21:24:41+00:00

Add and use a new simple helper logging module

2014-12-09T06:09:13+00:00

Add a new logging BLATHER level to easily allow its
usage for messages that are below the normal DEBUG level
such as compilation information and scope lookup info
which can be very verbose in logs if always enabled.

Change-Id: I828211403bd02bfd6777b10cdcfe58fb0637a52c

Add a history retry object, makes retry histories easier to use

2014-11-19T21:04:38+00:00

When a retry object is asked to make a decision about the atoms
it controls it is currently provided a complex object that contains
what has failed and why and what was provided to try to resolve this
failure as raw types. To make it easier to interact with that history
provide and use a more easier to interact with helper object that
provides useful functionality built ontop of the raw types.

Part of blueprint intuitive-retries

Change-Id: I93f86552f5a0c26b269319e4de6d9b8fb3b3b219

Use constants for retry automatically provided kwargs

2014-10-20T03:58:33+00:00

Instead of using strings use module level constants for
the automatically provided keyword arguments to the retry
revert/execution functions. This makes it easier for users
of taskflow to associate these constants with the actual
keywords, without having to resort to using raw strings
directly.

Change-Id: I739a0ad69819c3ca0d10c98966012cf9ef1b86bd

Document more function/class/method params

2014-09-26T18:43:45+00:00

To help fill out the docs start adding on docstrings
that document what a parameter is and what its meaning
and usage is to help users better understand the parameter.

Part of ongoing bug 1374202

Change-Id: I9f9a83cfb763a0a05d22efca4e0f80627ba8ca8f