Not an expert of Nova but I am really shocked by such a change. Because I'm not a Nova expert, I don't have a say on the *huge* efforts in maintaining some builtin/default flavors. As a user I don't care where the data have been stored, but I do care that they are gone. They are gone because they **WILL** be supported by devstack. They are gone with the workflow +1'ed **BEFORE** the devstack patch gets merged (many thanks to the depends-on tag). They are gone in hope that all deployment tools will know this when they fail, or fortunately they read this email, or they were reviewing nova patches.
It would be a little nicer to initiate a discussion on the mailinglist before such a change is introduced. Regards, Qiming On Tue, Apr 05, 2016 at 08:09:50AM -0700, Dan Smith wrote: > Just as a heads up, we are removing the default flavors from nova in > this patch: > > https://review.openstack.org/#/c/300127/ > > Since long ago, Nova's default flavors were baked in at the database > migration level. Now that we have moved them to another database > entirely, this means we have to migrate them from the old/original place > to the new one, even for new deployments. It also means that our tests > have flavor assumptions that run (way too) deep. > > Devstack will get support for auto-creating the flavors you are used to, > as well as some less-useless ones: > > https://review.openstack.org/#/c/301257/ > > Normal developers shouldn't really notice, but the deployment tool > projects may want/need to do something here along the same lines. > > --Dan > __________________________________________________________________________ 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
