<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:356467117;
mso-list-type:hybrid;
mso-list-template-ids:-1562851204 -702093734 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:20.25pt;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
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]-->
</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">Ryan,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> So this is intended to associate a contract with a source EPG and a destination EPG – right?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:20.25pt;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Louis<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"><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""> Mandeep Dhami [mailto:dhami@noironetworks.com]
<br>
<b>Sent:</b> Wednesday, July 30, 2014 12:21 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Cc:</b> Subrahmanyam Ongole<br>
<b>Subject:</b> Re: [openstack-dev] [neutron][policy] Bridging the 2-group gap in group policy<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi Ryan:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As I stated in the patch review, the suggestion to use a "profiled API" like IETF/CCITT is indeed very interesting. As a "profiled API" has not been tried with any neutron model before, and as there is no existing design pattern/best practices
for how best to structure that, my recommendation is to create a new patch (dependent on this patch) to try that experiment.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">That patch will also clarify what is meant you mean by a "profiled API" and how that might interact with other openstack services like Heat and Horizon.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Mandeep<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>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Jul 30, 2014 at 11:13 AM, Hemanth Ravi <<a href="mailto:hemanthraviml@gmail.com" target="_blank">hemanthraviml@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">Hi,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adding this CLI command seems to be a good way to provide support for the second model. This can be submitted as a new review patch to work through the approaches to implement this. I suggest the current CLI patch [1] be reviewed for the
existing spec and completed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Ryan, would it possible for you to start a new review submit for the new command(s). Could you also provide any references for "profiled" API in IETF, CCITT.<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">-hemanth<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">[1] <a href="https://review.openstack.org/#/c/104013" target="_blank">
https://review.openstack.org/#/c/104013</a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Jul 29, 2014 at 3:16 PM, Ryan Moats <<a href="mailto:rmoats@us.ibm.com" target="_blank">rmoats@us.ibm.com</a>> wrote:<o:p></o:p></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p><span style="font-family:"Arial","sans-serif"">As promised in Monday's Neutron IRC minutes [1], this mail is a "trip down memory lane" looking at the history of the</span><br>
<span style="font-family:"Arial","sans-serif"">Neutron GP project.. The original GP google doc [2] included specifying policy via both a produce/consume 1-group</span><br>
<span style="font-family:"Arial","sans-serif"">approach and as a link between two groups. There was an email thread [3] that discussed the relationship between</span><br>
<span style="font-family:"Arial","sans-serif"">these models early on, but that discussion petered out and during a later IRC meeting [4] the concept of contracts</span><br>
<span style="font-family:"Arial","sans-serif"">were added, but without changing the basic use case requirements from the original document. A followup meeting [5]</span><br>
<span style="font-family:"Arial","sans-serif"">began the discussion of how to express the original model from the contract data model but that discussion doesn't</span><br>
<span style="font-family:"Arial","sans-serif"">appear to have been completed either. The PoC in Atlanta raised a set of issues [6],[7] around the complexity of the</span><br>
<span style="font-family:"Arial","sans-serif"">resulting PoC code.</span><br>
<br>
<span style="font-family:"Arial","sans-serif"">The good news is that having looked through the proposed GP code commits (links to which can be found at [8) I</span><br>
<span style="font-family:"Arial","sans-serif"">believe that folks that want to be able to specify policies via the 2-group approach (and yes, I'm one of them) can have</span><br>
<span style="font-family:"Arial","sans-serif"">that without changing the model encoded in those commits. Rather, it can be done via the WiP CLI code commit by</span><br>
<span style="font-family:"Arial","sans-serif"">providing a "profiled" API - this is a technique used by the IETF, CCITT, etc. to allow a rich API to be consumed in</span><br>
<span style="font-family:"Arial","sans-serif"">common ways. In this case, what I'm envisioning is something like</span><br>
<br>
<span style="font-family:"Arial","sans-serif"">neutron policy-apply [policy rule] [src group] [destination group]</span><br>
<br>
<span style="font-family:"Arial","sans-serif"">in this case, the CLI would perform the contract creation for the policy rule, and assigning the proper produce/consume</span><br>
<span style="font-family:"Arial","sans-serif"">edits to the specified source and destination groups. Note: this is in addition to the CLI providing direct access to the</span><br>
<span style="font-family:"Arial","sans-serif"">underlying data model. I believe that this is the simplest way to "bridge the gap" and provide support to folks who want</span><br>
<span style="font-family:"Arial","sans-serif"">to specify policy as something between two groups.</span><br>
<br>
<span style="font-family:"Arial","sans-serif"">Ryan Moats (regXboi)</span><br>
<br>
<span style="font-family:"Arial","sans-serif"">References:</span><br>
<span style="font-family:"Arial","sans-serif"">[1] </span><a href="http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-07-28-21.02.log.txt" target="_blank"><span style="font-family:"Arial","sans-serif"">http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-07-28-21.02.log.txt</span></a><br>
<span style="font-family:"Arial","sans-serif"">[2] </span><a href="https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit" target="_blank"><span style="font-family:"Arial","sans-serif"">https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit#</span></a><br>
<span style="font-family:"Arial","sans-serif"">[3] </span><a href="http://lists.openstack.org/pipermail/openstack-dev/2013-December/022150.html" target="_blank"><span style="font-family:"Arial","sans-serif"">http://lists.openstack.org/pipermail/openstack-dev/2013-December/022150.html</span></a><br>
<span style="font-family:"Arial","sans-serif"">[4] </span><a href="http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-27-19.00.log.html" target="_blank"><span style="font-family:"Arial","sans-serif"">http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-27-19.00.log.html</span></a><br>
<span style="font-family:"Arial","sans-serif"">[5] </span><a href="http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-03-20-19.00.log.html" target="_blank"><span style="font-family:"Arial","sans-serif"">http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-03-20-19.00.log.html</span></a><br>
<span style="font-family:"Arial","sans-serif"">[6] </span><a href="http://lists.openstack.org/pipermail/openstack-dev/2014-May/035661.html" target="_blank"><span style="font-family:"Arial","sans-serif"">http://lists.openstack.org/pipermail/openstack-dev/2014-May/035661.html</span></a><br>
<span style="font-family:"Arial","sans-serif"">[7] </span><a href="http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-22-18.01.log.html" target="_blank"><span style="font-family:"Arial","sans-serif"">http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-22-18.01.log.html</span></a><br>
<span style="font-family:"Arial","sans-serif"">[8] </span><a href="https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy" target="_blank"><span style="font-family:"Arial","sans-serif"">https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy</span></a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>