1dec175241
This change converts the existing NIC templates to jinja2 in order to dynamically render the ports and networks according to the network_data.yaml. If networks are added to the network_data.yaml file, parameters will be added to all NIC templates. The YAML files (as output from jinja with the default network_data.yaml) are present as an example. The roles in roles_data.yaml are used to produce NIC configs for the standard and custom composable roles. In order to keep the ordering of NICs the same in the multiple-nics templates, the order of networks was changed in the network_data.yaml file. This is reflected in the network templates, and in some of the files that is the only change. The roles and roles_data.yaml were modified to include a legacy name for the NIC config templates for the built-in roles Controller, Compute, Object Storage, Block Storage, Ceph Storage, Compute-DPDK, and Networker roles. There will now be a file produced with the legacy name, but also one produced with the <role>-role.j2.yaml format (along with environment files to help use the new filenames). Note this change also fixes some typos as well as a number of templates that had VLANs with device: entries which were ignored. Closes-Bug: 1737041 Depends-On: I49c0245c36de3103671080fd1c8cfb3432856f35 Change-Id: I3bdb7d00dab5a023dd8b9c94c0f89f84357ae7a4 |
||
---|---|---|
.. | ||
network | ||
ceph-min-osds.yaml | ||
multinode_major_upgrade.yaml | ||
multinode-3nodes-registry.yaml | ||
multinode-3nodes.yaml | ||
multinode-containers.yaml | ||
multinode-core.yaml | ||
multinode.yaml | ||
ovb-ha.yaml | ||
README.rst | ||
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 |
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.