<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">I am one of the developers on the project, so I have a strong preference for option (1).<br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">
<br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">I think a 3rd option is also possible, which offers a scale down version of GBP APIs. Contracts could be added in kilo. Provide EndPoints, EndPointGroups, Rules and Policies. This is the simpler approach suggested in GBP document, where you have a policy with a single rule (classifier & action) applied between 2 EPGs. This approach minimizes complexity and therefore saves precious reviewer's time. This requires some code reorg, which may not be preferable to other developers on the project.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">Alternatively, contracts could be added as optional vendor extensions in Juno.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6"><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 6, 2014 at 8:50 PM, Alan Kavanagh <span dir="ltr"><<a href="mailto:alan.kavanagh@ericsson.com" target="_blank">alan.kavanagh@ericsson.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1<br>
I believe Pedro has a very valid point here, and that is the "the community to approve the spec and that decision should be respected". It makes sense to again clearly denote the "process and governance" and have this noted on the thread Stefano started earlier today.<br>
<br>
/Alan<br>
<div class=""><br>
-----Original Message-----<br>
From: Pedro Marques [mailto:<a href="mailto:pedro.r.marques@gmail.com">pedro.r.marques@gmail.com</a>]<br>
Sent: August-06-14 4:52 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
</div><div class="">Subject: Re: [openstack-dev] Fwd: FW: [Neutron] Group Based Policy and the way forward<br>
<br>
<br>
</div>On Aug 6, 2014, at 1:27 PM, Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
><br>
> However, it seems to me that the end-goal of the GBP effort is *actually* to provide a higher-layer API to Neutron that would essentially enable proprietary vendors to entirely swap out all of Neutron core for a new set of drivers that spoke proprietary device APIs.<br>
><br>
> If this is the end-goal, it should be stated more clearly, IMO.<br>
<br>
I believe that people should be considered innocent until proven otherwise. Is there a reason to believe there is some hidden reason behind this proposal ? It seems to me that this is uncalled for.<br>
<div class=""><br>
Neutron allows vendors to speak to proprietary device APIs, it was designed to do so, AFAIK. It is also possibly to "entirely swap out all of the Neutron core"... the proponents of the group based policy didn't have to go through so much trouble if that was their intent. As far as i know most plugins talk to a proprietary API.<br>
<br>
I happen to disagree technically with a couple of choices made by this proposal; but the blueprint was approved. Which means that i lost the argument, or didn't raise it on time, or didn't argue convincingly... regardless of the reason, the time to argue about the goal has passed. The decision of the community was to approve the spec and that decision should be respected.<br>
<br>
</div> Pedro.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<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><br clear="all"><div><br></div>-- <br><br>Thanks<br>OSM<br>(Subrahmanyam Ongole)<br>
</div>