sync: auto-sync from GURU-5070 at 2026-06-12 07:28:38

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-12 07:28:38
This commit is contained in:
2026-06-12 07:28:53 -07:00
parent 7f06e47f09
commit 95c96d5dec
4 changed files with 23 additions and 17 deletions

View File

@@ -10,7 +10,9 @@ cut over from **Ollama (qwen3:14b on Beast, `100.101.122.4:11434`)** to the
**Anthropic API (Claude Haiku 4.5)** on 2026-06-12 (decision: Mike).
**Why — the "Ollama unreachable" error was a mislabeled timeout, not reachability.**
The server VM `.30` (gururmm, `172.16.3.30`) reaches Beast fine for `/api/tags` and
The GuruRMM server `.30` (gururmm, `172.16.3.30` — a **physical box**, Ubuntu 26.04;
the VM-on-Jupiter was retired and the physical server took over the `.30` IP) reaches
Beast fine for `/api/tags` and
short warm `/api/chat` (warm "say OK" = 1.1s), but a fleet-sized `/api/chat`
(~1500 log lines / ~17KB) never completes — it hit the curl 300s ceiling even warm.
Cause is qwen3:14b's minutes-long inference on a big prompt over a flaky cross-LAN
@@ -33,9 +35,12 @@ per-project key, mint its own). **ZDR requested from Anthropic, pending** — or
not a console toggle (email sales@anthropic.com). Test fleet OK to run before ZDR
confirms; don't point a production fleet at it until ZDR is live.
**Deploy shape.** Production server is a **native binary** `/opt/gururmm/gururmm-server`
via systemd, `EnvironmentFile=/opt/gururmm/.env` (both root-only; `guru` can't write
.env or restart). A CI pipeline builds/ships the binary on commit (`[ci-version-bump]`
commits). `.30` has no cargo. So deploy = commit/push (CI builds binary) **+ a root
action on `.30`** to add `ANTHROPIC_API_KEY` (and optional `ANTHROPIC_MODEL`) to
`/opt/gururmm/.env` and restart `gururmm-server`.
**Deploy shape (DONE 2026-06-12).** Production server is a **native binary**
`/opt/gururmm/gururmm-server` via systemd, `EnvironmentFile=/opt/gururmm/.env`
(root-owned). A Gitea webhook → CI builds+ships the binary on push to gururmm `main`
(no cargo on `.30`). `guru` CAN do root ops via `sudo` with the password in vault
`infrastructure/gururmm-server` `credentials.password` (SSH via `~/.ssh/gururmm-physical`).
Shipped: gururmm `c869e4d` → CI redeployed the binary; `ANTHROPIC_API_KEY` appended to
`/opt/gururmm/.env`; `gururmm-server` restarted; `/api/logs/analyze` verified end-to-end
(1500 logs → 10 findings in 24s). **Migration note:** the key lives in `.30`'s local
`.env`, not the repo — already on the physical `.30`, so nothing to re-add.