llmgw

ilker/llmgw

0 Fork 1

Files

T

History

Ilker ManapandClaude Opus 5.5 e725adc2f0 Tracing beyond the router: reconcile passes, placement and a replica's start traced down to the node

A reconcile pass that does something is a trace, with placement (where it
went, or every candidate turned down), scale-up/down, drain, stop, eviction,
preemption, reaping and restarts beneath it. A replica's start is a span open
from placement until it serves; the start command carries its context in a
new ControlMessage.trace field, and the agent continues the trace through
the weights fetch, engine launch, rendezvous and readiness wait. Stops,
drains, adoption and engine installs are traced on the node, model jobs are
a trace with a span per step linked to the replica's start, and agent.yaml
takes the same tracing block as server.yaml. Off, every span is the no-op one
and commands carry nothing.

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

2026-10-05 00:03:17 +02:00

fetch_test.go

Fetch a model's weights when the simple arrangement needs it

2026-09-17 08:46:03 +02:00

fetch.go

Tracing beyond the router: reconcile passes, placement and a replica's start traced down to the node

2026-10-05 00:03:17 +02:00

gc_test.go

Refuse a node with no room, and take back only what llmgw put there

2026-09-18 09:51:05 +02:00

gc.go

Refuse a node with no room, and take back only what llmgw put there