Open Stack

On 17 October 2016 at 22:10, Wesley Hayutin <whayutin at redhat.com> wrote:

> Greetings,
>
> The RDO CI team is considering adding retries to our calls to
> introspection again [1].
> This is very handy for bare metal environments where retries may be needed
> due to random chaos in the environment itself.
>
> We're trying to balance two things here..
> 1. reduce the number of false negatives in CI
> 2. try not to overstep what CI should vs. what the product should do.
>
> We would like to hear your comments if you think this is acceptable for CI
> or if this may be overstepping.
>

I don't have a strong opinion about this, I'd be curious to hear what the
Ironic folk think.

However, if it is considered an okay idea, I wonder if this is something we
should add as a feature in Ocata to the Introspection workflows in Mistral.
It would presumably be more efficient to try failing nodes twice rather
than re-running the full process. We could then have various retry limits
to make it configurable for users.


Thank you
>
>
> [1] http://paste.openstack.org/show/586035/
>
> __________________________________________________________________________
> 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/20161018/00e445ef/attachment.html>