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

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:
2026-06-12 07:46:15 -07:00
parent e9a58fa8e4
commit 0665e3a007
9 changed files with 39 additions and 23 deletions

View File

@@ -1,7 +1,7 @@
---
type: system
name: gururmm-build
display_name: GuruRMM VM (gururmm-build)
display_name: GuruRMM server (gururmm-build, physical)
last_compiled: 2026-05-24
compiled_by: DESKTOP-0O8A1RL/claude-main
sources:
@@ -15,19 +15,19 @@ backlinks:
- systems/pluto
---
# GuruRMM VM (gururmm-build)
# GuruRMM server (gururmm-build, physical)
## Identity
- **Hostname:** gururmm / gururmm-build
- **IP:** 172.16.3.30
- **Role:** Production server — GuruRMM API, ClaudeTools API, Coord API, MariaDB, PostgreSQL, build pipeline
- **Location:** Linux VM on Jupiter (172.16.3.20), virsh domain "GuruRMM"
- **OS:** Ubuntu 22.04 LTS
- **History:** Originally ran as a Docker container on Jupiter; migrated to its own VM at 172.16.3.30
- **Location:** **Physical box** (Lenovo ThinkCentre M83) on the office LAN — NOT a Jupiter VM.
- **OS:** Ubuntu 26.04 LTS (PostgreSQL 18, MariaDB)
- **History:** Originally a Docker container on Jupiter → Ubuntu VM on Jupiter at 172.16.3.30 → **physical box took the same .30 IP on 2026-06-11** (rotational-disk WAL-fsync timeouts drove the move). Old VM decommissioned 2026-06-12.
## Specs
Linux VM — resource allocation managed via virsh on Jupiter (172.16.3.20). Exact vCPU/vRAM allocation not documented.
Physical: **Lenovo ThinkCentre M83** (desktop chassis). Storage: SSD ~915 GB (hot tier — OS, live PG, WAL, cargo targets, /opt/gururmm) + HDD 1 TB mounted `/data` (cold tier — aged partitions, downloads, backups).
## Services

View File

@@ -43,7 +43,7 @@ Not documented. iDRAC available at 172.16.1.73 (DHCP) for OOB management.
| VM | IP | State | Role |
|---|---|---|---|
| GuruRMM | 172.16.3.30 | running | Linux VM — GuruRMM API, ClaudeTools API, MariaDB, PostgreSQL, build pipeline |
| ~~GuruRMM~~ | ~~172.16.3.30~~ | **decommissioned 2026-06-12** | Former GuruRMM VM — migrated to a physical box that took the .30 IP (2026-06-11); virsh domain destroyed + disk deleted 2026-06-12. No longer on Jupiter. |
| Claude-Builder (Pluto) | 172.16.3.36 | running | Windows Server 2019 — MSI + cargo builds |
| OwnCloud | 172.16.3.22 | running | OwnCloud file sync VM (cloud.acghosting.com) |
| Unifi | (IP not documented) | running | UniFi Network controller |
@@ -93,6 +93,6 @@ Not documented. iDRAC available at 172.16.1.73 (DHCP) for OOB management.
## Backlinks
- [[systems/gururmm-build]] — GuruRMM VM hosted here (virsh domain "GuruRMM")
- [[systems/gururmm-build]] — GuruRMM **was** a VM here (virsh domain "GuruRMM"); decommissioned 2026-06-12, now a physical box at 172.16.3.30
- [[systems/pluto]] — Claude-Builder VM hosted here (virsh domain "Claude-Builder")
- [[systems/uranus]] — secondary storage Unraid node (separate machine, not hosted here)

View File

@@ -19,7 +19,7 @@ backlinks:
## Identity
- **Hostname:** Pluto / Claude-Builder
- **IP:** 172.16.3.36
- **Role:** Windows MSVC build server — produces GuruRMM Windows agent binaries + WiX MSI, and (2026-05-29) the **GuruConnect** Windows agent. Hosts a Gitea Actions runner for guru-connect's native MSVC builds.
- **Role:** Windows MSVC build server. For **GuruRMM** Windows agent + WiX MSI builds it is now the **FALLBACK** — Beast (GURU-BEAST-ROG, tailnet 100.101.122.4) is PRIMARY, and `build-windows.sh` only falls through to Pluto if Beast is unreachable/down or its build fails. Still produces the (2026-05-29) **GuruConnect** Windows agent and hosts a Gitea Actions runner for guru-connect's native MSVC builds.
- **RMM agent identity:** enrolled in GuruRMM as hostname **PLUTO** (client "AZ Computer Guru"). Drive it via `/rmm` (resolve PLUTO → agent id at runtime) when a workstation SSH key isn't authorized. There is **no dedicated `pluto` vault entry** — don't search for one.
- **Location:** VM on Jupiter (172.16.3.20), Unraid/virsh **VM name "Claude-Builder"** (= PLUTO = 172.16.3.36, same machine)
- **OS:** Windows Server 2019 Standard