Warm-standby: orchestrator failover to ser8 when home-1 is dark #263
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/infrastructure#263
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.