Open Stack

Hi Kevin,

On Tue, 2016-01-26 at 19:48 +0000, Kevin Carter wrote:
> Seems like a sensible change however I'd love to see it written up as a spec. Also do we know if there are any scenario tests in tempest for octavia or would we need to develop them/something?

There aren't any tempest tests specific to Octavia right now but they
are being worked on.  We've been using the tempest tests written for
neutron-lbaas for this and its been okay but it leaves many gaps because
neutron-lbaas tests should not be aware of how a driver implements what
it does.  Tempest tests just for octavia would fill in all those gaps
and make the product much more stable.

There is an effort going on to create the tempest tests right now
though.  I hope we can get some in by M3 but its uncertain right now.

>  
> 
> As for adding Octavia as a new service within OpenStack Ansible this makes sense. Another approach may be to add octavia to the existing neutron-agent container which would making coordinating some of the services easier while ensuring the service deployment is simpler but that has isolation and segmentation drawback so i have no strong opinions on whats best. 
> 
> I personally think it'd be great to see this feature in OSA and I look forward to reviewing the spec.
> 
> --
> 
> Kevin Carter
> IRC: cloudnull
> 
> 
> ________________________________________
> From: Major Hayden <major at mhtx.net>
> Sent: Tuesday, January 26, 2016 1:40 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [openstack-ansible] LBaaSv2 / Octavia support
> 
> 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
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Thanks,
Brandon