Merge "Stack Update - NetworkDeploymentActions"

This commit is contained in:
Zuul 2018-12-28 08:38:50 +00:00 committed by Gerrit Code Review
commit a466ac0197
2 changed files with 33 additions and 0 deletions

View File

@ -17,3 +17,4 @@ In this chapter you will find advanced management of various |project| areas.
upload_single_image
update_undercloud_ssh_keys
fernet_key_rotation
updating_network_configuration_post_deployment

View File

@ -0,0 +1,32 @@
.. _update_network_configuration_post_deploymenet:
Updating network configuration on the Overcloud after a deployment
==================================================================
By default, subsequent change(s) made to network configuration templates
(bonding options, mtu, bond type, etc) are not applied on existing nodes when
the overcloud stack is updated.
.. Warning:: Network configuration updates are disabled by default to avoid
issues that may arise from network reconfiguration.
Network configuration updates should only be enabled when needed.
To push an updated network configuration add ``UPDATE`` to list of actions set
in the ``NetworkDeploymentActions`` parameter. (The default is ``['CREATE']``,
to enable network configuration on stack update it must be changed to:
``['CREATE','UPDATE']``.)
* Enable update of the network configuration for all roles by adding the
following to ``parameter_defaults`` in an environment file::
parameter_defaults:
NetworkDeploymentActions: ['CREATE','UPDATE']
* Limit the network configuration update to nodes of a specific role by using a
role-specific parameter, i.e: ``{role.name}NetworkDeploymentActions``. For
example to update the network configuration on the nodes in the Compute role,
add the following to ``parameter_defaults`` in an environment file::
parameter_defaults:
ComputeNetworkDeploymentActions: ['CREATE','UPDATE']