docs: R-50 island-bridge spike attempt 2 (t740) — STILL BLOCKED (no drill VM there); nodes.md drill-host ruling; REPORT

2026-07-25 09:59:10 +02:00
parent 77119bd1b0
commit 5d56f93755
4 changed files with 91 additions and 39 deletions
@@ -57,7 +57,22 @@ that looked installed and could never call home. Repaired on the console by brid

 Current, post-repair: `vmbr0` static `192.168.0.87/24`, gw `192.168.0.1`, bridge-port `enp2s0f0`.
 No trace of `192.168.100.2` remains. `wg-felhom` `10.77.0.3/32` up to the hub. Guest **9201
-`demo-hp`** running.
+`demo-hp`** running. Agent **0.93.0** (behind demo-felhom's 0.95.0 — publish when convenient).
+
+### Designated drill + build VM host (operator ruling, 2026-07-25)
+
+**Ruling:** drill and build VMs are hosted on the **t740 from now on** — NOT on felhom-pve, and moving
+them off DooPlex (the production k3s node). **This is a VM-HOSTING ruling only; the build-PIPELINE
+relocation to the t740 is NOT ruled or implemented here.**
+
+**Current state (verified 2026-07-25):** the ruling is **forward-looking and not yet realized.** The
+t740 hosts **no drill/build VM yet** — `qm list` is empty, `/etc/pve/qemu-server/` is empty, it is a
+standalone PVE node running only its own LXC guest 9201. The historical drill appliance is still
+`drill.qcow2` on **DooPlex** (`/mnt/5_hdd/felhom.eu/drill/`, ~18G, powered off — a golden-bake VM whose
+nested guest is purged after each bake). felhom-pve likewise has no drill VM. **A nested-PVE drill VM
+(agent + a nested guest) must be provisioned on the t740** before the R-50 island-bridge empirical spike
+(`audits/SPIKE-island-bridge-2026-07-25.md`) can run its P2–P7 probes — that spike is blocked on exactly
+this. The t740's ~30 GB RAM / ~49 GB free local-lvm suit it as the drill host.

 ### Access — there is no baked SSH key