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

2014-01-29 Thread Shankhadeep Shome
Cool, very much appreciated :) On Wed, Jan 29, 2014 at 7:00 AM, Tino Vazquez wrote: > Hi Shankhadeep, > > We've evaluated the request and it looks like something that can make > it for 4.6. I've opened a ticket to keep track [1]. > > Regards, > > -Tino > > [1] http://dev.opennebula.org/issues/2

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

2014-01-29 Thread Tino Vazquez
Hi Shankhadeep, We've evaluated the request and it looks like something that can make it for 4.6. I've opened a ticket to keep track [1]. Regards, -Tino [1] http://dev.opennebula.org/issues/2690 -- OpenNebula - Flexible Enterprise Cloud Made Simple -- Constantino Vázquez Blanco, PhD, MSc Seni

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

2014-01-23 Thread Tino Vazquez
Hi Shankhadeep, We've already closed the roadmap for 4.6, but please consider open a feature request in dev.opennebula.org and we'll do our best to include it for the next release. Best regards, -Tino -- OpenNebula - Flexible Enterprise Cloud Made Simple -- Constantino Vázquez Blanco, PhD, MSc

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

2014-01-22 Thread Shankhadeep Shome
Could you guys consider pulling in the hyper-v libvirt tag support for sunstone that one of users contributed a patch for few weeks back? Anything that improves Windows guest performance on kvm is very much appreciated, at least by me On Tue, Jan 21, 2014 at 10:21 AM, Ruben S. Montero

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

2014-01-21 Thread Ruben S. Montero
Hi First, we'd like to thank you all the comments and feedback for OpenNebula 4.6. We really appreciate it :) Our goal for 4.6 is two-fold: improve federation module (aka ozones) and improve OpenNebula usability (based on OpenNebula user comments received during the last releases). It's been alwa

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

2014-01-17 Thread Karsten Nielsen
Hi, I would like to have support for docker.io that would be awesome. Thanks, - Karsten On 09/01/14 17:44, Tino Vazquez wrote: 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]

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

2014-01-17 Thread Stefan Kooman
Quoting Tino Vazquez (cvazq...@c12g.com): > Hi fellow OpenNebula users, > > First of all, thanks a lot for the feedback! > > We are going to take all this input and shape the roadmap to > accommodate as much features as we can for 4.6. We'll let you know in > this thread (individually and/or glob

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

2014-01-17 Thread Tino Vazquez
Hi fellow OpenNebula users, First of all, thanks a lot for the feedback! We are going to take all this input and shape the roadmap to accommodate as much features as we can for 4.6. We'll let you know in this thread (individually and/or globally) if we can make your feature for 4.6 or if we have

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

2014-01-16 Thread Stefan Kooman
Quoting Tino Vazquez (cvazq...@c12g.com): > 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. > The ideal process of the discussion would be for any person interested > in discussing a feature request to searc

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

2014-01-14 Thread Stefan Kooman
Quoting Ricardo Duarte (rjt...@hotmail.com): > 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

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

2014-01-13 Thread Ricardo Duarte
and then create a new template with that image, but that is not user friendly enough for me. Regards,Ricardo Duarte > From: cvazq...@c12g.com > Date: Thu, 9 Jan 2014 17:44:00 +0100 > To: users@lists.opennebula.org > Subject: [one-users] Closing OpenNebula 4.4 Cycle, Planning for

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

2014-01-12 Thread Daniel Dehennin
Tino Vazquez writes: [...] > 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. Hello, Thanks a lot for giving us the opportunity to participate on the roadmap pl

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

2014-01-09 Thread Nikita Balashov
Hi all, Feature #1727 "Patch for one.image.resize to resize image" is also useful for OpenVZ images as it also allows to specify image size on deploy. Regards, Nikita On 01/09/2014 11:45 PM, Tobias Brunner wrote: Hi all, Thanks a lot for letting the community participate on the roadmap plann

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

2014-01-09 Thread Kenneth
I agree with RBD format 2. And thanks a lot to the OpenNebula team for bringing the cloud infrastructure closer to end system administrators. I would specifically like to request to have the option of over-committing memory (ram) to VMs just like how you can set over commit in CPU. --- Th

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

2014-01-09 Thread Tobias Brunner
Hi all, Thanks a lot for letting the community participate on the roadmap planning! For me there are two features important, which are already described on the development portal: #2568 "Support for RBD Format 2 images" --- I have already tested the attac

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

2014-01-09 Thread Tino Vazquez
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 OpenNebu