Description
Changing the MEMORY_RESIZE_MODE to an existing VM only has the libvirt/KVM limitation of the VM being POWEROFF/undefined. Once the VM instance exists in OpenNebula, it is not possible to change the resize mode with an API Call, like one.vm.update because the resize mode lives on the VM.TEMPLATE section instead of the VM.USER_TEMPLATE section.
This results in the need to undeploy the VM which might not be feasible or hack the VM instance template with onedb update-body which is a risky alternative.
Use case
Allow to change the memory resize mode of existing VM instances without hacky workarounds.
Interface Changes
Extend the one.vm.resize call to handle also the MEMORY_RESIZE_MODE
Extend the onevm resize command to use the extension above
Description Changing the MEMORY_RESIZE_MODE to an existing VM only has the libvirt/KVM limitation of the VM being POWEROFF/undefined. Once the VM instance exists in OpenNebula, it is not possible to change the resize mode with an API Call, like
one.vm.updatebecause the resize mode lives on the VM.TEMPLATE section instead of the VM.USER_TEMPLATE section.This results in the need to undeploy the VM which might not be feasible or hack the VM instance template with
onedb update-bodywhich is a risky alternative.Use case Allow to change the memory resize mode of existing VM instances without hacky workarounds.
Interface Changes
one.vm.resizecall to handle also the MEMORY_RESIZE_MODEonevm resizecommand to use the extension aboveProgress Status