<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>I agree it may be odd, but is that a strong argument? To me, following RESTful style/constructs is the main thing to consider. If people can specify everything in the parent resource then let them (i.e. single call). If they want to specify at a more granular
level then let them do that too (i.e. multiple calls). At the end of the day the API user can choose the style they want.</div>
<div><br>
</div>
<div>
<div>Cheers,</div>
<div style="font-family: Calibri, sans-serif; "><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">--Jorge</font></font></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Youcef Laribi <<a href="mailto:Youcef.Laribi@citrix.com">Youcef.Laribi@citrix.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, April 30, 2014 1:35 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Neutron][LBaaS]Conforming to Open Stack API style in LBaaS<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1388261051;
mso-list-type:hybrid;
mso-list-template-ids:-196206992 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Sam,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I think it’s important to keep the Neutron API style consistent. It would be odd if LBaaS uses a different style than the rest of the Neutron APIs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Youcef<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "> Samuel Bercovici [<a href="mailto:SamuelB@Radware.com">mailto:SamuelB@Radware.com</a>]
<br>
<b>Sent:</b> Wednesday, April 30, 2014 10:59 AM<br>
<b>To:</b> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
<b>Subject:</b> [openstack-dev] [Neutron][LBaaS]Conforming to Open Stack API style in LBaaS<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">During the last few days I have looked into the different LBaaS API proposals.<o:p></o:p></p>
<p class="MsoNormal">I have also looked on the API style used in Neutron. I wanted to see how Neutron APIs addressed “tree” like object models.<o:p></o:p></p>
<p class="MsoNormal">Follows my observation:<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><!--[if !supportLists]--><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">Security groups - <a href="http://docs.openstack.org/api/openstack-network/2.0/content/security-groups-ext.html">http://docs.openstack.org/api/openstack-network/2.0/content/security-groups-ext.html</a>)
– <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<!--[if !supportLists]--><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black"><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroupRules_v2.0_security-group-rules_security-groups-ext.html" title="List security group rules"><span style="font-size: 10pt; font-family: 'Courier New'; ">security-group-rules</span></a>
are children of <a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroups_v2.0_security-groups_security-groups-ext.html" title="List security groups">
<span style="font-size: 10pt; font-family: 'Courier New'; ">security-groups</span></a>, the capability to create a security group with its children in a single call is not possible.
<span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<!--[if !supportLists]--><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black"><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">The capability to create
</span><a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroupRules_v2.0_security-group-rules_security-groups-ext.html" title="List security group rules"><span style="font-size: 10pt; font-family: 'Courier New'; ">security-group-rules</span></a>
using the following URI path <a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroups_v2.0_security-groups_security-groups-ext.html" title="List security groups">
<span style="font-size: 10pt; font-family: 'Courier New'; ">v2.0/security-groups</span></a>/{SG-ID}/<a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroupRules_v2.0_security-group-rules_security-groups-ext.html" title="List security group rules"><span style="font-size: 10pt; font-family: 'Courier New'; ">security-group-rules</span></a>
is not supported<span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; "><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<!--[if !supportLists]--><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black"><span style="mso-list:Ignore">c.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]-->The capability to update <a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroupRules_v2.0_security-group-rules_security-groups-ext.html" title="List security group rules">
<span style="font-size: 10pt; font-family: 'Courier New'; ">security-group-rules</span></a> using the following URI path
<a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroups_v2.0_security-groups_security-groups-ext.html" title="List security groups">
<span style="font-size: 10pt; font-family: 'Courier New'; ">v2.0/security-groups</span></a>/{SG-ID}/<a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroupRules_v2.0_security-group-rules_security-groups-ext.html" title="List security group rules"><span style="font-size: 10pt; font-family: 'Courier New'; ">security-group-rules</span></a>/{SGR-ID}
is not supported<span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; "><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<!--[if !supportLists]--><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif";color:black"><span style="mso-list:Ignore">d.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">The notion of creating
</span><a href="http://docs.openstack.org/api/openstack-network/2.0/content/GET_security-groups-v2.0_listSecGroupRules_v2.0_security-group-rules_security-groups-ext.html" title="List security group rules"><span style="font-size: 10pt; font-family: 'Courier New'; ">security-group-rules</span></a>
(child object) without providing the parent {SG-ID} is not supported<span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; "><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><!--[if !supportLists]--><strong><span style="font-family:"Calibri","sans-serif";font-weight:normal"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span></strong><!--[endif]-->Firewall as a service - <a href="http://docs.openstack.org/api/openstack-network/2.0/content/fwaas_ext.html">
http://docs.openstack.org/api/openstack-network/2.0/content/fwaas_ext.html</a> - the API to manage
<strong><span style="font-size: 10pt; color: black; font-weight: normal; font-family: Verdana, sans-serif; ">firewall_policy and firewall_rule which have parent child relationships behaves the same way as Security groups</span></strong><strong><span style="font-weight: normal; font-family: Calibri, sans-serif; "><o:p></o:p></span></strong></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><!--[if !supportLists]--><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><!--[endif]--><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">Group Policy – this is work in progress -
<a href="https://wiki.openstack.org/wiki/Neutron/GroupPolicy">https://wiki.openstack.org/wiki/Neutron/GroupPolicy</a> - If I understand correctly, this API has a complex object model while the API adheres to the way other neutron APIs are done (ex: flat model,
granular api, etc.)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">How critical is it to preserve a consistent API style for LBaaS?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">Should this be a consideration when evaluating API proposals?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; ">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; "> -Sam.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: 'Segoe UI', sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>