Integration
Every migration source and target in Condensa is a provider. You register providers once (credentials are stored encrypted), then pick a source and a target in the migration wizard.
Sources
| Vendor | Credentials |
|---|---|
| VMware vSphere / ESXi | Username + password |
| OVA / VHD file upload | — (file-based) |
Targets
| Target | When to choose it | Guide |
|---|---|---|
| Awanio Cockpit | You run a fleet of KVM hosts managed by the Cockpit control plane; you want host/pool/network placement per migration | Integrate with Cockpit |
| Awanio Vapor (standalone) | A single Vapor host with no control plane — small sites, proof-of-concepts | Integrate with Vapor |
| Awanio CEP (KubeVirt) | Migrating into Kubernetes/KubeVirt via CDI | (covered in the User Guide) |
Multiple providers of the same vendor can be registered side by side and are distinguished by their label — for example a production Cockpit and a DR Cockpit.
About VDDK (applies to Cockpit and Vapor targets)
For the fastest transfers — and for warm migration at all — the target host pulls disk data directly from ESXi using VMware's VDDK library with Changed Block Tracking. VDDK is proprietary and cannot be bundled, so it is installed once per target host:
- Download the VDDK tarball from the Broadcom developer portal (free account).
- Upload it on the target host's Vapor UI under System → Third-party Libraries — it is validated, installed, and detected immediately.
Condensa probes VDDK availability per migration:
- VDDK present → direct pull; warm migration available.
- VDDK absent → Cockpit targets fall back to a staged transfer (cold only); standalone Vapor targets require VDDK and fail fast with a clear message.