Open Stack

Lots of questions, I'm sorry.

Are you planning to drop them indefinitely or is it temporary ? Is it to
help alleviate the gate from it's current misery ?

Why were these tests introduced in the first place ? To find issues or
bottenecks relative to scale or amount of operations ? Was it a request
from the operator community ?

I have a strong feeling there is a very real need for *something* that is
able to find silly issues that only manifest themselves beyond the scale of
one VM before we ship something to the operator community.

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]
On Feb 10, 2016 7:37 AM, "Sean Dague" <sean at dague.net> wrote:

> The largeops tests at this point are mostly finding out that some of our
> new cloud providers are slow - http://tinyurl.com/j5u4nf5
>
> This is fundamentally a performance test, with timings having been tuned
> to pass 98% of the time on two clouds that were very predictable in
> performance. We're now running on 4 clouds, and the variance between
> them all, and between every run on each can be as much as a factor of 2.
>
> We could just bump all the timeouts again, but that's basically the same
> thing as dropping them.
>
> These tests are not instrumented in a way that any real solution can be
> addressed in most cases. Tests without a path forward, that are failing
> good patches a lot, are very much the kind of thing we should remove
> from the system.
>
>         -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160210/8dc4c1c1/attachment.html>