Feature Overview

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

Customers would like to be able their VMs and associated objects (like disks etc.) for different reasons like operational flexibility, automation etc.. This feature is available with other virtualization solutions 

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

• Who benefits from this feature, and how? Customers uses this for various reasons like naming conventions that may change over time, automation,  
• What is the difference between today’s current state and a world with this feature? Today we cannot rename a VM. The only way to do it is to recreate the VM (manually or using snapshots) which require downtime.

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.

1. Operational flexibility: Customers often need to align VM names with naming conventions that may evolve over time (e.g., application, environment, or compliance-driven standards).
2. Automation and integration: In environments migrating large numbers of workloads (e.g., from VMware), customers need to adjust VM names programmatically as part of automation pipelines.
3. Compliance and audits: Regulated industries (e.g., healthcare, finance) may require VM names to follow strict naming conventions. Lack of a rename option complicates compliance audits and remediation.

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.

We had few requests about this capability. Some of them were about adding an alias (e.g. display name) to a VM and some were about a changing the VM name. The concern with alias is that when using an alias, the UI (name) will not reflect the VM name and may cause confusion when working with the CLI/API. We also need to evaluate customer expectations of renaming all associated resources (like disk / secrets / configmaps etc.) which may make this much more complex.

Before we decide if we should do it or not, we need to evaluate the risks that are associated with such a change

Assumptions

• Customers would like to be able to rename a VM while it's running
• This rename should update all associated resources (like disks, virt-launcher pod etc.).

Customer Considerations

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

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.
<your text here>