From 6a61321a0afe193afa46dfef38b9305a41060605 Mon Sep 17 00:00:00 2001 From: Major Hayden Date: Thu, 19 May 2016 07:52:26 -0500 Subject: [PATCH] Add docs for LBaaSv2 Horizon panels This documentation explains how to enabe LBaaSv2 panels in Horizon in the Newton and Mitaka releases. Change-Id: I7c925e5d10b6f6f6219e764876e319927809628f --- .../configure-network-services.rst | 60 ++++++------------- 1 file changed, 17 insertions(+), 43 deletions(-) diff --git a/doc/source/install-guide/configure-network-services.rst b/doc/source/install-guide/configure-network-services.rst index 8a4ca77b37..a88f120479 100644 --- a/doc/source/install-guide/configure-network-services.rst +++ b/doc/source/install-guide/configure-network-services.rst @@ -60,49 +60,21 @@ dict. 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. +The `neutron-lbaas`_ plugin for neutron provides a software load balancer +service and can direct traffic to multiple servers. The service runs as an +agent and it manages `HAProxy`_ configuration files and daemons. -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. +The Newton release contains only the LBaaS v2 API. For more details about +transitioning from LBaaS v1 to v2, review the :ref:`lbaas-special-notes` +section below. -.. note:: - - Horizon panels for LBaaS v2 are not yet available. +Deployers can make changes to the LBaaS default configuration options via the +``neutron_lbaas_agent_ini_overrides`` dictionary. Review the documentation on +the `conf override`_ mechanism for more details. +.. _neutron-lbaas: https://wiki.openstack.org/wiki/Neutron/LBaaS .. _HAProxy: http://www.haproxy.org/ -Deploying LBaaS v1 ------------------- - -.. note:: - - We do not recommend LBaaS v1 for new deployments as it is deprecated as of Liberty. - -#. Add the LBaaS v1 plugin to the ``neutron_plugin_base`` variable - in ``/etc/openstack_deploy/user_variables.yml``: - - .. code-block:: yaml - - 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: - - .. code-block:: console - - # cd /opt/openstack-ansible/playbooks - # openstack-ansible os-neutron-install.yml - # openstack-ansible os-horizon-install.yml - Deploying LBaaS v2 ------------------ @@ -119,24 +91,26 @@ Deploying LBaaS v2 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: +#. Run the neutron and horizon playbooks to deploy the LBaaS v2 agent and + enable the LBaaS v2 panels in horizon: .. code-block:: console # cd /opt/openstack-ansible/playbooks # openstack-ansible os-neutron-install.yml + # openstack-ansible os-horizon-install.yml + +.. _lbaas-special-notes Special notes about LBaaS ------------------------- -The LBaaS default configuration options are changed through the -`conf override`_ mechanism using the ``neutron_lbaas_agent_ini_overrides`` -dict. +**LBaaS v1 was deprecated in the Mitaka release and is not available in the +Newton release.** LBaaS v1 and v2 agents are unable to run at the same time. If you switch LBaaS v1 to v2, the v2 agent is the only agent running. The LBaaS v1 agent stops along with any load balancers provisioned under the v1 agent. -The same is true if you choose 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. You need