v1 Deploy Runbook -- VR0 DC0 Omega Cloud (Caracal 2024.1, IPv4)

Command-label convention

Every command block below is bracketed by bold labels, so a command line is never mistaken for surrounding prose (these render in GitBucket and read clearly in a raw editor):

• RUN -- LOC -- the block CHANGES state; run it at LOC (e.g. jumphost, vault/0, jumphost -> magnum/0).
• CHECK (read-only) -- LOC -- a read-only verification; safe to re-run.
• GATE: -- a hard stop; do NOT proceed past the block unless the stated condition holds.
• Expect: -- what a passing result looks like.
• > CAUTION: -- marks a destructive, secret-handling, or irreversible step.

The deploy is a gated sequence: run phase-00 through phase-08 in order. Each phase ends in a hard gate (an explicit pass/fail check); do not start the next phase until the current gate passes. The two appendices are reference, not steps.

Conventions

• RUN location. Every command block is tagged with where it runs: # RUN: jumphost (the vopenstack-jesse jumphost, with juju + the openstack CLI), # RUN: mgmt VM (the in-cloud CAPI management VM, reached over SSH), or a charm unit via juju ssh <unit> -- '...' </dev/null.
• Gates. A line beginning GATE: or EXIT GATE is a stop-and-verify. Read-only verification precedes every mutation; destructive and secret-handling steps are individually gated, never batched.
• Dynamic lookups. VIPs, project names, IDs, and version constellations are discovered at run time, not hardcoded. Site-specific literals are tagged ENV(...) for the eventual generalization pass toward Roosevelt.
• Repo clone path. Never a literal (this repo has already been renamed/forked once -- DOCFIX-139/141). Set $REPO once per session to your clone's root (export REPO=$(git rev-parse --show-toplevel) if already cd'd into it, else export REPO=~/<wherever you cloned it>); every RUN block that needs the repo path below references $REPO, never a hardcoded name. repo-lint L9 fails a script/RUN-block/skill file that hardcodes the current repo's own directory name.
• ASCII only. All runbook content is ASCII (a mod_wsgi UnicodeDecodeError lesson); keep it that way on edit.

Phases

VR1 DC-DC track (separate from the VR0 phases above)

The dc-dc-phase*.md runbooks below are a SEPARATE track from the VR0 phase-NN sequence above: they build the two-DC + Office1-headend buildout ("VR1"), per docs/dc-dc-buildout-design.md and D-100..D-110, with VR0's own testcloud host becoming DC1 (repurposed, not a second concurrent cloud). The master tracker -- current stage status, the full tooling gap register, exit gates -- is docs/dc-dc-deployment-workflow.md; read that first, not just this table. "Stage" numbering here matches that tracker, not this README's own VR0 phase numbers (they are two independent sequences that happen to share a repo).

As of 2026-07-10: all seven Stage runbooks + the teardown/rollback runbook are WRITTEN, NONE EXECUTED. docs/dc-dc-deployment-workflow.md's tooling gap register tracks what's still open before each stage can run for real -- read it before starting Stage 1, not just this index.

Appendices

• appendix-A-troubleshooting.md -- symptom -> cause -> fix index, keyed by D-NNN / DOCFIX-NNN / lesson.
• appendix-B-asbuilt-version-lock.md -- charm channels, the CAPI version constellation, and the magnum-capi-helm driver pin.

History

This phase-NN set supersedes the earlier v1-do-doc-NN-* execution documents (and the older NN-*.md set and the deprecated/ folder), which were removed in the repo sanitation sweep. Git history preserves them.

• ops-capi-recovery.md -- parking, restart, and LB repair for the CAPI/Magnum stack (post-deploy operations companion; not a deploy phase). Added 2026-06-10.
• ops-restart-procedure.md -- full-cloud restart / recovery for planned windows and full power/network-loss events (DOCFIX-075). Indexed 2026-07-04 (was missing from this list since commit).
• ops-update-procedure.md -- routine update window: Juju controller patch, model agents, in-channel charm refreshes (DOCFIX-086; policy: D-071). Added 2026-07-04.