delta/openstack/taskflow.git/taskflow/engines/action_engine/executor.py, branch 2.5.0

remove unused LOG

2016-07-09T17:44:38+00:00

This is to remove unused LOG to keep code clean.

Change-Id: Ie44659f3b7af9612f127f7d46bb2c1481b6a634f

Instead of a multiprocessing queue use sockets via asyncore

2016-05-24T23:16:56+00:00

For a local process based executor usage currently to ensure
that task emitted notifications are proxied we use the multi
processing library and use its queue concept. This sadly creates
a proxy process that gets associated, and this proxy process
handles the queue and messages sent to and from it. Instead of
doing this we can instead just create a temporary local socket
using a random socket and have tasks (which are running in
different processes) use that to communicate back any emitted
notifications instead (and we can use the asyncore module to handle
the emitted notifications since it handles the lower level socket
reading, polling and dispatching).

To ensure that the socket created is somewhat secure we use a
similar process as the multi-processing library uses where we
sign all messages with a hmac that uses a one time key that only
the main process and the child process know about (and reject
any messages that do not validate using this key).

Change-Id: Iff9180054bf14495e5667af00ae2fafbdbc23791

Allow for specifying green threaded to parallel engine

2016-05-03T18:00:51+00:00

Currently when a string is passed to the parallel engine
it will only know how to create a process or a native thread
based executor. The futurist library also supports making
a green thread based executor, so support creating it.

This will save glance some code that they have to create
a executor based on different options (one of those is a
green option).

Change-Id: I15c164a38b4445d28eb6062aed6c56cce0e0364b

Move all internal blather usage/calls to trace usage/calls

2015-12-18T06:39:14+00:00

Change-Id: I415a81d3b6b15b17a9a91cc2a0681c159172a4e1

Merge "Convert executor proxied engine options into their correct type"

2015-11-24T11:44:10+00:00

Convert executor proxied engine options into their correct type

2015-11-18T20:42:06+00:00

Change-Id: If0f213a0304bc336e95d72157cc2d4d402ebdd3f

Relabel internal engine 'event' -> 'outcome'

2015-10-05T20:12:07+00:00

Instead of calling the variable name 'event' it is
more appropriate to call these variable names 'outcome' (or
'outcomes') since they represent the 'outcome' (EXECUTED,
or REVERTED) of a atom and are not event types.

To avoid the confusion just relabel these to be outcome(s)
instead.

Change-Id: Ia9caebe279145e4887491151d40a4f59650d40d4

Create and use a serial retry executor

2015-07-21T17:10:23+00:00

To make it easily possible to change the retry
atom execution from being in the engine thread this
creates a retry executor (which is similar to the task
executor) and provide that a serial executor (which it will
use to execute with). This makes the retry and task actions
closer to being the same and makes the surrounding code that
much similar (which makes understanding it easier).

Change-Id: I993e938280df3bd97f8076293183ef21989e2dba

Provide a deprecated alias for the now removed stop watch class

2015-07-13T01:44:57+00:00

This allows those who were using it to still continue using it
until 2.0 where it will be removed; this makes it possible for
those users to get off that code in a way that will be easily
do-able (without totally breaking there code-bases, until we do
that in the 2.0 release).

This also removes all internal usage of that stop watch class
so that the library itself will not reference it anymore.

Change-Id: If313d8e7b9bdc8741db2e2e1dfb381aa3260b971

Integrate futurist (and remove taskflow originating code)

2015-07-09T22:01:35+00:00

Change-Id: If89baa042695f19e42b6368034f3ccf22c2cf0aa