D-132 placement RULED: per-DC MAAS region VM at utility .6; D-134 map extended
GA-R5. Operator utterance: "Dedicated region VM per DC at utility .6
(Recommended)".

The region DB must not share fate with the hypervisor running every node it
manages -- also a precondition for D-132 q3 cross-site backup custody, which
stays pinned. The D-134 standing octet map now reads .4 artifact service /
.5 juju controller / .6 MAAS region, binding at every future DC standup.

Build notes carried, not ruled: author BOTH metal-admin and provider-public
legs at creation (the identical under-carve on the juju controller VM cost
three bootstrap attempts today); re-measure capacity before applying.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf
1 parent c7f098d commit 3045a02f54f75fa1a590cf99f4101ee8b330a583
@JANeumatrix JANeumatrix authored 2 hours ago
Showing 2 changed files
View
docs/CURRENT-STATE.md
View
docs/design-decisions.md