diff --git a/bundle.yaml b/bundle.yaml index 91a5040..8968ae8 100644 --- a/bundle.yaml +++ b/bundle.yaml @@ -673,7 +673,9 @@ # ----- PKI material ------------------------------------------------- # 5 lb-mgmt-* options are supplied via overlays/${DC}-octavia-pki.yaml # (gitignored, PER-DC under the D-109 amendment; .gitignore:46 covers it by - # glob). Generated per runbooks/01a-octavia-pki-generation.md. + # glob). Generated per runbooks/phase-01-bundle-deploy.md Step 1.0-GEN + # (run once PER DC with DC exported). The old pointer here named + # runbooks/01a-octavia-pki-generation.md, which does not exist. # Deploy with (the per-DC set preflight.sh P2 also validates): # juju deploy ./bundle.yaml \ # --overlay "overlays/${DC}-vips.yaml" \ diff --git a/runbooks/dc-dc-phase6-designate-cos-magnum.md b/runbooks/dc-dc-phase6-designate-cos-magnum.md index d4b10ae..e09b0fc 100644 --- a/runbooks/dc-dc-phase6-designate-cos-magnum.md +++ b/runbooks/dc-dc-phase6-designate-cos-magnum.md @@ -253,7 +253,9 @@ pattern already established for secrets (`overlays/${DC}-octavia-pki.yaml` -- itself made PER-DC by the D-109 amendment, gitignored by glob; Step 1.0 of `phase-01-bundle-deploy.md`) and add one per-DC hostnames overlay: -`overlays/dc1-hostnames.yaml`, `overlays/dc2-hostnames.yaml`, each setting +`overlays/vr1-dc0-hostnames.yaml`, `overlays/vr1-dc1-hostnames.yaml` (region- +qualified: the `dc1`/`dc2` spelling is retired -- item 3.1 measured "DC1" meaning +`vr1-dc0` on one surface and `vr1-dc1` on another), each setting only the `os-public-hostname` options for that DC, applied at deploy time with an additional `--overlay` alongside whichever overlays that DC's deploy already uses. This is a proposed pattern, not yet reviewed -- present it at @@ -745,8 +747,8 @@ their eight relations, and Stage 5 deploys them. Do NOT re-add them. The only Step 1 repo work still owed is the per-DC `os-public-hostname` overlay proposed in 1.4, which is NOT AUTHORED - (`overlays/dc1-hostnames.yaml` / `overlays/dc2-hostnames.yaml` do not - exist -- and neither does the `overlays/${DC}-hostnames.yaml` spelling + (`overlays/vr1-dc0-hostnames.yaml` / `overlays/vr1-dc1-hostnames.yaml` do + not exist -- and neither does the `overlays/${DC}-hostnames.yaml` spelling other surfaces used to reference; never pass a name from this bullet to `--overlay` before authoring the file, juju errors out on a missing overlay). It is a PROPOSED pattern per 1.4: present it at the review gate,