Open Stack

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/38118903/attachment.html>