[Linaro-validation] health job notifications

[Fathi Boudra]

On 4 April 2012 01:51, Michael Hudson-Doyle <michael.hudson at linaro.org> wrote:
> On Tue, 3 Apr 2012 11:09:14 +0300, Fathi Boudra <fathi.boudra at linaro.org> wrote:
>> On 3 April 2012 07:41, Michael Hudson-Doyle <michael.hudson at linaro.org> wrote:
>> > Hi all,
>> >
>> > One of the remaining pieces of the job health story is the
>> > notification side: we should get an email whenever a health job fails.
>> >
>> > The reason that I've been procrastinating about this for so long is
>> > that it feels cheap to simply do "if job_failed and is_health_job:
>> > send_email".  It would be better to implement some more general
>> > notification scheme and leverage that.
>>
>> +1
>>
>> > One existing blueprint in the area is this:
>> >
>> > https://blueprints.launchpad.net/lava-dashboard/+spec/linaro-platforms-o-notify-on-failure
>> >
>> > which would get us a little of the way there: we could subscribe to
>> > the failure of the job_complete test in the lava test suite, but that
>> > would tell us about all failing jobs.  We could beef up the
>> > subscription model to limit to a bundle stream or something, but
>> > *that* starts to feel a bit arbitrary (other options would be to
>> > filter on test run tags or other bits of metadata).
>>
>> I'd like to share some use cases for job notifications (not
>> specifically health jobs):
>
> Thanks.
>
>> * As a user or an admin, I want to know the lab health
>> I can subscribe to notifications (rss feed or e-mail) from
>> http://validation.linaro.org/lava-server/scheduler/labhealth/
>>
>> * As a user, I want to get my job results
>> I can subscribe to my notifications in my profile
>
> Here you're envisioning a setting that says "for all jobs I submit,
> please email me the results"?  Would what Paul suggested, i.e. putting
> your email address in the job file be an acceptable compromise?

Yes, that's acceptable.

> It would make subscribing to job health failures a lot less self-service
> but I think for the "own job" case it would be OK.
>
>> > I guess we should take this problem to the other WGs and find out what
>> > notifications they would like to receive (if we can convince them to
>> > care at all until we can test the bootloader :(), and in the mean time
>> > do the cheap thing?
>>
>> In general people care but they have to know the job id they're
>> looking for and monitor the job. It can take time to get a slot in the
>> queue and also to run the tests themselves. Receiving notifications is
>> a huge step forward for the users (at least me).
>
> Yeah.  Let's get something done this cycle!

Thanks.