
I think that docs will be better if the FWaaS, LBaaS and the VPNaaS be childs of the parent "Configuring the Network Services" instead of all be childs of "Deployment configuration". When I suggested the merge of all files in one didn't notice the existence of doctree, which I think its better. Change-Id: I9828ad579b9bc572a8cd6b6df700cab8a626506c
2.9 KiB
Home OpenStack-Ansible Installation Guide
Load Balancing Service (Optional)
OpenStack-Ansible currently provides the OpenStack Neutron LBaaS service using HAProxy as the load balancer. LBaaS has two implementations available: v1 and v2.
Both implementations use agents that manage HAProxy daemons. However, LBaaS v1 has a limitation of one port per load balancer. LBaaS v2 allows for multiple ports (called listeners) per load balancer.
Note
Horizon panels for LBaaS v2 are not yet available.
Deploying LBaaS v1
Note
LBaaS v1 was deprecated during the Liberty release and is not recommended for new deployments.
Start by adding the LBaaS v1 plugin to the
neutron_plugin_base
variable within/etc/openstack_deploy/user_variables.yml
.neutron_plugin_base: - router - metering - lbaas
Ensure that
neutron_plugin_base
includes all of the plugins that you want to deploy with Neutron in addition to the LBaaS plugin.Run the Neutron and Horizon playbooks to deploy the LBaaS v1 agent and enable the LBaaS panels in Horizon.
# cd /opt/openstack-ansible/playbooks # openstack-ansible os-neutron-install.yml # openstack-ansible os-horizon-install.yml
Deploying LBaaS v2
Start by adding the LBaaS v2 plugin to the
neutron_plugin_base
variable within/etc/openstack_deploy/user_variables.yml
.neutron_plugin_base: - router - metering - lbaasv2
Ensure that
neutron_plugin_base
includes all of the plugins that you want to deploy with Neutron in addition to the LBaaS plugin.Run the Neutron playbook to deploy the LBaaS v2 agent:
# cd /opt/openstack-ansible/playbooks # openstack-ansible os-neutron-install.yml
Special notes about LBaaS
The LBaaS default configuration options may be changed through the conf
override mechanism using the
neutron_lbaas_agent_ini_overrides
dict.
LBaaS v1 and v2 agents cannot run at the same time. If a deployer switches from LBaaS v1 to v2, the v2 agent will be the only agent running. The LBaaS v1 agent will be stopped along with any load balancers provisioned under the v1 agent. The same is true if a deployer chooses to move from LBaaS v2 to v1.
Load balancers are not migrated between LBaaS v1 and v2 automatically. Each implementation has different code paths and database tables. Deployers will need to manually delete load balancers, pools, and members before switching LBaaS versions. Those objects will need to be re-created afterwards.