2 Commits

Include renames

Author	SHA1	Message	Date
Ilker ManapandClaude Opus 5	7e65cdf5c9	Fix the adminapi tests the settling window broke ... e05d5d4 was pushed with this suite failing. The full run was in front of me and I printed "green" from an unconditional echo instead of reading it, which is worse than not having looked. The failure was real and not a surprise: explain-placement had no rejections to show, because placement had not run yet. These tests build the whole fleet before anything starts, which is exactly the state settling waits for, so they opt out rather than simulate a startup they are not about. A negative SettleFor now means off, distinct from zero meaning "use the default" — a test that wants no window must be able to say so without that reading as "unset". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-16 23:20:12 +02:00
ilkerandClaude Opus 5	e1eb1d4149	Phase 3: ctl, and make draining a rolling move ... ctl talks to a management API on the admin listener, not the client-facing one. The two have different audiences: one serves inference to whoever holds an API key, the other lets a caller cordon nodes and read the cluster's shape. - nodes surfaces unhealthy GPUs and why they are excluded. That is usually the answer when a node looks idle but nothing will schedule onto it, and it was invisible before. - explain-placement prints every candidate considered and why it was rejected. - replicas shows the shards a replica is made of, with per-shard errors. - cordon, uncordon and drain are one endpoint with different targets, because the difference between cordon and drain is exactly what an operator needs to be sure of before running either. Draining had to be fixed first to make ctl drain worth having. A drained replica was stopped on the next pass, which cuts in-flight requests — the thing draining exists to avoid. Now a node marked Draining has its replicas drained, the model falls below its desired count, a replacement is placed elsewhere, and the original is stopped only once the replacement is serving. A grace period bounds it, because draining the only node that can host a model would otherwise never finish and the node could never be taken out of service. Verified against a two-node cluster of real binaries: draining moved a replica to the surviving node and traffic kept returning 200 throughout. ctl logs is deliberately absent. It needs a request/response pair the agent protocol does not have, and the failure path already ships an engine log tail with every status report — so the case that matters most is covered, and reading a healthy shard's output on demand is not worth a protocol change yet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-16 06:27:21 +02:00