yahoo-eng-team team mailing list archive

[Armando Migliaccio <1511574@xxxxxxxxxxxxxxxxxx>]

** Also affects: python-neutronclient
   Importance: Undecided
       Status: New

** Changed in: neutron
       Status: In Progress => Won't Fix

** Changed in: neutron
     Assignee: John Davidge (john-davidge) => (unassigned)

** Changed in: python-neutronclient
     Assignee: (unassigned) => John Davidge (john-davidge)

** Changed in: python-neutronclient
       Status: New => Confirmed

-- 
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:
  Won't Fix
Status in python-neutronclient:
  Confirmed

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