delta/openstack/taskflow.git/taskflow/examples/graph_flow.py, branch master

Have this example exit non-zero if incorrect results

2015-03-13T23:14:34+00:00

When this examples engine does not produce the expected
results have it exit with a non-zero error code so that
the users knows (and so that the example testing system
fails when this happens).

Change-Id: I8c3b80a7dc1c7ef47d7804526346883b24caabc4

Deprecate `engine_conf` and prefer `engine` instead

2014-10-18T20:28:27+00:00

To avoid having one set of options coming from `engine_conf`
and another set of options coming from `kwargs` and another set
coming from `engine_conf` if it is a URI just start to shift
toward `engine_conf` being deprecated and `engine` being a string
type only (or a URI with additional query parameters) and having
any additional **kwargs that are provided just get merged into the
final engine options.

This adds a new helper function that handles all these various
options and adds in a keyword argument `engine` that will be shifted
to in a future version (in that future version we can also then
remove the `engine_conf` and just stick to a smaller set of option
mechanisms).

It also adjusts all examples to use this new and more easier to
understand format and adjusts tests, conductor interface to use
this new more easily understandable style of getting an engine.

Change-Id: Ic7617057338e0c63775cf38a24643cff6e454950

Cleanup some of the example code & docs

2014-07-11T21:20:02+00:00

This commit makes a set of small adjustments to examples.

- Rework some of the comments to be more clear.
- Add links to the original source tree file.
- Rename some of the examples to make it clear the
  concept the example is intented to show.
- Move some common example functionality to the
  example utility file.

Change-Id: I858e0dbf72fe8cb40a05bfdbb0857720ffb71c7f

Remove extraneous vim configuration comments

2014-02-14T08:56:50+00:00

Remove line containing

comment - # vim: tabstop=4 shiftwidth=4 softtabstop=4

Change-Id: I7581cc88b8de433d5609ed06c6570b0b45c13573
Closes-Bug:#1229324

Boost graph flow example comments

2013-10-16T20:56:03+00:00

Change-Id: Ibcfc2cd8e1b516d6481d3ae7e2c4fc753014fb53

Bump requirements to the latest

2013-10-05T21:49:08+00:00

Match the requirements for taskflow with
the openstack requirements (note the upstream
requirements are missing 'futures' and 'networkx')
and update the new hacking violations that were
detected due to the hacking requirement version
bump.

Change-Id: I8d1326cf2a8b1ea062f5e9aacd0c4f8261c6531a

Simpler API to load flows into engines

2013-10-03T06:08:55+00:00

Previously to run a flow client code had to put together the flow,
an engine, logbook, flowdetail, and storage backend. This commit
adds two helper functions, run() and load(), so that simplest usecase
now looks like

    taskflow.engines.run(flow)

Client code may also provide configuration for storage and engine if
needed, but if not needed it just works with defaults.

Engines are loaded via stevedore, as drivers in 'taskflow.engines'
backend. Now three entry points are defined in that namespace:
- 'default', for SingleThreadedActionEngine, used by default;
- 'serial', as another synonym for SingleThreadedActionEngine;
- 'parallel', for MultiThreadedActionEngine.

Closes-bug: #1224726
Change-Id: I7f4cb5c8ff7f5f12831ddd0952c202d2fd8cd6ef

Graph flow, sequential graph action

2013-09-18T16:04:18+00:00

Change-Id: I07cc820aa2f37d0f9599f34efab07b28cf47ca48