[openstack-dev] [Quantum][LBaaS] Default insertion mode for balancer device

Eugene Nikanorov enikanorov at mirantis.com
Fri Jan 25 20:29:06 UTC 2013

Hi folks,

Currently we're working on integrating together parts of LBaaS which will
allow the whole service to work.
As you know, the only driver that is under development now is HAProxy
Also, It seems to be the only type of balancer going into grizzly.

We faced a certain problem with that: it seems that the most viable use
case for HAProxy loadbalancer is private loadbalancer which is brought up
by a tenant in a private network (E.g. balancer is in the same L2 domain
with the pool members).
Then it is configured via LBaaS service and then tenant may assign floating
IP to the balancer device making possible to access its VMs from internet
through the balancer.
However it became obvious that this use case is incompatible with our
simplified device management based on configuration file.
Configuration file implies that it is edited by admin and modification
requires quantum restart. E.g. tenant can't add it's private device, etc.

If we go with conf-based device management, defining HAProxy to be shared
device, we will need some additional configuration of machine with HAProxy
to have connectivity with certain tenant network, possibly having OVS on
it, etc.
Also, pool members from different tenants having subnets with the same IP
ranges are indistinguishable from HAProxy conf-file perspective.
Solving any of mentioned problems with shared HAProxy seems to take some
time to implement, test and review and obviously that will miss grizzly.

So currently we're thinking again about having device management as a
plugin with it's extension, to focus "private devices" use case.
We have already written the code a while ago, but then went
with simpler conf-based approach.
I'd estimate we could get device management plugin code on gerrit in a week
from now, which will give ~2 weeks of time for review plus a week till g-3

We'd like to hear your opinion:
1) Is the mentioned use case of private HAProxy the one we should focus on
for G-3?
If not, then please describe alternatives.

I'd like to emphasize that this use case goes inline with our future plans
to make automatic provisioning of private tenant HAProxies via Nova.

2) Do you think it's ok to go further with dev management plugin? We need
it to provide tenants ability to add their private devices.
If you feel that we don't have enough time for that, please advise

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130126/54b26877/attachment.html>

More information about the OpenStack-dev mailing list