feat(ops): M8.9 upgrade rehearsal on clones, barrier and node plan (ADR-0076)

Drill-only --synthetic-until/--accelerate and evo-world-clone compare
(compare_region_histories) prove a candidate build runs the same world on
clones of one cut before any barrier. upgrade-check.sh rehearses a failed
migration under load and the version barrier with real hosts; upgrade-barrier.sh
retires an old build in dev/stage only once the new digest is Ready. Nodes:
aevolution.io/stores pins every objects-volume pod, aevolution.io/compute is
preference-only (Alertmanager first), checked by policy and scheduling-check.sh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-30 17:51:17 -04:00
co-authored by Claude Opus 5.5
parent 645d16b27a
commit 5b482ad6a3
19 changed files with 1028 additions and 12 deletions
+18
View File
@@ -1141,3 +1141,21 @@ ADR-0075:
- `fence-database.sh` supersedes the old database through the upgrade barrier: a
still-running old host quarantines, and no host can acquire it again.
- `tools/ci/dr-check.sh` rehearses it in every PostgreSQL build.
## M8.9 upgrade and growth (2026-09-30)
ADR-0076:
- **Compare before upgrading.** `evo-server --synthetic-until TICK --accelerate N`
(drill-only, refused without the synthetic driver) runs clones to an exact tick
faster than real time; `evo-world-clone compare` (library:
`compare_region_histories`) audits both and requires the same world: same
versions, identical rebound head state and identical outcomes. Builds may differ.
- **Failed migration and barrier rehearsed** with real hosts
(`tools/ci/upgrade-check.sh`): a failing migration leaves schema v9 and the host
serving; the barrier fences the old build (exit 4), the new one resumes under a
newer epoch, and the history across both builds audits.
- **Dev/stage barrier:** `tools/ops/upgrade-barrier.sh <env> --retire HEX` retires an
old build only when it is in `REGION_RETAINED` and the new digest is already Ready.
- **Nodes:** `aevolution.io/stores` (one worker; every objects-volume pod selects it)
and `aevolution.io/compute` (preferred only; Alertmanager first).
`tools/ops/scheduling-check.sh <env>` verifies placement read-only.