With python 3.x, classes can use the metaclass= logic
to not require usage of the six library.
Subsequent patches will replace other six usages.
Change-Id: Iefdc99c338c7aaea18d535426c4676dbedb44f32
* Now it is impossible to set the same
pool name for queue listeners which use
event engine. By default, it creates
an unique pool named <hostname> so each
event engine is in its own pool. Due to
that and documentation of oslo.messaging,
any message that comes to topic duplicates
across all event engines.
* But if they have the same pool name, the message
will be delivered only to one of event-engines
(by round-robin).
* This patch adds a possibility to change listener pool
name for each event-engine.
Change-Id: Iea83c461694a26d9cea810e6cc6169a0fe3f9f06
When using event trigger feature, some of the notification data may be
useful to end users in their workflows. However, the whole data can not
be visible to end users due to security reasons.
This patch will give operators a chance to define what information will
be available to end users. If the definition is not found, a 'safe'
default setting will be used.
Change-Id: I8b6e9cbe318011d2d11a2bb91aaff4d37222c7eb
Implements: blueprint event-notification-trigger
This patch adds a new optional service in Mistral, event engine
service will listen to the message queue with exchange and topic users
configed, and trigger the corresponding workflow via rpc call to
mistral engine. The event engine service will receive rpc messages
from mistral api
Change-Id: I8bef24822575670ca90ef0479b9ce2e3e330cdeb
Implements: blueprint event-notification-trigger
Co-Authored-By: Lingxian Kong <anlin.kong@gmail.com>