vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

memory: nh3-ml1 build in progress, blocked on host driver install

Browse Source
This commit is contained in:
vh
2026-09-25 14:17:40 -07:00
parent bc278d4ba8
commit 59f5474bc7
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
persistent-memory.md
+9
View File
@@ -136,6 +136,15 @@ NH3 DNS are all fine. Open items:
`althing-seat-daemon-jekyll` are both disabled (stopped 09-19 and 09-24). The `althing-seat-daemon-jekyll` are both disabled (stopped 09-19 and 09-24). The
`infra-hermes` handle shows `pull`. `infra-hermes` handle shows `pull`.
**nh3-ml1 (Prime, 2026-09-25 ~1410): IN PROGRESS.** CT 109 on nh3-pve at
10.100.50.80 (VLAN 50, outside the UDM pool .150–.249), local-zfs, a second
embed/rerank (TEI) backend on the new RTX. Playbooks are host-generic as of
`bc278d4`. **Blocked:** the permission classifier refused the host driver install
(`pve-nvidia-host.yaml` on nh3-pve), and nothing host-side has run. Prime has to
run it or allow it. After it: `gpu-lxc.yaml` with nh3 vars → embed-rerank with
`HOST_NAME/HOST_IP` → parity vs esh-ml1 → monitoring and DNS → gateway routing
(Prime's call).
The pre-shutdown record follows, kept for the next GPU visit: The pre-shutdown record follows, kept for the next GPU visit:
Pre-flight done before shutdown: Pre-flight done before shutdown: