Uploaded image for project: 'Virtualization Strategy'
  1. Virtualization Strategy
  2. VIRTSTRAT-56

ACM Business Continuity: add capabilities for Virtual machines

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Hide

      at the moment we investigate how we can provide value with RHACM regarding backup restore.
      we plan this by creating some policies using policy templating, doing some advanced checks if backups can be done..
      atm we do not plan any backend code

      Show
      at the moment we investigate how we can provide value with RHACM regarding backup restore. we plan this by creating some policies using policy templating, doing some advanced checks if backups can be done.. atm we do not plan any backend code

      Feature Overview

      ...

      Goals

      Investigate with BU to determine if we can add value when it comes to utilities for Business Continuity for Virtual Machines (i.e. Virtual machines that may be running on managed clusters).

       

      Possible capabilities:

      • Virtual Machine migration (underlying PVCs plus perhaps vm cr resources) between clusters
      • Virtual Machine backup and restore on other clusters

       

      Requirements

      This Section: A list of specific needs or objectives that a Feature must
      deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
      If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
      it does not shift the feature.

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a
      requirement for ALL features.      		 YES
      Release Technical Enablement Provide necessary release enablement details
      and documents.      		 YES

      (Optional) Use Cases

      This Section:

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

      Questions to answer

      • ...

      Out of Scope

      • …

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting
      need to know? What context can be provided to frame this feature?

      Assumptions

      • ...

      Customer Considerations

      • ...

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this
        product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have a doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content
        Strategy.
      • What concepts do customers need to understand to be successful in
        [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical
        Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or
        Release Note)?

              vbirsan@redhat.com Valentina Birsan
              rhn-support-cstark Christian Stark
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: