Epic Goal

based on input from CNV

• ready API GA
• storage-live-migration API GA

We want to offer a GA feature for Live-Migration between clusters (ACM ManagedClusters)

Why is this important?

This allows Virtual Machines to be moved between clusters and between namespaces on a given cluster. (cluster refers to ACM ManagedCluster). This is a basic Virtual Machine capability that is just expected.

Scenarios

1. Move a Virtual Machine from one namespace to another on the same ManagedCluster
2. Move a Virtual Machine from one ManagedCluster to another ManagedCluster

Acceptance Criteria

Both scenarios work from the CLI/API

Dependencies (internal and external)

1. CNV work is in place to support the live migration

Previous Work (Optional):

1. cross node migration within an existing ManagedCluster (does not change the namespace, just changes the underlying node in the same ManagedCluster, should be noted you can NOT pick the target node)
2. Proposal to use MTV

Open questions:

1. When
2. How reliable
3. How quick (down time)

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)