Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-21943

TP: VM disaster recovery in ODF Metro-DR for GitOps-based VMs

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • CNV v4.15.0
    • None
    • CNV Storage
    • cnv-vm-metro-dr-odf-gitops-tp
      • KCS article describing limitations of support
      • VMs defined as ACM apps and according to limitations of KCS article can failover and relocate
      • Manual testing
      • no-ux
    • Green
    • To Do
    • CNV-22072 - VM Disaster Recovery with OpenShift Data Foundation
    • CNV-22072VM Disaster Recovery with OpenShift Data Foundation
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Hide

      2024-02-12:   Automation tasks are in GA EPIC.

      alitke@redhat.com rh_pelauter@redhat.com For [In Progress]CNV-35100: Fix use of DataVolumes with Metro DR - The card is in the progress, not done yet.  As we talked on last Tue. Scrum of Scrum cal...

      Show
      2024-02-12:   Automation tasks are in GA EPIC. alitke@redhat.com rh_pelauter@redhat.com For [In Progress] CNV-35100: Fix use of DataVolumes with Metro DR - The card is in the progress, not done yet.  As we talked on last Tue. Scrum of Scrum cal...

      Goal

      To protect VM workload with a very low Recovery Time Objective (very small RTO) and Recovery Point Objective (RPO=0). This is required for standard IT workloads, as well as high performance databases. This epic is focused on VMs using storage deployed on OpenShift Data Foundation (ODF)

      User Stories

      • As a VM workload administrator/owner, I want to protect a VM based application so I can recover it at another site, with no data loss, and minimal recovery time.
        • Basic VM, one disk, no application workload required.
        • Windows and Linux
      • As a database administrator/owner, I want to protect a my database based application so I can recover it at another site, with no data loss, and minimal recovery time.
        • Basic VM with database workload
          • HammerDB or something similar workload generator.
        • Windows and Linux
        • Success criteria
          • VM restart on DR site
          • Database recovers
          • Workload continues from the last committed transaction before the failure.

      Non-Requirements

      • Regional (async) replication
      • Performance and scale

      Notes

      • This integration is to be considered tech preview until automated testing is enabled

      Done Checklist

      Who What Reference
      DEV Upstream roadmap issue (or individual upstream PRs) <link to GitHub Issue>
      DEV Upstream documentation merged <link to meaningful PR>
      DEV gap doc updated <name sheet and cell>
      DEV Upgrade consideration <link to upgrade-related test or design doc>
      DEV CEE/PX summary presentation label epic with cee-training and add a <link to your support-facing preso>
      QE Test plans in Polarion <link or reference to Polarion>
      QE Automated tests merged <link or reference to automated tests>
      DOC Downstream documentation merged <link to meaningful PR>

            alitke@redhat.com Adam Litke
            dkenigsb@redhat.com Dan Kenigsberg
            Kevin Alon Goldblatt Kevin Alon Goldblatt
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: