Case Study: Volume Populators for Virtual Disks?
summary
Volume Populators (Kubernetes 1.24 beta) integrate into Forklift / MTV 2.4 to populate VM disks from oVirt and OpenStack by launching populator pods that run native tools (ovirt-imageio, Gophercloud) and write directly to PVs; tests show reduced transfer time by up to 50% for oVirt, OpenStack migration ships on schedule, vSphere does not fit the model. Limitations include no multi-stage snapshot transfers, problems with multi-volume disks, dynamic provisioning edge cases, and several patches applied — forked lib-volume-populator to add labels, restart limits and namespace placement.
AI-written summary · about
chapters (11)
- 0:00Volume populators intro
- 4:40Feature overview and demo
- 7:48CDI comparison and design
- 11:22Forklift’s adoption
- 14:55Implementation challenges
- 18:12Dynamic provisioning issues
- 19:16Multi-volume disk migrations
- 21:07Remote cluster migrations
- 22:31Library adaptations and cleanup
- 24:22Assessing for virtual disk migrations
- 25:59Q&A
related talks
28mFrom Pre-Population To Disasters: Manage And Protect the State Of VMs
31mMigrating from VMware to Kubernetes
27mZero copy migration from VMware to Kubernetes
24mCapacity-aware Dynamic Volume Provisioning For LVM-based Local Storage
21mKeep Your VM Dancing With Volume Migration
42mVirtual Machine Orchestration in Kubernetes Utilizing KubeVirt
05mLightning Talk: Automate Local Volume Provisioning with Local-Volume-Provisioner
28mKubernetes Storage Evolution: Enabling High Performance Distributed Datastores
