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

ADR-009: control-node exception is a physical box, not a VM

Browse source
This commit is contained in:
sjat 2026-06-05 09:41:03 +02:00
parent 1064716d49
commit 07bc1c83f0
1 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docs/decisions/009-provisioning-handoff.md
View file

@ -126,12 +126,14 @@ convention only — it no longer implies any difference in how records are writt
## The control-node exception ## The control-node exception
The control node — the host that runs Terraform and Ansible — is the one VM The control node — the host that runs Terraform and Ansible — is `ubongo`, a
Terraform does **not** create. It cannot provision the infrastructure that would dedicated **physical** machine outside the cluster. It is not a VM at all, so
provision itself (chicken-and-egg). It is therefore the single documented exception Terraform genuinely never touches it: it cannot provision the infrastructure that
to "Terraform owns VM existence": would provision itself (chicken-and-egg). It is therefore the single documented
exception to "Terraform owns VM existence":
- Provisioned and bootstrapped manually, per the control-node section of ADR-005. - Provisioned and bootstrapped manually on bare metal, per the control-node section
of ADR-005; rationale, hardware, and recovery model in ADR-015.
- Listed in `inventories/<env>/hosts.yml` under the `control` group, and managed by - Listed in `inventories/<env>/hosts.yml` under the `control` group, and managed by
Ansible for baseline config only (no `docker_host` role). Ansible for baseline config only (no `docker_host` role).