Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/29/2015 09:19 PM, Jeremy Stanley wrote: > On 2015-04-29 16:46:13 -0700 (-0700), Joe Gordon wrote: >> On Wed, Apr 22, 2015 at 12:30 PM, Kyle Mestery wrote: >>> On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant > [...] 1) Project governance has moved to a "big tent" model [1]. The vast >>

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 2015-04-29 16:46:13 -0700 (-0700), Joe Gordon wrote: > On Wed, Apr 22, 2015 at 12:30 PM, Kyle Mestery wrote: > > On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant [...] > >> 1) Project governance has moved to a "big tent" model [1]. The vast > >> majority of projects that used to be in Stackfor

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 30, 2015 at 2:44 AM, Russell Bryant wrote: > On 04/29/2015 01:25 PM, Doug Wiegley wrote: >> My take on the “where does it fit” yardstick: >> >> Does it stand on its own and add value? Then consider it a standalone >> project, *or* part of neutron if you and neutron agree that it fits.

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Wed, Apr 22, 2015 at 12:30 PM, Kyle Mestery wrote: > On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant > wrote: > >> Hello! >> >> A couple of things I've been working on lately are project governance >> issues as a TC member and also implementation of a new virtual >> networking alternative wit

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/29/2015 01:25 PM, Doug Wiegley wrote: > My take on the “where does it fit” yardstick: > > Does it stand on its own and add value? Then consider it a standalone > project, *or* part of neutron if you and neutron agree that it fits. > > Does it *require* neutron to be useful? Then consider ha

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > Original Message > ‎ > From: Russell Bryant‎ > Sent: Tuesday, 28 April 2015 18:57 > To: openstack-dev@lists.openstack.org > Reply To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron ba

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/29/2015 12:33 PM, neil.jer...@metaswitch.com wrote: > ‎Thanks Russell and Kyle for explaining. I think I get the picture > now, in particular of how these backend projects are mostly under > separate management, but at the same time subject to PTL oversight > and 'part of the wider Neutron ef

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

sell Bryant‎ Sent: Tuesday, 28 April 2015 18:57 To: openstack-dev@lists.openstack.org Reply To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code On 04/28/2015 01:17 PM, Neil Jerram wrote: > Apologies for co

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Tue, Apr 28, 2015 at 8:00 AM, Russell Bryant wrote: > On 04/27/2015 08:52 PM, Armando M. wrote: > > > > Any project that fails to meet the criteria later can be dropped at > any > > time. For example, if some repo is clearly unmaintained, it can be > > removed. > > > > > > If we o

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Mon, Apr 27, 2015 at 3:58 PM, Russell Bryant wrote: > On 04/22/2015 02:19 PM, Russell Bryant wrote: > > a) Adopt these as repositories under the Neutron project team. > > > > In this case, I would see them operating with their own review teams as > > they do today to avoid imposing additional

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

*Sent:* 23 April 2015 15:05 > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Neutron] A big tent home for Neutron > backend code > > > > On Thu, Apr 23, 2015 at 10:28 AM, henry hly wrote: > >> On Thu, Apr 23, 201

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/28/2015 01:17 PM, Neil Jerram wrote: > Apologies for commenting so late, but I'm not clear on the concept of > bringing all possible backend projects back inside Neutron. > > > I think my question is similar to what Henry and Mathieu are getting at > below - viz: > > > We just recently de

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code On Thu, Apr 23, 2015 at 10:28 AM, henry hly mailto:henry4...@gmail.com>> wrote: On Thu, Apr 23, 2015 at 10:44 AM, Armando M. mailto:arma...@gmail.com>> wrote: >>

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/27/2015 08:52 PM, Armando M. wrote: > > Any project that fails to meet the criteria later can be dropped at any > time. For example, if some repo is clearly unmaintained, it can be > removed. > > > If we open the door to excluding projects down the road, then wouldn't > we nee

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > > Any project that fails to meet the criteria later can be dropped at any > time. For example, if some repo is clearly unmaintained, it can be > removed. > If we open the door to excluding projects down the road, then wouldn't we need to take into account some form of 3rd party CI validation

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/22/2015 02:19 PM, Russell Bryant wrote: > a) Adopt these as repositories under the Neutron project team. > > In this case, I would see them operating with their own review teams as > they do today to avoid imposing additional load on the neutron-core or > neutron-specs-core teams. However,

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > If we've reached the point where we're arguing about naming, dos this mean >> we've built consensus on the "yes, it makes sense for these to live under >> Neutron" argument? >> > > I think we are in agreement that these projects need to find a more obvious home, they feel somewhat orphan otherw

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 2015-04-23 12:45:14 -0700 (-0700), Joshua Harlow wrote: > Maybe about time we make something like: > > http://projects.apache.org/indexes/category.html > > And link names to repos there...? http://governance.openstack.org/reference/projects/ is sort of our analogue there, I think. It's not ex

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

