Feature Overview

Remove the need for a dedicated PVC for each VM for VM state by transitioning to a shared storage mechanism for this state across VMs. 

Goals
The VMState PVC was originally introduced to provide persistent storage for items like VM's TPM device state, changed block tracking and migration state synchronization. This is currently a 1:1 mapping to each VM. Minimum size of PVCs in cloud vendors can be as high as 50 G.  Need to move away from a dedicated PVC per VM design to store the state to a shared mechanism to reduce the amount of overhead per VM

• All customers utilizing cloud, incremental backup or live migration 
• Reduces the amount of overhead and removes scalability issues for environments with a large number of VMs

Requirements

(Optional) Use Cases

How will the user interact with this feature? 

It should be transparent to the end user as this is internal information for the VM 

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

• <your text here>

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.
No UX seemingly required based on the mention of 'It should be transparent to the end user as this is internal information for the VM' in the Use Cases above.