Software EBOM & Protocol Documentation

Deliverable 1 of Phase 12. A worked software EBOM and an ODM-facing interface spec — the contract that keeps a multi-party (you + Pegatron + ISVs) build coherent (WARMUP Ch. 2–3). Fill in the bracketed parts for your own node/rack; the result is both a real artifact and an interview portfolio piece.

Part A — Software/Firmware EBOM (example: one AI compute node)

The versioned, authoritative inventory reconciled against discovered reality at commissioning (Phase 01). A mismatch is a finding raised to the ODM, not a silent acceptance.

Firmware components & baseline (Phase 08)

Software components (Phase 11 compatibility)

Interfaces & config baselines

• Management: Redfish (primary), IPMI (fallback), SNMP (PDU/switch) — see Part B for the spec.
• Secure boot (Phase 09): PK/KEK provisioned; db includes [keys]; dbx revokes [list].
• Network (Phase 09): mgmt VLAN 10, tenant VLANs 100–199; mgmt reachable control-plane-only.
• Power/thermal budget (Phase 01): derated feed 17.3 kW; CDU 130 kW; N+1.

Provenance / traceability

• Each row: source, license, support status, security-contact, last-validated date.
• Reconciliation rule: at commissioning, discovered firmware/software/topology MUST match this EBOM; deviations are logged as findings and triaged with the responsible owner.

Part B — Interface Specification (ODM-facing, example: node power & telemetry)

Precise + testable enough that the ODM builds the same thing without us in the room (WARMUP Ch. 3). Pair every requirement with a conformance check (Part C).

B.1 Standard & deltas

• Base: DMTF Redfish 2023.2.
• Required resources: ServiceRoot, Systems/{id} (with PowerState, ProcessorSummary, Actions/#ComputerSystem.Reset), Chassis/{id} with Power and Thermal, Managers/{id}, UpdateService, EventService, TaskService.
• OEM extensions: Oem/Rackmgr block on Chassis MUST expose RackPosition, PowerBudgetW.

B.2 Behavior (not just shape)

• Reset action: MUST advertise ResetType@Redfish.AllowableValues and support {On, ForceOff, GracefulShutdown, ForceRestart, GracefulRestart, PowerCycle}. A GracefulShutdown to a hung host MUST NOT report success if the host did not power off (Phase 04 escalation relies on this).
• Firmware update: UpdateService.SimpleUpdate MUST return 202 + a Task; TaskState transitions New→Running→Completed|Exception; activation requirements stated per component (Phase 08).
• Sensors: Thermal.Temperatures[] MUST include inlet and per-accelerator accelN with ReadingCelsius and UpperThresholdCritical; units Celsius; names as listed.
• Errors: failures return a Redfish error body with @Message.ExtendedInfo; a 4xx for client errors, 5xx for service errors — never 200 with an error body.
• Auth: HTTPS only; Session tokens via SessionService; certificate chains to the management CA.
• Timing/resilience: the BMC SHOULD respond within [N]s; clients will retry with backoff (Phase 02) — the BMC MUST be idempotent for repeated GET/action submissions.

B.3 Events

• EventService MUST support subscriptions (EventDestination) and SHOULD support SSE; PSU/thermal/ fault events MUST be emitted (so we don't rely on polling alone — Phase 07).

Part C — Conformance hooks (the spec's executable form)

Prose drifts; tests don't (WARMUP Ch. 3; Phase 11). Each requirement maps to a conformance check the ODM runs against their firmware in CI/HIL.

Deliver this suite to the ODM; a failing check is an unambiguous, non-negotiable defect.

How to use this deliverable

1. Replace the bracketed/example values with your node's real components and interface.
2. Wire Part C into the Phase 11 conformance harness (run against the Redfish emulator + HIL).
3. Version this document (changelog + compatibility notes — Phase 11 Ch. 5); assign an owner.
4. Use it as the commissioning reconciliation source (Phase 01) and the ODM defect-feedback basis.