Open Stack

On Mon, 2019-04-01 at 17:40 +0200, Florian Engelmann wrote:
> Hi,
> 
> as far as I tested it is not possible to change a flavor from public to 
> private. Managing access to flavors on a project basis might be an 
> option for a private cloud but not for a public one.
if you cannot retrict a flavor to a singel porject in a public cloud
you also can never delete a flavor in a public cloud.

from an api perspective it will have the same effect.
> 
> There are a lot of unit tests about:
> 
>              "alias": "OS-FLV-DISABLED",
>              "description": "Support to show the disabled status of a 
> flavor.",
> 
> What's that feature for? How does it work? Is this ongoing?
> 
> I think we need some method to retire images and flavors.
well it depend on what you mean by retire.
my definition of retire means it still exist but is no longer
requestable for new instances. idealy if you retire something from
service it should be possible to reinstate it again even if that is unlikely.

if your definitoin of retire delete it then you can certenly do that.
restoring a delete flavor is technicaly possible as you cna just recreated it
but its harder to do that then unrestrict the acess to the flavor.

but yes we shoudl have a documented procedure to "retire" a flavor  or image in the
admin guide somewhere but we also need to define what that means first and that might
change form deployment to deployment at least in some cases.


> 
> All the best,
> Florian
> 
> Am 3/31/19 um 11:57 AM schrieb Sean Mooney:
> > 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
> > > 
> > > 
> > 
> > 
> 
>