On 25/07/13 18:44 -0600, John Griffith wrote:
Hey Everyone,
Something I've been kicking around for quite a while now but never really been
able to get around to is the idea of requiring that drivers in Cinder run a
qualification test and submit results prior to introduction in to Cinder.
FWIW
On 30 July 2013 21:36, Mark Washenberger wrote:
> - I'd love to use this as a way to OpenStack-validate plugins that live
> outside of the project--and then kick most plugins out of the project to
> some other semi-canonical area.
I don't think I'm alone within the cinder team in seeing significa
In general, I think this is fantastic and I know that Glance would benefit
from something similar.
I have a few opinions I want to share:
- I'd love to use this as a way to OpenStack-validate plugins that live
outside of the project--and then kick most plugins out of the project to
some other sem
On Tue, Jul 30, 2013 at 11:47 AM, Walter A. Boring IV
wrote:
> So how frequently would this be required and when do the results need to
> be provided?
>
To start I'd like to propose any new driver, and then each driver upon
milestone release, or at the very least each cycle.
> I generally t
So how frequently would this be required and when do the results need to
be provided?
I generally think this is a good idea, but as well all know that the
project seems to be in flux at times around the milestones. Especially
around G3 when we changed the way the CONF object was accessed, al
On Sun, Jul 28, 2013 at 3:56 AM, Avishay Traeger wrote:
> John Griffith wrote on 07/26/2013 03:44:12
> AM:
>
> > I think it would be a very useful tool for initial introduction of a
> > new driver and even perhaps some sort of check that's run and
> > submitted again prior to milestone releases
John Griffith wrote on 07/26/2013 03:44:12
AM:
> I think it would be a very useful tool for initial introduction of a
> new driver and even perhaps some sort of check that's run and
> submitted again prior to milestone releases.
+1. Do you see this happening for Havana? Or should this be a su
On Thu, Jul 25, 2013 at 5:44 PM, John Griffith
wrote:
> Hey Everyone,
>
> Something I've been kicking around for quite a while now but never really
> been able to get around to is the idea of requiring that drivers in Cinder
> run a qualification test and submit results prior to introduction in to
On Thu, Jul 25, 2013 at 7:37 PM, yang, xing wrote:
> +1. I like this idea. With this qualification test, is each driver still
> required to have its own unit test?
>
Keep in mind this is just a proposal that I wanted to get feed-back on,
I'll likely submit something more concrete shortly. Tha
+1. I like this idea. With this qualification test, is each driver still
required to have its own unit test?
Thanks,
Xing
On Jul 25, 2013, at 8:46 PM, "John Griffith"
mailto:john.griff...@solidfire.com>> wrote:
Hey Everyone,
Something I've been kicking around for quite a while now but neve
Great idea and 100% agree. It'd be even better if maintainer can publish
functional test results using their own back-ends on a regular basis
(weekly/bi-weekly test report) to 'openstack-dev' mailing list.
On Fri, Jul 26, 2013 at 9:05 AM, Joshua Harlow wrote:
> 100% agree, its hard to handle t
100% agree, its hard to handle these 3rd party type of drivers but I think we
need to find out a way that will test it in a way that doesn't require having
said 3rd party gear directly available.
Could it be possible to have CI gating be blocked/tested by individual
subfolders of cinder.
For e
On 07/25/2013 08:44 PM, John Griffith wrote:
> Hey Everyone,
>
> Something I've been kicking around for quite a while now but never
> really been able to get around to is the idea of requiring that drivers
> in Cinder run a qualification test and submit results prior to
> introduction in to Cinder
13 matches
Mail list logo
