Hi Simon, We'll probably start to work on this next week. The OpenNebula repository is organized as follow:
* Each feature or bug is developed in a separate in a separate branch. Development always happen in public branches. * Minor bugs could be directly applied to master * We name each branch after its issue number. In this case, you need to look for barnch feature-1224 (http://dev.opennebula.org/issues/1224). Your feedback on this will be more than welcome. Thanks again for your wonderful contributions :) Ruben On Fri, Feb 8, 2013 at 6:02 AM, Simon Boulet <[email protected]> wrote: > Hi Ruben > > Regarding the snapshots feature, is it possible to get a sneak peek at it? > Is the branch that feature is being developed public? > > I'm interested to hear how you are developing that feature, interaction > with the DS and VMM drivers, etc. I am planning on working on a similar > feature very soon. > > Simon > > > On Wed, Feb 6, 2013 at 5:18 AM, Ruben S. Montero <[email protected] > > wrote: > >> Hi Zeeshan >> >> Yes, one of the limitations of the current model ("save_as") is that a >> disk snapshot requires to shutdown the VM. We are currently working in >> snapshot capabilities for opennebula. The snapshoting functionality will be >> two-fold: >> >> 1. Disk snapshots. As the one described in your email. Disk consistency >> must be guaranteed by the user. (e.g. powering-off the VM, unmounting the >> disk...) >> >> 2. System snapshots. To offer the ability to revert the VM to a >> previously saved point. >> >> Cheers >> >> Ruben >> >> >> -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
