<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 9 November 2016 at 05:50, Gary Kotton <span dir="ltr"><<a href="mailto:gkotton@vmware.com" target="_blank">gkotton@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
What about neutron-lbaas project? Is this project still alive and kicking to the merge is done or are we going to continue to maintain it? I feel like we are between a rock and a hard place here. LBaaS is in production and it is not clear the migration process. Will Octavia have the same DB models as LBaaS or will there be a migration?<br>
Sorry for the pessimism but I feel that things are very unclear and that we cannot even indicate to our community/consumers what to use/expect.<br>
Thanks<br>
<span class="gmail-HOEnZb"><font color="#888888">Gary<br></font></span></blockquote><div><br></div><div><a href="http://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html">http://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-HOEnZb"><font color="#888888">
</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
On 11/8/16, 1:36 AM, "Michael Johnson" <<a href="mailto:johnsomor@gmail.com">johnsomor@gmail.com</a>> wrote:<br>
<br>
Ocata LBaaS retrospective and next steps recap<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
This session lightly touched on the work in the newton cycle, but<br>
primarily focused on planning for the Ocata release and the LBaaS spin<br>
out of neutron and merge into the octavia project [1]. Notes were<br>
captured on the etherpad [1].<br>
<br>
The focus of work for Ocata in neutron-lbaas and octavia will be on<br>
the spin out/merge and not new features.<br>
<br>
Work has started on merging neutron-lbaas into the octavia project<br>
with API sorting/pagination, quota support, keystone integration,<br>
neutron-lbaas driver shim, and documentation updates. Work is still<br>
needed for policy support, the API shim to handle capability gaps<br>
(example: stats are by listener in octavia, but by load balancer in<br>
neturon-lbaas), neutron api proxy, a database migration script from<br>
the neutron database to the octavia database for existing non-octavia<br>
load balancers, and adding the "bug for bug" neutron-lbaas v2 API to<br>
the octavia API server.<br>
<br>
The room agreed that since we will have a shim/proxy in neutron for<br>
some time, updating the OpenStack client can be deferred to a future<br>
cycle.<br>
<br>
There is a lot of concern about Ocata being a short cycle and the<br>
amount of work to be done. There is hope that additional resources<br>
will help out with this task to allow us to complete the spin<br>
out/merge for Ocata.<br>
<br>
We discussed the current state of the active/active topology patches<br>
and agreed that it is unlikely this will merge in Ocata. There are a<br>
lot of open comments and work to do on the patches. It appears that<br>
these patches may have been created against an old release and require<br>
significant updating.<br>
<br>
Finally there was a question about when octavia would implement<br>
metadata tags. When we dug into the need for the tags we found that<br>
what was really wanted is a full implementation of the flavors<br>
framework [3] [4]. Some vendors expressed interest in finishing the<br>
flavors framework for Octavia.<br>
<br>
Thank you to everyone that participated in our design session and etherpad.<br>
<br>
Michael<br>
<br>
[1] <a href="https://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html" rel="noreferrer" target="_blank">https://specs.openstack.org/<wbr>openstack/neutron-specs/specs/<wbr>newton/kill-neutron-lbaas.html</a><br>
[2] <a href="https://etherpad.openstack.org/p/ocata-neutron-octavia-lbaas-session" rel="noreferrer" target="_blank">https://etherpad.openstack.<wbr>org/p/ocata-neutron-octavia-<wbr>lbaas-session</a><br>
[3] <a href="https://specs.openstack.org/openstack/neutron-specs/specs/mitaka/neutron-flavor-framework-templates.html" rel="noreferrer" target="_blank">https://specs.openstack.org/<wbr>openstack/neutron-specs/specs/<wbr>mitaka/neutron-flavor-<wbr>framework-templates.html</a><br>
[4] <a href="https://specs.openstack.org/openstack/neutron-specs/specs/liberty/neutron-flavor-framework.html" rel="noreferrer" target="_blank">https://specs.openstack.org/<wbr>openstack/neutron-specs/specs/<wbr>liberty/neutron-flavor-<wbr>framework.html</a><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>