Feature Overview

...

In ACM 2.12 we have done nice improvements providing a new virtualization view in ACM, a video is attached you can review where we are.
Starting from here this feature is about to further improve this experience in the UI:

One way the feature could be implemented is to provide a link from the new Virtualization Tab to an individuals cluster Virtualization tab.
(This ticket is also directly related to the tree-view initiative.)

This should be considered as the most realistic approach to solve it:

_I think we should include the namespace/project column and the folder column (once available) since it would enable users to filter by them and then find VMs under each easily.
Btw do you have the column selector as we do in CNV? Users can add and remove columns according to their needs to make the table uncluttered._

Goals

Release goal:
Integrate OpenShift-Virt-Tree-View into RHACM
considering the results of ACM-14379: Investigate techniques to display VirtualMachine details in ACM

• …

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.

(Optional) Use Cases

VM lifecycle operations (available in CNV treeview once integrated into ACM 2.15)
Create
Start
Stop
Restart
Pause
Unpause
Launch VM VNC console
Delete

Snapshots:
Take snapshot
Restore from snapshot
Create VM from snapshot
Delete Protection
Clone
Copy SSH command
Migrate to a different Node
Migrate to a different cluster
VM Bulk operations

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