<div dir="ltr">Hi,<div class="gmail_extra"><br><br><div class="gmail_quote">On 4 September 2013 13:30, Pentium100 <span dir="ltr"><<a href="mailto:pentium100@gmail.com" target="_blank">pentium100@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hello,<br><br>
</div>While trying out OpenNebula, I noticed that the VM creation process is quite inconvenient if I want different VMs (as opposed to scaleout situation).<br><br>
</div>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).<br></div>2. Create a template that uses the image.<br></div>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).<br>
<br></div><div>To create 10 virtual servers (all the same "hardware" but different images) I need to repeat steps 1-3 ten times.<br></div><div><br></div>It would be nice, if there was a way to simplify this. I can think of 3 ways to do it:<br>
<br></div><div>1. Skip the creation of a template. Create an image then create a VM based on that image.<br></div><div>2. Do not define an image while creating a template. Assign the image when creating the VM.<br></div>
<div>
3. Have some "template" image that gets copied when a VM is created. The copy should be persistent.<br><br></div><div>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.<br>
</div><div><br></div><div>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.<br clear="all"></div></div></blockquote><div><br></div>
<div>In OpenNebula 4.2 we included a new Sunstone cloud view [1] that fits in your use case. You create base templates and create a set of images. Then a user just have to select a template and an image, both are merged and a new vm is created. </div>
<div><br></div><div>You can also use this functionality in the default Sunstone view, but you will have to enable it. If this the case just tell and will show you how.</div><div><br></div><div>Concerning the persistence of the images, you have 2 options</div>
<div> a) Persistent image: The information will be saved after a shutdown action, but you can only use it in one vm</div><div> b) Non persistent image: The information will be lost after a shutdown, but you can use other actions that will not finalized the instance. For example you can use the undeploy action [2] , it's like a shutdown but the instance id, ip, disks.. are kept. You can deploy the vm again using the resume action</div>
<div><br></div><div> Hope this helps</div><div><br></div><div>[1] <a href="http://opennebula.org/documentation:rel4.2:cloud_view">http://opennebula.org/documentation:rel4.2:cloud_view</a></div><div>[2] <a href="http://opennebula.org/documentation:rel4.2:vm_guide_2#pausing_vm_instances">http://opennebula.org/documentation:rel4.2:vm_guide_2#pausing_vm_instances</a></div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><br></div>-- <br>
<div dir="ltr">
<div>Join us at <a href="http://opennebulaconf.com/" target="_blank">OpenNebulaConf2013</a> in Berlin, 24-26 September, 2013<br></div><div>--</div>Daniel Molina<br>Project Engineer<br>OpenNebula - The Open Source Solution for Data Center Virtualization<br>
<a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a> | @OpenNebula</div>
<br>
</div></div></blockquote></div></div></div>