OpenStack/openstack-caracal-dc-dc

Fork: 0

OpenStack / openstack-caracal-dc-dc

History for openstack-caracal-dc-dc / docs / archive / dc-ha-scaleup-RETIRED-20260806.yaml

2026-08-06	5c2f335 Browse files » Stage 5 dc0: RETIRE + archive dc-ha-scaleup.yaml (operator-ruled; R6 superseded) [DOCFIX-211] ... Operator ruling 2026-08-06, exact utterance "Retire the redundancy and archive." The overlay was wholly redundant -- BUNDLEFIX-053 folded its entire content into bundle.yaml, so applying it was an all-keys no-op deep-merge (Task-#1 post-wave review, measured). - Archived: git mv overlays/dc-ha-scaleup.yaml -> docs/archive/dc-ha-scaleup-RETIRED-20260806.yaml + a do-not-deploy banner. docs/archive/ chosen explicitly (no prior overlay-archive precedent). - design-decisions.md: GA-R5 SUPERSESSION note on D-121's R6 (original 2026-07-27 record retained as history); fixed :503 and :4563 "overlay encodes v-a" refs -> bundle.yaml/BUNDLEFIX-053. - Harness (tests/provider-bundle-check): T17 REMOVED (== T18 once vault-hacluster is in base); T17b/T32/T33/T34 RE-POINTED onto good.yaml (base HA chain). T33/T34 now use the deterministic mutate() helper, not sed-on-overlay (no silent no-op fixture; a wrong key path KeyErrors). Each FAIL case proven to fire against the real checker message. 58->57 cases; provider-bundle-check 57/0. - Runbook dc-dc-phase4 Step-4 note + Step-12.3(a) gate: the two-phase "base at cluster_count:1 then apply the overlay to reach 3" model RETIRED -- base deploys 3-unit HA directly, so cluster_count:3 is the expected post-Step-4 value. - Rendered vips overlays: edited the render SOURCE (render/values/vr1-dc{0,1}-vips.yaml, D-136) and re-rendered (not hand-edited); overlay diff = the two comment lines only; render-drift 4/0. Hand-maintained vr1-dc{0,1}-machines.yaml deploy-command comments + provider-bundle-check.py + cloud-assert.sh comments + dc-dc-deployment-workflow.md item 22 reconciled. - CURRENT-STATE: no edit needed -- active status already omits the HA overlay from the deploy input; remaining mentions are dated historical narrative (retained as history, GA-R1). - Also finalizes Item 3/5 changelog notes (F9 approved+staged; Task #1 recommendation ruled). Gauntlet ALL GREEN (99 harnesses); repo-lint 0 fail (1 pre-existing legacy L1 warn). Staging: dc0 rack vr1-dc0-vips.yaml now stale-by-one-comment vs the re-render (functionally identical); re-syncs + sha-verifies at the next deploy per D-138 (logged, no rack write for a comment). Revert: git mv the overlay back (strip banner) + git revert this commit + re-render vips from reverted values. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fg98z7QyzwYUs8fsWCn728 JANeumatrix committed 17 hours ago

2026-08-06

5c2f335
Browse files »

Stage 5 dc0: RETIRE + archive dc-ha-scaleup.yaml (operator-ruled; R6 superseded) [DOCFIX-211] ...

Operator ruling 2026-08-06, exact utterance "Retire the redundancy and archive." The
overlay was wholly redundant -- BUNDLEFIX-053 folded its entire content into bundle.yaml,
so applying it was an all-keys no-op deep-merge (Task-#1 post-wave review, measured).

- Archived: git mv overlays/dc-ha-scaleup.yaml -> docs/archive/dc-ha-scaleup-RETIRED-20260806.yaml
  + a do-not-deploy banner. docs/archive/ chosen explicitly (no prior overlay-archive precedent).
- design-decisions.md: GA-R5 SUPERSESSION note on D-121's R6 (original 2026-07-27 record retained
  as history); fixed :503 and :4563 "overlay encodes v-a" refs -> bundle.yaml/BUNDLEFIX-053.
- Harness (tests/provider-bundle-check): T17 REMOVED (== T18 once vault-hacluster is in base);
  T17b/T32/T33/T34 RE-POINTED onto good.yaml (base HA chain). T33/T34 now use the deterministic
  mutate() helper, not sed-on-overlay (no silent no-op fixture; a wrong key path KeyErrors). Each
  FAIL case proven to fire against the real checker message. 58->57 cases; provider-bundle-check 57/0.
- Runbook dc-dc-phase4 Step-4 note + Step-12.3(a) gate: the two-phase "base at cluster_count:1 then
  apply the overlay to reach 3" model RETIRED -- base deploys 3-unit HA directly, so cluster_count:3
  is the expected post-Step-4 value.
- Rendered vips overlays: edited the render SOURCE (render/values/vr1-dc{0,1}-vips.yaml, D-136) and
  re-rendered (not hand-edited); overlay diff = the two comment lines only; render-drift 4/0.
  Hand-maintained vr1-dc{0,1}-machines.yaml deploy-command comments + provider-bundle-check.py +
  cloud-assert.sh comments + dc-dc-deployment-workflow.md item 22 reconciled.
- CURRENT-STATE: no edit needed -- active status already omits the HA overlay from the deploy input;
  remaining mentions are dated historical narrative (retained as history, GA-R1).
- Also finalizes Item 3/5 changelog notes (F9 approved+staged; Task #1 recommendation ruled).

Gauntlet ALL GREEN (99 harnesses); repo-lint 0 fail (1 pre-existing legacy L1 warn).
Staging: dc0 rack vr1-dc0-vips.yaml now stale-by-one-comment vs the re-render (functionally
identical); re-syncs + sha-verifies at the next deploy per D-138 (logged, no rack write for a comment).

Revert: git mv the overlay back (strip banner) + git revert this commit + re-render vips from
reverted values.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fg98z7QyzwYUs8fsWCn728

JANeumatrix committed 17 hours ago