<div dir="ltr"><div class="gmail_extra">Hi Samuel!</div><div class="gmail_extra"><br></div><div class="gmail_extra">Per your request, here's some feedback on the layer 7 proposal referenced below. Please let me know if by "comment is something missing there" you meant I should actually comment within the blueprint or wiki system instead of in this e-mail thread.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><ul><li>Are <span style="color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">L7Policy, </span><span style="color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">L7Rule, and </span><span style="color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">L7VipPolicyAssociation all new resources within the data model, or are any of these simply going to be implemented as additional fields to existing objects? (I'll try to produce a new diagram for y'all illustrating how these fit in with the existing data model, unless one of you has this already.)<br>
<br></span></li><li><span style="color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">I see the intent is to support L7 rules of the following types: "</span><span style="font-size:13px;background-color:rgb(245,245,245);color:rgb(51,51,51);font-family:Monaco,Menlo,Consolas,'Courier New',monospace;line-height:20px;white-space:pre-wrap">Hostname, Path, File Type, Header, Cookie" </span>Has there been discussion around supporting other types of L7 rules? (I ask mostly out of curiosity-- the list there actually covers the 90% use case for our customers just fine.)<br>
<br></li><li>Since the L7Rule object contains a position indicator, I assume, therefore, that a given L7Rule object cannot exist in more than one L7Policy, correct? Also, I assume that the first L7Rule added to an L7Policy becomes the rule at position 0 and that subsequent rules are added with incrementing positions. This is unless the position is specified, in which case, the rule is inserted into the policy list at the position specified, and all subsequent rule position indicators get incremented. Correct?<br>
<br></li><li>Shouldn't the L7Rule object also have a l7PolicyID attribute?<br><br></li><li>It is unclear from the proposal whether a given VIP can have multiple <span style="font-size:13px;background-color:rgb(245,245,245);color:rgb(51,51,51);font-family:Monaco,Menlo,Consolas,'Courier New',monospace;line-height:20px;white-space:pre-wrap">L7VipPolicyAssociation </span>objects associated with it. If not, then we've not really solved the problem of multiple back-end pools per VIP. If so, then the L7VipPolicyAssociation object is missing its own 'position' attribute (because order matters here, too!).<br>
<br></li><li>I assume any given pool can have multiple <span style="font-size:12.800000190734863px;background-color:rgb(245,245,245);color:rgb(51,51,51);font-family:Monaco,Menlo,Consolas,'Courier New',monospace;line-height:20px;white-space:pre-wrap">L7VipPolicyAssociations</span>. If this is not the case, then a given single pool can only be associated with one VIP.<br>
<br></li><li>There is currently no way to set a 'default' back-end pool in this proposal. Perhaps this could be solved by:<br></li><ul><li>Make 'DEFAULT' one of the actions possible for a L7VipPolicyAssociation</li>
<li>Any L7VipPolicyAssociation with an action of 'DEFAULT' would have a null position and null L7PolicyId.</li><li>We would need to enforce having only one L7VipPolicyAssociation object with a 'DEFAULT' action per VIP.</li>
</ul></ul></div><div class="gmail_extra"><br></div>Other than the last three points above, the L7Policy, L7Rule, and L7VipPolicyAssociation do essentially the same thing as the 'ACL' object in my proposal, albeit with more granularity in the objects themselves. (In our BLBv2 implementation, we have pretty loose rules around what can be specified in a given ACL, and allow haproxy to do syntax checking itself on the whole generated configuration file, returning an error and refusing to update a listener's in-production configuration until the error is resolved in the case where the user made an error on any given ACL.) I like that in this proposal, the model seems to enforce compliance with certain rule formats, which, presumably, could be syntax checked against what haproxy will allow without having to call haproxy directly.<div class="gmail_extra">
<br></div><div class="gmail_extra">The down-side of the above is that we start to enforce, at the model level, very haproxy-specific configuration terminology with this. This is fine, so long as load balancer vendors that want to write drivers for Neutron LBaaS are capable of translating haproxy-specific ACL language into whatever rules make sense for their appliance.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Having said the above, I don't see a way to expose a lot of L7 functionality and still be able to do syntax checking without choosing one particular configuration format in which rules can be specified (in our case, haproxy). I suppose we could invent our own pseudo rule language-- but why bother when haproxy has already done this, eh?</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">I'll take a look at the SSL stuff next, then the LoadBalancerInstance stuff...</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div>
<div class="gmail_extra">Stephen</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 11, 2014 at 5:26 AM, Samuel Bercovici <span dir="ltr"><<a href="mailto:SamuelB@radware.com" target="_blank">SamuelB@radware.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"><p class="MsoNormal"><span style="font-family:Cambria,serif">Please review the current work in progress and comment is something is missing there.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Cambria,serif">The logical load balancer API which is already addressed:<u></u><u></u></span></p>
<p style="margin-right:0in;margin-left:0.5in;margin-bottom:0.0001pt;vertical-align:baseline">
<u></u><span style="font-size:10pt;font-family:Symbol"><span>·<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span dir="LTR"></span><span style="font-family:Cambria,serif">Multiple pools per VIP (ie. “layer 7” support) -
<a href="https://blueprints.launchpad.net/neutron/+spec/lbaas-l7-rules" target="_blank">https://blueprints.launchpad.net/neutron/+spec/lbaas-l7-rules</a>.
<u></u><u></u></span></p>
<p style="margin-right:0in;margin-left:0.5in;margin-bottom:0.0001pt;vertical-align:baseline"></p></blockquote></div><br><br><br clear="all"><div><br></div>-- <br><span></span>Stephen Balukoff
<br>Blue Box Group, LLC
<br>(800)613-4305 x807
</div></div>