openstack/tripleo-docs
Code Issues Proposed changes

Update docs to reflect changes to update command

Browse Source 
The update command no longer requires --templates and --environment-file
args. This reflects that change in the docs.

Change-Id: I98416a1eda647d2725ce960b7f70a8392c9d9c93
Depends-On: I8aa6262716534dec7b51e64f491d7131c359f802
This commit is contained in:
Brad P. Crochet 2016-10-12 08:16:18 -04:00
parent 2cadb10bdb
commit be73a19f14
1 changed files with 7 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
doc/source/post_deployment/package_update.rst
View File

@ -6,7 +6,7 @@ Updating Packages on Overcloud Nodes
You can update packages on all overcloud nodes with a command similar to the
following::
openstack overcloud update stack --templates [templates dir] -i overcloud -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml -e <all extra files>
openstack overcloud update stack -i overcloud
This command updates the ``UpdateIdentifier`` parameter and triggers stack update
operation. If this parameter is set, ``yum update`` command is executed on each
@ -16,24 +16,6 @@ sets breakpoints on each overcloud node so nodes are updated one by one. When
the update is finished on a node the command will prompt for removing
breakpoint on next one.
.. note::
When passing any extra environment files while creating the overcloud (for
instance, in order to configure :doc:`network isolation
<../advanced_deployment/network_isolation>`), pass them again here using the
``-e`` or ``--environment-file`` option to avoid making undesired changes to
the overcloud.
If you use Heat templates from the default location
(`/usr/share/openstack-tripleo-heat-templates`), it is possible that
these templates have changed when updating the undercloud machine. When
updating overcloud nodes, make sure you pass both the default registry
file and any extra environment files.
The reason is that CLI commands, which are changing an existing overcloud,
will pass new templates to Heat reusing the existing environment of the
overcloud. This leads to the condition in which a new `resource type`
referenced in updated templates might be missing in the existing environment.
.. note::
Make sure you use the ``-i`` parameter, otherwise update runs on background
and does not prompt for removing of breakpoints.
@ -45,3 +27,9 @@ breakpoint on next one.
.. note::
If the update command is aborted for some reason you can always continue
in the process by re-running same command.
.. note::
The --templates and --environment-file (-e) are now deprecated. They can still
be passed to the command, but they will be silently ignored. This is due to
the plan now used for deployment should only be modified via plan modification
commands.