tripleo-heat-templates/ci/environments
Emilien Macchi 28f926f96e CI/scenarios: set NotificationDriver to 'noop'
So we don't waste RabbitMQ resources since nothing will actually consume
the messages sent on the queue.

Note: we don't change scenario001, since it's a Telemetry scenario and
the services require notifications enabled.

Change-Id: I7d1d80da4eda7c0385461fe62b1d3038022973c6
2017-07-14 17:13:04 +00:00
..
README.rst Add README to ci/environments directory 2017-06-27 14:47:55 -05:00
ceph-min-osds.yaml Add Ceph configuration with PoolDefaultSize 1 2017-06-27 22:41:56 +03:00
multinode-3nodes.yaml SSHD Service extensions 2017-04-19 18:03:02 +01:00
multinode-containers.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
multinode-core.yaml Update the template_version alias for all the templates to pike. 2017-05-19 09:58:07 +02:00
multinode.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
multinode_major_upgrade.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
scenario001-multinode-containers.yaml Disable network validation in multinode jobs 2017-07-08 14:49:42 +00:00
scenario001-multinode.yaml Disable network validation in multinode jobs 2017-07-08 14:49:42 +00:00
scenario002-multinode-containers.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
scenario002-multinode.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
scenario003-multinode-containers.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
scenario003-multinode.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
scenario004-multinode-containers.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
scenario004-multinode.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00
scenario006-multinode-containers.yaml CI/scenarios: set NotificationDriver to 'noop' 2017-07-14 17:13:04 +00:00

README.rst

This directory contains environments that are used in tripleo-ci. They may change from release to release or within a release, and should not be relied upon in a production environment. The top-level environments directory in tripleo-heat-templates contains the production-ready environment files.