![]() Congress doesn't seem to be used anywhere, we never had a bug report or any sign of somebody out there actually using it. Let's remove its support in TripleO, to reduce the codebase. Change-Id: Idca6b12f1c0ca3bc15bedf6469d4063a4dac31fa |
||
---|---|---|
.. | ||
network | ||
README.rst | ||
ceph-min-osds.yaml | ||
disable-unbound.yaml | ||
multinode-3nodes-registry.yaml | ||
multinode-3nodes.yaml | ||
multinode-containers.yaml | ||
multinode-core.yaml | ||
ovb-ha.yaml | ||
scenario000-multinode-containers.yaml | ||
scenario001-multinode-containers.yaml | ||
scenario001-standalone.yaml | ||
scenario002-multinode-containers.yaml | ||
scenario002-standalone.yaml | ||
scenario003-multinode-containers.yaml | ||
scenario003-standalone.yaml | ||
scenario004-multinode-containers.yaml | ||
scenario004-standalone.yaml | ||
scenario006-multinode-containers.yaml | ||
scenario006-multinode.yaml | ||
scenario007-multinode-containers.yaml | ||
scenario008-multinode-containers.yaml | ||
scenario009-multinode.yaml | ||
scenario010-multinode-containers.yaml | ||
scenario012-multinode-containers.yaml | ||
scenario012-standalone.yaml |
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.