VMs can be resized (memory & CPU) if they are not running
|Assignee:||Ruben S. Montero||% Done:|
|Target version:||Release 4.0|
- VM is not allocated to any host (HOLD, PENDING, STOP, FAILED). This way a resume or resubmit action will use the new values.
- VM is allocated (POWEROFF). In this case additional checks for host capacity may be needed.
Note that changing the values in PENDING or POWEROFF may lead to the scheduler using the old values (VM capacity or host usage) if the change takes place during the scheduling phase.
Before changing any value quotas need to be checked.
feature #1772:Resize VM capacity (cpu, memory and vcpu) offline
Feature #1772: Fix bug in RM, update VM owner/group quotas, not the caller's quotas.
Also take into account that we can delete users/groups and have orphan VMs
Feature #1772: Resize capacity enforce is mandatory for everyone, except for oneadmin
Feature #1772: Additional sanity checks for new capacity.
Even if it was not updated, VCPU was inserted with value "0",
causing the next deployment to fail