<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.m7254127914907924311gmail-hoenzb
{mso-style-name:m_7254127914907924311gmail-hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Will the same DB be maintained or will the LBaaS DB be moved to that of Octavia. I am really concerned about this and I feel that it will cause production problems.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Kevin Benton <kevin@benton.pub><br>
<b>Reply-To: </b>OpenStack List <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Wednesday, November 9, 2016 at 11:43 PM<br>
<b>To: </b>OpenStack List <openstack-dev@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The people working on the migration are ensuring API compatibility and are even leaving in a shim on the Neutron side for some time so you don't even have to change endpoints initially. It should be a seamless change.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Nov 9, 2016 at 12:28 PM, Fox, Kevin M <<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Tahoma;color:black">Just please don't make this a lbv3 thing that completely breaks compatibility of existing lb's yet again. If its just an "point url endpoint from thing like x to thing like y"
in one place, thats ok. I still have v1 lb's in existence though I have to deal with and a backwards incompatible v3 would just cause me to abandon lbaas all together I think as it would show the lbaas stuff is just not maintainable.<br>
<br>
Thanks,<br>
Kevin<o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div id="m_7254127914907924311divRpF44932">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;font-family:Tahoma;color:black">From:</span></b><span style="font-size:10.0pt;font-family:Tahoma;color:black"> Armando M. [<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>]<br>
<b>Sent:</b> Wednesday, November 09, 2016 8:05 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black">On 9 November 2016 at 05:50, Gary Kotton <<a href="mailto:gkotton@vmware.com" target="_blank">gkotton@vmware.com</a>> wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><span style="color:black">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><span class="m7254127914907924311gmail-hoenzb"><span style="color:#888888">Gary</span></span><span style="color:black"><o:p></o:p></span></p>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><a href="http://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html" target="_blank">http://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span style="color:black"><br>
On 11/8/16, 1:36 AM, "Michael Johnson" <<a href="mailto:johnsomor@gmail.com" target="_blank">johnsomor@gmail.com</a>> wrote:<br>
<br>
Ocata LBaaS retrospective and next steps recap<br>
----------------------------------------------------------------------<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" target="_blank">
https://specs.openstack.org/openstack/neutron-specs/specs/newton/kill-neutron-lbaas.html</a><br>
[2] <a href="https://etherpad.openstack.org/p/ocata-neutron-octavia-lbaas-session" target="_blank">
https://etherpad.openstack.org/p/ocata-neutron-octavia-lbaas-session</a><br>
[3] <a href="https://specs.openstack.org/openstack/neutron-specs/specs/mitaka/neutron-flavor-framework-templates.html" target="_blank">
https://specs.openstack.org/openstack/neutron-specs/specs/mitaka/neutron-flavor-framework-templates.html</a><br>
[4] <a href="https://specs.openstack.org/openstack/neutron-specs/specs/liberty/neutron-flavor-framework.html" target="_blank">
https://specs.openstack.org/openstack/neutron-specs/specs/liberty/neutron-flavor-framework.html</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>