OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

The CNV/MTV integration feature is an optional component that can be enabled on the MultiClusterHub instance to support multicluster virtualization scenarios. This integration automatically installs CNV and MTV on the hub cluster, so that users can take advantage of the OpenShift Virtualization Fleet Virtualization perspective, and sets up the prerequisites for cross-cluster migration of VMs. Enabling this component currently requires editing YAML. We want to provide a console solution for easily enabling this integration.

Why is this important?

We want to make configuration of a multicluster virtualization environment as easy as possible to reduce barriers to adoption.

Scenarios

1. A user can enable or disable the CNV/MTV integration feature from the console
2. Alerts implemented under https://issues.redhat.com/browse/ACM-22068 are updated to guide the user to the new UI for enablement of the integration
3. When the integration is enabled, the user can enable/disable automatic installation of CNV onto specific managed clusters via a cluster action.

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

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)