Follow  http://openstack.redhat.com/forum/discussion/comment/2178  
  and    http://openstack.redhat.com/Load_Balance_OpenStack_API#HAProxy

Edit /etc/neutron/neutron.conf and add the following in the default section:

[DEFAULT]
service_plugins = neutron.services.loadbalancer.plugin.LoadBalancerPlugin

Already there

Then edit the /etc/openstack-dashboard/local_settings file and search for enable_lb and set it to true:

OPENSTACK_NEUTRON_NETWORK = {
    'enable_lb': True
}

Done

# yum install haproxy - already installed
# vi /etc/neutron/lbaas_agent.ini - already done no changes

device_driver=neutron.services.loadbalancer.drivers.haproxy.namespace_driver.HaproxyNSDriver
interface_driver=neutron.agent.linux.interface.OVSInterfaceDriver
user_group=haproxy

Comment out the line in the service_providers section:

service_provider=LOADBALANCER:Haproxy:neutron.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default

Nothing to remove

service neutron-lbaas-agent start - already running , restarted
chkconfig neutron-lbaas-agent on  - skipped
service neutron-server restart  - done
service httpd restart  - done


HA enabled via keepalived , Virtual IP 192.168.1.132.

Follow http://openstack.redhat.com/Load_Balance_OpenStack_API#HAProxy 
and http://openstack.redhat.com/forum/discussion/798/enabling-lbaas-in-havana-and-why-is-it-not-on-by-default#Item_4  replacing "quantum" by "neutron" and using virirtual IP for one server creating /etc/haproxy/haproxy.cfg. Haproxy fails to start reporting:


Starting haproxy:

[ALERT] 006/135903 (12988) : Starting frontend keystone-admin-vip: cannot bind socket

[ALERT] 006/135903 (12988) : Starting frontend keystone-public-vip: cannot bind socket

. . . . . . .

Really , for any port mentioned in haproxy.cfg :-

# netstat -lnp | grep 35357 tcp 0 0 0.0.0.0:35357 0.0.0.0:* LISTEN 4189/python
# netstat -lnp | grep 5000 tcp 0 0 0.0.0.0:5000 0.0.0.0:*     LISTEN 4189/python
. . . . . . 

Haproxy may be started ahead of openstack services, but in this case openstack services fail to start.  I am missing something here