ca3d5e47b0
Used by a new featureset[1] that uses the neutron ansible-networking driver to configure the switch providing networking for overcloud ironic nodes such that tenant networks are segregated via vlan. This scenario also sets up ssh keys so that ansible inside the neutron container can ssh to the controller to configure OVS. The new scenario also includes a temporary workaround to upgrade ansible in the neutron container, this can be removed once ansible in the container is v2.5.8+ Also remove scenario011 as the patches that used it never merged and now the tennant networks are working in the overcloud, we'll test with this instead. [1] - https://review.openstack.org/#/c/579601/ Change-Id: Ife83825216ccb96a5f24918f42a757d0c48b0e9d |
||
---|---|---|
.. | ||
network | ||
ceph-min-osds.yaml | ||
disable-unbound.yaml | ||
multinode-3nodes-registry.yaml | ||
multinode-3nodes.yaml | ||
multinode-containers.yaml | ||
multinode-core.yaml | ||
ovb-ha.yaml | ||
README.rst | ||
scenario000-multinode-containers.yaml | ||
scenario001-multinode-containers.yaml | ||
scenario002-multinode-containers.yaml | ||
scenario003-multinode-containers.yaml | ||
scenario004-multinode-containers.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 |
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.