Hi Pentium100, What I can suggest to simplify VM deployment by developing a so called "golden image" and "golden template" in advanced. From there, you just make use of context and cloning features to ease your deployment.
Just my 20cent. Best regards, .fahmie From: [email protected] [mailto:[email protected]] On Behalf Of Pentium100 Sent: Wednesday, September 04, 2013 7:31 PM To: [email protected] Subject: [one-users] Simplified VM creation? Hello, While trying out OpenNebula, I noticed that the VM creation process is quite inconvenient if I want different VMs (as opposed to scaleout situation). 1. Create the image (upload a new one or copy some other image), set it as persistent (I don't want the VM to disappear if I shut it down). 2. Create a template that uses the image. 3. Finally create a VM from the template. There will only be one VM using that template (because I don't really need two identical VMs). To create 10 virtual servers (all the same "hardware" but different images) I need to repeat steps 1-3 ten times. It would be nice, if there was a way to simplify this. I can think of 3 ways to do it: 1. Skip the creation of a template. Create an image then create a VM based on that image. 2. Do not define an image while creating a template. Assign the image when creating the VM. 3. Have some "template" image that gets copied when a VM is created. The copy should be persistent. Is there a way to do it? Non-persistent images behave almost like option 3, but accidentally shutting down a VM would mean data loss. We have quite a few VMs, but they all are used as real servers would be - all have different data (no scaleout) and none can be deleted easily.
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
