Add a doc note about updating changed templates
Documents how to update an existing overcloud after new heat templates have been installed. Change-Id: I02c0610aca1cf7ac303a487326844d275b0ff1a6 Related-To: 1501296
This commit is contained in:
parent
4a189f2a9a
commit
a5c6420035
@ -16,4 +16,24 @@ You can upgrade any packages that are installed on the undercloud machine.
|
||||
|
||||
# You can specify the package names to update as options in the yum update command.
|
||||
|
||||
You do not need to restart any services after you update.
|
||||
.. note::
|
||||
|
||||
You do not need to restart any services after you update.
|
||||
|
||||
#. Update stack environment of the existing overcloud:
|
||||
|
||||
If you use heat templates from default location
|
||||
(`/usr/share/openstack-tripleo-heat-templates`), it's possible that these
|
||||
templates have changed when updating undercloud machine. You should update
|
||||
the existing overcloud to reflect any changes in template and environment
|
||||
files. The reason is that CLI commands which change existing overcloud pass
|
||||
new template to Heat but reuse existing environment of the overcloud so a
|
||||
new resource type referenced in updated template might be missing in the
|
||||
existing environment::
|
||||
|
||||
openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml -e <all extra files>
|
||||
|
||||
.. note::
|
||||
|
||||
Make sure you pass all environment files you used when deploying
|
||||
overcloud.
|
||||
|
Loading…
x
Reference in New Issue
Block a user