hi <div><br></div><div>First let me clarify that the design of OpenNebula does not make any assumption on the workload that the VMs will run, and it is totally agnostic to it. I dare to say that OpenNebula is as well suited for HPC as for enterprise or service provider clouds if not even more...</div>
<div><br></div><div>Individually persistence as described in your email is totally supported, power off / stop / reboot / power on / suspend / resume operations will move disk images (along with the VM state) through your clusters and hosts, so individually preserving its state. (This was in place since 3.2, am I missing something here?)</div>
<div><br></div><div>What happen if one of the users make a change to the VM state (e.g. installs and configure new software) and is so important that she wants to keep it, to persist beyond the VM life cycle, to even share it with others. In this case you can transform an individually persistent disk image to a globally persistent one. </div>
<div><br></div><div>Think of the EBS persistance model of Amazon EC2</div><div><br></div><div><a href="http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/concepts-spot-instances-applications-ebs.html">http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/concepts-spot-instances-applications-ebs.html</a></div>
<div><br></div><div>Best</div><div><br></div><div>Ruben</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Oct 16, 2012 at 9:33 PM, deeepdish <span dir="ltr"><<a href="mailto:deeepdish@gmail.com" target="_blank">deeepdish@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">HI Everyone,<br>
<br>
Can someone please explain the concept, requirement and rationale behind the SAVEAS operation on a virtual machine instance. I've evaluated ONE 3.2 and a bit of 3.4 so my information may be slightly dated. ONE seems to be a very robust environment, highly flexible and customizable and simple to deploy and operate. However I'm struggling to figure out why would one ever need to "SAVE" an instance when deploying it. Given a cloud application, either enterprise or service provider, I would imagine that any customer provisioned instance would be persistent (I have to be careful how I use persistent -- I mean, once it's deployed, it can be stopped, rebooted, started, etc with out loosing any data -- i.e. without have to have the template redeployed). Granted, there may be a requirement for this process flow. Is there a way or feature in the works to alter this behavior?<br>
<br>
My requirement is simple:<br>
<br>
- Create standard templates;<br>
- Customers login, pick the templates they like and deploy them.<br>
- Once deployed, the instances are individually persistent (meaning they are around as long as the customer does not destroy them).<br>
- The customer can power off / stop / reboot / power on / suspend / resume their instance as they wish without impacting or affecting any changes made to the instance since deployment (i.e. individually persistent).<br>
<br>
Think VMware, Cloudstack.<br>
<br>
ONE seems like a good platform, but the above has always puzzled me. It looks like a great platform for high performance computing, perhaps not for an enterprise or service provider cloud. Correct me if I'm wrong.<br>
<br>
<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>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Ruben S. Montero, PhD<br>Project co-Lead and Chief Architect<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:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a> | @OpenNebula<br>
</div>