Open Stack

Thanks for the clarification. Eugene.

A tangential point since you brought healthmon and pool.

There will be an additional entity called ‘PoolMonitorAssociation’ which results in a many to many relationship between pool and monitors. Right?

Now, the model is indicating a pool can have only one monitor. So a minor correction is required to indicate the many to many relationship via PoolMonitorAssociation.

Thanks,
Vijay V.


From: Eugene Nikanorov [mailto:enikanorov at mirantis.com]
Sent: Thursday, May 15, 2014 7:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Hi Vijay,


When you say API is not available, it means this should not be considered like a resource/entity. Correct?

But then, there would be API like a bind API, that accepts loadbalancer_id & listener_id,  which creates this object.
And also, there would be an API that will be used to list the listeners of a LoadBalancer.

Right?
Right, that's the same as health monitors and pools work right now: there are separate REST action to associate healthmon to a pool


Thanks,
Eugene.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140515/d1612049/attachment.html>