Hi Vijay, Currently Neutron LBaaS supports only namespace based implementation for HAProxy. You can however run LBaaS agent on the host other than network controller node - in that case HAProxy processes will be running on that host but still in namespaces.
Also there is an effort in Neutron regarding adding support of advanced services in VMs [1]. After it is completed I hope it will be possible to adopt it in LBaaS and run HAProxy in such a service VM. [1] https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms Thanks, Oleg On Tue, Mar 25, 2014 at 1:39 AM, Vijay B <[email protected]> wrote: > Hi Eugene, > > Thanks for the reply! How/where is the agent configuration done for > HAProxy? If I don't want to go with a network namespace based HAProxy > process, but want to deploy my own HAProxy instance on a host outside of > the network controller node, and make neutron deploy pools/VIPs on that > HAProxy instance, does neutron currently support this scenario? If so, what > are the configuration steps I will need to carry out to deploy HAProxy on a > separate host (for example, where do I specify the ip address of the > haproxy host, etc)? > > Regards, > Vijay > > > On Mon, Mar 24, 2014 at 2:04 PM, Eugene Nikanorov <[email protected] > > wrote: > >> Hi, >> >> HAProxy driver has not removed from the trunk, instead it became a base >> for agent-based driver, so the only haproxy-specific thing in the plugin >> driver is device driver name. Namespace driver is a device driver on the >> agent side and it was there from the beginning. >> The reason for the change is mere refactoring: it seems that solutions >> that employ agents could share the same code with only device driver being >> specific. >> >> So, everything is in place, HAProxy continues to be the default >> implementation of Neutron LBaaS service. It supports spawning haproxy >> processes on any host that runs lbaas agent. >> >> Thanks, >> Eugene. >> >> >> >> On Tue, Mar 25, 2014 at 12:33 AM, Vijay B <[email protected]> wrote: >> >>> Hi, >>> >>> I'm looking at HAProxy support in Neutron, and I observe that the >>> drivers/haproxy/plugin_driver.py file in the stable/havana release has been >>> effectively removed from trunk (master), in that the plugin driver in the >>> master simply points to the namespace driver. What was the reason to do >>> this? Was the plugin driver in havana tested and documented? I can't seem >>> to get hold of any relevant documentation that describes how to configure >>> HAProxy LBs installed on separate boxes (and not brought up in network >>> namespaces) - can anyone please point me to the same? >>> >>> Also, are there any plans to bring back the HAProxy plugin driver to >>> talk to remote HAProxy instances? >>> >>> Thanks, >>> Regards, >>> Vijay >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> [email protected] >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
