<div dir="ltr">German,<div><br></div><div>First of all extension list looks lbaas-centric right now.</div><div>Secondly, TLS and L7 are such APIs which objects should not require loadbalancer or flavor to be created (like pool or healthmonitor that are pure db objects).</div>
<div>Only when you associate those objects with loadbalancer (or its child objects), driver may tell if it supports them. <br></div><div>Which means that you can't really turn those on or off, it's a generic API.<br>
</div><div>From user perspective flavor description (as interim) is sufficient to show what is supported by drivers behind the flavor.</div><div><br></div><div>Also, I think that turning "extensions" on/off is a bit of side problem to a service specification, so let's resolve it separately.</div>
<div><br></div><div><br></div><div>Thanks,</div><div>Eugene.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 4, 2014 at 3:07 AM, Eichberger, German <span dir="ltr"><<a href="mailto:german.eichberger@hp.com" target="_blank">german.eichberger@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am actually a bit bummed that Extensions are postponed. In LBaaS we are working hard on L7 and TLS extensions which we (the operators) like to switch on and off with different flavors...<br>
<span class="HOEnZb"><font color="#888888"><br>
German<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: Kyle Mestery [mailto:<a href="mailto:mestery@noironetworks.com">mestery@noironetworks.com</a>]<br>
Sent: Thursday, July 03, 2014 2:00 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [neutron] Flavor framework: Conclusion<br>
<br>
Awesome, thanks for working on this Eugene and Mark! I'll still leave an item on Monday's meeting agenda to discuss this, hopefully it can be brief.<br>
<br>
Thanks,<br>
Kyle<br>
<br>
On Thu, Jul 3, 2014 at 10:32 AM, Eugene Nikanorov <<a href="mailto:enikanorov@mirantis.com">enikanorov@mirantis.com</a>> wrote:<br>
> Hi,<br>
><br>
> Mark and me has spent some time today discussing existing proposals<br>
> and I think we got to a consensus.<br>
> Initially I had two concerns about Mark's proposal which are<br>
> - extension list attribute on the flavor<br>
> - driver entry point on the service profile<br>
><br>
> The first idea (ext list) need to be clarified more as we get more<br>
> drivers that needs it.<br>
> Right now we have FWaaS/VPNaaS which don't have extensions at all and<br>
> we have LBaaS where all drivers support all extensions.<br>
> So extension list can be postponed until we clarify how exactly we<br>
> want this to be exposed to the user and how we want it to function on<br>
> implementation side.<br>
><br>
> Driver entry point which implies dynamic loading per admin's request<br>
> is a important discussion point (at least, previously this idea<br>
> received negative opinions from some cores) We'll implement service<br>
> profiles, but this exact aspect of how driver is specified/loadede<br>
> will be discussed futher.<br>
><br>
> So based on that I'm going to start implementing this.<br>
> I think that implementation result will allow us to develop in<br>
> different directions (extension list vs tags, dynamic loading and<br>
> such) depending on more information about how this is utilized by deployers and users.<br>
><br>
> Thanks,<br>
> Eugene.<br>
><br>
><br>
><br>
> On Thu, Jul 3, 2014 at 5:57 PM, Susanne Balle <<a href="mailto:sleipnir012@gmail.com">sleipnir012@gmail.com</a>> wrote:<br>
>><br>
>> +1<br>
>><br>
>><br>
>> On Wed, Jul 2, 2014 at 10:12 PM, Kyle Mestery<br>
>> <<a href="mailto:mestery@noironetworks.com">mestery@noironetworks.com</a>><br>
>> wrote:<br>
>>><br>
>>> We're coming down to the wire here with regards to Neutron BPs in<br>
>>> Juno, and I wanted to bring up the topic of the flavor framework BP.<br>
>>> This is a critical BP for things like LBaaS, FWaaS, etc. We need<br>
>>> this work to land in Juno, as these other work items are dependent on it.<br>
>>> There are still two proposals [1] [2], and after the meeting last<br>
>>> week [3] it appeared we were close to conclusion on this. I now see<br>
>>> a bunch of comments on both proposals.<br>
>>><br>
>>> I'm going to again suggest we spend some time discussing this at the<br>
>>> Neutron meeting on Monday to come to a closure on this. I think<br>
>>> we're close. I'd like to ask Mark and Eugene to both look at the<br>
>>> latest comments, hopefully address them before the meeting, and then<br>
>>> we can move forward with this work for Juno.<br>
>>><br>
>>> Thanks for all the work by all involved on this feature! I think<br>
>>> we're close and I hope we can close on it Monday at the Neutron meeting!<br>
>>><br>
>>> Kyle<br>
>>><br>
>>> [1] <a href="https://review.openstack.org/#/c/90070/" target="_blank">https://review.openstack.org/#/c/90070/</a><br>
>>> [2] <a href="https://review.openstack.org/102723" target="_blank">https://review.openstack.org/102723</a><br>
>>> [3]<br>
>>> <a href="http://eavesdrop.openstack.org/meetings/networking_advanced_services" target="_blank">http://eavesdrop.openstack.org/meetings/networking_advanced_services</a><br>
>>> /2014/networking_advanced_services.2014-06-27-17.30.log.html<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>
>> _______________________________________________<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>
> _______________________________________________<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>