I have one to users: - Have you need to add some customized features on upstream Nova code to meet your special needs? or Nova is out of the box project?
Thanks. 2016-12-27 7:18 GMT+08:00 Jay Pipes <jaypi...@gmail.com>: > On 12/26/2016 06:08 PM, Matt Riedemann wrote: > >> We have the opportunity to again [1] ask a question in the upcoming user >> survey which will be conducted in February. We can ask one question and >> have it directed to either *users* of Nova, people *testing* nova, or >> people *interested* in using/adopting nova. Given the existing adoption >> of Nova in OpenStack deployments (98% as of October 2016) I think that >> sliding scale really only makes sense to direct a question at existing >> users of the project. It's also suggested that for projects with over >> 50% adoption to make the question quantitative rather than qualitative. >> >> We have until January 9th to submit a question. If you have any >> quantitative questions about Nova to users, please reply to this thread >> before then. >> >> Personally I tend to be interested in feedback on recent development, so >> I'd like to ask questions about cells v2 or the placement API, i.e. they >> were optional in Newton but how many deployments that have upgraded to >> Newton are deploying those features (maybe also noting they will be >> required to upgrade to Ocata)? However, the other side of me knows that >> most major production deployments are also lagging behind by a few >> releases, and may only now be upgrading, or planning to upgrade, to >> Mitaka since we've recently end-of-life'd the Liberty release. So asking >> questions about cells v2 or the placement service is probably premature. >> It might be better to ask about microversion adoption, i.e. if you're >> monitoring API request traffic to your cloud, what % of compute API >> requests are using a microversion > 2.1. >> > > My vote would be to ask the following question: > > Have you considered using (or already chosen) an alternative to OpenStack > Nova for launching your software workloads? If you have, please list one to > three reasons why you chose this alternative. > > Thanks, > -jay > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev