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

ops: note railiance01 capacity upgrade claim vs live guest size
Some checks failed
CI Smoke / container-smoke (push) Successful in 2s
Details
ci / test (push) Failing after 5s
Details
CI Smoke / host-smoke (push) Successful in 0s
Details

Browse source 
Operator reported 4 vCPU / 16 GiB; verify shows guest still 2 / 3.8 GiB
after recent reboot. Document check report and keep open thread until
nproc/free match the new flavor.
This commit is contained in:
tegwick 2026-07-16 14:33:48 +02:00
parent 06037b0486
commit 776b7f8cc4
7 changed files with 82 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

37
engagements/pilots/eng-coulomb-railiance01-ho-001/vault/memory.md
View file

@ -3,7 +3,7 @@ agent: host-operator
engagement_id: eng-coulomb-railiance01-ho-001
project: coulomb-railiance01
last_updated: '2026-07-16'
session_count: 4
session_count: 5
confidentiality: client_owned
---
@ -28,7 +28,8 @@ forward-deployed host-operator pilot (KAIZEN-WP-0009).
| hostname | role | typical load | services | last review |
|----------|------|--------------|----------|-------------|
| railiance01 | k3s production single-node | overload on 2 cores under current mix | k3s, gitea/forgejo, temporal, activity-core, state-hub edge, traefik, platform pods | 2026-07-16 |
| railiance01 | k3s production single-node | calmer after reboot (~load 2 on 2 cores) | k3s, gitea, temporal, activity-core, state-hub | 2026-07-16 capacity check |
## OS & Patch State
@ -47,18 +48,18 @@ forward-deployed host-operator pilot (KAIZEN-WP-0009).
## Load & Workload Envelope
| Field | Post-remediation 2026-07-16 |
|-------|----------------------------|
| Cores | 2 |
| Load 1m | ~6 (was ~12) — still elevated |
| RAM | 3.8 GiB; MemAvailable ~625 Mi |
| Swap | **4 GiB /swapfile**, ~1.9 GiB used |
| PSI memory full avg60 | ~8% (was ~24%) |
| Disk / | ~55% |
| /var/log/journal | ~461 Mi (was ~4.1 Gi) |
| k3s node | Ready |
| Field | 2026-07-16 capacity check (post operator upgrade claim) |
|-------|--------------------------------------------------------|
| Cores (guest) | **still 2** — operator reported 4; not visible yet |
| RAM (guest) | **still ~3.8 GiB** — operator reported 16 GiB; not visible yet |
| Load 1m | ~2 (improved vs Critical era) |
| MemAvailable | ~0.9 GiB |
| Swap | 4 GiB file, ~300 Mi used |
| PSI memory full avg60 | ~0.2% |
| k3s | Ready |
Envelope: swap is emergency cushion; plan RAM upgrade if swap stays high.
Do **not** treat 4/16 as baseline until `nproc` and `free -h` match.
See reports/2026-07-16-capacity-upgrade-check.md
## Accumulated Findings
@ -99,10 +100,10 @@ Envelope: swap is emergency cushion; plan RAM upgrade if swap stays high.
## Open Threads
- Plan hardware/provider RAM increase (swap is temporary relief)
- Re-login stale SSH sessions after package upgrade
- Add UFW allow for new admin IPs when they change
- Monitor if 8472 needed for any multi-node peer (currently none)
- **Confirm VM resize:** operator reported 4 vCPU / 16 GiB; live guest still 2 / 3.8 GiB (2026-07-16 check)
- After 4/16 confirmed: update baseline; consider whether to keep full 4G swap or shrink
- Re-login stale SSH sessions after earlier apt upgrade if not done
- UFW: add new admin public IPs when they change (see access-plan allowlist procedure)
## Session Log
@ -112,3 +113,5 @@ Envelope: swap is emergency cushion; plan RAM upgrade if swap stays high.
- 2026-07-16 · railiance01 · deep_assessment · T10 ramp-up complete: Critical memory/load, k3s API unavailable, RU all done, phase operating · ok
- 2026-07-16 · railiance01 · privileged remediation P1–P4 applied (swap, journal, apt, ufw) · ok
- 2026-07-16 · railiance01 · deep_assessment · Approved P1-P4 done: 4G swap, journal vacuum, apt upgrade, UFW k3s API allowlist; k3s Ready; RAM still tight · ok
- 2026-07-16 · railiance01 · capacity check after operator 4CPU/16G report: guest still 2/3.8G · watch
- 2026-07-16 · railiance01 · standard_review · Operator reported 4CPU/16G upgrade; live guest still 2CPU/3.8G after reboot; k3s Ready; load calmer · ok