Feature Overview

Validate if the Redfish operations used by the bare metal operator against nodes (power on/power off/power cycle/change boot device order/use virtual media) work on target nodes.

This validation would use a specific OpenShift version, i.e it can validate if the bare metal operator shipped with OpenShift 4.x succeeds or fails in issuing the required operations to manage the nodes.

Use Cases

• As an infrastructure admin I want to validate that the firmware version in my servers work against an an specific version of OpenShift before I proceed with the firmware upgrade on all my nodes
• As an infrastructure admin I want to validate that my servers will work successfully when managed by the bare metal operator in OpenShift for new cluster installations
• As an infrastructure admin I want to validate that my servers will work successfully when I upgrade my OpenShift cluster, where I expect new versions of the libraries that the bare metal operator uses

Background, and strategic fit

Customers find that upgrading the firmware in their servers sometimes makes the bare metal operator to stop working and the management of their nodes for power operations fail.

This can happen within same version of OpenShift, succeeding in managing one firmware version while failing in a different one.

This has also been reported to happen sometimes when changing the OpenShift version, and so using newer libraries of Redfish against the same firmware version.

With this feature users can know if a specific combination of OpenShift version and firmware version will succeed or fail before proceeding with an installation or an upgrade.