<div dir="ltr">Hi Riccardo,<div class="gmail_extra"><br><br><div class="gmail_quote">On 7 August 2013 09:36, Riccardo Brunetti <span dir="ltr"><<a href="mailto:brunetti.riccardo@gmail.com" target="_blank">brunetti.riccardo@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"><br>
Thanks Steve and Olivier for your prompt reply.<br>
I will try to follow your suggestions, but I'm still missing a point:<br>
let's consider this use case (quite common I suppose in a cloud<br>
provisioning service).<br>
I have a user who wants 2 VMs, based on a given base image and template,<br>
and wants them persistent because he needs them to keep the<br>
modifications after a shutdown.<br>
The problem is that I can't have 2 instances of the same image if that<br>
image is marked persistent. On the other hand, if the image is not<br>
persistent, the user should instantiate the VMs, save them, mark the new<br>
ones persistent and re-deploy them. This is something that a, let's say,<br>
"non enough skilled" user can't do easily.<br>
What it seems to me is missing (or at least I can't find) is something<br>
like an atomic "clone-in-persistent-and-deploy" mechanism.<br></blockquote><div><br></div><div>There are available more actions to "shutdown" a VM that will keep the resources assigned to a given instance. You may find useful the following guide, "terminating vs pausing" [1]</div>
<div><br></div><div>You can configure the actions that will be available for a given user/group in Sunstone. For example, if you want to disable the shutdown action for your cloud users (/etc/one/sunstone-views/cloud.yaml):</div>
<div><div> vms-tab:</div><div> ...</div><div> actions:</div><div> ...</div><div> VM.poweroff: true</div><div> VM.poweroff_hard: true</div><div> VM.undeploy: true</div>
<div> VM.undeploy_hard: true</div><div> VM.shutdown: false</div><div> VM.shutdown_hard: false</div></div><div><br></div><div>Hope this helps</div><div><br></div><div>[1] <a href="http://opennebula.org/documentation:rel4.2:vm_guide_2#terminating_vm_instances">http://opennebula.org/documentation:rel4.2:vm_guide_2#terminating_vm_instances</a></div>
<div> </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">
<br>
Best Regards.<br>
<span class=""><font color="#888888">Riccardo<br>
</font></span><div class=""><div class="h5"><br>
On 08/06/2013 03:27 PM, Steven Timm wrote:<br>
> FermiCloud does something quite similar to what you are asking<br>
> for below, although we are currently using an earlier version<br>
> of OpenNebula.<br>
><br>
> The persistence of images and the persistence of IP addresses<br>
> are controlled independently in OpenNebula. Typically for<br>
> our fixed-ipVM's we do have a separate image for every<br>
> user and each one of those images is marked "persistent" in the VM<br>
> store. but we also have a standard image that anyone can use, with fixed<br>
> IP or with dynamic IP.. if the user then wants to make modifications<br>
> to their image and store their image, they can do that.<br>
><br>
> If you need more details, you can email me privately.<br>
><br>
> Steve Timm<br>
><br>
><br>
><br>
><br>
> On Tue, 6 Aug 2013, Riccardo Brunetti wrote:<br>
><br>
>> Dear OpenNebula users.<br>
>> We are setting up a IaaS service using opennebula 4.2, which should be<br>
>> used by our users to perform a self-provisioning of virtual machine.<br>
>> Basically, each user should choose one of the available VM templates and<br>
>> one of the available VM images and self-deploy a given number of VM for<br>
>> his personal use.<br>
>> It seems that this is really the use case of the Self-service Cloud<br>
>> described in:<br>
>><br>
>> <a href="http://opennebula.org/documentation:rel4.2:cloud_view" target="_blank">http://opennebula.org/documentation:rel4.2:cloud_view</a><br>
>><br>
>> but there is something that we are still missing.<br>
>> The point is that each user should be able to "buy" an instance, use it,<br>
>> modify it, switch it off and on and do whatever he wants preserving the<br>
>> changes.<br>
>> Moreover, each time the machine is instantiated it must get the same IP<br>
>> address. In other words, each instance should be persistent.<br>
>> From the above doc, it is not clear to us if this is actually the case.<br>
>> If the images are not defined persistent, the changes are lost and, on<br>
>> the other hand, we can't define them persistent since we want many users<br>
>> be able to use them.<br>
>> Moreover, it seems that it's possible to pin a given IP address only at<br>
>> the level of the template but, once again, the same template is supposed<br>
>> to be used by many customer.<br>
>><br>
>> The only possibility that we can see is to clone the same image for each<br>
>> user, making each clone persistent, and provide the same number of<br>
>> templates, but this is something that easily becomes unfeasible as soon<br>
>> as the number of users increases.<br>
>><br>
>> Anybody has ever tried to make such a service? Can you please give us<br>
>> some suggestions or show us what we are missing?<br>
>><br>
>> Best Regards.<br>
>> R. Brunetti<br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
>> <a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
>><br>
><br>
> ------------------------------------------------------------------<br>
> Steven C. Timm, Ph.D (630) 840-8525<br>
> <a href="mailto:timm@fnal.gov">timm@fnal.gov</a> <a href="http://home.fnal.gov/~timm/" target="_blank">http://home.fnal.gov/~timm/</a><br>
> Fermilab Scientific Computing Division, Scientific Computing Services<br>
> Quad.<br>
> Grid and Cloud Services Dept., Group leader of Grid and Cloud Services<br>
> Operations. Lead of FermiCloud Project.<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</div></div></blockquote></div><br><br clear="all"><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>
</div></div>