Software EBOM + Interface Spec — AI-Tray-2U Rev B

A complete, filled portfolio artifact (no placeholders) — the ODM-facing contract for a concrete node, as you'd hand to Pegatron. Derived from the template in ../EBOM-AND-PROTOCOL-DOCS.md. Status: Approved, owner: Rack SW Platform, last validated: 2026-06-13, applies to rack class rack-ai-01.

1. Node summary

  • Model: AI-Tray-2U Rev B · 2U · 1× host CPU socket · 4× AI accelerators · 1× 400G NIC · 1× BMC.
  • Power: typical 1.48 kW, nameplate 2.0 kW (cap), liquid-cooled (cold plates on accelerators + CPU).
  • Mgmt: BMC on mgmt VLAN 10; data NIC on tenant VLANs 100–199.

2. Firmware baseline (the reconciliation target — Phase 01/08)

ComponentBaselineMin (anti-rollback)Signed byA/BUpdate pathOwner
BIOS/UEFI2.4.12.4.0ODM key PGT-BIOS-2026yesRedfish UpdateService (Task)Pegatron
BMC (OpenBMC)obmc-1.8.0obmc-1.7.2Platform keyyesRedfish + JTAG recoveryUs + Pegatron (upstream)
Accelerator FWaccel-fw-2.1.0accel-fw-2.0.5Accel vendoryesvendor tool / RedfishAccel vendor
400G NIC FWnic-fw-3.2.0nic-fw-3.1.0NIC vendornoin-band agentNIC vendor
PSU FWpsu-1.0.3psu-1.0.3ODMnoBMC (PMBus)Pegatron
PCIe switchpex-4.1pex-4.0Switch vendornoBMCMicrochip
CPLDcpld-0.7cpld-0.7ODMnoBMC/JTAGPegatron

3. Software components (Phase 11 compatibility)

ComponentVersionCompat window
rack-agent (DaemonSet)1.5.3control-plane ≥ 1.4, ≤ 1.6
metrics exporter1.3.1Prometheus ≥ 2.40
RackNode operator0.9.0k8s/RKE2 ≥ 1.27

4. Config & security baselines (Phase 09)

  • Secure Boot: enabled; PK = RACKMGR-PK-2026; KEK = {RACKMGR-KEK, MS-UEFI-KEK}; db includes the signed shim/GRUB/kernel; dbx revokes grub-2.06-cve-2023-pre.
  • Attestation: required before tenant scheduling; golden PCR set published per (BIOS, BMC, OS) triple in the attestation service; AK enrolled at commissioning.
  • Network: mgmt VLAN 10 (control-plane only — hard boundary); tenant VLANs 100–199; QoS HTB with a reserved 10 Gbit management class.
  • Power/thermal: derated feed 17.3 kW; rack CDU 130 kW; N+1 power, N+1 pumps.

5. Interface spec (Redfish 2023.2) — the build-to-it contract

  • Required resources: ServiceRoot; Systems/{id} (PowerState, ProcessorSummary, Actions/#ComputerSystem.Reset); Chassis/{id} (Power, Thermal); Managers/{id}; UpdateService; EventService; TaskService. Oem/Rackmgr on Chassis MUST expose RackPosition (U), PowerBudgetW.
  • Sensors (Thermal.Temperatures[]): MUST include Inlet, CPU1 Temp, Accel0..3 Temp, each with ReadingCelsius (units Celsius) and UpperThresholdCritical. A sensor with no reading MUST return ReadingCelsius: null (not omit the entry, not 0).
  • Reset: MUST advertise ResetType@Redfish.AllowableValues ⊇ {On, ForceOff, GracefulShutdown, ForceRestart, GracefulRestart, PowerCycle}; a GracefulShutdown to a non-responsive host MUST NOT report success.
  • Firmware: UpdateService.SimpleUpdate MUST return 202 + a Task; TaskState New→Running→Completed|Exception; BMC update MUST be A/B with a recovery path.
  • Auth/transport: HTTPS only; cert chains to RACKMGR-MGMT-CA; Session tokens; least-privilege roles (ReadOnly for telemetry).
  • Errors: 4xx/5xx + @Message.ExtendedInfo; never 200 with an error body.
  • Events: EventService subscriptions + SSE; PSU, thermal, and PCIe-fatal events MUST be emitted.

6. Conformance checks (executable spec — Phase 11)

ReqCheckStatus (2026-06-13)
§5 resourcesGET each; assert presence + @odata.typePASS
§5 sensorsassert Inlet/CPU/Accel0..3 present, units, null for no-readingPASS
§5 ResetAllowableValues ⊇ set; illegal type → 4xxPASS
§5 firmware Tasksubmit → 202 + Task; poll to terminalPASS
§5 errorsforce error → 4xx/5xx + extended infoFAIL → finding RM-2026-014
§5 eventssubscribe + trigger fault → deliveryPASS

7. Open findings (raised to Pegatron)

  • RM-2026-014 (sev: medium): BMC obmc-1.8.0 returns 200 with an error body on an invalid PATCH instead of 4xx (violates §5). Owner: Pegatron FW. Target: obmc-1.8.1. Workaround: client inspects body for @Message.ExtendedInfo (defensive — Phase 03 Ch. 9).
  • RM-2026-019 (sev: low): CPU2 Temp present but unpopulated on single-socket SKUs; agreed to return null (done) rather than omit.

8. Change log

  • Rev B (2026-06-13): added attestation requirement; bumped accel-fw baseline 2.0.5→2.1.0; added conformance finding RM-2026-014. Rev A (2026-05-20): initial.