homelab-codex-ws/jobs/deploy-runner/systemd/homelab-deploy-runner.service
oskar da151fc8d3 fix(control-plane): redeploy wykonywalny — dispatch do host-side deploy-runnera
Executor odpalal scripts/deploy/deploy-node.sh <node> <service> wewnatrz
swojego kontenera: skrypt ignoruje oba argumenty i wymaga repo w
${HOME}/homelab-codex-ws (w kontenerze HOME=/home/homelab) -> exit 1 w 18.
linii. Za tym brak git, brak klienta docker w obrazie, a gdyby przeszedl —
deploy calego zestawu uslug hosta executora zamiast wezla z akcji. Kazdy
redeploy padal (recon D14/D15; 18 pending / 0 completed).

Redeploy idzie teraz ta sama sciezka pull co container_restart — VPS nigdy
nie inicjuje polaczenia do wezla:
  executor -> actions/deploy/<node>/<id>.json
  -> deploy-runner (systemd na hoscie) rsync-pull, walidacja, deploy
  -> action_result event -> executor rozlicza completed/failed

- scripts/deploy/deploy-service.sh: deploy jednej uslugi, wspoldzielony z
  deploy-node.sh, wiec inwokacja compose (a przez to nazwa projektu) jest
  identyczna jak przy deployu recznym
- jobs/deploy-runner/: host-level, nie kontener — compose rozwiazuje
  wzgledne bindy i nazwe projektu tak jak przy deployu czlowieka;
  niezalezny od node-agenta, wiec potrafi zredeployowac takze jego
- walidacja: tylko typ redeploy, node musi sie zgadzac, usluga musi byc w
  hosts/<node>/services.yaml, zadna tresc z payloadu nie trafia do shella
- --force-recreate bez --build i bez --remove-orphans: redeploy to
  rekoncyliacja, nie wysylka kodu
- executor: REDEPLOY_TIMEOUT_SECS=900, /repo zjechany do :ro (nieuzywany)

248 testow zielonych; deploy-node.sh przecwiczony na atrapie dockera —
argv compose bez zmian. Instalacja unitow na wezlach i E2E: backlog.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-03 18:26:30 +02:00

26 lines
1.2 KiB
Desktop File

# homelab-deploy-runner.service — host-side executor for control-plane `redeploy`
# actions (docs/architecture/RECON-multiagent-2026-07-27.md D14/D15).
#
# Host-level and NOT a container, deliberately: it runs `docker compose` the way
# a human deploy does, so relative bind mounts and the compose project name
# resolve identically. A containerised runner would resolve them against its own
# filesystem and hand the daemon host paths that do not exist.
#
# Install: see ../README.md (copy this + the timer to /etc/systemd/system/,
# create /opt/homelab/config/deploy-runner/env from env.example, daemon-reload,
# enable the TIMER — not this unit).
[Unit]
Description=Homelab deploy runner (executes approved redeploy actions on this node)
After=network-online.target docker.service
Wants=network-online.target
[Service]
Type=oneshot
User=oskar
# Runtime config: NODE_NAME, REPO_PATH, VPS_EVENTS_HOST, ... (see env.example).
EnvironmentFile=/opt/homelab/config/deploy-runner/env
ExecStart=/home/oskar/homelab-codex-ws/jobs/deploy-runner/deploy-runner.sh
# Slightly above the runner's own per-action DEPLOY_TIMEOUT_SECS (default 600)
# so the script always gets to report a result before systemd intervenes.
TimeoutStartSec=900