Integrate with Awanio Cockpit

With a Cockpit target, Condensa migrates VMs onto the fleet of KVM hosts managed by the Cockpit control plane. You choose the target host, storage pool, and network per migration, and migration transfer jobs appear in Cockpit's Tasks panel automatically.

Prerequisites

• A running Cockpit control plane, reachable from the Condensa server over HTTPS.
• The target hosts are registered in Cockpit (added through Cockpit's normal host-provisioning flow).
• A Cockpit service account (access key + secret) for Condensa.
• For direct-pull transfers and warm migration: VDDK installed on the target hosts and network access from those hosts to ESXi — see About VDDK.
• For the staged fallback (used automatically when a host has no VDDK; cold migrations only): the hosts must be able to reach CONDENSA_PUBLIC_URL.

1. Create a service account in Cockpit

In Cockpit, create a service account for Condensa and note its access key and secret.

2. Register the provider in Condensa

1. Go to Providers → Add Provider.
2. Choose vendor Awanio Cockpit.
3. Fill in:
   • Label — a name you'll recognize in the wizard (e.g. cockpit-prod)
   • API URL — the Cockpit endpoint, e.g. https://cockpit.example.com
   • Access key / secret — the service account credentials
4. Save, then click Test on the provider card — it must report success before migrations can run.

3. Run a migration

In the migration wizard select your VMware source, pick the VMs, then:

• Target provider — the Cockpit provider you registered
• Target host — which KVM host receives the VM
• Storage pool — where the converted qcow2 disks land
• Network — the switch the VM's NIC attaches to (default None, to avoid IP conflicts with a still-running source)

Warm migration is offered for powered-on VMware VMs with CBT available; the wizard flags each VM's readiness.

How the data moves

Engine	Path	Used when
VDDK direct pull	Target host pulls from ESXi, converts to qcow2 on the fly	Host has VDDK (preferred; required for warm)
Staged transfer	Condensa exports via vSphere, converts, host downloads	Automatic fallback, cold only

The engine that actually ran is shown on the migration detail page as the Method badge.

Troubleshooting

• Provider test fails — check the API URL, service account credentials, and that Cockpit's TLS certificate is accepted.
• Import jobs fail with a thumbprint/VDDK error — verify VDDK on the target host (Vapor UI → System → Third-party Libraries) and that the host can reach ESXi on port 443/902.
• Staged transfer used when you expected direct pull — the target host has no VDDK or cannot reach ESXi; the migration still completes cold via staging.