yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1169107] Re: lbaas: delete_health_monitor() should rely upon cascade operations

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 29 May 2013 11:08:32 -0000
Reply-to: Bug 1169107 <1169107@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: quantum
       Status: Fix Committed => Fix Released

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

Title:
  lbaas:  delete_health_monitor() should rely upon cascade operations

Status in OpenStack Quantum (virtual network service):
  Fix Released

Bug description:
  In LBaaS DB schema we have a Pool <--> HealthMonitor many-to-many association which is done 
  via the PoolMonitorAssociation model.

  A HealthMonitor instance may be deleted by calling the "delete_health_monitor()" method 
  which is defined in  quantum/db/loadbalancer/loadbalancer_db module.

  Currently, this method performs a "manual" deletion of a HealthMonitor instance given its id:
  it gets a list of all PoolMonitorAssociation instances filtered by a HealthMonitor id, for each of those
  instances it retrieves a corresponding Pool instance and finally removes the association instance
  from the "monitors" collection of a Pool instance.

  We can simplify the deletion of HealthMonitor instances by relying upon cascade operations
  defined for SQLAlchemy relationships (which is already done for Pool model).

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