<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="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@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","serif";}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Eugene,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My understanding of the flavor framework is the following:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Say I have an F5 load balancer supporting TLS, L7, and standard loadbalancing. For business reasons I want to offer a Bronze (“standard load balancing”), silver
(“Standard” + TLS), and gold (silver + L7) at different price points. What I absolutely don’t want is users getting Bronze load balancers and using TLS and L7 on them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My understanding of the flavor framework was that by specifying (or not specifying) extensions I can create a diverse offering meeting my business needs. The
way you are describing it the user selects, say a bronze flavor, and the system might or might not put it on a load balancer with TLS. This will lead to users asking for 10 Bronze load balancers test them and discard the ones which don’t support TLS – this
is something as a provider I would like to avoid.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Furthermore, in your example, say if I don’t have any TLS capable load balancers left and the user requests them it will take until scheduling for the user
to discover that we can’t accommodate him.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I can live with extensions coming in a later release but I am confused how your design will support above use case.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">German<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Eugene Nikanorov [mailto:enikanorov@mirantis.com]
<br>
<b>Sent:</b> Thursday, July 03, 2014 10:10 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [neutron] Flavor framework: Conclusion<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">German,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">First of all extension list looks lbaas-centric right now.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">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).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Only when you associate those objects with loadbalancer (or its child objects), driver may tell if it supports them. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Which means that you can't really turn those on or off, it's a generic API.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">From user perspective flavor description (as interim) is sufficient to show what is supported by drivers behind the flavor.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Also, I think that turning "extensions" on/off is a bit of side problem to a service specification, so let's resolve it separately.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Eugene.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Jul 4, 2014 at 3:07 AM, Eichberger, German <<a href="mailto:german.eichberger@hp.com" target="_blank">german.eichberger@hp.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">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 style="color:#888888"><br>
<span class="hoenzb">German</span></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><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><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>