[Openstack-operators] [openstack-operators][osops] Listing orphaned Neutron objects via listorphans.py
Kris G. Lindgren
klindgren at godaddy.com
Wed Nov 11 17:09:57 UTC 2015
The issue with ospurge is it only cleans up resources on a project to hasn't been deleted. It doesn't detect/cleanup resources tied to already deleted projects.
As I understand it, it suppose to be ran against a project - before the project is removed.
Senior Linux Systems Engineer
On 11/11/15, 10:03 AM, "Assaf Muller" <amuller at redhat.com> wrote:
>Are you aware of https://github.com/openstack/ospurge?
>On Wed, Nov 11, 2015 at 11:49 AM, Nick Jones
><nick.jones at datacentred.co.uk> wrote:
>> A while ago I knocked up a quick-and-dirty Python script to list various
>> ‘orphaned’ Neutron objects. By orphans I mean objects that OpenStack is
>> aware of but which don’t have a valid project ID any more. This is
>> something that we as a public cloud operator have to manage on a regular
>> basis, as it’s easy to chew through your public IPv4 address space with
>> orphaned routers that have a gateway set (as an example).
>> I’ve recently updated it so that it’s a lot quicker, but I’ve also changed
>> the output slightly making it easier to pipe directly into something else
>> (i.e some kind of deletion script). It’s part of the OSOps project and so
>> my change is here for review: https://review.openstack.org/#/c/244160/3
>> I’m posting this on the off chance that someone else is using it and for
>> whom the output change might cause a problem - if you could review and leave
>> a comment where appropriate then that’d be awesome.
>> DataCentred Limited registered in England and Wales no. 05611763
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>OpenStack-operators mailing list
>OpenStack-operators at lists.openstack.org
More information about the OpenStack-operators