Open Stack

Hi,

I agree with this.
We are facing challenges when the global health pool is changed to atomically modify all the groups that are linked to this health check as the groups might be configured in different devices.
So if one of the group modification fails it is very difficult to revert the change back.

-Sam.


From: Eugene Nikanorov [mailto:enikanorov at mirantis.com]
Sent: Thursday, June 20, 2013 3:10 PM
To: OpenStack Development Mailing List
Cc: Avishay Balderman; Samuel Bercovici
Subject: [Quantum][LBaaS] Feedback needed: Healthmonitor workflow.

Hi community,

Here's a question.
Currently Health monitors in Loadbalancer service are made in such way that health monitor itself is a global shared database object.
If user wants to add health monitor to a pool, it adds association between pool and health monitor.
In order to update existing health monitor (change url, for example) service will need to go over existing pool-health monitor associations notifying devices of this change.

I think it could be changed to the following workflow:
Instead of adding pool-healthmonitor association, use health monitor object as a template (probably renaming is needed) and add 'private' health monitor to the pool.
So all further operations would result in changing health monitor on one device only.

What do you think?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130620/ec042850/attachment.html>