Hi Carlos, Ruben,
Thanks for the feedback!
That's not exactly what I was thinking.
Although I can see the advantage of the call taking a template ex. for
someone that want resize to handle more than CPU, VCPU and MEMORY, the
resize operation could be extended to more attributes later without
cha
Hi Simon,
We decided to implement your suggestion. The CLI command stays the same,
but internally the call is done with a template and the restricted
attributes are enforced.
It makes perfect sense and is consistent with the attach methods, that also
require a template.
Thanks for your feedback,
Hi Simon
I noticed the one.vm.resize call in the upcoming 4.0. Can you provide a
> little more information about how this is going to work?
>
The process is described here:
http://opennebula.org/documentation:rel4.0:vm_guide_2#resizing_a_vm
let us know if you miss something...
Currently I am r
Hi,
I noticed the one.vm.resize call in the upcoming 4.0. Can you provide a
little more information about how this is going to work?
Currently I am relying on the VM ID to account my clients for each of their
VM usages (according to the CPU, MEMORY, VCPU). Those attributes are
checked only the f
