Ospurge or "project purge" - What's the right approach to cleanup projects prior to deletion

Artem Goncharov artem.goncharov at gmail.com
Mon Jan 18 17:56:42 UTC 2021

What do you mean it doesn’t implement anything at all? It does clean up compute, network, block_storage, orchestrate resources. Moreover it gives you possibility to clean “old” resources (created before or last updated before).

> On 18. Jan 2021, at 18:30, Thomas Goirand <zigo at debian.org> wrote:
> On 1/18/21 6:10 PM, Artem Goncharov wrote:
>> Hi,
>> Please
>> check https://review.opendev.org/c/openstack/python-openstackclient/+/734485
>> <https://review.opendev.org/c/openstack/python-openstackclient/+/734485> out.
>> This is a followup of the ospurge, which bases on the project cleanup
>> functionality built into OpenStackSDK. Idea is to replace “openstack
>> project purge” functionality to completely rely on SDK only. Please also
>> leave comments whether this works for you or not.
>> Regards,
>> Artem
> Hi,
> While all of this looks like a good idea, it's not implementing anything
> at all, just a few command line options. So it's currently of no use for
> operators.
> I'm still saluting the initiative, but in 6 months, it's kind of slow
> moving, IMO.
> Cheers,
> Thomas Goirand (zigo)

More information about the openstack-discuss mailing list