Ivan A. Melnikov 176bfa6ccb Do not erase task progress details ...

Before this change we used to loose any progress details set by task
when it was updating its progress when task state was changed from
RUNNING to SUCCESS (and thus progress forced to 1.0). This commit
fixes this, so that when progress is updated from the engine latest
progress details are preserved.

Breaking change: to allow details to be associated with progress
value they were set for we save progress and then return progress
value with details.

Change-Id: Ic90e61ee3dcf62731696a0f10134bc448e7d6384

2013-10-18 12:35:40 +04:00

..

engines

Do not erase task progress details

2013-10-18 12:35:40 +04:00

examples

Remove incorrect comment

2013-10-17 08:43:50 -07:00

jobs

Move toward python 3/2 compatible metaclass

2013-10-09 17:39:05 -07:00

listeners

Move toward python 3/2 compatible metaclass

2013-10-09 17:39:05 -07:00

openstack

Update oslo and bring py3kcompat in

2013-10-17 11:44:33 +04:00

patterns

Remove uuid from taskflow.flow.Flow

2013-10-15 10:52:05 +04:00

persistence

Use py3kcompat.urlutils from oslo instead of six.urllib_parse

2013-10-17 11:44:36 +04:00

tests

Do not erase task progress details

2013-10-18 12:35:40 +04:00

utils

Add debug logging showing what is flattened

2013-10-17 11:11:54 -07:00

__init__.py

Continue on getting ready for the memory impl. to be useful.

2013-05-12 14:45:24 -07:00

exceptions.py

Validate each flow state change

2013-10-07 16:46:02 +04:00

flow.py

Remove uuid from taskflow.flow.Flow

2013-10-15 10:52:05 +04:00

states.py

Remove task_action state checks

2013-10-16 20:05:17 -07:00

storage.py

Do not erase task progress details

2013-10-18 12:35:40 +04:00

task.py

Add more comments to flow/task

2013-10-12 22:47:35 -07:00

test.py

Add a flow flattening util

2013-09-20 12:41:57 +04:00