[one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6

[Ricardo Duarte]

Hi there,
One feature I would like to see would be a "recycle bin".Instead of deleting instances and their disks immediately after they terminate you could delay the actual operation to a different time, and allow the user to recover the instance.
Another feature would be what I call "instantiate to persistent".User would create a template based on a pre-existing image, with "persistent=yes". Opennebula would automatically clone the image disk and create the instance from it. I know currently it is possible to do it manually, by first cloning the image and then create a new template with that image, but that is not user friendly enough for me.
Regards,Ricardo Duarte

> From: cvazquez at c12g.com
> Date: Thu, 9 Jan 2014 17:44:00 +0100
> To: users at lists.opennebula.org
> Subject: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
> 
> Dear users,
> 
> Having released OpenNebula 4.4 Retina and closed its release cycle, it
> is time to open a new one for the next release.
> 
> We have identified the issues [1] (bugs + features) we deem important
> for the release, and we have including in that list the features that
> didn't make it in OpenNebula 4.4 in the end.
> 
> As discussed with the OpenNebula Conf attendees (see? you need to come
> next year ;) ), we want to give our users the chance to shape the
> roadmap for the upcoming OpenNebula 4.6. We invite you to submit your
> comments on the roadmap via email (ideally within this thread, but
> feel free to open a new one if you think it is necessary to discuss
> any particular topic). This valuable input will be used to shape the
> short-term roadmap with the features that will be part of the release
> cycle.
> 
> The ideal process of the discussion would be for any person interested
> in discussing a feature request to search first if there is already a
> similar one in the OpenNebula development portal [2]. If no similar
> request is found, please open one describing as best as you can what
> feature you have in mind, and let us know in this mailing list so we
> know there is interest and we need to shape the roadmap to accommodate
> it. If you find a similar request, read through the proposed approach
> and let us know if you agree on it. If not, please put a comment in
> the feature request explaining your concern, and let us know as well
> here.
> 
> We plan to close this discussion next Thursday, 16th, EOB.
> 
> It goes without saying that the more interest we see on a feature,
> more priority it will have in the short-term roadmap.
> 
> Tino, on behalf of the OpenNebula Team
> 
> [1] http://dev.opennebula.org/projects/opennebula/issues?query_id=45
> [2] http://dev.opennebula.org/
> [3] http://opennebula.org/community/contribute/
> 
> --
> OpenNebula - Flexible Enterprise Cloud Made Simple
> 
> --
> Constantino Vázquez Blanco, PhD, MSc
> Senior Infrastructure Architect at C12G Labs
> www.c12g.com | @C12G | es.linkedin.com/in/tinova
> 
> --
> Confidentiality Warning: The information contained in this e-mail and
> any accompanying documents, unless otherwise expressly indicated, is
> confidential and privileged, and is intended solely for the person
> and/or entity to whom it is addressed (i.e. those identified in the
> "To" and "cc" box). They are the property of C12G Labs S.L..
> Unauthorized distribution, review, use, disclosure, or copying of this
> communication, or any part thereof, is strictly prohibited and may be
> unlawful. If you have received this e-mail in error, please notify us
> immediately by e-mail at abuse at c12g.com and delete the e-mail and
> attachments and any copy from your system. C12G thanks you for your
> cooperation.
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140113/8974b175/attachment-0002.htm>