[nova] retire a flavor

Graham Hayes gr at ham.ie
Fri Apr 5 13:33:37 UTC 2019

On 01/04/2019 17:48, Matt Riedemann wrote:

> Now if you created a server or resized a server with a given flavor, and
> then modified that flavors extra_specs, that won't be reflected back in
> the persisted RequestSpec, but it's probably not a great idea in general
> to modify extra_specs on public flavors which are already being used.

There is a use case for this - if you have heterogeneous compute
environment (e.g. some nodes are set up for pinning, some for standard
overcommit, some for one to one (no over commit, but not pinned)), and
you make a mistake - being able to change the flavor makes fixing the
resultant mess a lot easier - especially if you can update the
RequestSpec to match the new flavor.

Without this (or doing DB surgery), the end result is potentially
resizing all the VMs in a region, which is not always possible (SR-IOV
or really large VMs that can't really be shutdown).

This is generally for provisioning suites that hardcode flavor IDs and
names into deployment templates, but unfortunately there quite a few of
them that still do this, even in newer versions.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190405/af5abc75/attachment-0001.sig>

More information about the openstack-discuss mailing list