Ivan A. Melnikov a91dd6b0e4 State management for engines ...

All state management moved to storage, including flow (engine) state,
task states, task results and failures.

Notifications for state changes were added.

Storage is now implemented using taskflow.persistence and enhanced with
means for result mapping and fetching task result by name.

Partially implements blueprint patterns-and-engines.

Co-authored-by: Anastasia Karpinska <akarpinska at griddynamics.com>
Change-Id: Ia4e5707687096c948bd8db4f3d8936bdac40dd6c

2013-09-04 16:52:36 +04:00

..

blocks

State management for engines

2013-09-04 16:52:36 +04:00

common

Dinky change to trigger jenkins so I can cleanup.

2013-06-19 13:20:31 -07:00

engines

State management for engines

2013-09-04 16:52:36 +04:00

examples

Split utils module

2013-09-03 11:42:53 +04:00

jobs

File movements

2013-08-17 20:34:19 -07:00

openstack

Use oslo's sqlalchemy layer

2013-08-18 09:17:51 -07:00

patterns

Initial implementation of action-based engine

2013-09-03 14:46:07 -07:00

persistence

State management for engines

2013-09-04 16:52:36 +04:00

tests

State management for engines

2013-09-04 16:52:36 +04:00

utils

Action engine: save task results

2013-09-03 14:52:50 -07:00

__init__.py

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

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

decorators.py

Rename "revert_with" => "revert" and "execute_with" to "execute"

2013-08-30 17:16:54 -04:00

exceptions.py

Add a locally running threaded flow

2013-08-26 12:45:21 -07:00

flow.py

Split utils module

2013-09-03 11:42:53 +04:00

states.py

Notify on task reversion

2013-08-29 12:41:22 -07:00

storage.py

State management for engines

2013-09-04 16:52:36 +04:00

task.py

State management for engines

2013-09-04 16:52:36 +04:00

test.py

Use the same root test class.

2013-08-26 17:26:03 -07:00