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

Progress

• February 18, 2025
  • We will close this spike story and start on a new set of spikes for more granular tracking.
    • ACM-17918
    • ACM-17914
    • ACM-17917
    • ACM-17919
  • We were able to demonstrate through prototyping that the key questions posed in this spike are possible.
  • Remaining issues we have identified are identified in this document.

• • • Fleet API compatibility (exploring a technical solution in ACM-17914)
    • Hub cluster compatibility
    • UX of where functionality lives
    • Packaging question of how UI is delivered
  • Initial discussions with CNV engineering focused on defining the interface between ACM and CNV; we will improve the design of the prototype via ACM-17918 and continue syncing with CNV on a weekly basis

• February 5, 2025
  • Investigation underway into retrieving usage metrics from the hub using multicluster observability
  • We are able to display the VM console preview and provide fully-functional standalone VNC and Serial consoles in ACM over the cluster proxy
    

• February 3, 2025
  • We are now able to patch a dev environment with builds of the prototype for demo purposes
  • As kubevirt-plugin is under active development, we had some work to rebase on current changes
  • VM details prototype now has some data being fetched over the cluster proxy (single fetch only; no live updates)
  • VM tree view prototype has custom columns when used in multicluster context; add Cluster column, remove columns for which ACM search does not currently collect data
• January 27, 2025: We have prototyped displaying parts of the VM details pages and tree view inside the ACM console, by loading them from the kubevirt-plugin console plugin. Minimal changes in kubevirt-plugin code allow us to override data functions. Currently working on loading cluster data for VM details via the cluster proxy and investigating sourcing usage data from metrics collected on the hub by multicluster observability. For the tree view, we have some data flowing into it from ACM search and are working on adding clusters as a higher level in the tree view hierarchy and as a new column in the table.