Feature #1772
VMs can be resized (memory & CPU) if they are not running
| Status: | Closed | Start date: | 02/20/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | - | |||
| Target version: | Release 4.0 | |||
| Resolution: | fixed | Pull request: |
Description
- 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.
Related issues
Associated revisions
feature #1772:Resize VM capacity (cpu, memory and vcpu) offline
Feature #1772: Minor edits
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: Save updated quotas to the DB
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
Feature #1772: Add vm resize method to Java OCA
Feature #1772: Change the one.vm.resize method to accept a template, instead of individual parameters
History
#1
Updated by Miloš Kozák over 8 years ago
I would like to add ability to resize HDD as well. Do you think is that possible? Somewhere here I found an issue for hdd resizing..
#2
Updated by Ruben S. Montero over 8 years ago
Yes there is a separate issue for image re-sizing...
#3
Updated by Ruben S. Montero over 8 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed
#4
Updated by Carlos Martín over 6 years ago
- Related to Feature #3395: VM capacity resize for running VMs added