Clean up resources when a tenant is deleted
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.
Blueprint information
- Status:
- Complete
- Approver:
- Assaf Muller
- Priority:
- High
- Drafter:
- Assaf Muller
- Direction:
- Approved
- Assignee:
- John Davidge
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-3
- Started by
- Henry Gessau
- Completed by
- Armando Migliaccio
Related branches
Related bugs
| Bug #1511574: [RFE] Support cleanup of all resources associated with a given tenant | Fix Released |
Sprints
Whiteboard
Feb-01-2016(armax): no code posted by owner:
https:/
Jan-18-2016(armax): no major code nor documentation as of today. Changes of getting in Mitaka are getting slim.
September-3 (mestery): Moving out of Juno, the last patch in this series will need to be proposed again for Kilo.
20-July (mestery): Juno-2 as medium.
Gerrit topic: https:/
Addressed by: https:/
Clean up tenant resources when one is deleted
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
Addressed by: https:/
[5/5] Clean up Neutron resources upon tenant deletion
Addressed by: https:/
[4/5] Clean up Neutron resources upon tenant deletion
Addressed by: https:/
[3/5] Clean up Neutron resources upon tenant deletion
Addressed by: https:/
[2/5] Clean up Neutron resources upon tenant deletion
Addressed by: https:/
[1/5] Clean up Neutron resources upon tenant deletion
Addressed by: https:/
Support cleanup of tenant resources with a single API call
