openstack/tripleo-docs
Code Issues Proposed changes
57ad98aa36
tripleo-docs/doc/source/install/post_deployment/updating-stacks-notes.rst
Bogdan Dobrelya e7c8bf345f Document standalone/UC update Heat stack specifics 
Explain the overcloud vs undercloud/standalone heat stack updates
Document use cases for the --force-stack-update option and how
it can be used with --dry-run and --output-only.
Briefly mention --dry-run and --output-only as well.

Depends-on: I7c7b2bd6d202268fdf4bc08f951ec4c9c4065c08
Related-bug: #1778505

Change-Id: Ie24eaec6871990e38df4e66abe2cc1ea866d9bd9
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
2018-09-25 12:23:42 +02:00

1.7 KiB
Raw Blame History

Understanding undercloud/standalone stack updates

To update a service password or a secret when upgrading from a non-containerized undercloud, you should edit undercloud.conf. Then you should use the openstack undercloud upgrade command.

Note

undercloud.conf takes priority over tripleo-undercloud-passwords.yaml only when running the undercloud upgrade command. For the undercloud install command, you should edit tripleo-undercloud-passwords.yaml instead.

In order to apply changes for an existing containerized undercloud or standalone installation, there is an important thing to remember.

Undercloud and standalone heat installers create one-time ephemeral stacks. Unlike the normal overcloud stacks, they cannot be updated via the regular stack update procedure. Instead, the created heat stacks may be updated virtually. For the most of the cases, the installer will take care of it automatically via the StackAction heat parameter overrides.

You can enforce the virtual update/create of the heat stack via the --force-stack-update and --force-stack-create options.

And the recommended command to apply changes for an existing containerized undercloud installation is:

openstack undercloud install --force-stack-update

Otherwise, start a new installation with --force-stack-create. New passwords will be generated in tripleo-undercloud-passwords.yaml.

It is better to be always explicit.

Note

The console log for these operations will always have heat reporting the STACK_CREATED status. Check the deployment logs for the actual virtual create or update actions taken.