Firmware: docs; lab emulator keeps state (StateDirectory)
CI / agent (push) Successful in 3s
CI / site (push) Successful in 2s
CI / go (push) Successful in 40s

Found in the lab run: pve-redfish runs with ProtectSystem=strict, so it
could not write its firmware state and dropped the reset request that
applies a staged BIOS. Tested end to end on the lab: iDRAC profile
multipart BMC update, iLO profile pull of BMC and BIOS through rack
controller pxe-rack2 with -reboot, model check and -force, resume of a
running update across a region restart.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-29 20:48:52 +01:00
1 parent b01d8e2b4d
commit e0cca3033e
4 files changed
+83 -2

No files matched your search

+9
View File
@@ -14,6 +14,15 @@ publish a tag that has no section here.
the PowerDNS API (ownership by RRset comment) or RFC 2136 dynamic update with TSIG (ownership by a
`_rollcall.<name>` TXT marker and update prerequisites, so foreign records are never overwritten;
drift is detected by querying). `rollcall dns`, `rollcall dns sync [-dry]`, a doctor check.
- Firmware updates over Redfish. A package repository on the region (`rollcall firmware import`
from a file or URL, served to BMCs through rack controllers) and each machine's firmware inventory.
- Update jobs: hand-over, task watch through BMC restarts, optional power cycle, version check
against the inventory. They resume after a region restart.
- Vendor plans from documentation or vendor tools: Dell, HPE (`.fwpkg` unpacked), Lenovo,
Supermicro, GIGABYTE/AMI/ASRock Rack, OpenBMC, xFusion, KAYTUS, Fujitsu iRMC. Cisco CIMC is
refused (SCP only).
- `fw_method`, `fw_params` and `firmware_base` on the BMC record.
- CLI `rollcall firmware`, a Firmware tab and repository in the web UI.
- Redfish vendor profiles: one standard driver plus per-vendor behaviour from public documentation,
for Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro, xFusion/Huawei iBMC, KAYTUS/Inspur, Fujitsu iRMC,
Cisco CIMC, GIGABYTE, ASRock Rack, OpenBMC and AMI MegaRAC.
+68
View File
@@ -567,6 +567,74 @@ rollcall bmc m-1234 -driver redfish -set system=/redfish/v1/Systems/1 -set verif
rollcall bmc m-1234 -probe # detect Redfish again
```
### Firmware updates (Redfish)
Rollcall keeps firmware packages in a repository on the region, reads each
machine's firmware inventory from its BMC, and runs updates as jobs.
```sh
# on the region: a file (or from anywhere: an https URL, which the region downloads)
sudo rollcall firmware import BIOS_R760_WN64_2.3.5.EXE -vendor idrac -component bios -version 2.3.5 -models R760 -sha256 ...
rollcall firmware list
rollcall firmware show m-1234 -refresh # what is installed, what the repository offers
rollcall firmware update m-1234 idrac-bios-2.3.5-2c49752f -reboot -watch
rollcall firmware update tag:r760 idrac-bmc-7.20.10.50-097a4a54
```
**The package.** A package names the BMC driver it is for (`idrac`, `ilo`,
`supermicro`, ...), a component (`bios`, `bmc`, `nic`, `raid`, `cpld`,
`psu`, `drive`, `other`), the version the component reports once installed,
and optionally the models it fits. An update refuses a package for another
vendor or model unless `-force`. The BMC checks the package itself:
signature, model and downgrade policy. An HPE `.fwpkg` is unpacked at
import to the iLO `.bin` or UEFI `.signed.flash` inside, because iLO's
SimpleUpdate accepts a `.fwpkg` and then flashes nothing.
**The job.** The region drives the update through the rack controller next
to the BMC:
1. It hands the package over: an upload, or the BMC downloads it from the
rack controller's `/firmware/`. Set `firmware_base=` on the BMC record
when BMCs reach another address.
2. It watches the BMC's task. A BMC that restarts after flashing itself is
waited for, up to 25 minutes.
3. It reads the inventory until the new version shows.
`-reboot` power-cycles the host when the update waits for a reset (BIOS on
most vendors), then verifies. Without it, a staged update ends as
"accepted, applies at the next reboot". A running update survives a region
restart. It cannot be cancelled once the BMC has the package.
**How each vendor takes a package.** Each vendor profile in
`cmd/rollcall/redfish_fwplans.go` carries its documented request, with
sources. Without a profile, the standard methods are tried in this order:
multipart push, SimpleUpdate pull, HttpPushUri.
| Driver | How | Packages | Notes |
|---|---|---|---|
| `idrac` | MultipartUpload (SimpleUpdate pull on older iDRAC 9) | DUP `.EXE`, `.d9` | OnReset by default; BIOS/RAID/NIC apply at the next reboot |
| `ilo` | SimpleUpdate: iLO pulls over HTTP | iLO `.bin`, UEFI `.signed.flash` (from `.fwpkg`) | components only an OS agent flashes need SUM/iSUT |
| `xcc` | `/mfwupdate`, after taking `HttpPushUriTargetsBusy` | `.uxz` | update XCC before UEFI |
| `supermicro` | `/UpdateService/upload` with targets and preserve options | `.bin` | licence SFT-OOB-LIC/SFT-DCMS-SINGLE; host powered off for BIOS |
| `gigabyte`, `ami`, `asrockrack` | `/UpdateService/upload` with `OemParameters` ImageType | `.ima`, `.ima_enc`, `.hpm`, `.bin` | the BMC restarts after a BMC flash; ASRock Rack unverified |
| `openbmc` | update-multipart (BMC Immediate, others OnReset) | signed `.tar` | |
| `xfusion` | upload to `/tmp/web`, then SimpleUpdate | `.hpm` | BMC, BIOS, CPLD |
| `kaytus` | upload, then OEM SimpleUpdate (FlashItem) | `.hpm`, `.bin` | from KAYTUS's own SDK; BMC and BIOS |
| `irmc` | OEM actions (FWUpdate, BiosUpdate) | iRMC `.bin`, BIOS `.UPC` | |
| `cimc` | not supported | | Cisco documents only SCP pulls |
Per machine, on the BMC record:
| Setting | Effect |
|---|---|
| `fw_method=multipart\|simple\|push` | skip the vendor plan and use this standard method |
| `fw_params={...}` | replace the plan's UpdateParameters (e.g. Supermicro Gen 13 BIOS preserve options) |
| `firmware_base=http://ADDR` | the address BMCs download from |
The lab Redfish emulator has an UpdateService of the same shape: iDRAC
profile multipart, iLO profile pull. The BMC version applies at once, the
BIOS at the next reset.
The lab has `lab/pve-vbmc/pve_redfish.py`, a Redfish service per Proxmox VM
with iDRAC, iLO and generic profiles, next to the IPMI emulator.
+1
View File
@@ -11,6 +11,7 @@ Restart=always
RestartSec=3
AmbientCapabilities=CAP_NET_BIND_SERVICE
User=pve-vbmc
StateDirectory=pve-vbmc
Group=pve-vbmc
NoNewPrivileges=yes
ProtectSystem=strict
+5 -2
View File
@@ -111,8 +111,11 @@ class Firmware:
self.v = {"bmc": "1.0.0", "bios": "1.0.0", "staged_bios": ""}
def save(self):
os.makedirs(os.path.dirname(self.path), exist_ok=True)
json.dump(self.v, open(self.path, "w"))
try:
os.makedirs(os.path.dirname(self.path), exist_ok=True)
json.dump(self.v, open(self.path, "w"))
except OSError as e: # the versions still hold in memory
log.warning("cannot keep firmware state in %s: %s", self.path, e)
def inventory(self):
return [{"@odata.id": f"/redfish/v1/UpdateService/FirmwareInventory/{self.prof['ids'][c]}-{self.v[c]}", "Id": f"{self.prof['ids'][c]}-{self.v[c]}",