Publish cluster resource evidence and gate ThreePhoenix
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
This commit is contained in:
codex 2026-08-22 12:34:25 +02:00
parent bfc991258d
commit ea0452b9a9
11 changed files with 2768 additions and 23 deletions

View file

@ -4,11 +4,11 @@ type: workplan
title: "Publish cluster capacity, utilization, and allocation evidence"
domain: financials
repo: railiance-cluster
status: ready
status: finished
owner: codex
topic_slug: railiance
created: "2026-08-11"
updated: "2026-08-15"
updated: "2026-08-22"
related:
- RAIL-BS-WP-0007
- RESOURCE-WP-0003
@ -42,7 +42,7 @@ fin-hub allocate. No booked EUR in this repo.
```task
id: RCLUSTER-WP-0014-T01
status: todo
status: done
priority: high
state_hub_task_id: "a144bf1d-0402-4526-9bda-17846390270c"
```
@ -56,11 +56,17 @@ metrics, and source commands.
Done when repeated observations use a stable machine-readable interface and
resource-control can distinguish headroom, reservations, and actual usage.
**Outcome (2026-08-22):** `make cluster-observe REMOTE=railiance01` now emits
versioned, timestamped JSON with node allocatable/observed resources,
namespace/workload requests and limits, PVC/PV/storage-class state, stable
units, source commands, and explicit gaps without reading Secrets or pod
environments.
## T02 — Publish the failure-domain and storage contract
```task
id: RCLUSTER-WP-0014-T02
status: todo
status: done
priority: high
state_hub_task_id: "6460d9aa-3ded-420a-bf01-f0ccdeee0a02"
```
@ -73,11 +79,16 @@ current capacity.
Done when consumers can calculate correlated-failure risk and recognize which
state remains local to `railiance01`.
**Outcome (2026-08-22):** the evidence contract reports one Ready node,
`local-path` storage, `threephoenix_ready: false`, and the missing independent
region/zone labels. Target HA and Longhorn capacity are not represented as
current facts.
## T03 — Define technical allocation-driver evidence
```task
id: RCLUSTER-WP-0014-T03
status: todo
status: done
priority: medium
state_hub_task_id: "e5ff9b6c-e883-4356-9eca-b31757661d2f"
```
@ -90,8 +101,22 @@ do not convert the result into booked spend.
Done when resource-control can create an explainable allocation and fin-hub can
reconcile it to referenced financial facts.
**Outcome (2026-08-22):** `cluster-raw-drivers-v1` publishes CPU requests,
memory requests, PVC bytes, observed usage, totals, residual capacity, and
uncertainty, while leaving formula selection and booked cost to
`resource-control`.
## Acceptance
- [ ] Capacity evidence separates allocatable, requested, limited, and observed.
- [ ] Current single-host/local-storage risk is machine-readable.
- [ ] Allocation drivers reconcile to explicit totals and residuals.
- [x] Capacity evidence separates allocatable, requested, limited, and observed.
- [x] Current single-host/local-storage risk is machine-readable.
- [x] Allocation drivers reconcile to explicit totals and residuals.
## Completion evidence
- `python3 -m unittest discover -s tests -p 'test_*.py' -v`: 2 tests passed.
- Live read-only capture:
`docs/evidence/resource-reef-railiance-k3s/observations/20260822T100349Z.json`.
- Observed totals: 1 node, 53 workloads, 25 claims; 4,000m allocatable CPU,
3,830m requested CPU, 16,770,076,672 allocatable memory bytes, and
137,438,953,472 requested PVC bytes.