homelab-codex-ws/services/stability-agent/service.yaml
oskar d8f65c3034 fix(hosts): align manifests with observed reality (recon B6/B7/C8/F20.5)
- hosts/solaria/services.yaml: add stability-agent and node_exporter
  (running on solaria since deployment, absent from desired state —
  recon B6); add planner-agent with monitor:false (legacy ai-cluster
  family, decision pending, do not remediate)
- services/stability-agent/service.yaml: owner_node chelsty (not a real
  node) -> per-host, same convention as node_exporter/ha-diag-agent; it
  runs on vps, piha, solaria (F20.5)
- services/mosquitto/: mark NOT DEPLOYED / legacy in service.yaml and
  README — the manifest matches nothing that runs (vps broker = legacy
  ai-cluster stack, piha broker = host systemd package, chelsty has its
  own runtime config; recon C8). Kept until the MQTT topology decision
  (recon open question 7); not deleted yet.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:15:55 +02:00

29 lines
808 B
YAML

service:
name: stability-agent
# Deployed per-host: runs on vps, piha and solaria (and chelsty-infra once the
# site is revived). Was owner_node: chelsty — not a real node name; fixed during
# the 2026-07 truth cleanup (recon B7/F20.5), closing the docs/backlog.md
# "stability-agent / node_exporter owner_node single" item for stability-agent.
owner_node: per-host
exposure: private
dependencies: []
healthcheck:
type: custom
interval: 60s
timeout: 10s
retries: 3
restart_policy: unless-stopped
persistence:
paths:
- /opt/homelab/state
- /opt/homelab/events
runtime:
directories:
- /opt/homelab/state
- /opt/homelab/events
env_vars:
- STABILITY_CHECK_INTERVAL
- DISK_THRESHOLD_PCT
- MQTT_HOST
- MQTT_PORT