Files
esh-pfi-infrastructure/stacks/augaman/README.md
T
vh d8f59a15d9 feat(esh-ml1): restic backup of augaman's gallery; augaman v0.1.2
esh-ml1 is outside vzdump, so augaman's face gallery reaches backup only
through restic. New playbooks/esh-ml1-restic.yaml installs restic 0.14.0 (the
same Debian package as the other ESH hosts) and resticprofile 0.33.1 (pinned,
sha256-checked). It uploads configs/restic/esh-ml1/ and schedules a daily
0100 PT backup plus a Sunday 0500 PT check to rest-server-ana. The CT runs UTC,
so both schedules name the zone explicitly.

pre-backup.sh is fail-closed: it runs augaman's own backup CLI, and any failure,
including a stopped container, aborts the run. Tested with a stub docker that
exits 1: the run returned 1, and neither the snapshot count nor last-success
moved. The restore was verified at identity level against augaman-dev's
public-domain canary (snapshot fd3061a1: the restored copy's digest over
identities and samples matches the live gallery). That meets the operator gate
for real enrollments.

The repository URL is read through repository-file rather than restic.env.
resticprofile schedule copies env-file values into world-readable systemd
units, which publishes the rest-server password on the env-file hosts
(observed on esh-docker-vm). This is recorded in the backups runbook under
Known gaps, and the playbook verifies no generated unit contains the URL.

esh-ml1 is added to the freshness check's expected ana-side repos and to the
runbook tables.

augaman moves to v0.1.2 (dependency layer keyed on the lock without the
project; per-crop embedding). pytest -m gpu tests/vision passes 3/3 on the
card, and the canary survived the container recreate.
2026-09-27 00:06:33 -07:00

3.6 KiB
Raw Blame History

augaman

The fleet's face-recognition service for Cicada (enroll, recognize, verify), on esh-ml1 (CT 110 on esh-pve, RTX 2000E Ada). buffalo_l (SCRFD detector + ArcFace w600k_r50) on ONNX Runtime CUDA. Code and the canonical compose live in gitea pfi/augaman (owner: augaman-dev); compose.yaml here is a verbatim mirror of that repo's deploy/compose.yaml at the deployed tag. Change it there first, then re-mirror it here.

URL http://10.0.50.80:8040 (/health is unauthenticated; everything else needs the bearer token)
Token secret get augaman/api-token (vault is the source of truth)
Image augaman:<version>, built locally on esh-ml1 (below)
State named volume augaman_gallery (SQLite, local disk; the app refuses NFS)
VRAM ~1.5 GB by design (embed batches capped at 16)

⚠ Biometric data: backup gate

The gallery holds face embeddings and crops of household members. esh-ml1 is outside vzdump, so the gallery reaches backup only through the app's backup CLI, which writes gallery.db (mode 0600) into BACKUP_DIR = /var/lib/restic/stage/augaman (owned 10001:10001, mode 0700).

Operator ruling: until a scheduled backup ships that file off-box AND one restore has been verified (the restored copy reports the same identities), only public-domain test fixtures may be enrolled. No household faces.

Backup status (2026-09-27): WIRED AND RESTORE-VERIFIED, so the gate is met. restic runs daily at 0100 PT to rest-server-ana, with a fail-closed pre-backup hook (configs/restic/esh-ml1/). The restore was verified against augaman-dev's public-domain canary identity (1 identity, 3 samples): the copy restored from snapshot fd3061a1 matched the live gallery (identities, samples and embeddings, by digest), and integrity_check returned ok.

docker exec augaman python -m augaman.gallery.backup --db /data/gallery.db --dest /backup/gallery.db
# one JSON line + exit 0, or "backup failed: ..." + exit 1

Building

The image is built on esh-ml1 from the release tag's content. esh-ml1 has no gitea credentials, so the source is shipped as a git archive:

# from nh3-dev, in a pfi/augaman checkout
git archive --format=tar vX.Y.Z | ssh esh-ml1 'sudo mkdir -p /opt/docker/src/augaman-vX.Y.Z && sudo tar -x -C /opt/docker/src/augaman-vX.Y.Z && sudo chown -R infra-ops:infra-ops /opt/docker/src'
# on esh-ml1
cd /opt/docker/src/augaman-vX.Y.Z && docker build -t augaman:X.Y.Z .

The build fetches the two pinned models and SHA-256-checks them; a mismatch fails the build. v0.1.0 built in under 2 minutes cold; v0.1.1 was the first version deployed (2026-09-26), then v0.1.2 (2026-09-27).

⚠ Disk: a build that has to install the third-party packages takes ~8–11 GB transiently (image ~5 GB plus the ~3 GB uv download cache). Beszel alerts at 85%. Before v0.1.2, every version bump re-installed them, and the v0.1.1 build hit 90%. From v0.1.2 the packages install from a layer keyed on uv export --no-emit-project, so a bump that changes no dependency reuses that layer. Keep the layer cache (docker builder prune --filter type=exec.cachemount drops only the download cache); a full docker builder prune forces the next build to re-install everything.

Startup is fail-closed on CUDA

The service refuses to serve unless CUDA really runs every convolution (profiled warmup, ORT CPU fallback disabled). /health reports backend cuda only then. Allow up to 180 s (start_period). The real GPU confirmation is the augaman process showing up in nvidia-smi on the host.