yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1870319] [NEW] [RFE] Network cascade deletion API call

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Slawek Kaplonski <1870319@xxxxxxxxxxxxxxxxxx>
Date: Thu, 02 Apr 2020 11:16:03 -0000
Reply-to: Bug 1870319 <1870319@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

It came originally from Kuryr team and it was already discussed on the
PTG in Shanghai.

Use case:
As a cloud user I would like to have API command similar to openstack loadbalancer delete --cascade LB_ID, where I trigger the deletion of a network (openstack network delete --cascade NET_ID) , and it automatically deletes the associated ports/subports and subnets.

Currently what kuryr needs to do to delete "namespace" is:

* Get the ACTIVE ports in the subnet
* Get the trunks
* For each of the ACTIVE port, obtain what trunk they are attached to and call neutron to detach it
* Remove the ports (one by one, there is no bulk deletion)
* Get the DOWN ports in the given subnet
* Remove the ports (one by one, there is no bulk deletion)
* Detach the subnet from the router
* Remove the network (which will also remove the subnet)

** Affects: neutron
     Importance: Wishlist
     Assignee: Slawek Kaplonski (slaweq)
         Status: Triaged


** Tags: api rfe-triaged

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1870319

Title:
  [RFE] Network cascade deletion API call

Status in neutron:
  Triaged

Bug description:
  It came originally from Kuryr team and it was already discussed on the
  PTG in Shanghai.

  Use case:
  As a cloud user I would like to have API command similar to openstack loadbalancer delete --cascade LB_ID, where I trigger the deletion of a network (openstack network delete --cascade NET_ID) , and it automatically deletes the associated ports/subports and subnets.

  Currently what kuryr needs to do to delete "namespace" is:

  * Get the ACTIVE ports in the subnet
  * Get the trunks
  * For each of the ACTIVE port, obtain what trunk they are attached to and call neutron to detach it
  * Remove the ports (one by one, there is no bulk deletion)
  * Get the DOWN ports in the given subnet
  * Remove the ports (one by one, there is no bulk deletion)
  * Detach the subnet from the router
  * Remove the network (which will also remove the subnet)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1870319/+subscriptions