vh
8c15ec2d5f
pfi-pve (Anaheim), nh3-pve (NH), esh-pve + esh-pve-nas (ESH home lab) now have servers/<host>/ entries with ssh-target files, README stubs, and first snapshots. Register all four via add-host.sh + ssh-copy-id; SSH auth is root@<name> with key-based access. Fix a resolver bug in the three workspace scripts: previously, when a hostname resolved via /etc/hosts, resolve_target returned the bare name and ssh dropped the user prefix stored in ssh-target (connecting as the wrong user). Now ssh-target wins whenever it's present, since it can carry user@ or port info that /etc/hosts + ssh_config cannot. Falls back to the dir name only when no ssh-target file exists. CLAUDE.md and README.md split the fleet table into Docker hosts vs hypervisors with an explicit placement rule: don't deploy Docker stacks on PVE hosts; capture host-level detail with server_inspect.sh, use Proxmox-native tooling (qm list, pvesh, zpool) for VM/storage audits.
esh-pve
Proxmox VE hypervisor for the ESH home lab (pve.esteban.net). Non-PFI scope.
Network
- LAN IP: 10.0.250.35
- FQDN:
pve.esteban.net - Web UI:
https://10.0.250.35:8006 - SSH:
root@esh-pve(key auth)
Hardware
- CPU: 13th Gen Intel Core i9-13900H
- RAM: 62.5 GB
- Kernel:
6.8.12-16-pve(Proxmox 8.x) - Storage: local
pve-rootat 94G (21% used) + two large NFS mounts from10.0.50.50:/mnt/pve/esh-nas— 92 TB available on/mnt/pvestore/mnt/pve/tank-vmbu— 93 TB, VM backup target (~1.4 TB used)
What it runs
esh-docker-vm (10.0.50.45) is a VM here. Other home-lab VMs are not yet catalogued in this workspace — run qm list on the host for the live inventory.
Refresh state
scripts/refresh-server-info.sh esh-pve
Same Proxmox-inspect caveat as pfi-pve.
Placement rule
Hypervisor for ESH home-lab VMs. Not part of the PFI colo topology.