-
Spike
-
Resolution: Unresolved
-
Blocker
-
None
-
False
-
None
-
False
-
-
-
-
ACM Console Sprint 265
-
None
Value Statement
This will help us to better understand the steps we need to take when building our ACM Virtualization experience.
This will be necessary for us to begin implementation during 2.13.
Definition of Done for Engineering Story Owner (Checklist)
- can we use existing YAML fetch/save techniques from ACM Search to connect to a managed cluster and properly fetch some UI to display it for the virtualMachine in ACM Search UI?
- can we use existing approaches elsewhere within ACM to connect to a managed cluster and properly fetch some UI to display it for the virtualMachine in ACM Search UI?
- can we reuse existing kubevirt component libs to render VM details locally at the hub?
- Can we reuse tree-view work, feedback we have from CNV team:
The tree will be build using labels on the VMs. If you have a VM specific view, you should be able to take the same code we'll implement in cluster and use it in ACM
- blocks
-
VIRTSTRAT-58 ACM Virtual Machine view provides multi select based on filters, sorting
- New
-
ACM-13255 define a new Virtual Machines entry on the left nav under Infrastructure
- Closed
- is depended on by
-
CNV-45822 VM grouping using a tree view
- Stakeholder Acceptance
-
VIRTSTRAT-53 ACM Virtual Machine view provides details card with links to the source CNV VM console
- New