sjat/boma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs(adr-016): soften the second stale off-site-backup claim (R8 consistency)

Browse source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
sjat 2026-06-20 11:42:49 +02:00
parent a483f4e55c
commit 0030b45bbd
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/decisions/016-mesh-vpn.md
View file

@ -85,8 +85,9 @@ allocated for it.
- **Bootstrap order:** stand up the coordinator on `askari` → enroll `ubongo` →
`base` enrolls the fleet.
- **Coordinator survival:** off-site on `askari` ⇒ mesh survives a homelab outage.
NetBird's management datastore is backed up encrypted off `askari` (synced to
`ubongo`/`mamba`); peers keep last-known config through a brief coordinator outage.
NetBird's management datastore is **intended** to be backed up encrypted off `askari`
(synced to `ubongo`/`mamba`; not yet built — see the Availability amendment / R8); peers
keep last-known config through a brief coordinator outage.
- **`askari` is Ansible-managed:** its own inventory group `offsite_hosts` — provisioned
as **Terraform IaC** (`hetznercloud/hcloud`), managed independently of the Proxmox
cluster (its own provider + local state). Ansible configuration: `base` role, plus a