openstack
/
tripleo-docs
Code Issues Proposed changes

Merge "Further document disable node updates"

This commit is contained in:
Jenkins 2017-08-18 16:50:32 +00:00 committed by Gerrit Code Review
parent 7277e51f7a b366707fd9
commit 0ac90d2a7c
1 changed files with 34 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
doc/source/install/advanced_deployment/server_blacklist.rst
View File

@ -1,11 +1,14 @@
Blacklisting Servers from Heat Deployments
==========================================
Disabling updates to certain nodes
==================================
Server blacklist
----------------
Servers can be excluded from getting any updated Heat deployments by adding
them to a blacklist parameter called ``DeploymentServerBlacklist``.
Setting the blacklist
---------------------
_____________________
The ``DeploymentServerBlacklist`` parameter is a list of Heat server names.
Write a new environment file, or add the parameter value to an existing
@ -41,8 +44,18 @@ to certain servers only.
would not support blacklisting certain cluster members since it
could result is a misconfigured cluster.
.. warning::
The blacklist should not be used during the update or upgrade procedures.
Those procedures have their own methods for isolating changes to particular
servers. See the documentation for updates/upgrades for more information.
.. warning::
In cases where servers are added to the blacklist, further changes to those
nodes are not supported until the server is removed from the blacklist. This
includes updates/upgrades/scale up/scale down/node replacement.
Clearing the blacklist
----------------------
______________________
When clearing the blacklist for subsequent stack operations, an empty parameter
value must be sent with the deploy command. It is not sufficient to simply omit
the parameter since Heat will use the previously saved value.
@ -51,3 +64,20 @@ Send an empty list value to force Heat to clear the blacklist::
parameter_defaults:
DeploymentServerBlacklist: []
Skip deploy identifier
----------------------
The default behavior during a stack update operation is to force puppet to
reapply all manifests. This can be a time consuming operation and is not always
required if not changing any configuration date such as in the case of only
scaling out certain roles.
The beavhior can be overridden by passing ``--skip-deploy-identifier`` to the
``openstack overcloud deploy`` command.
Similar to the server blacklist feature, this feature should be used only when
the operator is sure that puppet can be safely skipped on the stack update.
.. note::
In some cases, puppet will still run even when ``--skip-deploy-identifier``
is specified. These cases include changes to puppet manifests or hieradata.