Home > Design Patterns > Cross-Hypervisor Workload Mobility

Cross-Hypervisor Workload Mobility (Erl, Naserpour)

How can virtual servers be moved between hypervisors of varying brands and models across different environments?

Cross-Hypervisor Workload Mobility

Problem

Virtual servers need to be moved between different models and/or different brands of hypervisors within or across different environments.

Solution

The virtual server is converted and/or exported into a common, supported format that is imported into the destination hypervisor.

Application

The OVF format is the most commonly used and supported format for virtual server exporting and importing.
Cross-Hypervisor Workload Mobility: Virtual Server A is exported to an OVF package at the origin hypervisor, and then imported from the OVF package to the destination hypervisor.

Virtual Server A is exported to an OVF package at the origin hypervisor, and then imported from the OVF package to the destination hypervisor.

Cross-Hypervisor Workload Mobility: Virtual Server A is exported into an OVF package at Cloud A, and then imported from the OVF package into Cloud B.

Virtual Server A is exported into an OVF package at Cloud A, and then imported from the OVF package into Cloud B.

Cross-Hypervisor Workload Mobility: The six steps involved in the application of the Cross-Hypervisor Workload Mobility pattern.

The six steps involved in the application of the Cross-Hypervisor Workload Mobility pattern.