This ansible playbook bundle imports a Virtual Machine into a cluster with KubeVirt APB installed.

Virtual machines can be imported from a URL or from VMWare (coming soon).

To use this option, select the Import from URL plan. You will need to supply the location of a virtual machine disk image and other basic parameters to define the new virtual machine. Once deployed, a PVC is created and the disk image is downloaded from the specified location. A virtual machine is created and associated with the imported disk image.

The current design of this APB requires that an OpenShift User and corresponding password be specified. This is a temporary inconvenience which should be removed in the near future. Please be sure to choose an account that has privileges to create resources (PVC and VirtualMachine(s)) in the chosen project.

This APB relies on the Containerized Data Importer (CDI) which is installed along with KubeVirt. CDI can import images in raw and qcow2 format. Compressed images in the gz and xz formats are supported.

The operating system installed in a virtual machine disk image may make certain assumptions about the underlying hardware platform. In order for the virtual machine to run properly, choose a virtual machine type that most closely matches the virtual machine being imported. Currently only 'default' is available but more types will be added as needed.

To use this option, select the Import from VMWare plan. You will need to supply VMware's url from where you want to import, virtual machine name to be imported and the VMware's administrator credentials. Once deployed, a virtual machine is created with a PVC containing imported image from VMware.

The current design of this APB requires that an OpenShift User and corresponding password be specified. This is a temporary inconvenience which should be removed in the near future. Please be sure to choose an account that has privileges to create resources (PVC and VirtualMachine(s)) in the chosen project.

At the moment we can import virtual machine having one disk and one network interface.

Note: After adding PVC name and pushing the newly build apb image to the broker, you would see 2 apb of the same name in the console. To avoid this, while editing the PVC details change the displayName of the apb under metadata in apb.yml