Open Stack

On 06/12/2014 08:15 AM, Julien Danjou wrote:
> On Thu, Jun 12 2014, Sean Dague wrote:
> 
>> However Monty brought up a good point at Summit, that MySQL has a strict
>> mode. That should actually enforce the same strictness.
> 
> I would vote -1 on that, simply because using PostgreSQL should be more
> than that just doing strict SQL.
> 
> For example, in Ceilometer and Gnocchi we have custom SQL type that are
> implemented with different data type depending on the SQL engine that's
> being used. PostgreSQL proposes better and more optimized data type in
> certain case (timestamp or UUID from the top of my head). Not gating
> against PostgreSQL would potentially introduce bugs in that support for
> us.
> 
> Oh sure, I can easily imagine that it's not the case currently in many
> other OpenStack projects. But that IMHO would be a terrible move towards
> leveling down the SQL usage in OpenStack, which is already pretty low
> IMHO.

That's not cacthable in unit or functional tests?

My experience is that it's *really* hard to tickle stuff like that from
Tempest in any meaningful way that's not catchable at lower levels.
Especially as we're going through SQLA for all this access in the first
place.

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.

	-Sean

-- 
Sean Dague
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140612/97415d89/attachment.pgp>