tripleo-heat-templates/sample-env-generator/messaging.yaml
Cédric Jeanneret c9adaaeb2f Flatten rabbitmq service - step 2
Now that we could get rid of the puppet dedicated definitions,
we can move the docker/* rabbitmq related stuff to the final
location, and correct the paths and some nits.

Change-Id: I47ca1e303bd38642200ccb7f6823bcd06cd00255
2019-02-06 12:50:51 +01:00

36 lines
1.5 KiB
YAML

environments:
-
name: messaging/rpc-rabbitmq-notify-rabbitmq-shared
title: Share single rabbitmq backend for rpc and notify messaging backend
files:
deployment/rabbitmq/rabbitmq-messaging-rpc-container-puppet.yaml:
parameters:
- RpcPort
sample_value:
RpcPort: 5672
resource_registry:
OS::TripleO::Services::OsloMessagingRpc: ../../deployment/rabbitmq/rabbitmq-messaging-rpc-container-puppet.yaml
OS::TripleO::Services::OsloMessagingNotify: ../../deployment/rabbitmq/rabbitmq-messaging-notify-shared-puppet.yaml
description: |
Include this environment to enable a shared rabbitmq backend for
oslo.messaging rpc and notification services
-
name: messaging/rpc-qdrouterd-notify-rabbitmq-hybrid
title: Hybrid qdrouterd for rpc and rabbitmq for notify messaging backend
files:
puppet/services/messaging/rpc-qdrouterd.yaml:
parameters:
- RpcPort
deployment/rabbitmq/rabbitmq-messaging-notify-container-puppet.yaml:
parameters:
- NotifyPort
sample_values:
RpcPort: 31459
NotifyPort: 5672
resource_registry:
OS::TripleO::Services::OsloMessagingRpc: ../../docker/services/messaging/rpc-qdrouterd.yaml
OS::TripleO::Services::OsloMessagingNotify: ../../deployment/rabbitmq/rabbitmq-messaging-notify-container-puppet.yaml
description: |
Include this environment to enable hybrid messaging backends for
oslo.messaging rpc and notification services