Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-26602

SiteConfig Operator backup and restore

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • ACM 2.16.0
    • ACM 2.16.0
    • SiteConfig Operator
    • None
    • Ensure SiteConfig Operator is fully DR enabled
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • eng-lead, devel-ack
    • Not Selected
    • In Progress
    • 50% To Do, 25% In Progress, 25% Done

      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

      Ensure that all the resources associated with the SiteConfig Operator can be properly backed up and restored using ACM's hub disaster recovery mechanism.

      Why is this important?

      Users expect all components of ACM to be compatible with the built-in backup and restore solution. SiteConfig Operator should be usable and the resources relating to previously installed clusters should retain data about the install after a restore.

      Scenarios

      ...

      Acceptance Criteria

      Currently the following resources are explicitly labeled for backup and restore:

      ConfigMaps:

      1. User-provided install template ConfigMaps 

       

      This leaves at least the extra-manifest ConfigMaps, pull secret and BMC credentials that need to be handled. Additionally, the BareMetalHost and the ClusterInstance status also need to be handled. 

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      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)

              deslimi@redhat.com Dariush Eslimi
              sakhoury@redhat.com Sharat Akhoury
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: