openstack/tripleo-docs
Code Issues Proposed changes
tripleo-docs/doc/source/post_deployment/package_update.rst
Dougal Matthews b2ad22819b Remove Tuskar from the CLI usage 
The command line workflows with Tuskar have proven to be more limited than
using Heat directly. This change removes Tuskar from the CLI documentation and
updates all the examples.

Essentially this means removing all uses of --plan in the deploy command and
all other 'openstack management ...' commands.

Tuskar is still referenced in a number of places and can't be fully removed
until there is an alternative for the Tuskar UI.

Change-Id: I2d4aa114156c5bafb003e6a67862ed6d1449fd98
2015-09-23 15:16:24 +01:00

1.4 KiB
Raw Blame History

Updating Packages on Overcloud Nodes

You can update packages on all overcloud nodes with command:

openstack overcloud update stack --templates [templates dir] -i overcloud

This command updates the UpdateIdentifier parameter and triggers stack update operation. If this parameter is set 'yum update' command is executed and each node. Because running update on all nodes in parallel might be unsafe (an update of a package might involve restarting a service), the command above sets breakpoints on each overcloud node so nodes are updated one by one. When the update is finished on a node the command will prompt for removing breakpoint on next one.

Note

If you passed any extra environment files when you created the overcloud (for instance, in order to configure network isolation <../advanced_deployment/network_isolation>), you must pass them again here using the -e or --environment-file option to avoid making undesired changes to the overcloud.

Note

Multiple breakpoints can be removed by specifying list of nodes with a regular expression.

Note

Make sure you use -i parameter, otherwise update runs on background and doesn't prompt for removing of breakpoints.

Note

If the update command is aborted for some reason you can always continue in the process by re-running same command.