Doug, HMS Octavia was a British mine sweeper that served during WW2 figthing German warships and u-boats somewhere in the sea. I therefore believe if you have anything against this name you are secretly a nazi. Does that work for the Godwin's law call? Salvatore On 23 April 2015 at 22:09, Doug W

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> On Apr 23, 2015, at 1:42 PM, Russell Bryant wrote: > > On 04/23/2015 03:23 PM, Kyle Mestery wrote: >> On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley >> mailto:doug...@parksidesoftware.com>> wrote: >> >> >>> On Apr 23, 2015, at 11:57 AM, Russell Bryant >> wrote:

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

Russell Bryant wrote: On 04/23/2015 03:23 PM, Kyle Mestery wrote: On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley mailto:doug...@parksidesoftware.com>> wrote: > On Apr 23, 2015, at 11:57 AM, Russell Bryantmailto:rbry...@redhat.com>> wrote: > > On 04/23/2015 01:19 PM, Armando M

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/23/2015 03:23 PM, Kyle Mestery wrote: > On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley > mailto:doug...@parksidesoftware.com>> wrote: > > > > On Apr 23, 2015, at 11:57 AM, Russell Bryant > wrote: > > > > On 04/23/2015 01:19 PM, Armando M. wrote: >

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley wrote: > > > On Apr 23, 2015, at 11:57 AM, Russell Bryant wrote: > > > > On 04/23/2015 01:19 PM, Armando M. wrote: > >> > >> > >> On 23 April 2015 at 09:58, Russell Bryant >> > wrote: > >> > >>On 04/23/2015 12:14 PM, A

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> On Apr 23, 2015, at 11:57 AM, Russell Bryant wrote: > > On 04/23/2015 01:19 PM, Armando M. wrote: >> >> >> On 23 April 2015 at 09:58, Russell Bryant > > wrote: >> >>On 04/23/2015 12:14 PM, Armando M. wrote: >>> >>> >>> On 23 April 2015 at 07:32, Russell Brya

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

f the proposed split. Thanks, Kyle > Thanks, > Kevin > -- > *From:* Armando M. [arma...@gmail.com] > *Sent:* Thursday, April 23, 2015 9:10 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Neutr

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

9:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code I agree with henry here. Armando, If we use your analogy with nova that doesn't build and deliver KVM, we can say that Neutron doesn'

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/23/2015 01:19 PM, Armando M. wrote: > > > On 23 April 2015 at 09:58, Russell Bryant > wrote: > > On 04/23/2015 12:14 PM, Armando M. wrote: > > > > > > On 23 April 2015 at 07:32, Russell Bryant > >

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 23 April 2015 at 09:58, Russell Bryant wrote: > On 04/23/2015 12:14 PM, Armando M. wrote: > > > > > > On 23 April 2015 at 07:32, Russell Bryant > > wrote: > > > > On 04/22/2015 10:33 PM, Armando M. wrote: > > > > > > Would it make sense to captur

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/23/2015 12:14 PM, Armando M. wrote: > > > On 23 April 2015 at 07:32, Russell Bryant > wrote: > > On 04/22/2015 10:33 PM, Armando M. wrote: > > > > Would it make sense to capture these projects as simply > > 'affiliated', ie. with

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

