Feature Overview
To non-disruptively move a VM workload from one OpenShift Cluster to another OpenShift cluster.

Goals
Provide high-level goal statement, providing user context and expected user outcome(s) for this Initiative

• Who benefits from this feature, and how?
• What is the difference between today’s current state and a world with this feature?

Requirements

(Optional) Use Cases

• workload balancing to accommodate seasonal peaks.
  • As a cluster admin, I want to move VM workloads to other clusters to free capacity
• hardware refresh
  • As a cluster admin, I want to migrate VM workloads from one cluster to another cluster on different vendor hardware.

Questions to answer...
How will the user interact with this feature? Both in web console and API
Which users will use this and when will they use it? Cluster admin

Out of Scope

1. Configuration of the storage and network of the target cluster is a separate workflow.
2. Any storage specific optimizations like ODF application mobility
3. VMs with directly attached LUNs

Background, and strategic fit
This is a common capability on other virtualization platforms, which move both the compture and storage from one cluster to another.

Assumptions

• The OpenShift and CNV versions are of the same minor release (i.e. 4.16.z)
• The appropriate networks and storage is already configure in the target cluster
• Leverage existing mechanisms like live migration, and storage live migration.
• Cluster admin has appropriate RBAC privs to manage VMs on both clusters.

Customer Considerations

• VMs deployed on any bare metal OpenShift clusters, including bare metal IPI, HCP, and cloud providers

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this product feature? Cluster admin worklflow, and requirements.