diff --git a/10-systems/services/navi-zoe.md b/10-systems/services/navi-zoe.md index 89a23fe..a6be4d2 100644 --- a/10-systems/services/navi-zoe.md +++ b/10-systems/services/navi-zoe.md @@ -1,7 +1,7 @@ --- owner: gmikcon status: active -last_reviewed: 2026-09-10 +last_reviewed: 2026-09-16 review_interval: 90d confidence: high source_of_truth: deployment-verified @@ -31,6 +31,7 @@ - Chat LLM: Ollama Cloud (`OLLAMA_HOST=https://ollama.com`), default model `glm-5.3-flash:cloud`; API key stored in `.env` on the VM (not documented here). - Embeddings: local Ollama `http://192.168.1.168:11434` (`EMBEDDING_OLLAMA_HOST`), model `nomic-embed-text:latest`. +- Multi-backend file (`ollama_backends_file` setting) is not configured — no `ollama_backends.json` exists on the VM; the Ollama backend is built from `OLLAMA_HOST`/`OLLAMA_API_KEY` in `.env`. ## MCP integrations @@ -51,3 +52,7 @@ ``` Updating: `git pull && bash deploy/install.sh && sudo systemctl restart navi`. + +## Maintenance log + +- 2026-09-16: rotated `OLLAMA_API_KEY` in `/home/ubuntu/navi-1/.env` (line 10, old key replaced; backup `.env.bak-ollama-20260916` kept next to it) and restarted `navi.service` — `active (running)`, health endpoint returned `status: ok`. No `ollama_backends.json` on the host, so no backend-file change was needed. Host-level doc: `10-systems/servers/service-host-navi-zoe.md`. diff --git a/90-maintenance/pending-changes/20260916163354-51ab4e24.json b/90-maintenance/pending-changes/20260916163354-51ab4e24.json new file mode 100644 index 0000000..40946de --- /dev/null +++ b/90-maintenance/pending-changes/20260916163354-51ab4e24.json @@ -0,0 +1,19 @@ +{ + "id": "20260916163354-51ab4e24", + "kind": "doc", + "target": "10-systems/services/navi-zoe.md", + "summary": "Add 2026-09-16 Ollama key rotation maintenance note to navi-zoe doc", + "reason": "Record the 2026-09-16 Ollama API key rotation on the zoe instance and the verified fact that no ollama_backends.json is used.", + "payload": { + "content": "---\nowner: gmikcon\nstatus: active\nlast_reviewed: 2026-09-16\nreview_interval: 90d\nconfidence: high\nsource_of_truth: deployment-verified\n---\n\n# Navi zoe (192.168.1.176)\n\nNavi instance `zoe` deployed on the libvirt VM `service` (hypervisor `hp-proliant-dl380-g6`). Deployed 2026-09-10 by `rei` on request of the owner.\n\n## Deployment\n\n- Method: `git clone -b deploy https://git.gnexus.space/git/root/navi-1.git` + `bash deploy/install.sh` (idempotent).\n- Repo: `/home/ubuntu/navi-1` on the VM, branch `deploy`.\n- Python: standalone CPython 3.12.14 in `~/navi-1/.python` (system python is 3.10, untouched).\n- API server: systemd unit `navi.service`, `Restart=always`, binds `0.0.0.0:8099`.\n- PostgreSQL: docker container `navi-postgres` (pgvector image), `127.0.0.1:5432`, volume `navi-pgdata`.\n- Terminal client: `navi-code` symlinked into `/usr/local/bin`.\n- Web UI: off (`NAVI_WEBCLIENT_ENABLED=false`), auth off (`NAVI_AUTH_ENABLED=false`) — LAN-trusted module.\n\n## Swarm\n\n- Hive: `http://192.168.1.168:8087` (`HIVE_URL` in `.env`), announce interval 120 s.\n- Swarm key: `.swarm-key` copied from the hive host (rei on `192.168.1.168`); not stored here.\n- Instance identity: `instance.json`, name `zoe`, instance_id `72a27598-d648-4b13-9caf-8ad195a838da`.\n\n## LLM / embeddings\n\n- Chat LLM: Ollama Cloud (`OLLAMA_HOST=https://ollama.com`), default model `glm-5.3-flash:cloud`; API key stored in `.env` on the VM (not documented here).\n- Embeddings: local Ollama `http://192.168.1.168:11434` (`EMBEDDING_OLLAMA_HOST`), model `nomic-embed-text:latest`.\n- Multi-backend file (`ollama_backends_file` setting) is not configured — no `ollama_backends.json` exists on the VM; the Ollama backend is built from `OLLAMA_HOST`/`OLLAMA_API_KEY` in `.env`.\n\n## MCP integrations\n\n- `gnexus-book` (17 tools) and `gnexus-creds` (7 tools) registered at startup.\n- Note: `mcp` python package pinned to `1.27.1` — version `2.2.0` breaks startup MCP registration (`'Tool' object has no attribute 'inputSchema'`).\n\n## Access\n\n- SSH: user `ubuntu`, password shared with other DL380 VMs — see gnexus-creds secret `gnauth-gnbook-ssh`. sudo requires password (use `ssh -tt` + `sudo -S` for non-interactive installs).\n- Health: `curl http://192.168.1.176:8099/health`.\n\n## Day-2 operations\n\n```bash\nsystemctl status navi\njournalctl -u navi -f\nsudo docker compose -f deploy/docker-compose.yml --env-file .env ps\n```\n\nUpdating: `git pull && bash deploy/install.sh && sudo systemctl restart navi`.\n\n## Maintenance log\n\n- 2026-09-16: rotated `OLLAMA_API_KEY` in `/home/ubuntu/navi-1/.env` (line 10, old key replaced; backup `.env.bak-ollama-20260916` kept next to it) and restarted `navi.service` — `active (running)`, health endpoint returned `status: ok`. No `ollama_backends.json` on the host, so no backend-file change was needed. Host-level doc: `10-systems/servers/service-host-navi-zoe.md`." + }, + "status": "applied", + "created_at": "2026-09-16T16:33:54Z", + "updated_at": "2026-09-16T16:33:55Z", + "applied_at": "2026-09-16T16:33:55Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}