openstack/tripleo-docs
Code Issues Proposed changes

Add the update-plan-only step for the minor updates workflow

Browse Source 
Currently we are missing the step to bring updated tht templates
in the swift container. Without that step you will run a minor update
which will always run the yum_update.sh script that was around
deployment time, making it impossible to ship fixes to the script
itself.

Change-Id: I28696be9925a31d305a4faca10a95ce7c7644cb3
This commit is contained in:
Michele Baldessari 2017-04-28 14:17:38 +02:00
parent d6ea7a94a4
commit a1be08894b
1 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -3,8 +3,20 @@
Updating Packages on Overcloud Nodes
====================================
You can update packages on all overcloud nodes with a command similar to the
following::
Updating packages on all overcloud nodes involves two steps. The first one
makes sure that the overcloud plan is updated (a new tripleo-heat-templates rpm
might have brought fixes/changes to the templates)::
openstack overcloud deploy --update-plan-only \
--templates \
-e <full environment>
By using the parameter ``--update-plan-only`` we make sure we update only the
stored overcloud plan and not the overcloud itself. Make sure you pass the
exact same environment parameters that were used at deployment time.
The second step consists in updating the packages themselves on all overcloud
nodes with a command similar to the following::
openstack overcloud update stack -i overcloud
@ -32,4 +44,4 @@ breakpoint on next one.
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.
commands.