[one-users] Version 4.0 requests

[Simon Boulet]

Hi André,

On Wed, Dec 5, 2012 at 10:53 AM, André Monteiro <andre.monteir at gmail.com>wrote:

> Secondly, some of the functionalities that libvirt has and virt-manager
> uses, like increasing/decreasing RAM (after a shutdown) or CPU.
>

In OpenNebula you would need to stop the VM and submit a new deployment
with the updated RAM / CPU template attributes, of course preserving the
same DISK image (persistent image). It's quite common on other Cloud
platforms too, for example EC2. One benefit is to allow the scheduler to
rebalance resources on your Cloud according to the new RAM /
CPU resources the VM needs.

However, one problem with this (at least, in my use case), is the IP
address of the VM will most likely change (OpenNebula will pick a new,
unused, IP address in the VNET). I don't think there is a way in the
current version of OpenNebula to preserve IP addresses between resubmission.



> Also there is one operation that I often use, "Force off" when a VM
> freezes/blocks and ACPI doesn't work.
>
>

I think that could be implemented in the VMM driver. The driver could wait
ex. 60 seconds for the VM to gracefully shutdown, and if the VM hasn't
stop, issue a force shutdown / destroy. I don't think "Force off" should
be implemented as a separate action in OpenNebula.

Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20121205/842eca91/attachment-0002.htm>