Suppose you want to import virtual machines you already have into oVirt to enjoy a features-rich open sourced management system. You will soon figure out that the conversion of virtual machines running on different hypervisors or managed by different management systems into oVirt is not an easy task. The next major version of oVirt is going to introduce an integrated process that will simplify import of virtual machines not being managed by oVirt into oVirt. This session gives a heads up for the feature: we will go over the design and see how it solves issues that we had before to provide better way for import virtual machines to oVirt.
Until now from oVirt one could only import virtual machines (VMs) that were managed once by oVirt, either VMs that were exported from oVirt or VMs that reside on storage that was attached once to oVirt. In order to import VMs that run on different hypervisors or managed by different tools/management solutions, one had to use external tool, such as virt-v2v, separately to convert the VMs so they will fit to oVirt and then import the VMs from oVirt. This results in a slow, tedious and error-prone process. An important feature in oVirt 3.6 is going to be the extension of import VMs capabilities to provide users with a process that is integrated within oVirt web-admin ui for import VMs from external environments, i.e VMs that run on different hypervisors and managed by different management solutions. We produce a process based on integration with virt-v2v, for import such VMs to oVirt which is better in terms of usability, performance and monitoring. The new process will ease migration of existing VMs into oVirt, encouraging people to have their existing virtual environments replaced with oVirt. In this session we will analyse the problems with the previous process, go over the design of the new one and see how it address the problems we used to have, producing a better way for migrate existing virtual environments to open source virtualization platform.
Speakers: Arik Hadas