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

Configure the invited Vergabe prototype at 60m CPU
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

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 18:47:52 +02:00
parent 1f19a123d2
commit 9491744e5a
4 changed files with 112 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -9,7 +9,7 @@ owner: the-custodian
topic_slug: railiance
created: "2026-09-11"
updated: "2026-09-11"
related: [VERGABE-WP-0019, VERGABE-WP-0018, HFACT-WP-0001]
related: [VERGABE-WP-0019, VERGABE-WP-0018, HFACT-WP-0001, CUST-WP-0071]
state_hub_workstream_id: "c7fdaa7e-cab8-5d1d-86c2-f1aad7927c57"
---
@ -51,14 +51,23 @@ 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.
The user explicitly accepts a 60m CPU request for one tenant with very few
users on 2026-09-11. This prototype prioritizes the deployment/onboarding path;
60m is not a measured minimum or a production sizing claim. The pilot values
now override the inherited 100m request; CPU limit and memory remain unchanged.
Fresh metadata still shows `databases/apps-pg` healthy (1/1), 3905m requested
against 4000m allocatable and 95m available. A 60m application pod fits that
CPU snapshot with 35m remaining; refresh exact placement and any transient
migration/rollout demand before applying. This supersedes the earlier demand-
measurement prerequisite for this specific prototype, not unrelated allocations.
CUST-WP-0071 is persisted/registered for later measured sizing and a final weekly
assessment setup. STATE-WP-0091 retains release preflight and shared-headroom
work. Neither is a new prerequisite for this accepted pilot. Fresh CNPG metadata reports `vergabe-db` applied for `vergabe_db`/`vergabe`,
two managed consumer roles with 20-connection limits, and a successful apps-pg
backup at 2026-09-11T02:15:11Z. Database contents have not been inspected or
modified; metadata does not select reuse or grant access to that data. See the
dated inventory and pilot allocation receipt.
Use `docs/vergabe-teilnahme-pilot.md` for the review packet. Secret creation,
operator access and placement consume existing platform lanes; they do not