44ef2a3ec1
The new master branch should point now to rocky. So, HOT templates should specify that they might contain features for rocky release [1] Also, this submission updates the yaml validation to use only latest heat_version alias. There are cases in which we will need to set the version for specific templates i.e. mixed versions, so there is added a variable to assign specific templates to specific heat_version aliases, avoiding the introductions of error by bulk replacing the the old version in new releases. [1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b |
||
---|---|---|
.. | ||
network | ||
README.rst | ||
ceph-min-osds.yaml | ||
multinode-3nodes-registry.yaml | ||
multinode-3nodes.yaml | ||
multinode-containers.yaml | ||
multinode-core.yaml | ||
multinode.yaml | ||
multinode_major_upgrade.yaml | ||
ovb-ha.yaml | ||
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 | ||
scenario009-multinode.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.