8ec4cae920
Co-Authored-By: Ana Krivokapic <akrivoka@redhat.com> Co-Authored-By: Ben Nemec <bnemec@redhat.com> Co-Authored-By: Ben Nemec <cybertron@nemebean.com> Co-Authored-By: Brad P. Crochet <brad@redhat.com> Co-Authored-By: Crag Wolfe <cwolfe@redhat.com> Co-Authored-By: Dan Sneddon <dsneddon@redhat.com> Co-Authored-By: David Kranz <dkranz@redhat.com> Co-Authored-By: Derek Higgins <derekh@redhat.com> Co-Authored-By: Dimitri Savineau <dsavinea@redhat.com> Co-Authored-By: Dmitry Tantsur <divius.inside@gmail.com> Co-Authored-By: Dmitry Tantsur <dtantsur@redhat.com> Co-Authored-By: Dougal Matthews <dougal@redhat.com> Co-Authored-By: François Charlier <francois.charlier@redhat.com> Co-Authored-By: Giulio Fidente <gfidente@redhat.com> Co-Authored-By: Imre Farkas <ifarkas@redhat.com> Co-Authored-By: James Slagle <jslagle@redhat.com> Co-Authored-By: Jan Provaznik <jprovazn@redhat.com> Co-Authored-By: Jaromir Coufal <jcoufal@redhat.com> Co-Authored-By: Jay Dobies <jason.dobies@redhat.com> Co-Authored-By: Jeff Peeler <jpeeler@redhat.com> Co-Authored-By: Jiri Stransky <jistr@redhat.com> Co-Authored-By: Jiri Tomasek <jtomasek@redhat.com> Co-Authored-By: John Trowbridge <trown@redhat.com> Co-Authored-By: Lennart Regebro <regebro@gmail.com> Co-Authored-By: Lucas Alvares Gomes <lucasagomes@gmail.com> Co-Authored-By: Marek Aufart <maufart@redhat.com> Co-Authored-By: Ronelle Landy <rlandy@redhat.com> Co-Authored-By: Sasha Chuzhoy <sasha@redhat.com> Co-Authored-By: Sasha Chuzhoy <sashac88@hotmail.com> Co-Authored-By: Steven Hardy <shardy@redhat.com> Co-Authored-By: Zane Bitter <zbitter@redhat.com> Co-Authored-By: marios <marios@redhat.com>
1.7 KiB
Updating Packages on Overcloud Nodes
You can update packages on all overcloud nodes with command:
openstack overcloud update stack --plan $PLAN_UUID -i overcloudThis command updates UpdateIdentifier parameter in the overcloud tuskar plan 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
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.
Updating Packages on Overcloud Nodes Without Using Tuskar
If the overcloud was deployed from heat templates directly
<../advanced_deployment/template_deploy> then use the
--templates parameter when updating packages:
openstack overcloud update stack --templates [templates dir] -i overcloudIf 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.