ilkerandClaude Opus 5 55417546fc Phase 2 (2/2): NVML backend behind a build tag ...

NVML is the only source of NVLink topology, and that topology is what keeps a
tensor-parallel group off the slow path inside a node. It needs cgo, so it sits
behind the nvml tag and the default build keeps using nvidia-smi.

Discover() picks the backend and falls back to nvidia-smi when NVML fails,
logging the fallback rather than performing it silently: on a node that is meant
to have working NVML, a quiet downgrade hides a broken driver installation and
costs the scheduler its topology.

CI now compiles the tagged build. That immediately paid for itself: ErrNoNVML
was declared only in the untagged file, so the tests did not compile under
-tags nvml. It is now declared where both builds can see it.

Not verified: the NVML path has never run against a driver, because there is no
GPU machine available. The NVLink domains it reports should be treated as
unverified until someone runs `llmgw agent inventory` on a real node.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-16 02:05:25 +02:00

..

discovery

Phase 2 (2/2): NVML backend behind a build tag

2026-09-16 02:05:25 +02:00

engines

Phase 2 (1/2): node discovery, engine adapters, process supervisor

2026-09-16 02:01:59 +02:00

supervisor

Phase 2 (1/2): node discovery, engine adapters, process supervisor

2026-09-16 02:01:59 +02:00