coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Warm-standby: snapshot-ship automation home-1 -> ser8 (sqlite/kine + local-path PVs) #261

New issue
Closed
opened 2026-06-07 05:27:12 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-06-07 05:27:12 +00:00
Owner
Copy link

Warm-standby follow-up from #99. Automate scheduled state replication from home-1 (kai-server) to home-2 (ser8) over Tailscale. RPO = snapshot interval.

Key constraint: kai-server's k3s runs on sqlite/kine, not embedded etcd (confirmed 2026-06-06; scripts/k3s-start.sh has no --cluster-init). So k3s etcd-snapshot does not apply. Replication is:

  • the sqlite datastore (/var/lib/rancher/k3s/server/db/state.db + WAL) captured consistently (sqlite .backup/online backup, not a raw cp of a live file), plus
  • explicit PV backups — kai-server uses local-path-provisioner (node-pinned PVs), so PV data is not in the datastore and must be shipped separately.

Ship to ser8 over the tailnet on a timer (systemd timer or k3s CronJob). Decide retention + interval (drives RPO). Depends on ser8 being a cluster member (#258).

Warm-standby follow-up from #99. Automate scheduled state replication from home-1 (kai-server) to home-2 (ser8) over Tailscale. RPO = snapshot interval. **Key constraint:** kai-server's k3s runs on **sqlite/kine, not embedded etcd** (confirmed 2026-06-06; `scripts/k3s-start.sh` has no `--cluster-init`). So `k3s etcd-snapshot` does **not** apply. Replication is: - the sqlite datastore (`/var/lib/rancher/k3s/server/db/state.db` + WAL) captured consistently (sqlite `.backup`/online backup, not a raw cp of a live file), plus - explicit PV backups — kai-server uses local-path-provisioner (node-pinned PVs), so PV data is **not** in the datastore and must be shipped separately. Ship to ser8 over the tailnet on a timer (systemd timer or k3s CronJob). Decide retention + interval (drives RPO). Depends on ser8 being a cluster member (#258).
coilysiren commented 2026-06-17 08:22:34 +00:00
Author
Owner
Copy link

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 Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#261
No description provided.