openstack/tripleo-heat-templates
Code Issues Proposed changes
9f7c5e70db
tripleo-heat-templates/ci/environments
History
Ade Lee ec6a94bd79 Autogenerate the barbican simple crypto KEK 
Code recently merged in tripleo-common to autogenerate the simple
crypto KEK.  Can therefore not specify it in scenario002.

Change-Id: I8e432b3500fc0e65154c34b292d05ff8c19c45d6
2017-12-12 15:37:23 -05:00
..
network Change template names to queens 2017-11-23 10:15:32 +01:00
ceph-min-osds.yaml Add Ceph configuration with PoolDefaultSize 1 2017-06-27 22:41:56 +03:00
multinode_major_upgrade.yaml Remove Heat Cloudwatch API 2017-10-11 09:54:38 +02:00
multinode-3nodes-registry.yaml Adding multinode-3nodes-registry.yaml 2017-10-18 09:28:21 +02:00
multinode-3nodes.yaml Remove Heat Cloudwatch API 2017-10-11 09:54:38 +02:00
multinode-containers.yaml Reintroduce TripleoPackages in the default Controller service. 2017-11-30 18:21:04 +01:00
multinode-core.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
multinode.yaml Remove Heat Cloudwatch API 2017-10-11 09:54:38 +02:00
ovb-ha.yaml ci: add ovb-ha.yaml 2017-11-28 16:49:30 +00:00
README.rst Add README to ci/environments directory 2017-06-27 14:47:55 -05:00
scenario001-multinode-containers.yaml CI: Test multi-rbd backend for cinder in scenario001 2017-12-04 16:25:51 -05:00
scenario002-multinode-containers.yaml Autogenerate the barbican simple crypto KEK 2017-12-12 15:37:23 -05:00
scenario003-multinode-containers.yaml ci: remove Heat services from some scenarios 2017-11-22 12:07:43 -08:00
scenario004-multinode-containers.yaml ci: remove Heat services from some scenarios 2017-11-22 12:07:43 -08:00
scenario006-multinode-containers.yaml Stop mapping docker to OS::Heat::None in scenarios 2017-09-27 11:15:35 +02:00
scenario006-multinode.yaml Don't fail Kubespray scenario if swap is enabled 2017-11-29 13:40:20 +01:00
scenario007-multinode-containers.yaml Merge "ci-ovn: Disable Swift services in scenario 007 container job" 2017-10-19 03:35:10 +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.