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

Fix a couple of spelling and grammar errors

2015-03-28T16:11:08+00:00

Some things that popped out while reading the
comments/documentation.

Change-Id: I0ccecae3381447ede44bb855d91f997349be1562

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

Doc strings and comments clean-up

2014-01-26T21:08:39+00:00

* Added missing period for doc strings
* Correct syntax errors
* Remove H402 from flake8 ignore list

Change-Id: Ia8592bf99378e3658d6cca2ceb148bf9eb0b5de8

Fix misspellings

2013-12-10T12:09:17+00:00

Change-Id: I6f332f01d197c6ba1b02de1145714718f8aea6fb

Add docs/intro to simple_linear example

2013-10-16T23:56:44+00:00

Change-Id: I6911337bf492d5cfc7e48a006dbf076826a18a62

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

Engine, task, linear_flow unification

2013-09-06T02:26:36+00:00

In order to move away from the existing flows having their
own implementation of running, start moving the existing
flows to be  patterns that only structure tasks (and impose
constraints about how the group of tasks can run) in useful
ways.

Let the concept of running those patterns be handled by an
engine instead of being handled by the flow itself. This
will allow for varying engines to be able to run flows in
whichever way the engine chooses (as long as the constraints
set up by the flow are observed).

Currently threaded flow and graph flow are broken by this
commit, since they have not been converted to being a
structure of tasks + constraints. The existing engine has
not yet been modified to run those structures either, work
is underway  to remediate this.

Part of: blueprint patterns-and-engines

Followup bugs that must be addressed:
  Bug: 1221448
  Bug: 1221505

Change-Id: I3a8b96179f336d1defe269728ebae0caa3d832d7

Converted some examples to use patterns/engines

2013-09-04T15:33:12+00:00

Change-Id: If7154019f1cb5e723069ff35f6301fce048323b5