[RFE] Support cleanup of all resources associated with a given tenant

[John Davidge]

Following discussion in [1] this functionality is being moved onto the client side.

Copied from [1]:

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.

[1] https://bugs.launchpad.net/neutron/+bug/1511574

[Richard Theis (rtheis)]

I think this RFE should be filed against neutron instead of python-neutronclient per http://docs.openstack.org/developer/neutron/policies/blueprints.html. Also consideration should be given to implement this in OSC per http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html.