Open Stack

On 21 October 2015 at 09:52, Gal Sagie <gal.sagie at gmail.com> wrote:

>
>
> On Wed, Oct 21, 2015 at 7:37 PM, Armando M. <armamig at gmail.com> wrote:
>
>>
>>
>> On 21 October 2015 at 04:12, Gal Sagie <gal.sagie at gmail.com> wrote:
>>
>>> Do we also want to consider Project Kuryr part of this?
>>>
>>
>> No, why would we?
>>
>
> [Gal] Because Kuryr is a special project which was created in order to
> expose Neutron and its services to containers networking,
>          its mission (at least as defined right now) is to bridge the gaps
> between containers networking world and Neutron and for doing it
>          it already depends on the feature/spec process of Neutron.
>          That is why it make sense to me that just like the services
> projects, our spec approval process will be handled
>          as part of Neutron.
>

Kuryr is no more special than any other Neutron affiliated project, let's
be 100% clear about that: there is no double-standard here.

If you really think that Kuryr should be an integral part of the Neutron
project, then it should not exist, but fold within Neutron entirely. I
don't know the backstory of why this was spun off as a separate project in
the first place, but I think that there's some merits in having it as
standalone entity.

You are always welcome to reach out for feedback, after all the same people
may work/have an interest in multiple projects (fingers stuck in many pies
if you will :P), but going from there to what you're proposing is too big
of a leap which I find hard to justify.


>
>
>
>>
>>
>>> We already started sending Kuryr spec to the Neutron repository and I
>>> think it would make sense to manage it
>>> as part of Neutron spec process.
>>>
>>
>> No, unless what you are asking are changes to the core. Do you have a
>> reference for me to look at?
>>
>>
>   [Gal]   I dont understand what you mean "No" here, first this spec is
> sent to Mitaka:
>              https://review.openstack.org/#/c/213490/
>
>             And as i mentioned above Kuryr spec process depends on Neutron
> (and the specs that are sent
>             to Neutron core)
>

I'll review it and provide feedback. 'Depending on Neutron' means requiring
actual enhancement to the core platform that makes sense to be
tracked/discussed in Neutron. Everything else can be tracked independently:
this is the separation of concerns that we should strive for.


>
>
>>> Any opinions on that?
>>>
>>> Gal.
>>>
>>> On Tue, Oct 20, 2015 at 11:10 PM, Armando M. <armamig at gmail.com> wrote:
>>>
>>>> Hi folks,
>>>>
>>>> During revision of the Neutron teams [1], we made clear that the
>>>> neutron-specs repo is to be targeted by specs for all the Neutron projects
>>>> (core + *-aas).
>>>>
>>>> For this reason I made sure that the neutron-specs-core team +2 right
>>>> was extended to all the core teams.
>>>>
>>>> Be mindful, use your +2 rights with care: if you are core on a *-aas
>>>> project, you should exercise that vote only for specs that pertain the
>>>> project you're core of.
>>>>
>>>> If I could use this email as a reminder also of the core hierarchy and
>>>> lieutenant system we switched to in Liberty ([3]): if you have been made
>>>> core by a lieutenant of a sub-system, please use your +2/+A only within
>>>> your area of comfort and reach out for help if in doubt.
>>>>
>>>> Reviews are always welcome though!
>>>>
>>>> Cheers,
>>>> Armando
>>>>
>>>> [1] https://review.openstack.org/#/c/237180/
>>>> [2] https://review.openstack.org/#/admin/groups/314,members
>>>> [3]
>>>> http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#core-review-hierarchy
>>>>
>>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards ,
>>>
>>> The G.
>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best Regards ,
>
> The G.
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/db8ca0c9/attachment.html>