python-tripleoclient/releasenotes/notes/ephemeral-heat-by-default-4ed05e8b82f41c4b.yaml
James Slagle 9ae6487b6d Use ephemeral Heat by default
Switches to use ephemeral Heat by default for all overcloud operations
and defaults enable_heat to False in undercloud.conf. Stack data will be
migrated to the ephemeral Heat model (to use the consistent working
directory) as part of the upgrade with the inclusion of the depends-on.

To improve the UX when using ephemeral Heat, "stack resource list" is
now run after "stack failures list" automaticaly in the case of Heat
stack failures.

Signed-off-by: James Slagle <jslagle@redhat.com>
Change-Id: I22b2ec530f8b888a94a88e1726792a8afef227ab
(cherry picked from commit 030e9f0b57)
2021-06-30 07:12:18 -04:00

11 lines
524 B
YAML

---
features:
- An ephemeral Heat process is now used by default for overcloud deployment.
On each overcloud management operation (deploy/update/upgrade), a
containerized Heat process will be started, the stack will be created new,
and then the Heat process will be stopped. The enable_heat option is
undercloud.conf is now defaulted to False.
deprecations:
- Setting enable_heat=True in undercloud.conf is deprecated.
- Using --heat-type=installed is deprecated with the openstack overcloud commands.