Plane IPAM complete on the new region: 24/0 PASS, existing tooling only
dc-plane-ipam.sh check vr1-dc0 goes from pass 7 / fail 17 to pass 24 /
fail 0, exit 0. Two idempotent applies, dry-run first, every write read
back: 13 D-134 reserved bands plus the FIP pool, then the 5 missing v6
plane subnets each created on the same MAAS vlan as its v4 twin.

No new code was needed. The tool's forced sequencing also proved itself --
the reserve run skipped every v6 band with 'not in MAAS yet, run carve-v6
first' rather than failing or silently no-opping, so running the two out of
order is safe.

This is the step that justifies the tunnel architecture: carve-v6 derives
its prefixes from the NetBox apex, reachable only from voffice1, while the
target region is reachable only via the rack. Neither host alone could have
run it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf
1 parent 1bb8eac commit 31411bcaf57d8c65767bd35297ebf61b96b8c0bd
@JANeumatrix JANeumatrix authored 22 hours ago
Showing 3 changed files
View
docs/CURRENT-STATE.md
View
docs/audit/dc0-region-plane-ipam-20260730.txt 0 → 100644
View
docs/changelog-20260730-dc0-region-migration.md