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

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

@ -108,9 +108,32 @@ 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.
## Accepted prototype allocation — 2026-09-11
The user explicitly accepts a 60m CPU request for this invited prototype with
one tenant and very few users. Set `resources.requests.cpu: 60m` in the company
binding, as shown in the pilot example. The chart's inherited 100m was an initial
May 19 default, not a measured requirement. CPU limit remains 1000m, memory
request 256Mi and memory limit 1Gi; one replica and Recreate remain in effect.
Fresh metadata shows `databases/apps-pg` healthy (1/1), 4000m allocatable CPU and
3905m requested. The 60m pilot application fits the current 95m reservation
headroom with 35m remaining. This is a scheduling snapshot, not a throughput,
latency or availability guarantee; database and host demand are separate.
Refresh the actual rendered placement and transient migration demand before
applying. The user accepts low allocation to exercise deployment and onboarding
without first optimizing other infrastructure. Do not change unrelated services.
CUST-WP-0071 (`the-custodian/workplans/CUST-WP-0071-measured-workload-sizing-and-weekly-review.md`)
is registered for later measurement, sizing changes and a final weekly
assessment setup. It is not a prerequisite to this prototype. Exact tenant/host/
data binding, protected access and the pilot's existing recovery/onboarding
checks continue in RAPPS-WP-0014 and VERGABE-WP-0019. See factory decision
`decisions/0012-accept-60m-invited-prototype.md`.
Read-only CNPG metadata also reports `vergabe-db` applied for `vergabe_db` owned
by `vergabe`, two managed consumers with 20-connection limits, and the most recent
apps-pg backup successful at 2026-09-11T02:15:11Z. This establishes the declared
database/backup metadata; no customer data was read, selected for reuse or
modified. The tenant/data choice remains open.