coulomb/railiance-apps
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record pilot CPU reservation constraint before placement

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-11 16:49:54 +02:00
parent 6988111303
commit f390c9f91d
3 changed files with 35 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/vergabe-teilnahme-pilot.md
View file

@ -106,3 +106,11 @@ The published image contains the invited login/private-download gate. Exact
company/host/data binding, native deployment, coherent restore and two-user
acceptance remain open. See `docs/evidence/2026-09-11-invited-pilot-release.json`
for source, CI and artifact receipts; this candidate has not been deployed.
The shared `databases/apps-pg` cluster is currently healthy (1/1). The node has
4000m allocatable CPU and 3905m in requests, leaving 95m against this pilot's
100m request. This is a reservation constraint, not a utilization measurement.
RAPPS-WP-0014-T02 retains capacity admission before deployment; use existing
owner observations or add capacity, and retain operating room for factory
services. Do not silently reduce the pilot request to make the chart fit.