Open Stack

On 21 March 2016 at 04:15, Rossella Sblendido <rsblendido at suse.com> wrote:

> Hello all,
>
> the tests that we run on the gate for Neutron take pretty long (longer
> than one hour). I think we can improve that and make better use of the
> resources.

Here are some ideas that came up when Ihar and I discussed this topic
> during the sprint in Brno:
>
> 1) We have few jobs that are non-voting. I think it's OK to have
> non-voting jobs for a limited amount of time, while we try to make them
> stable but this shouldn't be too long, otherwise we waste time running
> those tests without even using the results. If a job is still not-voting
> after 3 months (or 4 or 6, we can find a good time interval) the job
> should be removed. My hope is that this threat will make us find some
> time to actually fix the job and make it vote :)
>
> 2) multi-node jobs run for every patch set. Is that really what we want?
> They take pretty long. We could move them to a periodic job. I know we
> can easily forget about periodic jobs, to avoid that we could run them
> in the gate queue too. If a patch can't merge because of a failure we
> will fix the issue. To trigger them for a specific patch that might
> affect multi-node we can run the experimental jobs.
>
> Thoughts?
>

Thanks for raising the topic. That said, I am not sure I see how what you
propose is going to make things better. Jobs, either non voting or multnode
run in parallel, thus reducing the number of jobs won't reduce the time to
feedback though it would improve resource usage. We are already pretty
conscious of that and compared to other projects we already run a limited
numbers of jobs, but we can do better, of course.

Do you have an a better insight of job runtimes vs jobs in other projects?
Most of the time in the job runtime is actually spent setting the
infrastructure up, and I am not sure we can do anything about it, unless we
take this with Infra.


>
> Rossella
>
> __________________________________________________________________________
> 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/20160321/7887a6dd/attachment.html>