-
Epic
-
Resolution: Done
-
Major
-
None
-
cnv-instancetypes-hotplug
-
-
Green
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
Goal
Currently, VMs defined using instance types do not support the LiveUpdate VMRolloutStrategy feature. Any attempt to modify a running VM referencing an instance type with the LiveUpdate VMRolloutStrategy feature enabled will be rejected.
The goal of this epic is to extend the LiveUpdate VMRolloutStrategy feature to allow for the instance type or preference of a running VM to be modified and where possible have the resulting resource changes propagated down to the running VMI and guest.
For example, a running VM using the u1.medium (1vCPU (socket by default) and 1Gi RAM) common instance type could be updated to reference the u1.large (2vCPU (socket by default) and 4Gi RAM) common instance type.
This should result in an additional socket and RAM being plugged into the running VMI/Guest.
User Stories
- As a VM owner, I want to change the instance type and/or preference associated with my running VM and where possible have updates propagated to the running guest
Non-Requirements
- Additional LiveUpdate VMRolloutStrategy support for attributes of an instance type or preference not already supported in a vanilla VirtualMachine. For example, GPUs, Host devices, NUMA etc
- No UI/UX updates are required for this TP version of the epic
Notes
- blocks
-
CNV-33843 GA: LiveUpdate VM roll-out strategy support for instance types and preferences
- In Progress
- is blocked by
-
CNV-32072 GA: Memory Hotplug
- Closed
-
CNV-36354 Implement VMRolloutStrategy as a means of updating VMs
- Closed
- is documented by
-
CNV-39770 TP: Downstream documentation LiveUpdate VM roll-out strategy support for instance types
- Closed
- is related to
-
CNV-39963 Release notes: CPU hot plugging
- Closed
- relates to
-
CNV-21978 GA: Move instancetype API to GA
- Closed