Docs: improve package update admin docs
Add information on updating package repos and rebooting after a kernel update. Change-Id: If6b637a0fac58ac7564c051e15b86a483b040a34
This commit is contained in:
parent
3bc8d89577
commit
e884faab61
@ -5,8 +5,21 @@ Overcloud Administration
|
||||
Updating Packages
|
||||
=================
|
||||
|
||||
It is possible to update packages on the overcloud hosts. To update one or more
|
||||
packages::
|
||||
It is possible to update packages on the overcloud hosts.
|
||||
|
||||
Package Repositories
|
||||
--------------------
|
||||
|
||||
If using custom package repositories, it may be necessary to update these prior
|
||||
to running a package update. To do this, update the configuration in
|
||||
``${KAYOBE_CONFIG_PATH}/yum.yml`` and run the following command::
|
||||
|
||||
(kayobe) $ kayobe overcloud host configure --tags yum --kolla-tags none
|
||||
|
||||
Package Update
|
||||
--------------
|
||||
|
||||
To update one or more packages::
|
||||
|
||||
(kayobe) $ kayobe overcloud host package update --packages <package1>,<package2>
|
||||
|
||||
@ -21,6 +34,20 @@ To only install updates that have been marked security related::
|
||||
Note that these commands do not affect packages installed in containers, only
|
||||
those installed on the host.
|
||||
|
||||
Kernel Updates
|
||||
--------------
|
||||
|
||||
If the kernel has been updated, you will probably want to reboot the hosts to
|
||||
boot into the new kernel. This can be done using a command such as the
|
||||
following::
|
||||
|
||||
(kayobe) $ kayobe overcloud host command run --command "shutdown -r" --become
|
||||
|
||||
It is normally best to apply this to control plane hosts in batches to avoid
|
||||
clustered services from losing quorum. This can be achieved using the
|
||||
``--limit`` argument, and ensuring services are fully up after rebooting before
|
||||
proceeding with the next batch.
|
||||
|
||||
Running Commands
|
||||
================
|
||||
|
||||
|
@ -16,8 +16,21 @@ To deprovision the seed VM::
|
||||
Updating Packages
|
||||
=================
|
||||
|
||||
It is possible to update packages on the seed host. To update one or more
|
||||
packages::
|
||||
It is possible to update packages on the seed host.
|
||||
|
||||
Package Repositories
|
||||
--------------------
|
||||
|
||||
If using custom package repositories, it may be necessary to update these prior
|
||||
to running a package update. To do this, update the configuration in
|
||||
``${KAYOBE_CONFIG_PATH}/yum.yml`` and run the following command::
|
||||
|
||||
(kayobe) $ kayobe seed host configure --tags yum --kolla-tags none
|
||||
|
||||
Package Update
|
||||
--------------
|
||||
|
||||
To update one or more packages::
|
||||
|
||||
(kayobe) $ kayobe seed host package update --packages <package1>,<package2>
|
||||
|
||||
@ -32,6 +45,15 @@ To only install updates that have been marked security related::
|
||||
Note that these commands do not affect packages installed in containers, only
|
||||
those installed on the host.
|
||||
|
||||
Kernel Updates
|
||||
--------------
|
||||
|
||||
If the kernel has been updated, you will probably want to reboot the seed host
|
||||
to boot into the new kernel. This can be done using a command such as the
|
||||
following::
|
||||
|
||||
(kayobe) $ kayobe seed host command run --command "shutdown -r" --become
|
||||
|
||||
Examining the Bifrost Container
|
||||
===============================
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user