yahoo-eng-team team mailing list archive

[OpenStack Infra <1521783@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/268237
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=06482f2ef8070bb8e5d308b978d03fdeb221cea6
Submitter: Jenkins
Branch:    master

commit 06482f2ef8070bb8e5d308b978d03fdeb221cea6
Author: German Eichberger <german.eichberger@xxxxxx>
Date:   Fri Jan 15 11:11:25 2016 -0600

    Adds Cascade option for load balancer drivers
    
    Adds a cascade option to be used by load balancer drivers
    Per Brandon's suggestion introduce new driver method
    delete_cascade to facilitate that functionality.
    
    Added a new property to decide if we need to delete in
    the DB.
    
    Closes-bug: #1521783
    
    Change-Id: Icebbf83130fae0eb606113616702d2aeb9687f88


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  RfE: Cascading delete for LBaaS Objects

Status in neutron:
  Fix Released

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...

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