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

• Create a user experience within the ACM console for a user to configure a hub backup and restore
• We need
  • a UI design for the scenarios covered below, then based on that
  • implement and deliver these with the product

Why is this important?

• The hub cluster is the focal point of management for a fleet of clusters, in the event of a disaster, we need an easy solution for the user to migrate a hub to a new cluster
• A user experience can help walk a user through
  • how to configure the hub DR
  • how to start a backup schedule on the active hub
  • how to restore the hub backup on a new hub
  • how to view current backup status ( backup/restore errors errors, pause/start schedule , current backup )

Scenarios

We are documenting the DR active-passive configuration here and show the steps required to configure and move sides in a DR setup

Tasks we should review for possible UI support:

1. Configure the initial backup storage connection :

• 1.1 Create the storage secret
• 1.2 Create the DPA oadp resource used to make the connection to the storage
• 1.3 Easy way to get to the list of Velero backups or restores, from a common UI ( we now use the OADP operator generic UI )
  https://github.com/stolostron/blog-drafts/blob/a78c41f351fb06c8a8447675907e7295231c2912/hub-backup/acm-backup.md#setting-up-the-storage-location

2. View the backup Policy status and view any alerts; (create alerts)
https://github.com/stolostron/cluster-backup-operator#backup-validation-using-a-policy

3. create a BackupSchedule (primary hub) or Restore resource (passive) ; we use now the generic CRD UI
The user should be able to view the backup or restore status and make updates, from one place( UI )

Acceptance Criteria

UI design and implementation provided with the product

Dependencies (internal and external)

1. Design UX
2. Console UI work
3. Business Continuity component may need to implement 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)