3 Commits

Include renames

Author	SHA1	Message	Date
Ilker ManapandClaude Opus 5.5	63f7c8cfd7	llmgw start --wait waits for the models, not for the setting ... Every model of a stopped system asks for no replica and so has what it asks for. Until the control plane took the setting up, seconds later, start --wait saw 18 of 18 satisfied and returned at once, with nothing started. It now counts only once the control plane says it is in the state asked for, both ways. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-07 21:43:45 +02:00
Ilker ManapandClaude Opus 5.5	7245dbe1dd	llmgw stop, start and restart act on the whole system ... Issue #3 asked for commands to stop and start the system, and 05aa21c gave only one machine's services. Now: - llmgw stop sets serving.stopped in the cluster's settings, live: the reconciler wants every model at no replicas, freeing every GPU, and the gateway answers every POST under /v1/ with 503 system_stopped. The control planes, agents and mirror keep running, and no model's definition changes. - llmgw start clears it; every model is placed again as it asks. - llmgw restart has every agent restart over its stream (RestartAgent), then the other control planes over ssh, standbys before a leader, then this one; engines keep serving. - llmgw status is the cluster's summary, saying when it is stopped. One machine's services moved to llmgw service status|start|stop|restart. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-07 18:01:45 +02:00
Ilker ManapandClaude Opus 5.5	05aa21c4d4	llmgw status, start, stop and restart for this machine's services ... There was no command to stop or start llmgw on a machine (issue #3). These act on the llmgw units the machine has - mirror, server, agent - or those named, in dependency order, saying what each did. stop leaves a node's engines serving unless --engines. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-07 14:52:52 +02:00