[openstack-dev] Fwd: FW: [Neutron] Group Based Policy and the way forward

Kevin Benton blak111 at gmail.com
Thu Aug 7 00:20:29 UTC 2014


I prefer merged because moving it to a separate project blocks it from
enforcing policy on the current API (including calls between service
plugins).


On Wed, Aug 6, 2014 at 4:56 PM, Armando M. <armamig at gmail.com> wrote:

>
> On 6 August 2014 15:47, Kevin Benton <blak111 at gmail.com> wrote:
>
>> I think we should merge it and just prefix the API for now with
>> '/your_application_will_break_after_juno_if_you_use_this/'
>>
>
> And you make your call based and what pros and cons exactly, If I am ask?
>
> Let me start:
>
> Option 1:
>    - pros
>     - immediate delivery vehicle for consumption by operators
>   - cons
>     - code is burder from a number of standpoints (review, test, etc)
>
> Option 2:
>   - pros
>     - enable a small set of Illuminati to iterate faster
>   - cons
>     - integration burden with other OpenStack projects (keystone, nova,
> neutron, etc)
>
> Cheers,
> Armando
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140806/1832295a/attachment.html>


More information about the OpenStack-dev mailing list