Ilker ManapandClaude Opus 5.5
3568c4866e
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>