Feature Overview

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Many virtualization customers are running large environments with multiple clusters. If the customer is using ACM, the OpenShift Virtualization UI need to be able work with the ACM data and provide a way to manage all virtualization related tasks on all managed clusters from a single place

Goals
Provide high-level goal statement, providing user context and expected user outcome(s) for this Initiative

• Customers that run multiple clusters and have ACM can manage all the virtualization tasks in a single pane of glass without the need to connect to each cluster. 
• In the current state, most virtualization actions requires the user to know on which cluster the VM is running and log in to that cluster to manage it. This is also true for new VM creation, InstanceType management and more. With this feature, all those operation would be enabled in the cluster that is running ACM

Requirements

(Optional) Use Cases

How will the user interact with this feature? 
Which users will use this and when will they use it?

• Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>
Questions to answer...

Out of Scope

1. High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>
**

Background, and strategic fit

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Assumptions

• ACM search engine can provide us all the data that is needed
• To avoid performance issues, pagination is done in one of the layers that handle the data
• All required VM attributes are indexed by ACM search
• To provide good UX, we need ACM to be able to refresh only the data that is changed as the change occur, i.e. if we display multiple VMs and one of the VMs is stopped by another user, the new status of the VM is streamed to the UI for this specific VM, without the need to refresh all information in the page 

Customer Considerations

• Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

User Experience Considerations

Provide information that needs to be considered and planned so that the user experience will meet customer needs. These could include impacts to the UI or other areas of the user experience, as well as user research needs. Please add the 'UXD' component to this JIRA if there are User Experience considerations. Initial completion during Refinement status.

There are many UX implications to this feature, as we should determine how users are expecting to interact with many VMs and how best to support those interactions.