[openstack-dev] [openstack-ansible] LBaaSv2 / Octavia support

Fox, Kevin M Kevin.Fox at pnnl.gov
Tue Jan 26 20:01:51 UTC 2016

I believe lbaas v1 and v2 are different then every other openstack api version in that while you can run v1 and v2 at the same time but they are completely different systems that just share a name. A lb created in v1 doesn't show up in v2 or vis a versa. But being able to enable both at once gives users a migration path. If you don't do this, all their lb's will just disappear when going to octavia. :/

From: Major Hayden [major at mhtx.net]
Sent: Tuesday, January 26, 2016 11:40 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstack-ansible] LBaaSv2 / Octavia support

Hash: SHA256

Hey there,

After poking around a bit at LBaaS in OpenStack-Ansible, I discovered that LBaaS v2[1] was available in Liberty and Mitaka.  At first, I thought it involved switching agents from neutron-lbaas-agent to neutron-lbaasv2-agent, but things are a little bit more involved.

LBaaS v1 works by configuring HAProxy within agent containers.  However, LBaaS v2 creates virtual machines to hold load balancers and attaches those virtual machines to the appropriate subnet.  It offers some active/passive failover capabilities, but a single load balancer is the default.  One of the biggest benefits of v2 is that you can put multiple listeners on the same load balancer.  For example, you could host a website on ports 80 and 443 on the same VIP and floating IP address.

The provisioning would look like this for v2:

  * Create a load balancer
  * Create a listener
  * Create a pool
  * Create members in the pool

Many thanks to Brandon Logan (blogan) for sitting down with me this morning to go over it.  It looks like we'd need to do the following to get LBaaS v2 into OpenStack-Ansible:

  1) Build a new container to hold an Octavia venv

  2) Run four new daemons in that container:

    * octavia-api
    * octavia-worker
    * octavia-housekeeping
    * octavia-health-manager

  3) Ensure that neutron-lbaas-agent isn't running at the same time as the octavia stack

  4) Create a new RabbitMQ queue for octavia along with credentials

  5) Create a new MariaDB database for octavia along with credentials

At this moment, LBaaS v2 panels are planned for Horizon in Mitaka, but they're not available as of right now.  It seems like a spec would be necessary for this effort.

Are there users/deployers who would like to have this feature available?

[1] http://docs.openstack.org/developer/devstack/guides/devstack-with-lbaas-v2.html

- --
Major Hayden
Version: GnuPG v2


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list