Open Stack

>> 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.
> 

That's also my definition of retire. It still exists but no new instance 
can choose it and is no more listed for normal (member) users. And I 
agree - re-enable should be possible.

> 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.
> 

Yes but if the database schema is already prepared to disable (=retire?) 
a flavor we should implement this in the API first and then document it?

> 
>>
>> 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
>>>>
>>>>
>>>
>>>
>>
>>
> 

-- 

EveryWare AG
Florian Engelmann
Senior UNIX Systems Engineer
Zurlindenstrasse 52a
CH-8003 Zürich

tel: +41 44 466 60 00
fax: +41 44 466 60 10
mail: mailto:florian.engelmann at everyware.ch
web: http://www.everyware.ch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5230 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190405/3c9abdf7/attachment.bin>