4 Commits

Include renames

Author	SHA1	Message	Date
joshandClaude Opus 4.7	481b67fb69	feat(firmware): install probe tools in live image + surface nic/hba gaps ... mkosi.conf: add ipmitool, ethtool, nvme-cli so the Firmware stage can actually read BMC revisions, NIC firmware versions, and fall back to nvme-cli when sysfs firmware_rev is missing. firmware.go: probeNICFirmware and probeHBAFirmware now return (snapshots, warning) so a missing ethtool/lspci surfaces in the stage log the same way probeBIOS/probeBMC already do. Before, a host without ethtool silently reported "bios=1 nvme_fw=1 microcode=1" with no hint that nic coverage was dropped. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-19 21:56:18 -04:00
joshandClaude Opus 4.7	23c689aa5b	deep profile + threshold gating + firmware stage + Burn super-stage ... Ships all five phases of the deep-profile overhaul together. Runs now carry a profile (quick/deep/soak); every profile walks the same 11-stage order — Inventory → Firmware → SpecValidate → SMART → CPUStress → Storage → Network → Burn → GPU → PSU → Reporting — with only per-stage durations and concurrency scaled. Phase 1: profiles.ProfileRegistry loaded from vetting.yaml; runs.profile column + CreateWithProfile; threshold table + evaluator seeded per-run from the shared vetting.thresholds block; breach flips result at /sensor + /result. Phase 2: upgraded CPUStress (stress-ng --cpu-method=all --verify + EDAC/MCE poll), Storage (fio --verify=md5 + SMART start/end delta), Network (sustained iperf + /proc/net/dev deltas) with per-profile knobs from Deps. Phase 3: Burn super-stage with goroutine fan-out for CPU + memory + fio + iperf, PSU rails sampled across the Burn window, SensorMux (2 s flush, 500-sample cap) to absorb backpressure. Phase 4: Firmware stage + firmware_snapshots table; probes dmidecode (BIOS), ipmitool (BMC), ethtool -i (NIC), nvme (sysfs + id-ctrl), lspci (HBA), /proc/cpuinfo (microcode). spec.DiffFirmware folds into SpecValidate with pin-by-identifier and fan-out-across-component matching; mismatches park the run in FailedHolding. Phase 5: profile radio on the host start form, profile chip on the run header, Firmware section in the HTML report, coverage artifact uploaded from CI, agent/tests/fakes/ scaffold with Deps.LookPath seam + stress_ng and dmidecode example fakes. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-18 22:50:57 -04:00
josh	5e9ad7f569	probes: sanitize disk serials and normalize GPU model for stable spec keys ... Two related bugs were producing different map keys for identical hardware depending on whether the inventory probe ran in the reporter on the Proxmox host or in the live-image agent after PXE boot. 1. diskSerial read /sys/block/<dev>/device/{serial,vpd_pg80} and only TrimSpace'd the result. vpd_pg80 is a binary SCSI VPD page with a 4-byte header, and some SSDs leak NUL/control bytes into the text serial file. Those bytes survive into the Go string, lowercase unchanged, and become a garbage map key that the reporter's cleaner read can't match. Sanitize to ASCII-printable range at ingest. 2. probeGPUs built the model slug from fields[2] + " " + fields[3] of `lspci -mm -nnk` output. fields[3] is subsystem vendor/device info, which varies between otherwise-identical cards and carries the `-rXX` revision marker — stable-enough for display but not for identity. Use fields[2] alone, strip the trailing `[NNNN]` PCI device-ID that lspci -nn appends, and sanitize for consistency. After deploying the new orchestrator + re-running the configure step on each registered host, SpecValidate will match cleanly. Disk diffs self-resolve because the reporter already stored clean serials; GPU diffs need one reporter re-run because the old expected slug still carries subsystem noise.	2026-04-18 16:06:18 -04:00
josh	9bb4b09a04	Initial commit: full Phases 1-6 implementation ... Post-repair hardware validation pipeline for Proxmox cluster hosts. Go orchestrator + in-image agent + mkosi live image + bundled dnsmasq PXE + SQLite + HTMX/SSE UI + notify registry + janitor + full docs.	2026-04-17 21:32:10 -04:00