Home / Projects / Orchestrata Ultimate / Decisions / ADR index / ADR-0080

ADR-0080: Every fleet container's address is pinned as nic ipv4.address

← ADR-0079 · ADR-0081 →

The record

Status: Accepted (Mohamed, 2026-10-09 — ruling "a"; see Provenance) · Date: 2026-10-09

Context

Since the 2026-09-24 rebuild on orch-prod-br the live fleets ran on DHCP leases — the nic devices carried no ipv4.address, so a bridge or host restart could renumber the fleet while every env profile and config file references the containers BY ADDRESS. ADR-0077 imported the fleets as-built (zero-diff); re-pinning was recorded as a managed change needing Mohamed's ruling (infra/README.md, "Managed changes after import").

Decision (Mohamed, ruling "a" on the presented pair)

Pin every prod and dev container's address as ipv4.address on its nic, equal to its current lease. (Test was already pinned 2026-10-08.)

Alternatives rejected

• Stay on DHCP: free today, but every bridge restart is a renumbering dice roll that every env file loses.

Consequences

• coordinators.tf, data_nodes.tf, prolog.tf, redis.tf, prometheus.tf, dev_fleet.tf declare the pin; variables.tf gains dev_fleet_ips; pins apply lazily on each container's next restart (lease == pin, verified by census, so every application is a no-op).
• tofu apply 2026-10-09: 13 changed / 0 added / 0 destroyed; post-apply plan clean; pins verified live (incus config show) on prod and dev.

Provenance

Mohamed, 2026-10-09, in the Kimi Code session — presented (a) pin / (b) stay on DHCP, ruled "a". Pre-pin census: every live lease matched the declared maps (prod .160/.109/.198/.128/.123, prolog .16/.17/.18, redis .10, prometheus .40, dev .20/.21/.22). The ruling was first recorded in infra/README.md; this ADR is the recoverable home (ADR-0085's rule).

Related ADRs

• Also mentioned: ADR-0077, ADR-0085

Rulings cited

None.

Specs cited

None (or no spec page exists for the ones named).