Joshua Harlow 359cc490bd Create and use a serial retry executor ...

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

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

..

__init__.py

Removed copyright from empty files

2014-02-22 17:16:29 +08:00

test_creation.py

Increase robustness of WBE producer/consumers

2015-01-20 15:07:56 -08:00

test_dispatcher.py

Make the dispatcher handler be an actual type

2015-02-15 20:21:24 -08:00

test_endpoint.py

Switch to using 'oslo_utils' vs 'oslo.utils'

2015-01-14 23:56:11 -08:00

test_executor.py

Create and use a serial retry executor

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

test_message_pump.py

Remove 2.6 classifier + 2.6 compatibility code

2015-06-21 09:39:12 -07:00

test_pipeline.py

Create and use a serial retry executor

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

test_protocol.py

Integrate futurist (and **remove** taskflow originating code)

2015-07-09 15:01:35 -07:00

test_proxy.py

Use explicit WBE object arguments (instead of kwargs)

2015-01-22 12:13:17 -08:00

test_server.py

Add + use failure json schema validation

2015-03-11 12:53:15 -07:00

test_types.py

Move to using the oslo.utils stop watch

2015-03-20 17:40:24 -07:00

test_worker.py

Merge "Retain atom 'revert' result (or failure)"

2015-07-15 00:02:41 +00:00