Warm-standby: orchestrator failover to ser8 when home-1 is dark #263

Closed
opened 2026-06-07 05:27:14 +00:00 by coilysiren · 1 comment
Owner

Warm-standby follow-up from #99. Ensure the orchestrator has a live home when home-1 is dark — i.e. the orchestrator (and any control-loop it depends on) can run on ser8 after promotion, not only on kai-server.

Inventory what "the orchestrator" concretely is here, what it binds to on kai-server, and what has to move/replicate so a promoted ser8 can drive the cluster standalone. Depends on the promote runbook.

Warm-standby follow-up from #99. Ensure the orchestrator has a live home when home-1 is dark — i.e. the orchestrator (and any control-loop it depends on) can run on ser8 after promotion, not only on kai-server. Inventory what "the orchestrator" concretely is here, what it binds to on kai-server, and what has to move/replicate so a promoted ser8 can drive the cluster standalone. Depends on the promote runbook.
Author
Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:22:34 +00:00
Sign in to join this conversation.
No description provided.