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

Virtual Machine actions from RHACM

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      2025-07-09:no significant updates this week...

      Show
      2025-07-09:no significant updates this week...
    • Red Hat Advanced Cluster Management for Kubernetes

      Feature Overview

      Virtual Machine administrators must be able to execute lifecycle actions from ACM.

      Goals

      This Section: Provide high-level goal statement, providing user context
      and expected user outcome(s) for this feature

      • Actions for virtual machines are enabled by default ACM-16146 
      • VM lifecycle operations
        • Create      (UXD needed), might not be needed here, is a different flow
        • Start        ( ACM 2.12)
        • Stop        ( ACM 2.12)
        • Restart    ( ACM 2.12)
        • Pause      ( ACM 2.12)
        • Unpause ( ACM 2.12)
        • Launch VM VNC console ( ACM 2.13) ACM-16138
        • Snapshots ( ACM 2.14) 
          • Take snapshot ACM-17416
          • Restore from snapshot ACM-18854 (ACM 2.14)
          • Delete Protection (ACM 2.14)
          • Create VM from snapshot ACM-18855 after ACM 2.14
        • Clone ( Clone you need to make a copy ( backup ) and then restore that) backup and restore should be exposed separately ACM-17419
        • Migrate to different Node ACM-17417
        • Copy SSH command
        • Move to a different cluster ACM-13311
        • Delete    ( ACM 2.12)
      • Bulk operations ACM-16039
      • Actions from the Global Hub context ACM-16296

      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)?

              rhn-support-cstark Christian Stark
              jpadilla@redhat.com Jorge Padilla
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: