Files
cozystack/packages/system/migration-controller/Makefile
Andrei Kvapil 54621bc046 feat(migration): tenant self-service VM import from VMware vSphere
Hidora's customers are leaving VMware now, and a tenant has to be able to
import their own machines without a platform administrator. The chart
approach could not express that: a tenant can neither create the Secret
holding vCenter credentials nor name the VDDK image, so both had to come
from somewhere they cannot reach.

Two CRDs in a new `forklift.cozystack.io` group, split by lifecycle. A
VMImportSource is a long-lived connection -- type, endpoint, credentials,
readiness -- and a VMImportTask is the one-shot operation that names
machines and produces VMDisks and VMInstances. The outputs carry no owner
reference back to the task, so deleting a finished import leaves the
machines alone. Konveyor Forklift does the transfer underneath; the
controller renders its objects, mirrors its verdicts, and hands each
finished volume into a VMDisk without copying it.

What a live vCenter migration forced out, and no amount of source reading
would have:

- A guest copied verbatim keeps the drivers it had under VMware and no
  virtio, so on a virtio disk it does not fail the import -- it succeeds
  and then does not boot. Imported disks go on SATA.
- VDDK connects straight to the ESXi host at the address vCenter
  advertises, which is routinely unreachable, and on the first cluster
  collided with the Service CIDR. `spec.hosts` redirects per host.
- Firmware must be carried across or a UEFI guest imports as BIOS and
  never boots (stacked on #3002).
- Deleting a task mid-transfer orphaned its DataVolume; a finalizer now
  removes the engine's volumes and leaves the outputs.

The console gains a Migration section: connections are editable, and the
VM field is a picker built from a machine list the controller publishes,
since the aggregated API cannot reach the inventory and should not hold a
source's credentials to try. Two general mechanisms fall out of that --
an option source may take an argument, and one named in a CRD annotation
may reference a sibling field.

Design: cozystack/community#62. Docs: cozystack/website#673.

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
2026-09-07 17:03:44 +02:00

21 lines
717 B
Makefile

NAME=migration-controller
NAMESPACE=cozy-migration-controller
include ../../../hack/common-envs.mk
include ../../../hack/package.mk
test:
helm unittest .
image: image-migration-controller
image-migration-controller:
docker buildx build -f images/migration-controller/Dockerfile ../../.. \
$(call image-tags,migration-controller,v$(COZYSTACK_VERSION)) \
$(call cache-args,migration-controller) \
--metadata-file images/migration-controller.json \
$(BUILDX_ARGS)
IMAGE="$(REGISTRY)/migration-controller:$(IMAGE_TAG)@$$(yq e '."containerimage.digest"' images/migration-controller.json -o json -r)" \
yq -i '.migrationController.image = strenv(IMAGE)' values.yaml
rm -f images/migration-controller.json