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
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
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
After reading the ON docs and explanation from panoramisk I understand
the behaviour of persistent vs non-persistent image. But I do not get
idea behind this. It seems to be opposite to ON simplicity.
We had a following situation:
* the machine was running with non-persistent image
W dniu 2014-07-16 19:31, Aradyel napisał(a):
Hello,
We would like to create a few templates with persistent images so they
can be shared with a group of users, so then users can provision new
VM's, each having its own VM with persistent image. The persistent
image
is bacause we want that
Hello,
We would like to create a few templates with persistent images so they
can be shared with a group of users, so then users can provision new
VM's, each having its own VM with persistent image. The persistent image
is bacause we want that VM's be users personal VM's (aka desktops).
But if
Hello,
We would like to create a few templates with persistent images so they
can be shared with a group of users, so then users can provision new
VM's, each having its own VM with persistent image. The persistent image
is bacause we want that VM's be users personal VM's (aka desktops).
But
