Let a worker say what machine it is

A worker reported its labels and nothing about the machine behind them, so the
engine could route a node to a GPU box but not tell whether that box had a GPU
free. Inventory — cores, GPUs, memory — now arrives with the hello frame, and
the run frame carries back what the engine allocated for that call.

Which is protocol 2 on both ends. GPUs are never probed: asking a vendor tool
would make the one dependency two, so a GPU is what the batch job says it was
given or what --gpus says. A worker that reports nothing still attaches and is
scheduled by its label alone.

Two things a job scheduler needs: --max-idle stops a worker started for one job
rather than letting it hold its allocation to the walltime, and a refusal is now
fatal instead of a reconnect loop that reads as a hang in a job's log.
This commit is contained in:
2026-08-27 08:29:35 +02:00
parent a1509f29da
commit 718b32a625
7 changed files with 359 additions and 36 deletions
Generated
+1 -1
View File
@@ -948,7 +948,7 @@ dev = [
[[package]]
name = "fluksio-worker"
version = "0.1.4"
version = "0.2.0"
source = { editable = "worker" }
dependencies = [
{ name = "websockets" },