hn.today

Terraform Meets Proxmox: Lessons from a VMware Migration

goncharov.xyz26 points2 comments
Screenshot of Terraform Meets Proxmox: Lessons from a VMware Migration

A migration from VMware to Proxmox is presented as more than a simple hypervisor swap: infrastructure-as-code workflows, template building, VM initialization, storage selection and failure handling all change in subtle ways. A mature VMware stack using Packer, Terraform and Ansible could not be lifted unchanged; assumptions about templates, boot devices, networking and DHCP/hostname behavior broke repeatedly. Proxmox and XCP‑NG are singled out as realistic, low‑cost replacements with Packer/Terraform support and live migration, while vanilla KVM and Hyper‑V have tradeoffs. The author argues that careful planning is required around how images are produced, how VMs are instantiated, and how partial deployment failures are detected and remediated.

Storage choices drove many design decisions. Reusing an existing array pushed a shortlist of NFS and FC (shared LVM) and ultimately a mixed approach; Ceph was rejected because it wouldn’t reuse current hardware. Performance testing used fio (64 GiB files, 3,600 s, randread/randwrite 4 KiB and 1 MiB sequential profiles) and showed no universal winner: VMware delivered far better small‑random IOPS/latency (realistic workloads), while Proxmox performed better on large sequential transfers. Practical Terraform fixes and examples are provided for common problems: set bios=ovmf, machine=q35 and efidisk to ensure a boot disk; define VLAN tags/bridge for SSH reachability; and enable cloud‑init to ensure correct DHCP hostnames.

Read on goncharov.xyz2 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Other

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.