Redfish vendor profiles from public documentation
One DMTF Redfish implementation, plus a profile per vendor with what its documentation (or Ironic/sushy, MAAS, bmclib field notes) says is different, each with sources: Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro, xFusion/Huawei iBMC, KAYTUS/Inspur, Fujitsu iRMC, Cisco CIMC, GIGABYTE, ASRock Rack, OpenBMC, AMI MegaRAC. Generic rules: reset types and boot targets from AllowableValues or ActionInfo; boot target, enable and mode in one PATCH, the mode kept, omitted or tried per profile; If-Match from header or @odata.etag with 412 (strong, then none) and 428 handling; AMI future-state /SD and @Redfish.Settings targets; busy retries (POST, 409, 503, "Retry in"); 202 task following; chassis reset fallback; emulated power cycle; session login; 400 answers that say Success. Probe results (reset types, boot targets, mode, profile) are kept on the BMC record and shown in the UI; the UI's driver list comes from the server. Each profile has a fake BMC test built from its sources. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a549f01ef5
commit
3568c4866e
6 files changed
+1293
-297
No files matched your search
@@ -498,13 +498,64 @@ that reaches the BMC network.
|
||||
| Driver | For |
|
||||
|---|---|
|
||||
| `ipmi` | IPMI 2.0 over LAN (ipmitool lanplus), any vendor; settings `cipher` (17 on newer BMCs), `privilege`, `interface` |
|
||||
| `redfish` | DMTF Redfish, any vendor: system discovered, ResetType chosen from what the BMC allows, boot override once (with If-Match where the BMC wants it) |
|
||||
| `idrac` | Dell iDRAC 8/9 (Redfish, `System.Embedded.1`) |
|
||||
| `ilo` | HPE iLO 4 (2.30+), 5, 6 (Redfish; no PowerCycle, so ForceRestart; PushPowerButton for soft off on older firmware) |
|
||||
| `supermicro`, `xcc`, `openbmc` | Supermicro, Lenovo XClarity, OpenBMC (Redfish) |
|
||||
| `redfish` and the vendor drivers below | DMTF Redfish (see below) |
|
||||
| `proxmox` | Proxmox VE VMs: API token (user = token id, password = secret), settings `node`, `vmid` |
|
||||
| `manual` | no power control; actions say so |
|
||||
|
||||
### Redfish across vendors
|
||||
|
||||
There is one Redfish implementation of the DMTF standard. These rules hold for
|
||||
every vendor:
|
||||
|
||||
- **Reset types and boot targets.** Read from what the BMC advertises
|
||||
(`@Redfish.AllowableValues` or the action's ActionInfo), never assumed.
|
||||
- **Boot override.** Target and enable go in one PATCH.
|
||||
- **If-Match.** Sent with the resource's ETag (header or `@odata.etag`). On
|
||||
412 it is retried with the strong form, then without; on 428 it is fetched
|
||||
first.
|
||||
- **Pending settings.** A BMC that keeps them elsewhere (`.../SD`,
|
||||
`@Redfish.Settings`) gets the same PATCH there.
|
||||
- **Busy answers.** Retried for up to a minute: the server is in POST, 409
|
||||
right after a power change, 503, "Retry in N seconds".
|
||||
- **202 answers.** Followed to their task monitor.
|
||||
- **Reset on the chassis.** Used when the system has no reset of its own.
|
||||
- **Missing power cycle.** ForceOff, wait for Off, then On.
|
||||
- **Paths from the BMC.** Only followed if they stay on the BMC and under
|
||||
`/redfish/`.
|
||||
|
||||
What a vendor documents differently is a profile in
|
||||
`cmd/rollcall/redfish.go`, with its sources. The profile decides the driver
|
||||
name, how the BMC is recognised, its usual system path, the boot mode rule, how
|
||||
to clear an override and the login method.
|
||||
|
||||
| Driver | Vendor | Boot mode in an override | Notes |
|
||||
|---|---|---|---|
|
||||
| `idrac` | Dell iDRAC 8/9/10 | not sent: a change starts a BIOS job | `System.Embedded.1`; iDRAC 10 takes boot settings at `.../Settings` |
|
||||
| `ilo` | HPE iLO 4 (2.30+), 5, 6 | current one, without it if refused | no PowerCycle (ForceRestart); no boot changes during POST (retried) |
|
||||
| `xcc` | Lenovo XCC, XCC2 | current one, without it if refused | override is Once only |
|
||||
| `supermicro` | Supermicro X11+, H12+ | always the current one | left out, some boards switch to Legacy |
|
||||
| `xfusion` | xFusion / Huawei iBMC | current one, without it if refused | session login; If-Match on every PATCH; ForcePowerCycle |
|
||||
| `kaytus` | KAYTUS / Inspur | current one, without it if refused | no public Redfish guide: reset may be on the chassis, a PATCH that worked can answer 400 |
|
||||
| `irmc` | Fujitsu / Fsas iRMC S5, S6 | not sent | `Systems/0`; ETag from the body; clearing is Target None (never Enabled Disabled); no GracefulShutdown (power button) |
|
||||
| `cimc` | Cisco UCS C-series CIMC | current one, without it if refused | `Systems/<serial>`, found through the collection |
|
||||
| `gigabyte` | GIGABYTE (MegaRAC SP-X) | always the current one | `Systems/Self`; If-Match required; short reset list |
|
||||
| `asrockrack` | ASRock Rack (MegaRAC) | always the current one | boot settings in `Systems/Self/SD` |
|
||||
| `openbmc` | OpenBMC (bmcweb) | current one, without it if refused | `Systems/system` |
|
||||
| `ami` | AMI MegaRAC SP-X boards | always the current one | `Systems/Self`; If-Match required |
|
||||
|
||||
Settings a machine can override:
|
||||
|
||||
| Setting | Effect |
|
||||
|---|---|
|
||||
| `system=` | the system path |
|
||||
| `boot_mode=UEFI\|Legacy` | always send this mode |
|
||||
| `auth=session\|basic` | login method |
|
||||
| `verify_tls=true` | check the BMC's certificate |
|
||||
|
||||
Every profile is tested against a fake service that behaves as its sources
|
||||
describe (`redfish_test.go`). The profiles have not yet run against the real
|
||||
machines.
|
||||
|
||||
After commissioning, a BMC still on IPMI is asked whether it speaks Redfish
|
||||
with the same account; if it does, the driver for its vendor takes over
|
||||
(event `bmc driver`). An operator's choice is never overridden.
|
||||
|
||||
Reference in new issue
Block a user