redfish

Redfish BMC: an infrastructure controller type, version 1. A controller of this type is written under controllers.infrastructure with type: redfish.

Its connectivity test identifies the system it reaches by service_root.uuid, so that a second controller for the same system is warned of.

Connection

In the controller’s connection:

• endpoint (string, required): BMC base URL, e.g. https://bmc-dc1.example.com
• insecure_skip_verify (bool): accept a self-signed BMC certificate
• timeout (duration, default 10s): per-request timeout

Auth methods

The controller’s auth.method is one of these. A field marked secret comes only from the secret auth.credentials_ref names; the others are set in auth.config, or in that secret.

basic

A BMC account.

• username (string, required)
• password (string, required, secret)

Capabilities

The controller enables each it uses in its capabilities list.

power.off

Force the system off; power it on to unfence.

Category: actuator; bound as fence; fencing level compute; resource system.

Settings, in its entry’s config:

• durable_power_fence (bool, default true): set PowerRestorePolicy to AlwaysOff before a fence, so the host stays off when power returns (ADR 0009 §3)
• unfenced_power_restore_policy (string, default LastState, one of AlwaysOn, AlwaysOff, LastState): PowerRestorePolicy set on unfence

Validation checks: role.ConfigureComponents.

power.evidence

Prove the system is off without switching it off (ADR 0007 §2); power it on to unfence.

Category: actuator; bound as fence; fencing level compute; resource system.

Validation checks: role.ConfigureComponents.

systems.list

The BMC’s computer systems, by id.

Category: discovery; resource system.

Addresses

Every address the type contacts. A secret’s scope (-scope-host) is checked against each that receives credentials.

• connection.endpoint (port url, receives credentials): the BMC’s Redfish service, sent its credentials with every call