coulomb/resource-control
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Consume Vergabe target replay into node allocation budget; finish T02

Browse source 
Fill the Vergabe slot from railiance-apps 1af6d82 (RAPPS-WP-0014-T04): keep
60m request and 1000m/1Gi limits, raise memory request 256Mi->512Mi next wave,
keep apps-pg at 100m for incremental pilot DB demand. Regenerated budget:
serialized CPU +90m / memory +165Mi; all-concurrent CPU -390m / memory -347Mi.
T03 stays in progress pending wave-1/wave-2 receiving tasks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 8340@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
This commit is contained in:
tegwick 2026-10-21 08:40:36 +02:00
parent e72c5de92f
commit 3d9b1bd080
6 changed files with 208 additions and 86 deletions
Download patch file Download diff file Expand all files Collapse all files

28
workplans/RESOURCE-WP-0008-custodian-allocation-review.md
View file

@ -42,9 +42,8 @@ refreshing stale utilization metrics or inventing financial attribution.
```task
id: RESOURCE-WP-0008-T02
status: progress
status: done
priority: high
blocking_reason: "Node budget and per-workload comparison done 2026-10-21; only the Vergabe target replay result (RAPPS-WP-0014-T04) remains to be inserted into the 60m provisional slot."
state_hub_task_id: "1f538441-8b45-5d37-aeb3-345204b75117"
```
@ -66,7 +65,7 @@ whole node budget fits. Do not infer human workflow acceptance.
id: RESOURCE-WP-0008-T03
status: progress
priority: medium
blocking_reason: "Proposal and node budget published 2026-10-21, but none of the 54 owner changes has a receiving task in its owner repo (26 repos listed in the review), the coulomb probe owner is unconfirmed, and the Vergabe slot awaits RAPPS-WP-0014-T04."
blocking_reason: "Proposal and node budget published 2026-10-21 (Vergabe replay consumed). 54 owner changes in 27 repos still lack receiving tasks: wave 1 (rail-knative, railiance-forge, state-hub, then rapp-telemetry) is being prepared, wave 2 per-repo tasks follow, and the coulomb probe owner must be found first."
state_hub_task_id: "3e6e6a59-71a5-5048-b7a5-ed61416a442c"
```
@ -102,3 +101,26 @@ T03 cannot finish because every non-Vergabe change still needs a receiving task
its owner repo. The per-repo list is in `2026-10-21-node-budget.md`. Creating
those records is the owners' or the Custodian's decision; this record does not
create them.
## Vergabe replay consumed — 2026-10-21
Source: railiance-apps `1af6d82` (RAPPS-WP-0014-T04), which replayed the deployed
digest on the target node. Results: 0 errors in 3675 ordinary operations, ordinary
p95 0.192s, app CPU p95 998m under 36% throttling, memory peak 483MiB, and
incremental database CPU of about 320m mean / 480m p95 on an isolated PostgreSQL.
T02 is done, with this qualified allocation:
- Keep the 60m request and the 1000m/1Gi limits.
- Raise the memory request from 256Mi to 512Mi in the next wave (receiving owner
railiance-apps).
- Keep apps-pg at 100m rather than the rule's 50m.
Regenerated budget, all events concurrent: CPU −390m, memory −347Mi.
Regenerated budget, one disruptive event at a time: CPU +90m, memory +165Mi.
The replay does not establish shared-apps-pg contention, production settings,
human demand or human acceptance (RAPPS-WP-0014-T03).
T03 stays in progress under the founder's wave rollout. Wave 1 is rail-knative,
railiance-forge, state-hub and rapp-telemetry; wave 2 is batched per-repo tasks.
The ihp-railiance-probe owner must be confirmed first.