2026-05-17 15:54:19 +02:00
|
|
|
host: piha
|
|
|
|
|
|
|
|
|
|
services:
|
2026-05-29 12:26:34 +02:00
|
|
|
ha-diag-agent:
|
|
|
|
|
role: ha-diagnostic-agent
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: local-only
|
|
|
|
|
offline_required: false
|
|
|
|
|
depends_on:
|
|
|
|
|
local: []
|
|
|
|
|
external: [homeassistant]
|
|
|
|
|
config:
|
|
|
|
|
target_url: http://localhost:8123
|
|
|
|
|
location_tag: "ken"
|
|
|
|
|
events_dir: /opt/homelab/events/piha
|
|
|
|
|
runtime:
|
|
|
|
|
config_path: /opt/homelab/config/ha-diag-agent
|
|
|
|
|
data_path: /var/lib/ha-diag-agent
|
|
|
|
|
|
feat(node-agent): implement health monitor and safe cleanup policy
scripts/monitor/health-monitor.sh (new):
- Standalone bash health monitor: disk/RAM/CPU checks + docker container health
- Per-node-type cleanup policy enforced:
lte_node (chelsty-infra, chelsty-ha): NO cleanup, no docker ops
sd_card (piha, saturn): dangling images + containers, rate-limited once/24h
ai_node (solaria): dangling + containers + build cache, NEVER -a
standard (vps): dangling + containers + build cache + CP filesystem rotation
- VPS filesystem rotation: completed/failed actions >7d, deploy logs >30d,
events >3d AND past observer checkpoint
- Emits structured JSON events (node_health, disk_pressure, high_memory, high_cpu,
containers_not_running, healthcheck_failed)
services/node-agent/ (new):
- Python daemon (node_agent.py): same policy as bash script, Docker SDK
for container checks and cleanup, /proc for system metrics
- Optional event shipping to VPS via rsync+SSH (VPS_EVENTS_HOST env var)
- Dockerfile: python:3.11-slim + openssh-client + rsync + docker>=6.0
- docker-compose.yml: mounts docker socket, /opt/homelab, repo read-only
observer.py:
- Handle node_health: update node status + disk/mem/cpu metrics, clear disk_pressure
- Handle disk_pressure: record severity on node, clear when healthy
- Handle high_memory / high_cpu: record pressure level for correlation
supervisor.py:
- Add NO_DISK_CLEANUP_NODES = {chelsty-infra, chelsty-ha}
- reconcile() step 3: generate disk_cleanup actions for nodes with high disk pressure
- _generate_disk_cleanup_recommendation(): stable ID disk-cleanup-{node},
checks all active states, risk=guarded (operator approval required)
executor.py:
- Handle disk_cleanup action type via _execute_disk_cleanup()
- Commands come from action payload; safety gate rejects any command touching
/opt/homelab/data/, /opt/homelab/config/, /opt/homelab/state/, or rm -rf /
hosts/*/services.yaml:
- Rename stability-agent -> node-agent on piha, vps, solaria, chelsty-infra
- Add node-agent to chelsty-ha (previously missing)
- Add cleanup policy notes to LTE node comments
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 13:15:06 +02:00
|
|
|
node-agent:
|
2026-05-17 15:54:19 +02:00
|
|
|
role: node-stability-monitor
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: local-only
|
|
|
|
|
offline_required: true
|
|
|
|
|
depends_on:
|
|
|
|
|
local: []
|
|
|
|
|
external: []
|
|
|
|
|
runtime:
|
feat(node-agent): implement health monitor and safe cleanup policy
scripts/monitor/health-monitor.sh (new):
- Standalone bash health monitor: disk/RAM/CPU checks + docker container health
- Per-node-type cleanup policy enforced:
lte_node (chelsty-infra, chelsty-ha): NO cleanup, no docker ops
sd_card (piha, saturn): dangling images + containers, rate-limited once/24h
ai_node (solaria): dangling + containers + build cache, NEVER -a
standard (vps): dangling + containers + build cache + CP filesystem rotation
- VPS filesystem rotation: completed/failed actions >7d, deploy logs >30d,
events >3d AND past observer checkpoint
- Emits structured JSON events (node_health, disk_pressure, high_memory, high_cpu,
containers_not_running, healthcheck_failed)
services/node-agent/ (new):
- Python daemon (node_agent.py): same policy as bash script, Docker SDK
for container checks and cleanup, /proc for system metrics
- Optional event shipping to VPS via rsync+SSH (VPS_EVENTS_HOST env var)
- Dockerfile: python:3.11-slim + openssh-client + rsync + docker>=6.0
- docker-compose.yml: mounts docker socket, /opt/homelab, repo read-only
observer.py:
- Handle node_health: update node status + disk/mem/cpu metrics, clear disk_pressure
- Handle disk_pressure: record severity on node, clear when healthy
- Handle high_memory / high_cpu: record pressure level for correlation
supervisor.py:
- Add NO_DISK_CLEANUP_NODES = {chelsty-infra, chelsty-ha}
- reconcile() step 3: generate disk_cleanup actions for nodes with high disk pressure
- _generate_disk_cleanup_recommendation(): stable ID disk-cleanup-{node},
checks all active states, risk=guarded (operator approval required)
executor.py:
- Handle disk_cleanup action type via _execute_disk_cleanup()
- Commands come from action payload; safety gate rejects any command touching
/opt/homelab/data/, /opt/homelab/config/, /opt/homelab/state/, or rm -rf /
hosts/*/services.yaml:
- Rename stability-agent -> node-agent on piha, vps, solaria, chelsty-infra
- Add node-agent to chelsty-ha (previously missing)
- Add cleanup policy notes to LTE node comments
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 13:15:06 +02:00
|
|
|
config_path: /opt/homelab/config/node-agent
|
2026-05-17 15:54:19 +02:00
|
|
|
data_path: /opt/homelab/state
|
|
|
|
|
logs_path: /opt/homelab/events
|
2026-06-01 17:54:36 +02:00
|
|
|
|
|
|
|
|
brain-watchdog:
|
|
|
|
|
role: control-plane-watchdog
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: private
|
|
|
|
|
offline_required: false
|
|
|
|
|
depends_on:
|
|
|
|
|
local: []
|
|
|
|
|
external: [control-plane]
|
|
|
|
|
runtime:
|
|
|
|
|
config_path: /opt/homelab/config/brain-watchdog
|
2026-06-17 15:02:37 +02:00
|
|
|
|
|
|
|
|
vikunja:
|
|
|
|
|
role: task-management
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: private # public via npm reverse proxy at vikunja.okit.pl
|
|
|
|
|
offline_required: false
|
|
|
|
|
depends_on:
|
|
|
|
|
local: []
|
|
|
|
|
external: [forgejo] # OIDC identity provider
|
|
|
|
|
ports:
|
|
|
|
|
- name: http
|
|
|
|
|
container_port: 3456
|
|
|
|
|
protocol: tcp
|
|
|
|
|
runtime:
|
|
|
|
|
# secrets (.env) + OIDC config (config.yml) live alongside the compose file
|
|
|
|
|
config_path: services/vikunja
|
|
|
|
|
# data is in Docker named volumes: vikunja_vikunja_db, vikunja_vikunja_files
|
2026-06-22 19:59:58 +02:00
|
|
|
|
2026-07-03 13:41:44 +02:00
|
|
|
llm-gateway:
|
|
|
|
|
role: llm-router # FastAPI proxy -> Ollama @ SOLARIA :11434
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: private # Tailscale-only bind (TAILSCALE_BIND_IP); no public ingress
|
|
|
|
|
offline_required: false
|
|
|
|
|
depends_on:
|
|
|
|
|
local: []
|
|
|
|
|
external: [ollama] # SOLARIA may be powered down -> routes 502, health stays ok
|
|
|
|
|
ports:
|
|
|
|
|
- name: http
|
|
|
|
|
container_port: 8080
|
|
|
|
|
protocol: tcp
|
|
|
|
|
runtime:
|
|
|
|
|
# .env (TAILSCALE_BIND_IP) lives alongside the compose file; stateless, no data path
|
|
|
|
|
config_path: services/llm-gateway
|
|
|
|
|
|
feat(kb): faza 3 krok 5 — cykliczny ingest (systemd timer) + alerting
documents-ingest-cyclic (jobs/documents-ingest/src/documents_ingest/cyclic_ingest.py):
orkiestruje paperless_adapter -> chunk_embed -> summarize(--backend anthropic,
claude-haiku-4-5) -> summarize(--embed-summaries) bez zmian w samych jobach. Ollama@SOLARIA
(availability_target: medium) jest tolerowana offline: probe GET /api/tags przed obu
etapami embed, brak -> pominięcie, nie fail (oba embed passy idempotentne, nadrobią się na
kolejnym ticku). Czwarty etap (embed-summaries) dopisany ponad plan §7.1 (który wymieniał
tylko 3 kroki) — bez niego nowe streszczenia miałyby embedding=NULL i byłyby niewidoczne dla
cascade_query (bramka kroku 4, WHERE embedding IS NOT NULL); potwierdzone z Oskarem.
Predykaty pass/fail każdego etapu 1:1 z exit-checkiem danego joba (chunks_errors,
llm_errors, stats-balance itd.) — etapy izolowane, nie fail-fast (wcześniejszy fail nie
blokuje kolejnych, tak jak joby izolują błędy per wiersz). Metryki .prom (atomowy zapis,
last_success_timestamp trzymany z poprzedniego pliku przy failu) do
/opt/homelab/state/node-exporter/kb-ingest.prom. 36 nowych testów (202/202 pakietu).
systemd (jobs/documents-ingest/systemd/): pierwszy systemd-timer w repo — kb-ingest.timer
(OnCalendar=*-*-* 03:30, Persistent=true, plan §7.1) + kb-ingest.service (host-level, User
oskar, EnvironmentFile /opt/homelab/kb/.env) + kb-ingest-run.sh (log per-run do
/opt/homelab/logs/kb-ingest/, konwencja repo). Instalacja i sekrety udokumentowane w
README (Faza 3 krok 5) — instalacja na PIHA dopiero po merge.
fleet-prometheus (rules/kb-ingest.yml): KbIngestStale (>172800s od last_success, critical)
+ KbEmbedBacklogGrowing (backlog>0 przez 72h, warning) — dostawa istniejącym torem
brain-watchdog->Telegram, bez Alertmanagera (konwencja liveness.yml).
node_exporter: owner_node vps -> per-host (service.yaml) + wpis + override
(--collector.textfile.directory, bez nowego mountu — czyta przez istniejący /:/host:ro) +
topology.yaml dla PIHA. Domyka pozycję z docs/backlog.md "stability-agent / node_exporter
owner_node single, biegaja wielomiejscowo -> per-host" (połowę — node_exporter; stability-agent
zostaje osobnym follow-upem) w ramach paczki B inwentaryzacji monitoringu dla PIHA.
Test end-to-end na żywo na PIHA (2× --apply, po potwierdzeniu z Oskarem): pierwszy run
złapał 5 dokumentów faktycznie nowych w Paperless (nieoczekiwane, niezwiązane z tym
taskiem) -> 82 nowe chunki (2 ocr_junk), 5 nowych streszczeń, 5 embeddingów streszczeń,
0 błędów, metryki zapisane. Drugi run: pełna idempotencja, wszystko 0. ANTHROPIC_API_KEY
dodany przez Oskara ręcznie do /opt/homelab/kb/.env (nigdy nie logowany/generowany).
Co dalej: prawdziwa instalacja systemd (services.yaml już przygotowany, po merge),
zdecydowanie czy stability-agent też idzie na per-host przy okazji.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-17 15:05:18 +02:00
|
|
|
node_exporter:
|
|
|
|
|
role: metrics-exporter
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: local-only
|
|
|
|
|
offline_required: true
|
|
|
|
|
depends_on:
|
|
|
|
|
local: []
|
|
|
|
|
external: []
|
|
|
|
|
runtime:
|
|
|
|
|
# textfile collector reads /opt/homelab/state/node-exporter (module 5 phase 3 step 5,
|
|
|
|
|
# docs/kb/modules/05-faza3-plan.md §7.2 — kb-ingest.prom) via the existing /:/host:ro
|
|
|
|
|
# mount, see hosts/piha/runtime/node_exporter/docker-compose.override.yml.
|
|
|
|
|
data_path: /opt/homelab/state/node-exporter
|
|
|
|
|
|
2026-06-22 19:59:58 +02:00
|
|
|
kb-postgres:
|
|
|
|
|
role: kb-database # KB spine: Postgres 16 + pgvector (always-on)
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: local-only # Tailscale-accessible; no public ingress
|
|
|
|
|
offline_required: false
|
|
|
|
|
depends_on:
|
|
|
|
|
local: []
|
|
|
|
|
external: []
|
|
|
|
|
ports:
|
|
|
|
|
- name: postgres
|
|
|
|
|
host_port: 5433
|
|
|
|
|
protocol: tcp
|
|
|
|
|
runtime:
|
|
|
|
|
config_path: /opt/homelab/config/kb-postgres
|
|
|
|
|
# data is in Docker named volume kb_postgres_data — must land on the NVMe
|
|
|
|
|
# (Docker data-root on /home); see hosts/piha/runtime/kb-postgres override.
|
feat(kb): add kb-query service skeleton (search API, no ingress yet)
Module 5 phase 4 step 1 (docs/kb/modules/05-faza4-plan.md, §4): first
user-facing HTTP entry point to the KB. FastAPI wrapping
kb_retrieval.cascade_query/flat_query — GET /search (query_text -> embed via
Ollama@SOLARIA -> cascade/flat -> envelope join -> JSON with per-source
links) and GET /healthz. Search API only, no answer synthesis (phase 5) and
no server-side dist filtering — the 0.45/0.55 colour thresholds are a
frontend concern (plan §7, a later step).
Hard startup invariant (plan §2 decision 2): refuses to start unless the
configured EMBED_MODEL is present in both document_chunk.model and
document_summary.embedding_model. Note the latter: document_summary.model is
the LLM that *wrote* the summary (claude-haiku-4-5/gemma3:12b), not the
embedder — checked live against kb-postgres@PIHA before writing this, see
app/startup.py's docstring. Verified end-to-end with a live docker run: the
invariant crash-loops on a mismatched EMBED_MODEL and passes through to a
real /search hit against the live corpus with a correct model.
Repo-only: no deploy, no npm/OIDC/DNS wiring (plan §8, later step), no local
embed fallback (plan §5, later step) — Ollama@SOLARIA is called directly and
a failure surfaces as 503, not a crash.
Also: scripts/deploy/deploy.sh's gate now builds each service via
`docker compose build` instead of a raw `docker build <svc_dir>`, so a
service whose docker-compose.yml declares a repo-root build context (needed
here to COPY packages/kb-retrieval/, the packages/ Dockerfile convention
already documented in CLAUDE.md) resolves the same way in the gate as it
does at real deploy time (deploy-node.sh's `docker compose ... up --build`).
No behavior change for existing single-context services — verified against
llm-gateway's compose file.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-22 16:06:18 +02:00
|
|
|
|
|
|
|
|
kb-query:
|
|
|
|
|
role: kb-search-api # module 5 phase 4: FastAPI wrapper over kb_retrieval cascade/flat query
|
|
|
|
|
deployment_model: docker-compose
|
|
|
|
|
exposure: private # LAN bind (LAN_BIND_IP); npm@PIHA vhost + OIDC is a later step
|
|
|
|
|
offline_required: false
|
|
|
|
|
depends_on:
|
|
|
|
|
local: [kb-postgres]
|
|
|
|
|
external: [ollama] # SOLARIA may be offline -> /search 502/503, /healthz stays ok
|
|
|
|
|
ports:
|
|
|
|
|
- name: http
|
|
|
|
|
container_port: 8080
|
|
|
|
|
host_port: 8230
|
|
|
|
|
protocol: tcp
|
|
|
|
|
runtime:
|
|
|
|
|
# .env (KB_DSN, LAN_BIND_IP) lives alongside the compose file; stateless, no data path
|
|
|
|
|
config_path: services/kb-query
|