48fda1c675
In https://review.openstack.org/#/c/542875 we created --output-dir with the default to $HOME/.undercloud-heat-installer which is not backward compatible when you upgrade from a non-containerized undercloud. Indeed, it'll fail to re-use the same passwords as the previous deployment because the undercloud-passwords.conf file is in $HOME. For backward compatibility, we should keep $HOME as default output_dir, and allow deployers to override it. Change-Id: I3b8464a3a2761d6cef319f2a1d08baedc9d8cc3e
21 lines
774 B
YAML
21 lines
774 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fix undercloud heat installer renders Heat templates in
|
|
`/usr/share`, which contains t-h-t installed from the package.
|
|
features:
|
|
- |
|
|
New command line arguments `--output-dir` and `--cleanup`
|
|
define the heat templates processing rules for undercloud:
|
|
``undercloud deploy --cleanup --output-dir /tmp/tht``.
|
|
|
|
The `output_dir` and `cleanup` configuration options
|
|
for `undercloud.conf` may be used the same way and allow to
|
|
configure ``undercloud install --use-heat`` behavior.
|
|
upgrade:
|
|
- |
|
|
The content of the processed heat templates will be persisted
|
|
under the given path as `$output_dir/$tempdir/templates`, for
|
|
each run of the undercloud deploy or install commands, unless
|
|
the `cleanup` mode is requested.
|