![Dougal Matthews](/assets/img/avatar_default.png)
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
34 lines
1.4 KiB
ReStructuredText
34 lines
1.4 KiB
ReStructuredText
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 :doc:`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.
|