[Linaro-validation] Improving health checks

Le.chi Thu le.chi.thu at linaro.org
Fri Feb 10 20:09:06 UTC 2012


I think we should have a status field per device rather than per device type.

Since the scheduler is firing the heath check job, if the device have
run job successfully recently (last 24 hour for example), the health
check should be skip for that device.

The heath check jobs should have lower prio that the job submit by our user.

/Chi Thu

On 10 February 2012 09:01, Paul Larson <paul.larson at linaro.org> wrote:
> Following on to the discussion earlier this week, I wanted to kick off a
> discussion about how to implement one part we discussed, which is to make
> health checks something that lava natively understands and knows how to do,
> rather than just a lump of jobs scheduled daily from cron.  Here are my
> thoughts, and I'll let you decide how much it's crack.
>
> 1. extend the scheduler model for devices? to add a text blob for storing a
> health check job
>   - downside is that we would have add one of these for every single board
>   - maybe it makes sense to do this for device type instead and have the
> scheduler just start it on the proper board?
>   - we should make sure that these jobs use a locally downloadable, complete
> image
> 2. at the beginning of every day, if the board is NOT in offline or going
> offline state, insert this job into the queue for the board
>   - Is there a good way to do this automatically with some internal
> mechanism - not cron from the outside?
> 3. Link the result of this job to the health check stuff already in progress
>
> thoughts? suggestions?
>
> _______________________________________________
> linaro-validation mailing list
> linaro-validation at lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-validation
>



More information about the linaro-validation mailing list