[RFE] Cascading delete for LBaaS Objects
Bug #1521783 reported by
German Eichberger
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...
Changed in neutron: | |
importance: | Undecided → Wishlist |
Changed in neutron: | |
assignee: | nobody → Bharath (bharathm) |
status: | Triaged → In Progress |
Changed in neutron: | |
assignee: | Bharath (bharathm) → German Eichberger (german-eichberger) |
Changed in neutron: | |
assignee: | German Eichberger (german-eichberger) → Brandon Logan (brandon-logan) |
Changed in neutron: | |
assignee: | nobody → German Eichberger (german-eichberger) |
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 |
Changed in neutron: | |
milestone: | mitaka-3 → mitaka-rc1 |
Changed in neutron: | |
milestone: | mitaka-rc1 → newton-1 |
summary: |
- RfE: Cascading delete for LBaaS Objects + [RFE] Cascading delete for LBaaS Objects |
Changed in neutron: | |
milestone: | newton-1 → newton-2 |
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 |
To post a comment you must log in.
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.