4 Commits

Include renames

Author	SHA1	Message	Date
Ilker ManapandClaude Opus 5.5	77fb48ba32	The probe reads the floating address from its file each time ... The change to read it each time left the constructor storing the address itself, so the file read each time was one named 10.0.0.161. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-05 02:56:23 +02:00
Ilker ManapandClaude Opus 5.5	c2b4985abe	The floating address is read each time the summary is asked ... server add records it after restarting the new control plane, which then never named it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-05 02:29:00 +02:00
Ilker ManapandClaude Opus 5.5	adef25d709	server add records the floating address where the summary can read it ... keepalived's file holds its password and is root's alone; the control plane runs as llmgw and could not read it, so the CONTROL line never named the floating address. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-05 02:19:48 +02:00
Ilker ManapandClaude Opus 5.5	ec1918b23b	Two control planes: a failover in seconds, and the console to set one up ... A control plane being stopped held every agent's stream for the thirty seconds of a graceful shutdown, so the standby led within four seconds and had no nodes for thirty. The agent server is now closed, not drained. A control plane that loses its lease while it lives on lets its agents go, rather than keeping nodes the new leader cannot reach. ctl status and the console's Overview say which control plane leads, which stand by, and whether the floating address is on the leader. The console adds a control plane (Do → Add a control plane), asking for the machine and the floating address. server add says when the mirror would refuse the new control plane. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-05 02:17:51 +02:00