Matt Crees 09df6fc1aa Add a flag to handle RabbitMQ high availability ... A combination of durable queues and classic queue mirroring can be used to provide high availability of RabbitMQ. However, these options should only be used together, otherwise the system will become unstable. Using the flag ``om_enable_rabbitmq_high_availability`` will either enable both options at once, or neither of them. There are some queues that should not be mirrored: * ``reply`` queues (these have a single consumer and TTL policy) * ``fanout`` queues (these have a TTL policy) * ``amq`` queues (these are auto-delete queues, with a single consumer) An exclusionary pattern is used in the classic mirroring policy. This pattern is ``^(?!(amq\\.)|(.*_fanout_)|(reply_)).*`` Change-Id: I51c8023b260eb40b2eaa91bd276b46890c215c25		2023-01-13 15:40:08 +00:00
..
event_definitions.yaml.j2	Deploy mistral-event-engine service	2018-11-06 17:50:54 +00:00
mistral-api.json.j2	Support policy.yaml file [part 3]	2018-01-22 08:50:54 +07:00
mistral-engine.json.j2	Support policy.yaml file [part 3]	2018-01-22 08:50:54 +07:00
mistral-event-engine.json.j2	Deploy mistral-event-engine service	2018-11-06 17:50:54 +00:00
mistral-executor.json.j2	Support policy.yaml file [part 3]	2018-01-22 08:50:54 +07:00
mistral.conf.j2	Add a flag to handle RabbitMQ high availability	2023-01-13 15:40:08 +00:00