Open Stack

On Fri, 2019-03-29 at 11:25 -0500, Eric Fried wrote:
> Florian-
> 
> You can definitely delete a flavor [1].
> 
> Don't worry about it affecting existing instances that were created with
> that flavor: nova stores a copy of the flavor with the instance itself
> so the information is preserved.
> 
> Thanks for the question!
the other option if you want to keep the flavor but not make it usable by
new instances in general is to use the os-flavor-access api.
https://developer.openstack.org/api-ref/compute/?expanded=#flavors-access-flavors-os-flavor-access
This allows you to make a flavor private and control what project can use it.


unfortunetly we seam to have almost no documentation for this however that is what the --project argument
to openstack flavor set is used to contol.
https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/flavor.html#flavor-set
e.g. openstack flavor set --project <my admin/hidden project> <flavor i want to retire>

this will allow you to retire the flavor more selectively.
so if you have a important customer that needs a little more time to move to your new flavor offerings
you can similarly add them to the now private flavor to aide there transition before you actually delete it.

as efried said you can delete the flavor without issue so if you are not worred about it breaking
ci or other automation and can simply remove the flavor that hsould be safe to do so.
> 
> -efried
> 
> [1]
> https://docs.openstack.org/nova/latest/admin/flavors.html#delete-a-flavor
> 
> On 3/29/19 10:43 AM, Florian Engelmann wrote:
> > Hi,
> > 
> > I would like to retire old flavors we don't want to be use any more. I
> > guess deleting is the wrong way to retire flavors? I was not able to
> > find any documentation about how the life-cycle of a flavor works.
> > 
> > Any help is very welcome.
> > 
> > All the best,
> > Florian
> 
>