openstack
/
tripleo-heat-templates
Code Issues Proposed changes
tripleo-heat-templates/environments/updates
History
Jiri Stransky a12087715f Always use parameter_defaults in environment files 
In the environments/ subdirectory of tripleo-heat-templates, we mostly
use parameter_defaults, but some of the environment files still use
parameters. This can lead to confusing behavior with respect to
parameter priority when passing environment files to deploy/update
commands. Users might expect that subsequent environment files take
priority over preceding ones, but that might not be the case if the
preceding environment files use `parameters`, while the subsequent ones
use `parameter_defaults`.

This commit switches all `parameters:` uses in environments/
subdirectory to `parameter_defaults:`.

Change-Id: Ie4c03c7e7f5a5004a0384d35817135f357e9719b
Closes-Bug: #1567837
 		2016-04-11 14:15:39 -04:00
..
README.md Add update yaml backward compatibe with PublicVirtualIP on ctlplane 2015-12-15 12:59:22 +01:00
update-from-keystone-admin-internal-api.yaml Always use parameter_defaults in environment files 2016-04-11 14:15:39 -04:00
update-from-publicvip-on-ctlplane.yaml Add update yaml backward compatibe with PublicVirtualIP on ctlplane 2015-12-15 12:59:22 +01:00

README.md

This directory contains Heat environment file snippets which can be used to ensure smooth updates of the Overcloud.

Contents

update-from-keystone-admin-internal-api.yaml To be used if the Keystone Admin API was originally deployed on the Internal API network.

update-from-publicvip-on-ctlplane.yaml To be used if the PublicVirtualIP resource was deployed as an additional VIP on the 'ctlplane'.