1. Proposed title of this feature request

OpenShift VIrtualization storage migration

2. What is the nature and description of the request?

One of the current capability gaps between OpenShift Virtualization and RHV/VMware is an inability to migrate virtual machines in an "Hot" automated fashion between backend storage providers (e.g. hardware storage arrays from two different vendors).

As Virtual Machines are long lived instances that often cannot be taken offline without affecting the service they support, it is desireable to be able to perform platform operations without having to taken them offline.  OpenShift Virtualization currently supports migration of VMs between platform hosts, thus providing a mechanism to refresh/replace server hardware - but, currently if a customer wants to migrate a VM between backend storage providers, they must perform a manual cold migration of the VM by likes of data volume cloning.

3. Why does the customer need this? (List the business requirements here)

When a customer refreshes their storage, without an automated way of performing the migration service outages must be scheduled, plus there is a significant amount of labour to perform the work on each of the running instances. Compared with competing technologies this adds an amount of effort to day-2-day lifecycle management of the end-2-end stack.

4. List any affected packages or components.

OpenShift Virtualization