How to enable LBaaS on Havana (Controller+Compute) CentOS 6.5 ?
I followed
I have updated haproxy.cfg just for one controller (test)
[root@openstack2 haproxy(keystone_admin)]# cat haproxy.cfg
global
daemon
defaults
mode http
maxconn 10000
timeout connect 10s
timeout client 10s
timeout server 10s
frontend keystone-admin-vip
bind 192.168.1.137:35357
default_backend keystone-admin-api
frontend keystone-public-vip
bind 192.168.1.137:5000
default_backend keystone-public-api
frontend neutron-vip
bind 192.168.1.137:9696
default_backend neutron-api
frontend glance-vip
bind 192.168.1.137:9191
default_backend glance-api
frontend glance-registry-vip
bind 192.168.1.137:9292
default_backend glance-registry-api
frontend nova-ec2-vip
bind 192.168.1.137:8773
default_backend nova-ec2-api
frontend nova-compute-vip
bind 192.168.1.137:8774
default_backend nova-compute-api
frontend nova-metadata-vip
bind 192.168.1.137:8775
default_backend nova-metadata-api
frontend cinder-vip
bind 192.168.1.137:8776
default_backend cinder-api
backend keystone-admin-api
balance roundrobin
server openstack2 192.168.1.137:35357 check inter 10s
backend keystone-public-api
balance roundrobin
server openstack2 192.168.1.137:5000 check inter 10s
backend neutron-api
balance roundrobin
server openstack2 192.168.1.137:9696 check inter 10s
backend glance-api
balance roundrobin
server openstack2 192.168.1.137:9191 check inter 10s
backend glance-registry-api
balance roundrobin
server openstack2 192.168.1.137:9292 check inter 10s
backend nova-ec2-api
balance roundrobin
server openstack2 192.168.1.137:8773 check inter 10s
backend nova-compute-api
balance roundrobin
server openstack2 192.168.1.137:8774 check inter 10s
backend nova-metadata-api
balance roundrobin
server openstack2 192.168.1.137:8775 check inter 10s
backend cinder-api
balance roundrobin
server openstack2 192.168.1.137:8776 check inter 10s
[root@openstack2 haproxy(keystone_admin)]# service haproxy start
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
[ALERT] 006/135903 (12988) : Starting frontend neutron-vip: cannot bind socket
[ALERT] 006/135903 (12988) : Starting frontend glance-vip: cannot bind socket
[ALERT] 006/135903 (12988) : Starting frontend glance-registry-vip: cannot bind socket
[ALERT] 006/135903 (12988) : Starting frontend nova-ec2-vip: cannot bind socket
[ALERT] 006/135903 (12988) : Starting frontend nova-compute-vip: cannot bind socket
[ALERT] 006/135903 (12988) : Starting frontend nova-metadata-vip: cannot bind socket
[ALERT] 006/135903 (12988) : Starting frontend cinder-vip: cannot bind socket
[FAILED]
On the other hand
[root@openstack2 ~(keystone_admin)]# netstat -lnp | grep 35357
tcp 0 0 0.0.0.0:35357 0.0.0.0:* LISTEN 4189/python
[root@openstack2 ~(keystone_admin)]# netstat -lnp | grep 5000
tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 4189/python
[root@openstack2 ~(keystone_admin)]# netstat -lnp | grep 9696
tcp 0 0 0.0.0.0:9696 0.0.0.0:* LISTEN 4037/python
[root@openstack2 ~(keystone_admin)]# netstat -lnp | grep 9191
tcp 0 0 0.0.0.0:9191 0.0.0.0:* LISTEN 4159/python
[root@openstack2 ~(keystone_admin)]# netstat -lnp | grep 9292
tcp 0 0 0.0.0.0:9292 0.0.0.0:* LISTEN 4147/python
[root@openstack2 ~(keystone_admin)]# netstat -lnp | grep 8774
tcp 0 0 0.0.0.0:8774 0.0.0.0:* LISTEN 4523/python
Ports for ...