4a59519f6b
First review in a group to change instances of stx-openstack to |prefix|-openstack This group includes non-install guides. Fixed 1 file. Change-Id: Ib7e03b64373ca5e608be8b082ac2f26be5a4e50a Signed-off-by: MCamp859 <maryx.camp@intel.com>
2.0 KiB
Overview
Firmware update orchestration allows the firmware on the hosts of an entire system to be updated with a single operation.
You can configure and run firmware update orchestration using the , or the stx-nfv VIM REST API.
Note
Firmware update is currently not supported on the Horizon Web interface. Only host device firmware update is currently supported.
Firmware update orchestration requirements
Firmware update orchestration can only be done on a system that meets the following conditions:
The system is clear of alarms (with the exception of alarms for locked hosts, stopped instances, and firmware updates in progress).
Note
When configuring firmware update orchestration, you have the option to ignore alarms that are not management-affecting severity. For more information, see
Kubernetes Version Upgrade Cloud Orchestration <configuring-kubernetes-update-orchestration>.There are unlocked-enabled worker function hosts in the system that requires firmware update. The Firmware Update Orchestration Strategy creation step will fail if there are no qualified hosts detected.
Firmware update is a reboot required operation. Therefore, in systems that have the -openstack application applied with running instances, if the migrate option is selected there must be spare openstack-compute (worker) capacity to move instances off the openstack-compute (worker) host(s) being updated.
Note
Administrative controller Swacts should be avoided during firmware update orchestration.
For more information, refer to the following:
the-firmware-update-orchestration-process firmware-update-operations-requiring-manual-migration