llmgw

375 Commits 9 Branches 95 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
Ilker ManapandClaude Opus 5.5	4f280a3546	Give each GPU node a vLLM build it can run, chosen on the cluster page Release / build (push) Successful in 1m12s Details Release / notes (push) Successful in 3s Details CI / test (push) Successful in 3m55s Details A node that cannot run the CUDA 13 build installs the same version's CUDA 12.9 build from vLLM's GitHub release, with PyTorch's cu129 torch; the install computes on the GPU before it counts. The build can be chosen per node — auto, cu13, cu129, none — on the cluster page, with ctl engine-build, or over the admin API; the control plane keeps the choice and tells the node at once. Refs #2. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-01 12:39:14 +02:00
Ilker ManapandClaude Opus 5.5	e313f32696	Decide engines per node, and let a node join without one it cannot run engine_overrides give nodes picked by GPU class, id or labels their own engine versions; node add --disable-engine keeps one off a node; what vLLM cannot do on a node is a warning rather than a refused node; the CUDA requirement follows the version; a hand-named binary is no longer replaced by an installed one. Refs #2 (items 4 and 7). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-01 12:07:25 +02:00
Ilker ManapandClaude Opus 5.5	590e5b9f3e	Ask a node only for engines it can install; doctor says when AVX2 is hidden A control plane of this release asks every node for vLLM. An agent of the last one does not know how to install it, and answered "unsupported", so a cluster half way through its upgrade showed every node as failing. Agents now say which engines they can install (Register.installable_engines), and are asked for no others; an agent that says nothing is asked for llama.cpp alone, as it always was. doctor reports the CPU's vector extensions, and warns when AVX2 is missing, with the fix for a VM: the test node for node add was one, on QEMU's default CPU model, where llama.cpp runs several times slower and nothing else looks wrong. node add shows it, since it runs doctor. The changelog's unreleased section was two releases' worth of sections one after the other, with two lists of fixes and the upgrade notes in the middle. It is one entry now: largest changes first, the fixes together, and every upgrade note at the end, with vLLM's default install and how to keep your own. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-09-29 21:03:03 +02:00

Author

SHA1

Message

Date

Ilker ManapandClaude Opus 5.5

4f280a3546

Give each GPU node a vLLM build it can run, chosen on the cluster page

Release / build (push) Successful in 1m12s

Details

Release / notes (push) Successful in 3s

Details

CI / test (push) Successful in 3m55s

Details

A node that cannot run the CUDA 13 build installs the same version's
CUDA 12.9 build from vLLM's GitHub release, with PyTorch's cu129 torch;
the install computes on the GPU before it counts. The build can be
chosen per node — auto, cu13, cu129, none — on the cluster page, with
ctl engine-build, or over the admin API; the control plane keeps the
choice and tells the node at once.

Refs #2.

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

2026-10-01 12:39:14 +02:00

Ilker ManapandClaude Opus 5.5

e313f32696

Decide engines per node, and let a node join without one it cannot run

engine_overrides give nodes picked by GPU class, id or labels their own
engine versions; node add --disable-engine keeps one off a node; what
vLLM cannot do on a node is a warning rather than a refused node; the
CUDA requirement follows the version; a hand-named binary is no longer
replaced by an installed one.

Refs #2 (items 4 and 7).

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

2026-10-01 12:07:25 +02:00

Ilker ManapandClaude Opus 5.5

590e5b9f3e

Ask a node only for engines it can install; doctor says when AVX2 is hidden

A control plane of this release asks every node for vLLM. An agent of the
last one does not know how to install it, and answered "unsupported", so a
cluster half way through its upgrade showed every node as failing. Agents
now say which engines they can install (Register.installable_engines), and
are asked for no others; an agent that says nothing is asked for llama.cpp
alone, as it always was.

doctor reports the CPU's vector extensions, and warns when AVX2 is missing,
with the fix for a VM: the test node for node add was one, on QEMU's default
CPU model, where llama.cpp runs several times slower and nothing else looks
wrong. node add shows it, since it runs doctor.

The changelog's unreleased section was two releases' worth of sections one
after the other, with two lists of fixes and the upgrade notes in the
middle. It is one entry now: largest changes first, the fixes together, and
every upgrade note at the end, with vLLM's default install and how to keep
your own.

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

2026-09-29 21:03:03 +02:00