Home OpenStack-Ansible Installation Guide

Configuring HAProxy (optional)

For evaluation, testing, and development, HAProxy can temporarily provide load balancing services in lieu of hardware load balancers. The default HAProxy configuration does not provide highly-available load balancing services. For production deployments, deploy a hardware load balancer prior to deploying OSA.

  • In the /etc/openstack_deploy/openstack_user_config.yml file, add the haproxy_hosts section with one or more infrastructure target hosts, for example:

    haproxy_hosts:
      123456-infra01:
        ip: 172.29.236.51
      123457-infra02:
        ip: 172.29.236.52
      123458-infra03:
        ip: 172.29.236.53
    

Making HAProxy highly-available

HAProxy will be deployed in a highly-available manner, by installing keepalived if multiple hosts are found in the inventory.

Note

A bug affects keepalived shipped by default with Ubuntu 14.04. You are probably affected if you have more than two HAProxy/keepalived nodes. If you are running a keepalived version < 1.2.8, you’ll encounter a bug when two (or more) backup hosts have the same priority. (cf. http://keepalived.org/changelog.html - 1.2.8 - Boon Ang’s fix). Please check/adapt your keepalived version and the priorities defined in your deployment.

To skip the deployment of keepalived along HAProxy when installing HAProxy on multiple hosts, edit the /etc/openstack_deploy/user_variables.yml by setting:

haproxy_use_keepalived: False

Otherwise, edit at least the following variables in user_variables.yml to make keepalived work:

haproxy_keepalived_external_vip_cidr: 192.168.0.4/25
haproxy_keepalived_internal_vip_cidr: 172.29.236.54/16
haproxy_keepalived_external_interface: br-flat
haproxy_keepalived_internal_interface: br-mgmt

haproxy_keepalived_internal_interface represents the interface on the deployed node where the keepalived master will bind the internal vip. By default the br-mgmt will be used.

haproxy_keepalived_external_interface represents the interface on the deployed node where the keepalived master will bind the external vip. By default the br-mgmt will be used.

haproxy_keepalived_external_vip_cidr represents the external vip (and its netmask) that will be used on keepalived master host.

haproxy_keepalived_internal_vip_cidr represents the internal vip (and its netmask) that will be used on keepalived master host.

Additional variables can be set to adapt keepalived in the deployed environment. Please refer to the user_variables.yml for more descriptions.

All the variables mentionned here before are used in the variable files vars/configs/keepalived_haproxy_master.yml and vars/configs/keepalived_haproxy_backup.yml to feed the keepalived role. More information can be found on the keepalived role documentation. You can use your own file by setting their path in your /etc/openstack_deploy/user_variables.yml:

haproxy_keepalived_vars_file:

Securing HAProxy communication with SSL certificates

The OpenStack-Ansible project provides the ability to secure HAProxy communications with self-signed or user-provided SSL certificates.

Refer to Securing services with SSL certificates for available configuration options.


Table Of Contents

Previous topic

Storage Policies

Next topic

Configuring Horizon (optional)

Project Source

This Page