Two Intel NUCs running Proxmox VE 8.3.0 (kernel 6.8.12-4-pve), the compute
for the lab. Both started fresh — no VMs, no CTs. Access is the id_rsa key
(Proxmox may grant it for root) with a root-password fallback.
| nadia (192.168.50.74) | natasha (192.168.50.217) | |
|---|---|---|
| Proxmox | VE 8.3.0 | VE 8.3.0 |
| RAM | 16 GB — 2× 8 GB, both slots full | 16 GB — 1× 16 GB, one slot open (→ 32 GB with a second stick) |
| Disks | 1× WD Blue 500 GB SSD | 1× Samsung 850 250 GB (boot) + 1× WD 500 GB |
local-lvm (thin) |
~354 GB | ~619 GB (the 500 GB folded in) |
| Web UI | https://192.168.50.74:8006 | https://192.168.50.217:8006 |
natasha's second 500 GB disk held a pvestorage VG of orphaned 2020 VM disks;
those were removed and the disk folded into the pve VG, so local-lvm is now
one ~619 GB thin pool.
Edit a config, push it, watch the VM/CT/service appear — the way the work infra
is managed, not click-ops. Candidate control planes: Terraform (the
bpg/proxmox provider), Ansible, or the vivarta-drones engine. The aim:
create a VM, or push a service into a VM, from a config file + one command.
local-lvm is
LVM-thin, so base images + copy-on-write keep overlapping disk low (a handful
of VMs, mostly containers inside the VMs).