Freeze HA scoring and document reported production failover

This commit is contained in:
Lyncoln
2026-09-12 18:07:28 -04:00
parent c8636ed6d4
commit 488a1672d7
29 changed files with 2285 additions and 46 deletions
+14 -1
View File
@@ -5,7 +5,7 @@ Fedora 43, matching the saved lab package context. The workstation currently
reports Fedora 44; this first workflow does not claim a Fedora 44 build test.
It runs on main pushes, pull requests and manual dispatch.
The build installs only the OCF executable and nine modules, plus documentation.
The build installs only the OCF executable and nine shell modules, one Python state helper, plus documentation.
It includes no Quadlet, secrets, databases or cluster configuration. There are
no RPM lifecycle scriptlets. Installation does not start, stop or restart a
service or change maintenance mode. Host PostgreSQL packages are not required.
@@ -72,3 +72,16 @@ on Fedora 43). No package was installed on either lab host.
The Gitea server reports 1.27.3. Its Actions API returned HTTP 401 without
authentication, so a successful local build does not establish runner checkout
or artifact upload success. Check the first run in the repository's Actions tab.
The promotion-scoring review candidate additionally requires pacemaker-cli
2.1.0 or later. Its %check includes scoring and synthetic-CIB scheduler tests.
See notes/PROMOTION-SCORING.md in the source checkout for the unresolved
disconnected-standby policy; do not deploy the candidate from CI artifacts.
The disconnected candidate adds a runtime Python 3 dependency and advertises
`disconnected_max_age` (default 300 seconds). See
[the current policy](../notes/DISCONNECTED-STANDBY.md) before any installation.
Current operating policy and operator-reported production validation are packaged
from `docs/`. The source freeze is distinct from verified deployed-byte identity;
see [testing](../docs/testing.md) for production snapshot status.