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

Implement virtual machine actions for backing up VMs with OADP in RHACM

Why is this important?

OADP supports backing up / restoring VMs and ACM ( starting with version 2.13 ) provides a set of policies out of the box that could be used to backup or restore VMs on hub or managed clusters.

Documented here https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/virtualization/acm-virt#backup-config-policy-virt

We want to create a user experience where these functionality can be accessed directly from the VNC console. 

We want to integrate this with the existing functions ( snapshot, clone, start VM, etc )

Scenarios

A user wants to backup the entire VM which is running on the hub or managed cluster. 

A global action would be available on the CNV console, on the hub, to configure the backup ( where to store the data, credentials, etc - all that is needed to setup OADP ).

Then the user can select what VMs to backup and on what schedule.

( For a restore scenario there should be a mechanism to point to the backup to restore )

Acceptance Criteria

UI design and implementation provided with the product

Dependencies (internal and external)

1. Design UX
2. Virtualization Console UI work
3. Business Continuity component may need to implement VM policy changes in support of this design

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)