Open Stack

On 6/12/2014 9:38 AM, Mike Bayer wrote:
>
> On 6/12/14, 8:26 AM, Julien Danjou wrote:
>> On Thu, Jun 12 2014, Sean Dague wrote:
>>
>>> That's not cacthable in unit or functional tests?
>> Not in an accurate manner, no.
>>
>>> Keeping jobs alive based on the theory that they might one day be useful
>>> is something we just don't have the liberty to do any more. We've not
>>> seen an idle node in zuul in 2 days... and we're only at j-1. j-3 will
>>> be at least +50% of this load.
>> Sure, I'm not saying we don't have a problem. I'm just saying it's not a
>> good solution to fix that problem IMHO.
>
> Just my 2c without having a full understanding of all of OpenStack's CI
> environment, Postgresql is definitely different enough that MySQL
> "strict mode" could still allow issues to slip through quite easily, and
> also as far as capacity issues, this might be longer term but I'm hoping
> to get database-related tests to be lots faster if we can move to a
> model that spends much less time creating databases and schemas.
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

Is there some organization out there that uses PostgreSQL in production 
that could stand up 3rd party CI with it?

I know that at least for the DB2 support we're adding across the 
projects we're doing 3rd party CI for that. Granted it's a proprietary 
DB unlike PG but if we're talking about spending resources on testing 
for something that's not widely used, but there is a niche set of users 
that rely on it, we could/should move that to 3rd party CI.

I'd much rather see us spend our test resources on getting multi-node 
testing running in the gate so we can test migrations in Nova.

-- 

Thanks,

Matt Riedemann