+1 From: Armando M. [arma...@gmail.com] Sent: Wednesday, April 22, 2015 7:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code Could you please also pay some

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 23 April 2015 at 07:32, Russell Bryant wrote: > On 04/22/2015 10:33 PM, Armando M. wrote: > > > > Would it make sense to capture these projects as simply > > 'affiliated', ie. with a loose relationship to Neutron, because > > they use/integrate with Neutron in some form

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > >> I agree with henry here. > Armando, If we use your analogy with nova that doesn't build and deliver > KVM, we can say that Neutron doesn't build or deliver OVS. It builds a > driver and an agent which manage OVS, just like nova which provides a > driver to manage libvirt/KVM. > Moreover, ext

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 23 April 2015 at 01:49, Thierry Carrez wrote: > Armando M. wrote: > > Is it sensible to assume that Stackforge is going away entirely at some > > point in the future, and we'll have a single namespace - OpenStack? > > The key difference between Stackforge and OpenStack is governance. Any > pro

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/22/2015 10:33 PM, Armando M. wrote: > > Would it make sense to capture these projects as simply > 'affiliated', ie. with a loose relationship to Neutron, because > they use/integrate with Neutron in some form or another (e.g. > having 3rd-party, extending-api,

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/22/2015 09:55 PM, Anita Kuno wrote: > On 04/22/2015 09:46 PM, Kyle Mestery wrote: >> On Wed, Apr 22, 2015 at 7:44 PM, Armando M. wrote: >> >>> >>> >>> On 22 April 2015 at 11:19, Russell Bryant wrote: >>> Hello! A couple of things I've been working on lately are project govern

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 23, 2015 at 10:28 AM, henry hly wrote: > On Thu, Apr 23, 2015 at 10:44 AM, Armando M. wrote: > >> > >> Could you please also pay some attention on Cons of this ultimate > >> splitting Kyle? I'm afraid it would hurt the user experiences. > >> > >> On the position of Dev, A naked Neutr

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

Armando M. wrote: > Is it sensible to assume that Stackforge is going away entirely at some > point in the future, and we'll have a single namespace - OpenStack? The key difference between Stackforge and OpenStack is governance. Any project can be in Stackforge. Projects that are considered "OpenS

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 23, 2015 at 10:44 AM, Armando M. wrote: >> >> Could you please also pay some attention on Cons of this ultimate >> splitting Kyle? I'm afraid it would hurt the user experiences. >> >> On the position of Dev, A naked Neutron without "official" built-in >> reference implementation probab

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > > Could you please also pay some attention on Cons of this ultimate > splitting Kyle? I'm afraid it would hurt the user experiences. > > On the position of Dev, A naked Neutron without "official" built-in > reference implementation probably has a more clear architecture. On > the other side, us

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > >> Would it make sense to capture these projects as simply 'affiliated', ie. >> with a loose relationship to Neutron, because they use/integrate with >> Neutron in some form or another (e.g. having 3rd-party, extending-api, >> integrating-via-plugin-model, etc)? Then we could simply consider ex

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 23, 2015 at 3:30 AM, Kyle Mestery wrote: > On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant wrote: >> >> Hello! >> >> A couple of things I've been working on lately are project governance >> issues as a TC member and also implementation of a new virtual >> networking alternative with a

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/22/2015 09:46 PM, Kyle Mestery wrote: > On Wed, Apr 22, 2015 at 7:44 PM, Armando M. wrote: > >> >> >> On 22 April 2015 at 11:19, Russell Bryant wrote: >> >>> Hello! >>> >>> A couple of things I've been working on lately are project governance >>> issues as a TC member and also implementati

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Wed, Apr 22, 2015 at 7:44 PM, Armando M. wrote: > > > On 22 April 2015 at 11:19, Russell Bryant wrote: > >> Hello! >> >> A couple of things I've been working on lately are project governance >> issues as a TC member and also implementation of a new virtual >> networking alternative with a Neu

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 22 April 2015 at 11:19, Russell Bryant wrote: > Hello! > > A couple of things I've been working on lately are project governance > issues as a TC member and also implementation of a new virtual > networking alternative with a Neutron driver. So, naturally I started > thinking about how the Ne

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

k Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code +1 I was in the middle of writing an email asking about the possibility of splitting out the reference implementation. you beat me to it. :) I also like the idea of

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

From: Kyle Mestery [mest...@mestery.com] Sent: Wednesday, April 22, 2015 12:30 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant wrote: > Hello! > > A couple of things I've been working on lately are project governance > issues as a TC member and also implementation of a new virtual > networking alternative with a Neutron driver. So, naturally I started > thinking about how

[openstack-dev] [Neutron] A big tent home for Neutron backend code

Hello! A couple of things I've been working on lately are project governance issues as a TC member and also implementation of a new virtual networking alternative with a Neutron driver. So, naturally I started thinking about how the Neutron driver code fits in to OpenStack governance. There are