[openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap
johnsomor at gmail.com
Mon Nov 7 23:36:10 UTC 2016
Ocata LBaaS retrospective and next steps recap
This session lightly touched on the work in the newton cycle, but
primarily focused on planning for the Ocata release and the LBaaS spin
out of neutron and merge into the octavia project . Notes were
captured on the etherpad .
The focus of work for Ocata in neutron-lbaas and octavia will be on
the spin out/merge and not new features.
Work has started on merging neutron-lbaas into the octavia project
with API sorting/pagination, quota support, keystone integration,
neutron-lbaas driver shim, and documentation updates. Work is still
needed for policy support, the API shim to handle capability gaps
(example: stats are by listener in octavia, but by load balancer in
neturon-lbaas), neutron api proxy, a database migration script from
the neutron database to the octavia database for existing non-octavia
load balancers, and adding the "bug for bug" neutron-lbaas v2 API to
the octavia API server.
The room agreed that since we will have a shim/proxy in neutron for
some time, updating the OpenStack client can be deferred to a future
There is a lot of concern about Ocata being a short cycle and the
amount of work to be done. There is hope that additional resources
will help out with this task to allow us to complete the spin
out/merge for Ocata.
We discussed the current state of the active/active topology patches
and agreed that it is unlikely this will merge in Ocata. There are a
lot of open comments and work to do on the patches. It appears that
these patches may have been created against an old release and require
Finally there was a question about when octavia would implement
metadata tags. When we dug into the need for the tags we found that
what was really wanted is a full implementation of the flavors
framework  . Some vendors expressed interest in finishing the
flavors framework for Octavia.
Thank you to everyone that participated in our design session and etherpad.
More information about the OpenStack-dev