I recall these being embedded being a real operational pain when my team wanted to replace the defaults. +1 on removal On Mar 31, 2016 2:27 PM, "Dan Smith" <d...@danplanet.com> wrote:
> Hi all, > > I just wanted to float this past the operators list for visibility: > > Historically Nova has seeded some default flavors in an initial install. > The way it has done this is really atypical of anything else we do, as > it's embedded in the initial database schema migration. Since we're > moving where we store those flavors now, leaving their creation in the > original migration means even new deploys will just have to move them to > the new location. That, and we don't even use them for our own testing > as they're too large. > > So, this will involve removing them from that migration, making sure > that devstack creates you some flavors to use if you're going that > route, and updates to the manuals describing the creation of base > flavors alongside getting an image set up to use. > > For real deployments, there should be little or no effect, but PoC type > deploys that are used to those flavors being present may need to run a > couple of flavor-create commands when bootstrapping, just like you have > to do for images. > > Thanks! > > --Dan > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
