On 28 April 2015 at 21:59, Kevin Benton blak...@gmail.com wrote:
The concern is that having broken drivers out there that claim to work
with an OpenStack project end up making the project look bad. It's similar
to a first time Linux user experiencing frequent kernel panics because they
are
From: loy wolfe
Sent: Tuesday, April 28, 2015 6:16:03 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] [Nova] [Cinder] [tc] Should Openstack
project maintained by core team keep only API/DB in the future?
On Wed, Apr 29
On Wed, Apr 29, 2015 at 2:59 AM, Kevin Benton blak...@gmail.com wrote:
The concern is that having broken drivers out there that claim to work with
an OpenStack project end up making the project look bad. It's similar to a
first time Linux user experiencing frequent kernel panics because they
On 28 April 2015 at 10:14, Duncan Thomas duncan.tho...@gmail.com wrote:
If we allow third party CI to fail and wait for vendors to fix their
stuff, experience has shown that they won't, and there'll be broken or
barely functional drivers out there, and no easy way for the community to
exert
wolfe
Sent: Tuesday, April 28, 2015 6:16:03 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] [Nova] [Cinder] [tc] Should Openstack
project maintained by core team keep only API/DB in the future?
On Wed, Apr 29, 2015 at 2:59 AM, Kevin Benton
The concern is that having broken drivers out there that claim to work with
an OpenStack project end up making the project look bad. It's similar to a
first time Linux user experiencing frequent kernel panics because they are
using hardware with terrible drivers. They aren't going to recognize the
On Fri, Apr 24, 2015 at 9:46 PM, Salvatore Orlando sorla...@nicira.com wrote:
On 24 April 2015 at 15:13, Kyle Mestery mest...@mestery.com wrote:
On Fri, Apr 24, 2015 at 4:06 AM, loy wolfe loywo...@gmail.com wrote:
It's already away from the original thread, so I start this new one,
also
On 24 April 2015 at 12:06, loy wolfe loywo...@gmail.com wrote:
Background summary:
All in-tree implementation would be splitted from Openstack
networking, leaving Neutron as a naked API/DB platform, with a list
of out-tree implementation git repos, which are not maintained by core
team any
On Fri, Apr 24, 2015 at 9:13 PM, Kyle Mestery mest...@mestery.com wrote:
On Fri, Apr 24, 2015 at 4:06 AM, loy wolfe loywo...@gmail.com wrote:
It's already away from the original thread, so I start this new one,
also with some extra tag because I think it touch some corss-project
area.
It's already away from the original thread, so I start this new one,
also with some extra tag because I think it touch some corss-project
area.
Original discuss and reference:
http://lists.openstack.org/pipermail/openstack-dev/2015-April/062384.html
On Fri, Apr 24, 2015 at 4:06 AM, loy wolfe loywo...@gmail.com wrote:
It's already away from the original thread, so I start this new one,
also with some extra tag because I think it touch some corss-project
area.
Original discuss and reference:
On 24 April 2015 at 15:13, Kyle Mestery mest...@mestery.com wrote:
On Fri, Apr 24, 2015 at 4:06 AM, loy wolfe loywo...@gmail.com wrote:
It's already away from the original thread, so I start this new one,
also with some extra tag because I think it touch some corss-project
area.
Original
Hi loy, thanks for this dedicated thread.
On Fri, Apr 24, 2015 at 3:13 PM, Kyle Mestery mest...@mestery.com wrote:
On Fri, Apr 24, 2015 at 4:06 AM, loy wolfe loywo...@gmail.com wrote:
It's already away from the original thread, so I start this new one,
also with some extra tag because I
13 matches
Mail list logo
