azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wiki/memory: retire GuruRMM 'VM' framing + correct Windows build chain

Browse Source 
Two sweeps:
1. .30 is a PHYSICAL box (Lenovo ThinkCentre M83, Ubuntu 26.04), not a Jupiter
   VM — the VM was decommissioned 2026-06-12. Fixed inventory tables and the
   gururmm-build system page (overview, index, jupiter, gururmm-build,
   POWER_FAILURE_RUNBOOK).
2. Windows build chain: Beast (GURU-BEAST-ROG, tailnet 100.101.122.4, i9-14900K)
   is PRIMARY; Pluto (172.16.3.36) is FALLBACK. Verified against build-windows.sh
   (`attempt_build beast || attempt_build pluto`). Fixed overview, index,
   projects/gururmm (build-host table + flow + host detail), systems/pluto, and
   the reference_pluto_build_server memory.

Submodule advanced: build-pipeline doc comments corrected to match.
This commit is contained in:
Mike Swanson
2026-06-12 07:46:15 -07:00
parent e9a58fa8e4
commit 0665e3a007
9 changed files with 39 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
wiki/projects/gururmm.md
View File

@@ -308,8 +308,9 @@ The `enrolled_agents` table is the authoritative enrollment history log:
| PostgreSQL DB | localhost:5432 on 172.16.3.30, database `gururmm` | PostgreSQL 18 | deployed (migrated from PG VM, backfilled 2026-06-11) |
| Coord API | 172.16.3.30:8001/api/coord | FastAPI (part of ClaudeTools API) | deployed |
| Build pipeline | 172.16.3.30:9000 webhook + `/opt/gururmm/` scripts | Python (webhook-handler.py), Bash | deployed; builds agents AND server (server auto-deploy wired 2026-06-02) |
| Pluto (Windows build VM) | 172.16.3.36, Windows Server 2019 VM on Jupiter (Unraid) | Rust MSVC, WiX v4 | operational; Xeon E5-2695 v3 8c/16t, sequential build ~23min (parallel prototype 3.51x speedup, deferred integration) |
| Old VM (rollback anchor) | 172.16.3.46, powered on, data pristine | Ubuntu (original) | parked; do NOT delete until soak completes |
| Windows build — **Beast (PRIMARY)** | GURU-BEAST-ROG, i9-14900K (24c/32t), RTX 4090; reached over Tailscale at tailnet IP 100.101.122.4 as user `guru` | Rust MSVC, WiX 4.x | **primary** Windows build host — `build-windows.sh` tries Beast first |
| Windows build — Pluto (FALLBACK) | 172.16.3.36, Windows Server 2019 VM on Jupiter (Unraid), Xeon E5-2695 v3 8c/16t | Rust MSVC, WiX v4 | **fallback only** — used if Beast is unreachable/down OR its build fails (`attempt_build beast \|\| attempt_build pluto`) |
| Old VM (decommissioned) | was 172.16.3.46 | Ubuntu (original) | DELETED 2026-06-12 after stability soak — virsh domain + disk removed; no longer exists |
### Key Files & Repos
@@ -455,7 +456,9 @@ Gitea push to main
-> webhook-handler.py (172.16.3.30:9000 via nginx :80 /webhook/, parallel threads per platform)
-> build-shared.sh (auto-version bump, git sync — runs once)
-> build-linux.sh (cargo build on .30; log: /var/log/gururmm-build-linux.log)
-> build-windows.sh (SSH -> Pluto 172.16.3.36 via pinned known-hosts
-> build-windows.sh (SSH -> Beast PRIMARY (guru@100.101.122.4 over Tailscale)
|| fall back to Pluto Administrator@172.16.3.36;
each via its own pinned known-hosts
cargo build --release x64 MSVC + i686 MSVC
+1.77 legacy builds with --ignore-rust-version
WiX MSI build for site-specific base
@@ -490,7 +493,19 @@ Do NOT hand-rsync into the prod web root. One artifact serves both channels —
**DB migrations** — manual; must insert SHA-384 checksum into `_sqlx_migrations` or server crashes on start. Migrations run automatically on server restart (sqlx), but the checksum must be correct.
**Pluto (172.16.3.36):**
**Windows build hosts — Beast PRIMARY, Pluto FALLBACK.** `build-windows.sh` runs
`attempt_build beast || attempt_build pluto`: Beast is tried first; Pluto is used only if Beast
is unreachable/down or its build fails. Both build the same `C:\gururmm` checkout; host keys at
`/opt/gururmm/{beast,pluto}_known_hosts`.
**Beast (GURU-BEAST-ROG) — PRIMARY:**
- Physical workstation, **i9-14900K (24c/32t)**, RTX 4090. Much faster per-core than Pluto.
- Reached from `.30` over **Tailscale** (installed on `.30`) at tailnet IP **100.101.122.4**, user `guru`.
- SSH: `ssh -o UserKnownHostsFile=/opt/gururmm/beast_known_hosts guru@100.101.122.4`
- Rust MSVC toolchain, **WiX 4.x** (WiX v6+ pulls OSMF and breaks the build), Gitea clone at `C:\gururmm\`.
- On a different LAN (Wi-Fi `10.2.51.228`) + tailnet — reachability depends on Beast being up on the tailnet.
**Pluto (172.16.3.36) — FALLBACK:**
- Windows Server 2019 VM on Jupiter (Unraid)
- SSH: `ssh -o UserKnownHostsFile=/opt/gururmm/pluto_known_hosts Administrator@172.16.3.36`
- Rust stable 1.95.0 + 1.77 pinned for legacy builds