nixos/slop-cannon: Move to a VM on palace
CI / Check, build and cache nixfiles (push) Successful in 45m39s
Update docs / update (push) Successful in 1m0s

Give agents their own kernel, Nix daemon and disk for workloads that
need root. Put the VM on the `untrusted` VLAN with MAC spoof
checking on VF 5.

Export a dedicated partition from `cellar` and connect it on
`palace`. Give the VM its own SSH host key and age secrets for Paseo
and Gitea. Keep the agent home and Paseo identity on persistent
storage and provide `slop-pair` for pairing clients.

Retire the container, restore `sfh` to 8 cores and 32 GiB, and rekey
the shared password secret. Document the VM and its operating
procedures on the relevant box pages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-18 22:02:14 +00:00
co-authored by Claude Opus 5.5
parent 5058dec3f1
commit a6491c7535
20 changed files with 588 additions and 353 deletions
-3
View File
@@ -24,8 +24,6 @@ from `river` and runs its root off NVMe-oF from `cellar`.
`/var/lib/frigate`.
- USB: two host ports are passed to the VM (qemu flags) for the Zigbee coordinator and webcam used
by `hass`; the nspawn unit gets `DeviceAllow` for `char-ttyUSB` and `char-video4linux`.
- `slop-cannon`'s nspawn unit gets a low `CPUWeight` and a `MemoryMax`, so agent builds can't starve
`hass` and `unifi`, and a larger `/tmp` tmpfs than nspawn's default (10% of RAM).
## Network assignments
@@ -55,7 +53,6 @@ back through the VM handoffs to the physical switch connections.
|---|---|
| [`hass`](containers/hass.md) | Home Assistant + Frigate + MQTT |
| [`unifi`](containers/unifi.md) | UniFi controller |
| [`slop-cannon`](containers/slop-cannon.md) | Coding agents, driven remotely through Paseo |
## Notable config files