Joshua Harlow 756e09778d Rename get_graph() -> execution_graph ...

Instead of having a generic get_graph()
it is nicer to have this function be named
closer to what it returns (the graph of tasks
to be executed) as well as make it a property
since it is more of a property of the engine.

Change-Id: I4bb458b1069d7e6877f1cc51d42bfc0d8c751951

2013-10-13 02:03:37 +00:00

..

engines

Rename get_graph() -> execution_graph

2013-10-13 02:03:37 +00:00

examples

Merge "Add more comments that explain example & usage"

2013-10-12 00:05:43 +00: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 copy and bring over versionutils

2013-10-09 19:19:47 -07:00

patterns

Add reasons as to why the edges were created

2013-10-07 15:39:44 -07:00

persistence

Fix several python3 incompatibilities

2013-10-11 11:32:56 +04:00

tests

Rename get_graph() -> execution_graph

2013-10-13 02:03:37 +00:00

utils

Fix several python3 incompatibilities

2013-10-11 11:32:56 +04: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

Move toward python 3/2 compatible metaclass

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

states.py

A few wording/spelling adjustments

2013-10-08 14:16:57 -07:00

storage.py

Fix several python3 incompatibilities

2013-10-11 11:32:56 +04:00

task.py

Move toward python 3/2 compatible metaclass

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

test.py

Add a flow flattening util

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