Backlog #3735

Add maxMemory and vcpu current parameters to allow online resizing of cpu and memory of a VM

Added by Tim Verhoeven over 5 years ago. Updated almost 5 years ago.

Status:NewStart date:04/02/2015
Priority:SponsoredDue date:
Assignee:-% Done:

0%

Category:Drivers - VM
Target version:-

Description

With the current OpenNebula using the KVM driver when a VM is created online dynamic resizing is not possible. Because in the XML definition that is generated no provisions are present that would allow upward scaling.

For the CPU these settings would be needed:
vcpu
The content of this element defines the maximum number of virtual CPUs allocated for the guest OS, which must be between 1 and the maximum supported by the hypervisor.
current
The optional attribute current can be used to specify whether fewer than the maximum number of virtual CPUs should be enabled. Since 0.8.5

And for memory:
maxMemory
The run time maximum memory allocation of the guest. The initial memory specified by either the <memory> element or the NUMA cell size configuration can be increased by hot-plugging of memory to the limit specified by this element. The unit attribute behaves the same as for <memory>. The slots attribute specifies the number of slots available for adding memory to the guest. The bounds are hypervisor specific. Note that due to alignment of the memory chunks added via memory hotplug the full size allocation specified by this element may be impossible to achieve. Since 1.2.14 supported by the QEMU driver.

The maximum values I would just define in the KVM vmm driver settings file.

Enabling these would allow us to manually (e.g. using virsh commands) to scale a VM online. I'm going to create a second request to have the online scaling also enabled in OpenNebula itself.


Related issues

Related to Feature #3736: Allow of online resizing of a KVM based VM inside OpenNebula Closed 04/02/2015
Related to Backlog #2002: Adjust CPU ratio on running instances New 05/07/2013

History

#1 Updated by Ruben S. Montero over 5 years ago

  • Tracker changed from Feature to Backlog
  • Priority changed from Normal to High
  • Target version deleted (Release 4.14)

#2 Updated by Ruben S. Montero over 5 years ago

  • Related to Feature #3736: Allow of online resizing of a KVM based VM inside OpenNebula added

#3 Updated by Ruben S. Montero over 5 years ago

  • Tracker changed from Backlog to Feature
  • Status changed from Pending to New
  • Priority changed from High to Sponsored
  • Target version set to Release 4.14

#4 Updated by Carlos Martín over 5 years ago

  • Related to Backlog #2002: Adjust CPU ratio on running instances added

#5 Updated by Ruben S. Montero about 5 years ago

  • Tracker changed from Feature to Backlog
  • Target version changed from Release 4.14 to Release 5.0

#6 Updated by Ruben S. Montero almost 5 years ago

  • Target version deleted (Release 5.0)

Also available in: Atom PDF