Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

If you update the stack with additional networks enabled, then TripleO will attempt to add the network to every node. This will also have the effect of changing the VIP addresses for services hosted by default on the new network. This will most likely require some manual recovery, as OpenStack services will break during the network changes. This is not well tested, but adding networks should be more successful than deleting or changing deployed networks.

In order to cause the network to be updated on a stack update (instead of only on deploy), you will need to set NetworkDeploymentActions for only one update. Update the network-related templates and environment files to include the new network(s). Add this to an environment file, for instance update_network.yaml, and run the original deployment command (along with any environment files originally included), and include the update_network.yaml environment file (only for this update):

update_network.yaml

parameter_defaults: NetworkDeploymentActions: ['CREATE', 'UPDATE']

Please not that since this procedure has not been well tested, there may be unintended consequences, up to and including rendering the deployment unusable.

If you update the stack with additional networks enabled, then TripleO will attempt to add the network to every node. This will also have the effect of changing the VIP addresses for services hosted by default on the new network. This will most likely require some manual recovery, as OpenStack services will break during the network changes. This is not well tested, but adding networks should be more successful than deleting or changing deployed networks.

In order to cause the network to be updated on a stack update (instead of only on deploy), you will need to set NetworkDeploymentActions for only one update. Update the network-related templates and environment files to include the new network(s). Add this to an environment file, for instance update_network.yaml, and run the original deployment command (along with any environment files originally included), and include the update_network.yaml environment file (only for this update):

update_network.yaml

# update_network.yaml
parameter_defaults:
  NetworkDeploymentActions: ['CREATE', 'UPDATE']

'UPDATE']

Please not that since this procedure has not been well tested, there may be unintended consequences, up to and including rendering the deployment unusable.