Hi, This is in our radar and something we'd like to prioritize. The relevant issues in our roadmap are:
http://dev.opennebula.org/issues/2637 http://dev.opennebula.org/issues/2051 Feel free to add comment to them if they do not capture completely your use case. The above feature (for single disk VMs) is implemented through the cloud view. You can save a VM (non-persistent) as a template and instantiate a new (different) VM from it. Also the above are now somehow available but with a few clicks in between (i.e. clone image, clone associated template, update cloned template to point to the image, instantiate it...) The above issues will provide it as a single operation, in the meantime it could be easily scripted. Cheers On Wed Feb 04 2015 at 12:11:24 PM David Komanek <koma...@natur.cuni.cz> wrote: > Hi, > > I am also completely frustrated by this. In my opinion, templates should > allow us to do simple "mass instantiation" even with persistent disks: > create VM => save it as a template => instantiate i.e. 10 new VMs at > once, each with its own copy of template-based persistent disk > > Another highly appreciated feature of templates would be the "linked" > state: to propagate future changes in the template to the VMs > instantiated from it, at least for some attributes. > > Is there any chance some of those features get implemented in the near > future ? Or has it already been done and I am just missing the whole > concept by misunderstandning the documentation ? If so, is there any > direct URL to a step-by-step guide, how to achieve this ? > > Thanks in advance, > > David > > > > Hi, > > > > I'm running against this same issue as described here. > > Regardless of how I try to look at it, non-persistent (and thus, > volatile > > images) are kinda annoying. > > > > I understand how to create a template, install an OS using that template > > (CDROM and persistent OS images linked) and then after installation > marking > > the OS image as non persistent which then can be used to deploy multiple > > VM's with that image as "base". > > > > But what I would expect (in experience with other virtualisation > > technologies) is the creation of a clone image in the *Image datastore*, > > which would be linked to the new VM. But instead I see that these VM's > use > > the non persistent image, which is physically stored in the *System > > datastore* and at that point it's still a volatile image. Also, when > > shutting down that VM it simple deletes it all together (same as > > any volatile image, I really don't see the point of it). > > > > So basically, de deployment works, but what I want is the deployment of > > "persistent" images (in the image datastore) which are based on a "non > > persistent" base image. Is this at all possible? > > > > So in any way, my questions are pretty much the same as Pawel. > > > > Based on this topic I don't see any answers, so could someone please help > > us understand how this is all supposed to work and what the basic idea is > > behind it all? > > > > Thanks in advance!!! > > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
