Skip to main content
Loading navigation
Back to prompt library

Build a Hardware Inventory and Firmware Change Impact Reviewer — implementation

Linked challenge: Build a Hardware Inventory and Firmware Change Impact Reviewer

Prompt source

implementation91 lines11 sectionsNo variables1 code block
## Build
Cross-reference multi-accelerator inventory reports with vendor firmware release bulletins. Hosted Claude analyzes driver compatibility tables to evaluate update risks before site rollouts.

## User
Datacenter Platform Architect

## Workflow
1. Parse server hardware inventory records including accelerator models, baseboard management versions, and host driver revisions.
2. Compare installed revisions against vendor release notes and known regression advisories.
3. Use hosted Claude to evaluate firmware upgrade paths, dependency breaks, and mandatory reboot constraints.
4. Export a staged roll-out risk assessment document and firmware change ticket manifest.

## Interface
Web review queue listing pending server chassis updates with risk score tags.

## Data
Create synthetic JSON files listing rack chassis IDs, PCI device IDs, installed firmware versions, and vendor bulletin diffs.
Starter examples below are synthetic. They are not downloaded records.

## Source
[Anthropic Python SDK](https://raw.githubusercontent.com/anthropics/anthropic-sdk-python/main/README.md)
Uses the Anthropic Python SDK to submit inventory diffs to hosted Claude for structured change advisory analysis.

## Tools
langfuse, anthropic, pydantic, pandas.
Langfuse provides telemetry and prompt tracing for tracking firmware review latency, evaluations, and decision auditing.
Hosted Claude API for technical compatibility evaluation and change impact summarization.

## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

## Acceptance
- Isolates every chassis running outdated firmware below the required baseline version.
- Identifies compatibility conflicts between kernel drivers and accelerator runtime versions.
- Produces structured change-order stages grouping nodes to maintain high-availability minimums.

## Starter Examples
```json
[
  {
    "input": {
      "cluster_id": "compute-pod-alpha",
      "target_firmware": "v550.54.15",
      "installed_inventory": [
        {
          "chassis_id": "srv-01",
          "accel_model": "H100-SXM",
          "current_fw": "v535.129.03",
          "driver_compat": "OK"
        },
        {
          "chassis_id": "srv-02",
          "accel_model": "H100-SXM",
          "current_fw": "v550.54.15",
          "driver_compat": "OK"
        }
      ]
    },
    "expected_output": {
      "upgrade_candidates_count": 1,
      "flagged_chassis": [
        "srv-01"
      ],
      "rollout_groups": [
        {
          "phase": 1,
          "chassis_ids": [
            "srv-01"
          ],
          "drain_required": true
        }
      ],
      "high_availability_risk": "LOW"
    }
  },
  {
    "input": {
      "cluster_id": "compute-pod-beta",
      "target_firmware": "v550.54.15",
      "installed_inventory": [
        {
          "chassis_id": "srv-10",
          "accel_model": "A100-SXM",
          "current_fw": "v515.65.01",
          "driver_compat": "INCOMPATIBLE_KERNEL"
        }
      ]
    },
    "expected_output": {
      "upgrade_candidates_count": 0,
      "flagged_chassis": [],
      "rollout_groups": [],
      "high_availability_risk": "BLOCKED_BY_DEPENDENCY"
    }
  }
]
```

## Safety
Review and simulation only. Does not flash firmware or issue remote execution commands to actual IPMI/BMC interfaces.
Use mock external writes. Require human review before any real deployment.