Quoting Ruben S. Montero (rsmont...@opennebula.org): > Hi > > These two are on our radar and probably scheduled for the next release. I > totally agree that we need to simplify the provision process even more. > > About feature 1. > > We have two issues: > > [1] Clone a running VM. http://dev.opennebula.org/issues/2637 > [2] Clone a template . http://dev.opennebula.org/issues/2051 > > Last one includes images (pretty much the procedure outlined by Anandharaj > under "New VM request") and I think this will cover exactly your request. > > About feature 2. > > We want to add the ability to update any part of a template for VM, most of > it can be done if the VM is running (eg. attach a new disk or nic). Others > like memory can be resized when the VM is powered off. You would not need > to update and recreate the template. > > [3] http://dev.opennebula.org/issues/2065
It would be nice if some actions could be "suspended" until the desired state has been reached. This would give you the possibility to perform for example resize actions (change (v)CPU, RAM, etc.) and have them be applied later, after the VM changes state: running -> poweroff -> running. Similar to the "Some changes may require a guest shutdown to take effect." message of "virt-manager". You can then schedule a power cycle to have the VM resized when convenient (midnight for example). Sure you could script this as (one)admin but for an end user this is more convenient. Gr. Stefan -- | BIT BV http://www.bit.nl/ Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org