On 13 Jun 2014, at 07:03, W Chan wrote:
> Design proposal for blueprint
> https://blueprints.launchpad.net/mistral/+spec/mistral-engine-executor-protocol
> Rename Executor to Worker.
I’d be ok with Worker but would prefer ActionRunner since it reflects the
purpose a little better although being
Hi Winson,
Sorry, I haven’t responded so far for I was on vacation. So getting back to you
now..
It’s my fault that the notes in the BP are not fairly clear.
1. By “worker parallelism” we meant that one worker (which is called “executor"
now) can poll and handle more than one task from the tas
Design proposal for blueprint
https://blueprints.launchpad.net/mistral/+spec/mistral-engine-executor-protocol
- Rename Executor to Worker.
- Continue to use RPC server-client model in oslo.messaging for Engine
and Worker protocol.
- Use asynchronous call (cast) between Worker and Engi
Renat,
Regarding blueprint
https://blueprints.launchpad.net/mistral/+spec/mistral-engine-executor-protocol,
can you clarify what it means by worker parallelism and
engine-executor parallelism?
Currently, the engine and executor are launched with the eventlet driver
in oslo.messaging. Once a mess
