Reviewed: https://review.openstack.org/276541 Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=88fbd3870cf3872fb0c9b4269503c62458664b3b Submitter: Jenkins Branch: master
commit 88fbd3870cf3872fb0c9b4269503c62458664b3b Author: John Davidge <[email protected]> Date: Mon Feb 15 10:02:54 2016 -0800 Support cleanup of tenant resources with a single API call The addition of the 'neutron purge' command allows cloud admins to conveniently delete multiple neutron resources associated with a given tenant. The command will delete all supported resources provided that they can be deleted (not in use, etc) and feedback the amount of each resource deleted to the user. A completion percentage is also given to keep the user informed of progress. Currently supports deletion of: Networks Subnets (implicitly) Routers Ports (including router interfaces) Floating IPs Security Groups This feature can be easily extended to support more resource types in the future. DocImpact: Update API documentation to describe neutron-purge usage Change-Id: I5a366d3537191045eb53f9cccd8cd0f7ce54a63b Closes-Bug: 1511574 Partially-Implements: blueprint tenant-delete ** Changed in: python-neutronclient Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1511574 Title: [RFE] Support cleanup of all resources associated with a given tenant Status in neutron: Invalid Status in python-neutronclient: Fix Released Bug description: In the ops painpoints session (https://etherpad.openstack.org/p /mitaka-neutron-next-ops-painpoints) a problem was identified where removing a tenant can leave behind stray routers, ports, etc. It was suggested that a simple 'neutron purge <tenant_id>' command or similar would simplify the process of cleaning up these stray resources by removing everything associated with the given tenant. The expectation is that this command would be admin-only, and neutron should not be responsible for deciding whether the action is 'safe'. It should work regardless of whether the given tenant is active or not. This suggestion was very popular with the operators in the room. The consensus was that this would save a lot of time and effort where currently these resources have to be discovered and then removed one by one. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1511574/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
