<div dir="ltr">Hi Brandon!<div><br></div><div>Please see inline..</div><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 28, 2014 at 12:01 PM, Brandon Logan <span dir="ltr"><<a href="mailto:brandon.logan@rackspace.com" target="_blank">brandon.logan@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Vijay,<br>
<div class=""><br>
On Tue, 2014-05-27 at 16:27 -0700, Vijay B wrote:<br>
> Hi Brandon,<br>
><br>
><br>
> The current reviews of the schema itself are absolutely valid and<br>
> necessary, and must go on. However, the place of implementation of<br>
> this schema needs to be clarified. Rather than make any changes<br>
> whatsoever to the existing neutron db schema for LBaaS, this new db<br>
> schema outlined needs to be implemented for a separate LBaaS core<br>
> service.<br>
><br>
</div>Are you suggesting a separate lbaas database from the neutron database?<br>
If not, then I could use some clarification. If so, I'd advocate against<br>
that right now because there's just too many things that would need to<br>
be changed. Later, when LBaaS becomes its own service then yeah that<br>
will need to happen.<br></blockquote><div><br></div><div>v> Ok, so as I understand it, in this scheme, there is no new schema or db, there will be a new set of tables resident in neutron_db schema itself, alongside legacy lbaas tables. Let's consider a rough view of the implementation.</div>
<div><br></div><div>Layer 1 - We'll have a new lbaas v3.0 api in neutron, with the current lbaas service plugin having to support it in addition to the legacy lbaas extensions that it already supports. We'll need to put in new code anyway that will process the v3.0 lbaas api no matter what our approach is.</div>
<div>Layer 2 - Management code that will take care of updating the db with entities in pending_create, then invoking the right provider driver, choosing/scheduling the plugin drivers or the agent drivers, invoking them, getting the results, and updating the db.</div>
<div>Layer 3 - The drivers themselves (either plugin drivers (like the HAProxy namespace driver/Netscaler) or plugin drivers + agent drivers).</div><div><br></div><div>While having the new tables sit alongside the legacy tables is one way to implement the changes, I don't see how this approach leads to a lesser amount of changes overall. Layer 2 above will be the major place where changes can be complicated. Also, it will be confusing to have two sets of lbaas tables in the same schema.</div>
<div><br></div><div>I don't want a separate lbaas database under neutron, and neither do I want it within neutron. I'm not suggesting that we create a db schema alone, I'm saying we must build it with the new LBaaS service (just like neutron itself when it got created). If we don't do this now, we'll end up reimplementing the logic implemented in neutron for the new lbaas v3.0 API all over again for the new core LBaaS service. We'd rather do it in the new one in one effort.<br>
</div><div><br></div><div>I could be missing some constraints that drive taking the former approach - please help me understand those - I don't want to be discounting any one approach without thorough consideration. Right now, it looks to me like this approach is being taken only to accommodate the HAProxy namespace driver. Really that is the only driver which seems to be very intertwined with neutron in the way it uses namespaces.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="">><br>
> What we should be providing in neutron is a switch (a global conf)<br>
> that can be set to instruct neutron to do one of two things:<br>
><br>
><br>
> 1. Use the existing neutron LBaaS API, with the backend being the<br>
> existing neutron LBaaS db schema. This is the status quo.<br>
> 2. Use the existing neutron LBaaS API, with the backend being the new<br>
> LBaaS service. This will invoke calls not to neutron's current LBaaS<br>
> code at all, rather, it will call into a new set of proxy "backend"<br>
> code in neutron that will translate the older LBaaS API calls into the<br>
> newer REST calls serviced by the new LBaaS service, which will write<br>
> down these details accordingly in its new db schema. As long as the<br>
> request and response objects to legacy neutron LBaaS calls are<br>
> preserved as is, there should be no issues. Writing unit tests should<br>
> also be comparatively more straightforward, and old functional tests<br>
> can be retained, and newer ones will not clash with legacy code.<br>
> Legacy code itself will work, having not been touched at all. The<br>
> blueprint for the db schema that you have referenced<br>
> (<a href="https://review.openstack.org/#/c/89903/5/specs/juno/lbaas-api-and-objmodel-improvement.rst" target="_blank">https://review.openstack.org/#/c/89903/5/specs/juno/lbaas-api-and-objmodel-improvement.rst</a>) should be implemented for this new LBaaS service, post reviews.<br>
><br>
</div>I think the point of this blueprint is to get the API and object model<br>
less confusing for the Neutron LBaaS service plugin. I think it's too<br>
early to create an LBaaS service because we have not yet cleaned up the<br>
tight integration points between Neutron LBaaS and LBaaS. Creating a<br>
new service would require only API interactions between Neutron and this<br>
LBaaS service, which currently is not possible due to these tight<br>
integration points.<br></blockquote><div><br></div><div>v> The tight integration points between LBaaS and neutron that I see are:</div><div><br></div><div>1. The usage of namespaces.</div><div>2. L2 and L3 plumbing within the namespaces and tracking them in the neutron and lbaas tables,</div>
<div>3. Plugin driver and agent driver scheduling framework/mechanism for LB drivers.</div><div>4. The way drivers directly update the neutron db, which I think makes for a lack of clear functional demarcation.</div><div>
<br></div><div>Regardless of how we use the new API and db model, will namespaces be used? If they still need to be supported, the tight integration isn't going to go anywhere. </div><div><br></div><div>This is why I think it will be best to keep the legacy drivers within neutron, and not give an option to newer deployments to use that concurrently with the new lbaas core service. The changes will be lesser this way because we won't touch legacy code.<br>
</div><div><br></div><div>While I fully understand that we're trying to change the way we look at the lbaas deployments, and the db object model is an effort towards that, we need to ensure that the execution is kept elegant as well. For drivers for lb solutions like f5 or Netscaler, these pain points can be done away with because they do their own network provisioning and we keep track of them only to clean up (especially for virtual appliance solutions).</div>
<div><br></div><div>It will however mean that we'll have the additional task of implementing the new core service before we can use the new db object model. I say we should just go for that effort and make it happen.<br>
</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><br>
><br>
> The third option would be to turn off neutron LBaaS API, and use the<br>
> new LBaaS core service directly, but for this we can simply disable<br>
> neutron lbaas, and don't need a config parameter in neutron.<br>
><br>
><br>
> Implementing this db schema within neutron instead will be not just<br>
> complicated, but a huge effort that will go waste in future once the<br>
> new LBaaS service is implemented. Also, migration will unnecessarily<br>
> retain the same steps needed to go from legacy neutron LBaaS to the<br>
> new core LBaaS service in this approach (twice, in succession) in case<br>
> for any reason the version goes from legacy neutron LBaaS -> new<br>
> neutron LBaaS -> new LBaaS core service.<br>
</div>I totally agree that this is technical debt, but I believe it is the<br>
best option we have right now since LBaaS needs to live in the Neutron<br>
code and process because of the tight integration points. Since this<br>
object model refactor has been slated for Juno, and these tight<br>
integration points may or may not be cleaned up by Juno, staying within<br>
Neutron seems to be the best option right now.<br></blockquote><div><br></div><div>v> As I described above, I think the tight integration points are best kept in legacy code and not carried over to the new implementation. The cleanest way to do it would be to clearly demarcate neutron related operations (L2/L3) from LBaaS. But I am keen to get your views on what the difficult integration points are so that I get a better understanding of the motivations behind keeping the new tables in neutron.</div>
<div><br></div><div><br></div><div>Regards,</div><div>Vijay</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5">><br>
><br>
> Going forward, the legacy neutron LBaaS API can be deprecated, and the<br>
> new API that directly contacts the new LBaaS core service can be used.<br>
><br>
><br>
> We have discussed the above architecture previously, but outside of<br>
> the ML, and a draft of the blueprint for this new LBaaS core service<br>
> is underway, and is a collation of all the discussions among a large<br>
> number of LBaaS engineers including yourself during the summit - I<br>
> will be posting it for review within a couple of days, as planned.<br>
><br>
><br>
><br>
><br>
> Regards,<br>
> Vijay<br>
><br>
><br>
> On Tue, May 27, 2014 at 12:32 PM, Brandon Logan<br>
> <<a href="mailto:brandon.logan@rackspace.com">brandon.logan@rackspace.com</a>> wrote:<br>
> Referencing this blueprint:<br>
> <a href="https://review.openstack.org/#/c/89903/5/specs/juno/lbaas-api-and-objmodel-improvement.rst" target="_blank">https://review.openstack.org/#/c/89903/5/specs/juno/lbaas-api-and-objmodel-improvement.rst</a><br>
><br>
> Anyone who has suggestions to possible issues or can answer<br>
> some of<br>
> these questions please respond.<br>
><br>
><br>
> 1. LoadBalancer to Listener relationship M:N vs 1:N<br>
> The main reason we went with the M:N was so IPv6 could use the<br>
> same<br>
> listener as IPv4. However this can be accomplished by the<br>
> user just<br>
> creating a second listener and pool with the same<br>
> configuration. This<br>
> will end up being a bad user experience when the listener and<br>
> pool<br>
> configuration starts getting complex (adding in TLS, health<br>
> monitors,<br>
> SNI, etc). A good reason to not do the M:N is because the<br>
> logic on might<br>
> get complex when dealing with status. I'd like to get<br>
> people's opinions<br>
> on this on whether we should do M:N or just 1:N. Another<br>
> option, is to<br>
> just implement 1:N right now and later implement the M:N in<br>
> another<br>
> blueprint if it is decided that the user experience suffers<br>
> greatly.<br>
><br>
> My opinion: I like the idea of leaving it to another blueprint<br>
> to<br>
> implement. However, we would need to watch out for any major<br>
> architecture changes in the time itis not implemented that<br>
> could make<br>
> this more difficult than what it needs to be.<br>
><br>
> 2. Pool to Health Monitor relationship 1:N vs 1:1<br>
> Currently, I believe this is 1:N however it was suggested to<br>
> deprecate<br>
> this in favor of 1:1 by Susanne and Kyle agreed. Are there<br>
> any<br>
> objections to channging to 1:1?<br>
><br>
> My opinion: I'm for 1:1 as long as there aren't any major<br>
> reasons why<br>
> there needs to be 1:N.<br>
><br>
> 3. Does the Pool object need a status field now that it is a<br>
> pure<br>
> logical object?<br>
><br>
> My opinion: I don't think it needs the status field. I think<br>
> the<br>
> LoadBalancer object may be the only thing that needs a status,<br>
> other<br>
> than the pool members for health monitoring. I might be<br>
> corrected on<br>
> this though.<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
</div></div></blockquote></div><br></div></div>