Re: [Openstack-operators] [nova] Removing seeded flavors

Another remove vote. The only people this may affect are people standing up test clouds or new to OpenStack. For those folks that use puppet, the puppet community will be adding a provider to setup flavors since it's a feature that's been missing. I'll add a vote for removal, given how varied

Re: [Openstack-operators] [nova] Removing seeded flavors

On 4/4/2016 3:43 PM, Joseph Bajin wrote: While I think it's fine to remove this from the normal setup, I think there should be either a file or process that one could run to add these basic flavors. I think without you will have things such as DevStack and other beginners not being able to

Re: [Openstack-operators] [nova] Removing seeded flavors

While I think it's fine to remove this from the normal setup, I think there should be either a file or process that one could run to add these basic flavors. I think without you will have things such as DevStack and other beginners not being able to get up and going. I think having the migration

Re: [Openstack-operators] [nova] Removing seeded flavors

I'll add a vote for removal, given how varied private clouds tend to be, the flavors are often "wrong" for any one particular purpose. R On Sat, Apr 2, 2016 at 8:41 PM, Mike Smith wrote: > +1 from me. We always just remove them and add our own. Like Dan said, > it’s

[Openstack-operators] [nova] Removing seeded flavors

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