Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 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 ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On 23 January 2014 11:20, Tino Vazquez cvazq...@c12g.com wrote: 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 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 ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Thu, Jan 23, 2014 at 5:24 AM, Shankhadeep Shome shank15...@gmail.com wrote: 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 hyperv relaxed state='on'/ vapic state='on'/ spinlocks state='on' retries='4096'/ /hyperv On Tue, Jan 21, 2014 at 10:21 AM, Ruben S. Montero rsmont...@opennebula.org wrote: 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 always difficult to prioritize the new features considering the limited time-frame of a release, so we tried to balance the effort and number of features. The complete list of features is here [1]. About the specific requests in this thread. In 4.6, We are going for: - #2568 Support for RBD Format 2 images - #1727 Patch for one.image.resize to resize image - #1818 Support for IP reservations along with #2545 Decorrelate networks TYPE and IP management - #1696 Add the ability to select datastore for Clone operation as a previous step for #2417 Move images between datastores. #2417 requires preserving the ID, so let see if we can easily get both - #2453 Add hostname configuration to contexualization - #2048. Instantiate to persistent - #2648: ACL edit/view wizard - #2649: sunstone, occi, econe, novncserver ability to log to syslog server These issues have been moved to the backlog, with a high priority to consider them for 4.8, complete backlog [2]: - oneacct extended to the webinterface. This is issue #1607, in this release we are going for #1484 (output in csv format of accounting data) - over-committing memory (ram) to VMs just like how you can set over commit in CPU. This is issue #1328 - One feature I would like to see would be a recycle bin this has been merge with #2412 Ability to lock VM from accidental actions - #2560 Re-read oned.conf on reload - #2651 Implement mailbox to prevent vm from running twice. Again thanks for the feedback. Cheers PS: A more prosaic form of this mail has been published in the blog [3] [1] http://dev.opennebula.org/projects/opennebula/issues?query_id=45 [2] http://dev.opennebula.org/projects/opennebula/issues?query_id=46 [3] http://opennebula.org/blueprints-for-opennebula-4-6/ On Fri, Jan 17, 2014 at 8:41 PM, Karsten Nielsen kars...@unity3d.com wrote: Hi, I would like to have support for docker.io that would be
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
Cool, very much appreciated :) On Wed, Jan 29, 2014 at 7:00 AM, Tino Vazquez cvazq...@c12g.com 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/2690 -- 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 ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On 23 January 2014 11:20, Tino Vazquez cvazq...@c12g.com wrote: 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 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 ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Thu, Jan 23, 2014 at 5:24 AM, Shankhadeep Shome shank15...@gmail.com wrote: 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 hyperv relaxed state='on'/ vapic state='on'/ spinlocks state='on' retries='4096'/ /hyperv On Tue, Jan 21, 2014 at 10:21 AM, Ruben S. Montero rsmont...@opennebula.org wrote: 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 always difficult to prioritize the new features considering the limited time-frame of a release, so we tried to balance the effort and number of features. The complete list of features is here [1]. About the specific requests in this thread. In 4.6, We are going for: - #2568 Support for RBD Format 2 images - #1727 Patch for one.image.resize to resize image - #1818 Support for IP reservations along with #2545 Decorrelate networks TYPE and IP management - #1696 Add the ability to select datastore for Clone operation as a previous step for #2417 Move images between datastores. #2417 requires preserving the ID, so let see if we can easily get both - #2453 Add hostname configuration to contexualization - #2048. Instantiate to persistent - #2648: ACL edit/view wizard - #2649: sunstone, occi, econe, novncserver ability to log to syslog server These issues have been moved to the backlog, with a high priority to consider them for 4.8, complete backlog [2]: - oneacct extended to the webinterface. This is issue #1607, in this release we are going for #1484 (output in csv format of accounting data) - over-committing memory (ram) to VMs just like how you can set over commit in CPU. This is issue #1328 - One feature I would like to see would be a recycle bin this has been merge with #2412 Ability to lock VM from accidental actions - #2560 Re-read oned.conf on reload - #2651 Implement mailbox to prevent vm from running twice. Again thanks for the feedback. Cheers PS: A more prosaic form of this mail has been published in the blog [3] [1] http://dev.opennebula.org/projects/opennebula/issues?query_id=45 [2]
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 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 ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Thu, Jan 23, 2014 at 5:24 AM, Shankhadeep Shome shank15...@gmail.com wrote: 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 hyperv relaxed state='on'/ vapic state='on'/ spinlocks state='on' retries='4096'/ /hyperv On Tue, Jan 21, 2014 at 10:21 AM, Ruben S. Montero rsmont...@opennebula.org wrote: 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 always difficult to prioritize the new features considering the limited time-frame of a release, so we tried to balance the effort and number of features. The complete list of features is here [1]. About the specific requests in this thread. In 4.6, We are going for: - #2568 Support for RBD Format 2 images - #1727 Patch for one.image.resize to resize image - #1818 Support for IP reservations along with #2545 Decorrelate networks TYPE and IP management - #1696 Add the ability to select datastore for Clone operation as a previous step for #2417 “Move images between datastores”. #2417 requires preserving the ID, so let see if we can easily get both - #2453 Add hostname configuration to contexualization - #2048. Instantiate to persistent - #2648: ACL edit/view wizard - #2649: sunstone, occi, econe, novncserver ability to log to syslog server These issues have been moved to the backlog, with a high priority to consider them for 4.8, complete backlog [2]: - oneacct extended to the webinterface. This is issue #1607, in this release we are going for #1484 (output in csv format of accounting data) - over-committing memory (ram) to VMs just like how you can set over commit in CPU. This is issue #1328 - One feature I would like to see would be a recycle bin this has been merge with #2412 Ability to lock VM from accidental actions - #2560 Re-read oned.conf on reload - #2651 Implement mailbox to prevent vm from running twice. Again thanks for the feedback. Cheers PS: A more prosaic form of this mail has been published in the blog [3] [1] http://dev.opennebula.org/projects/opennebula/issues?query_id=45 [2] http://dev.opennebula.org/projects/opennebula/issues?query_id=46 [3] http://opennebula.org/blueprints-for-opennebula-4-6/ On Fri, Jan 17, 2014 at 8:41 PM, Karsten Nielsen kars...@unity3d.com wrote: 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] (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
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 hyperv relaxed state='on'/ vapic state='on'/ spinlocks state='on' retries='4096'/ /hyperv On Tue, Jan 21, 2014 at 10:21 AM, Ruben S. Montero rsmont...@opennebula.org wrote: 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 always difficult to prioritize the new features considering the limited time-frame of a release, so we tried to balance the effort and number of features. The complete list of features is here [1]. About the specific requests in this thread. In 4.6, We are going for: - #2568 Support for RBD Format 2 images - #1727 Patch for one.image.resize to resize image - #1818 Support for IP reservations along with #2545 Decorrelate networks TYPE and IP management - #1696 Add the ability to select datastore for Clone operation as a previous step for #2417 “Move images between datastores”. #2417 requires preserving the ID, so let see if we can easily get both - #2453 Add hostname configuration to contexualization - #2048. Instantiate to persistent - #2648: ACL edit/view wizard - #2649: sunstone, occi, econe, novncserver ability to log to syslog server These issues have been moved to the backlog, with a high priority to consider them for 4.8, complete backlog [2]: - oneacct extended to the webinterface. This is issue #1607, in this release we are going for #1484 (output in csv format of accounting data) - over-committing memory (ram) to VMs just like how you can set over commit in CPU. This is issue #1328 - One feature I would like to see would be a recycle bin this has been merge with #2412 Ability to lock VM from accidental actions - #2560 Re-read oned.conf on reload - #2651 Implement mailbox to prevent vm from running twice. Again thanks for the feedback. Cheers PS: A more prosaic form of this mail has been published in the blog [3] [1] http://dev.opennebula.org/projects/opennebula/issues?query_id=45 [2] http://dev.opennebula.org/projects/opennebula/issues?query_id=46 [3] http://opennebula.org/blueprints-for-opennebula-4-6/ On Fri, Jan 17, 2014 at 8:41 PM, Karsten Nielsen kars...@unity3d.comwrote: 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] (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
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 always difficult to prioritize the new features considering the limited time-frame of a release, so we tried to balance the effort and number of features. The complete list of features is here [1]. About the specific requests in this thread. In 4.6, We are going for: - #2568 Support for RBD Format 2 images - #1727 Patch for one.image.resize to resize image - #1818 Support for IP reservations along with #2545 Decorrelate networks TYPE and IP management - #1696 Add the ability to select datastore for Clone operation as a previous step for #2417 “Move images between datastores”. #2417 requires preserving the ID, so let see if we can easily get both - #2453 Add hostname configuration to contexualization - #2048. Instantiate to persistent - #2648: ACL edit/view wizard - #2649: sunstone, occi, econe, novncserver ability to log to syslog server These issues have been moved to the backlog, with a high priority to consider them for 4.8, complete backlog [2]: - oneacct extended to the webinterface. This is issue #1607, in this release we are going for #1484 (output in csv format of accounting data) - over-committing memory (ram) to VMs just like how you can set over commit in CPU. This is issue #1328 - One feature I would like to see would be a recycle bin this has been merge with #2412 Ability to lock VM from accidental actions - #2560 Re-read oned.conf on reload - #2651 Implement mailbox to prevent vm from running twice. Again thanks for the feedback. Cheers PS: A more prosaic form of this mail has been published in the blog [3] [1] http://dev.opennebula.org/projects/opennebula/issues?query_id=45 [2] http://dev.opennebula.org/projects/opennebula/issues?query_id=46 [3] http://opennebula.org/blueprints-for-opennebula-4-6/ On Fri, Jan 17, 2014 at 8:41 PM, Karsten Nielsen kars...@unity3d.comwrote: 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] (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 ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 globally) if we can make your feature for 4.6 or if we have to unfortunately postpone it for lack of resources. Nooo, wait! ;). this just in: #2655 Support for novnc token through xmlrpc api (i.e. one.vm.token/one.vm.novnctoken). Gr. Stefan -- | BIT BV http://www.bit.nl/Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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] (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 ab...@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@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 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. Here's my wishlist: #2560 Re-read oned.conf on reload #2648: ACL edit/view wizard #2649: sunstone, occi, econe, novncserver ability to log to syslog server SIGHUP handling for ONED, referenced by #409 (so logrotate can correctly rotate oned.log) #2651 Implement mailbox to prevent vm from running twice Gr. Stefan -- | BIT BV http://www.bit.nl/Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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. 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 Just like you described in: http://dev.opennebula.org/issues/2048. I understand your use case. A collegue of mine exptected to be able to do just this and was surprised he couldn't. The most important thing here is that to be able to clone the image it has to be non-persistent, and if the cloned image should be persistent, you should _not_ forget to change the cloned image to be persistent. Having a (known working) template (persistent=yes) will prevent data loss sooner or later. Yes, I know you can make a (defered/hot) snapshot but if you forget to do this before the vm is shutdown you lose your data. +1 vote for this feature. Gr. Stefan -- | BIT BV http://www.bit.nl/Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
Tino Vazquez cvazq...@c12g.com 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 plan. It already seems quite busy, looking at issues not in 4.6 roadmap I would say, for my personal use: #1290 “Allowing autostart setting for KVM deployed VMs with persistent images, to restart them upon node reboot” It ease the “reboot after upgrade” for single node configuration. Today, on my single node, I need to stop all my VMs before doing the reboot and resume them by hand when reboot is done for my professional use: #2417 “Move images between datastores” -- It may be somewhat related to #2591 “Share resources between clusters” #2545 “Decorrelate networks TYPE and IP management” --- I'm quite sure this one is big enough to be delayed after 4.6. Ideally, the VM name and its IPs should match between ONE leases and my DHCP server but I don't figure it out. I think it's related to #2348 “Add static MAC address to” (I forget the VM NIC) Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x7A6FE2DF pgpf0JWXR92Gu.pgp Description: PGP signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[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 ab...@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@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 attached patch on version 4.4 and it just works great. VM provisioning using this method is A LOT faster than with Format 1 images, like lightning speed. #1727 Patch for one.image.resize to resize image -- I'd like to specify the target image size in the template. The Ubuntu Cloud Images are able to resize themself during the first boot (see http://packages.ubuntu.com/saucy/cloud-initramfs-growroot, installed by default on the cloud images). So you just need the original image (which is 2GB) and specify the size you need in the template. This is mainly very useful for the public cloud interface where you could provide some templates to the users which specifies not only the ram size and cpu count, but also the image size. So you don't have to prepare an image for every size you'd like to provide. Other ideas and votes - To extend the public cloud capabilities, a customer management and billing interface (think of oneacct extended to the webinterface) would be a nice feature I'd like to see in the future. Better handling of VMs which are stopped by the user from inside the VM (f.e. shutdown -h now) would make admins life easier. I also vote for the following Redmine tickets assigned to Release 4.6 target version: * #2453 Add hostname configuration to contexualization * #1818 Support for IP reservations Looking forward to comments on my ideas. Cheers, Tobias On 09.01.2014 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] (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/ ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Closing OpenNebula 4.4 Cycle, Planning for 4.6
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 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 attached patch on version 4.4 and it just works great. VM provisioning using this method is A LOT faster than with Format 1 images, like lightning speed. #1727 Patch for one.image.resize to resize image -- I'd like to specify the target image size in the template. The Ubuntu Cloud Images are able to resize themself during the first boot (see http://packages.ubuntu.com/saucy/cloud-initramfs-growroot, installed by default on the cloud images). So you just need the original image (which is 2GB) and specify the size you need in the template. This is mainly very useful for the public cloud interface where you could provide some templates to the users which specifies not only the ram size and cpu count, but also the image size. So you don't have to prepare an image for every size you'd like to provide. Other ideas and votes - To extend the public cloud capabilities, a customer management and billing interface (think of oneacct extended to the webinterface) would be a nice feature I'd like to see in the future. Better handling of VMs which are stopped by the user from inside the VM (f.e. shutdown -h now) would make admins life easier. I also vote for the following Redmine tickets assigned to Release 4.6 target version: * #2453 Add hostname configuration to contexualization * #1818 Support for IP reservations Looking forward to comments on my ideas. Cheers, Tobias On 09.01.2014 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] (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/ ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
