openstack
/
tripleo-docs
Code Issues Proposed changes

Stack Update - NetworkDeploymentActions 

Add a page regarding network configuration changes in post
deployment. Network configuration changes are disabled by
default, parameter override is required to enable network
re-configuration when necessary.

Related-Bug: #1804642
Change-Id: I0f834af0391649ac51e41fc1e9bbf3db458beac6
This commit is contained in:
Harald Jensås 2018-12-20 21:07:11 +01:00
parent 851030f9d3
commit 974cfb247f
2 changed files with 33 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/install/post_deployment/post_deployment.rst
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

32
doc/source/install/post_deployment/updating_network_configuration_post_deployment.rst Normal file
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']