[RFE] Cascading delete for LBaaS Objects

Bug #1521783 reported by German Eichberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Wishlist
Unassigned

Bug Description

The LBaaS-Horizon Dashboard people requested a cascading delete in the LBaaS V2 REST API. So that if say you use an additional parameter (let's call it force=True) by deleting a load balancer it will also delete listeners, pools, and members. The same should be true for listeners, pools, etc.

In a first step we likely should just a dd that to the API, and then in a next step add it to the CLI.

As a side effect that might help operators cleaning out accounts efficiently...

Revision history for this message
Doug Wiegley (dougwig) wrote :

I'd like to see this proposal match/be similar to the "make a load balancer tree in one api" proposal, since it's a complementary operation.

Changed in neutron:
status: New → Confirmed
tags: added: rfe
tags: added: lbaas
Revision history for this message
Brandon Logan (brandon-logan) wrote :

cascade=True would probably be better than force IMO

Changed in neutron:
importance: Undecided → Wishlist
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

 I personally would like to see these orchestration-oriented API die, but it looks like I am the only one who has this sentiment

Changed in neutron:
milestone: mitaka-2 → none
status: Confirmed → Triaged
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Where do we draw a line and stop adding these orchestration APIs? Let's see if this is the last one that ever makes it.

Changed in neutron:
assignee: Bharath (bharathm) → nobody
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This has shown no activity for a while. I was informed by Doug that someone might have already started working on it, and there may be code posted soon. On that basis I would be ok accepting this RFE. However, I generally feel strongly against orchestration APIs that can easily be replaced by primitive calls. Unless someone revives this bug report soon, I am going to mark it WONTFIX

Changed in neutron:
assignee: nobody → Bharath (bharathm)
status: Triaged → In Progress
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Not sure what triggered the state change. I can't seem to find anything pertinent.

Revision history for this message
Henry Gessau (gessau) wrote :

It was triggered by https://review.openstack.org/268237

FYI you can find reviews referencing a bug by searching gerrit for "message:<bug number>".

Changed in neutron:
assignee: Bharath (bharathm) → German Eichberger (german-eichberger)
Changed in neutron:
assignee: German Eichberger (german-eichberger) → Brandon Logan (brandon-logan)
Revision history for this message
Brandon Logan (brandon-logan) wrote :

I meant to readd german to the assignee but its not finding his name, so leaving it blank for now. I was just pushing up a PS to his review to show him something.

Changed in neutron:
assignee: Brandon Logan (brandon-logan) → nobody
Changed in neutron:
assignee: nobody → German Eichberger (german-eichberger)
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Since the code is being churned...I stay true to my promise on comment #5

tags: added: rfe-approved
removed: rfe
Changed in neutron:
milestone: none → mitaka-3
Changed in neutron:
assignee: German Eichberger (german-eichberger) → Bharath (bharathm)
Changed in neutron:
assignee: Bharath (bharathm) → German Eichberger (german-eichberger)
Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote : Re: RfE: Cascading delete for LBaaS Objects

This is being reverted.

Changed in neutron:
status: Fix Released → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-lbaas (master)

Fix proposed to branch: master
Review: https://review.openstack.org/287593

Changed in neutron:
assignee: German Eichberger (german-eichberger) → Brandon Logan (brandon-logan)
Changed in neutron:
milestone: mitaka-3 → mitaka-rc1
Revision history for this message
Michael Johnson (johnsom) wrote : Re: RfE: Cascading delete for LBaaS Objects
Changed in neutron:
milestone: mitaka-rc1 → newton-1
Henry Gessau (gessau)
summary: - RfE: Cascading delete for LBaaS Objects
+ [RFE] Cascading delete for LBaaS Objects
Changed in neutron:
milestone: newton-1 → newton-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron-lbaas (master)

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/287593
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Changed in neutron:
status: In Progress → Incomplete
Changed in neutron:
milestone: newton-2 → newton-3
Changed in neutron:
milestone: newton-3 → newton-rc1
Changed in neutron:
milestone: newton-rc1 → none
assignee: Brandon Logan (brandon-logan) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.