chore(augaman): remove the fv-ml1 instance (Prime)
Prime removed the second instance after the v0.1.3 bench. esh-ml1 handles a face in ~48 ms, sits in the house next to the cameras, and holds the verified backup. fv-ml1's gallery was empty (0 identities). The container, gallery volume, image, compose dir (with its .env), backup dir and build sources are removed from fv-ml1. GPU_ID / CARD_SUFFIX stay in the compose for any future second host.
This commit is contained in:
@@ -13,17 +13,15 @@ HOST_IP=10.0.50.80
|
||||
|
||||
# The host's card index for the GPU reservation (default 0). The container always
|
||||
# sees its one card as index 0, so AUGAMAN_CUDA_DEVICE_ID never changes.
|
||||
# esh-ml1: 0 (the only card) fv-ml1: 1 (the utility card, beside vllm-coder)
|
||||
# esh-ml1: 0 (the only card). fv-ml1 used 1 while its instance existed (removed 2026-09-27).
|
||||
GPU_ID=0
|
||||
# Appended to the Homepage card name so the two instances are distinguishable.
|
||||
# Note the leading space. esh-ml1 (the primary) leaves it empty.
|
||||
# fv-ml1: CARD_SUFFIX=" (fv-ml1)"
|
||||
# Note the leading space, e.g. CARD_SUFFIX=" (fv-ml1)". esh-ml1 leaves it empty.
|
||||
CARD_SUFFIX=
|
||||
|
||||
# Where the backup CLI writes gallery.db. Owned 10001:10001 (the container user),
|
||||
# mode 0700. On esh-ml1 it is the restic stage dir, so the backup run that copies the
|
||||
# gallery here is the same run that ships it off-box (README "Backup").
|
||||
# fv-ml1 (fixtures-only, no scheduled gallery backup): /opt/docker/backup/augaman.
|
||||
BACKUP_DIR=/var/lib/restic/stage/augaman
|
||||
|
||||
# >= 32 visible-ASCII characters. Source of truth is the vault:
|
||||
|
||||
@@ -13,14 +13,14 @@ first, then re-mirror it here.
|
||||
| **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** | ~0.5 GB on esh-ml1, ~1.3 GB on fv-ml1 (measured) |
|
||||
| **VRAM** | ~0.74 GB on v0.1.3 (measured after the bench; 0.51 GB on v0.1.2) |
|
||||
|
||||
**Two instances (2026-09-27).** The **primary is on esh-ml1** (`GPU_ID=0`): it holds
|
||||
the gallery and has the verified backup. A **second instance runs on fv-ml1**
|
||||
(`GPU_ID=1`, the utility card beside `vllm-coder`; `CARD_SUFFIX=" (fv-ml1)"`;
|
||||
`BACKUP_DIR=/opt/docker/backup/augaman`) at Prime's request. It has its own,
|
||||
separate gallery, and it is **fixtures-only**: no gallery backup is wired there,
|
||||
and the two galleries do not sync. Speed comparison: [`docs/pfi/augaman-speed-bench/`](../../docs/pfi/augaman-speed-bench/README.md).
|
||||
**One instance: esh-ml1.** A second, fixtures-only instance ran on fv-ml1's GPU 1
|
||||
(`GPU_ID=1`) from 2026-09-27 0017 to 0125 PT, for the speed comparison in
|
||||
[`docs/pfi/augaman-speed-bench/`](../../docs/pfi/augaman-speed-bench/README.md).
|
||||
**Prime removed it** after v0.1.3 put esh-ml1 at ~48 ms per face: it is in the house
|
||||
next to the cameras and it holds the verified backup. `GPU_ID` / `CARD_SUFFIX` stay in
|
||||
the compose for any future second host.
|
||||
|
||||
## ⚠ Biometric data: backup gate
|
||||
|
||||
|
||||
Reference in New Issue
Block a user