Skip to content

v0.22.0 — fleet-node server

Latest

Choose a tag to compare

@dmmdea dmmdea released this 18 Jul 05:31
· 826 commits to main since this release

The harness can now join a Fleet Dispatcher fleet as a first-class node.

  • fleet-serve — implements the dispatcher's CONTRACT v2 node endpoints: health with live GiB VRAM and measured model footprints, ack-then-poll dispatch (202 + exact echo, idempotent duplicates, failures always non-2xx), and per-job status with ~1h terminal retention. Loopback by default; production binds your tailnet address behind an explicit --listen-trusted-network.
  • Measured footprints, passively — every image/video/audio/run-graph render records its observed VRAM peak per (model family, quant, task) — via the Windows PDH per-process counter set (the only per-process VRAM source under WDDM; nvidia-smi global-delta as fallback) — so the dispatcher routes on what jobs actually cost on this box, offload strategy included, not on full-residency formulas. fleet-measure primes an empty store in one command.
  • Full task surface — image-gen, video-gen, stt, audio-gen, and run-graph (arbitrary ComfyUI graph + self-provisioned node manifest) over the fleet wire.
  • Operator guidedocs/FLEET-NODE.md, including the recommended MSI Afterburner companion setup for per-process VRAM validation and monitoring.

Live-validated cross-box over a tailnet: dispatch → running → duplicate re-ack (exactly one render) → done with results; measured wan2.2 footprint within 0.3 GiB of the dispatcher contract's own worked example.