4274ea94d9
for scenario004 We were using extra config to set ganesha_vip because it was unset if the isolated StorageNFS network is not deployed, as it is with Standalone deployment in CI. Now it is set, and set to an address on the external net where guest VMs can reach it. Related-Bug: #1911022 Change-Id: Ic20b3aaccc18c19973a07798f20a63ac9d5c0bb7 (cherry picked from commit |
||
---|---|---|
.. | ||
network | ||
README.rst | ||
ceph-min-osds.yaml | ||
disable-unbound.yaml | ||
multinode-3nodes-registry.yaml | ||
multinode-3nodes.yaml | ||
multinode-containers.yaml | ||
multinode-core.yaml | ||
neutron_l3_qos.yaml | ||
octavia-kvm.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 | ||
scenario007-standalone.yaml | ||
scenario010-multinode-containers.yaml | ||
scenario010-standalone.yaml | ||
scenario012-multinode-containers.yaml | ||
scenario012-standalone.yaml | ||
standalone-ipa.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.