Open Stack

Excerpts from Herndon, John Luke's message of 2014-01-03 08:17:15 -0800:
> 
> On 1/2/14, 7:06 PM, "Sean Dague" <sean at dague.net> wrote:
> 
> >On 01/02/2014 08:36 PM, Robert Collins wrote:
> >> On 3 January 2014 14:34, Robert Collins <robertc at robertcollins.net>
> >>wrote:
> >>> On 3 January 2014 12:40, Herndon, John Luke <john.herndon at hp.com>
> >>>wrote:
> >>>>
> >>>>
> >>>> On 1/2/14, 4:27 PM, "Clint Byrum" <clint at fewbar.com> wrote:
> >>>>
> >>>
> >>>
> >>>> I don¹t think it would be that hard to get the review or gate jobs to
> >>>>use
> >>>> a real vertica instance, actually. Who do I talk to about that?
> >>>
> >>> http://ci.openstack.org/third_party.html
> >>
> >> Oh, if you meant setting up a gate variant to use vertica community
> >> edition - I'd run it past the ceilometer folk and then just submit
> >> patches to devstack, devstack-gate and infra/config to do it.
> >>
> >> devstack - code for setting up a real vertica
> >> devstack-gate - handles passing the right flags to devstack for the
> >> configuration scenarios we test against
> >> infra/config - has the jenkins job builder definitions to define the
> >>jobs
> >
> >I think general policy (thus far) has been that we're not going to put
> >non Open Source software into upstream gate jobs.
> >
> >So you really should approach this via 3rd party testing instead. The
> >DB2 folks are approaching it that way, for that reason.
> 
> Ok, that makes sense, but tbh, setting up 3rd party testing is going to be
> as much or more work than writing the driver. Given schedule constraints,
> it probably isn¹t feasible right now. I think for starters, I will write
> some unit tests that ensure that changes to the storage interface don¹t
> break the driver, and will work on a 3rd party testing strategy over time.
> 

>From my perspective, I would -2 any change to projects I'm a core on if
they just add a 3rd party driver without a commitment to testing. After
seeing what Nova went through with this, it doesn't seem like a "should"
but a "must".