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

9
workplans/RAPPS-WP-0014-vergabe-invited-pilot.md
View file

@ -48,6 +48,15 @@ data. Resolve target inventory before using historical runbook names: the
checked Railiance cluster has no vergabe-teilnahme namespace or matching
Deployment on 2026-09-11. Do not infer data loss or authorization to recreate it.
Current metadata also shows `databases/apps-pg` healthy (1/1), but the sole node
has 3905m CPU requests against 4000m allocatable: only 95m remains versus the
pilot's 100m request. Placement does not currently fit. Resolve capacity with
the Railiance owner using measured demand or added capacity, and reserve room
for the remaining factory services/operations; do not lower requests merely
to pass scheduling. STATE-WP-0091 is the existing shared-headroom observation
return, not a grant to resize unrelated workloads. Database/role/data presence
has not been read. See the dated inventory receipt.
Use `docs/vergabe-teilnahme-pilot.md` for the review packet. Secret creation,
operator access and placement consume existing platform lanes; they do not
create a parallel identity framework. The public edge needs an admitted login