@Milosz Wasilewski 

Do you have more infomation about labgrid/lava integration. Month ago, I also trid labgrid, but it seems the "labgrid-client lock" is not so compatatable with current lava scheduler.
I mean:
a) If I do labgrid lock before submit job to lava, then later if I resubmit the job from web using labgrid, it will surely failure, I lose the benifit of websubmit.
b) If I do it in device.jinja2, something like "labgrid lock" when power on, meanwhile "labgrid unlock" when powner down. Then there is a chance even lava think the resource is idle in lava master, but dispatcher may also fail to lock the device as it's accquired by others, then the job will fail. Even we poll, the job still have timeout impact this.

Anyway, as you said you already tried such, could you share any experience about "when to lock the labgrid resource" in lava, which part is better to do this?
In fact, I assume this is the responsiblity of lava scheduler, but it did not have any customized part for us to add hook unless direct modify code.
What's the best experience for "labgrid lock" in lava? Thanks.
------------------------------------------------------------------
Sender:Milosz Wasilewski <milosz.wasilewski@linaro.org>
Sent At:2019 Nov. 2 (Sat.) 16:29
Recipient:cnspring2002 <cnspring2002@aliyun.com>
Cc:lava-users <lava-users@lists.lavasoftware.org>
Subject:Re: [Lava-users] about lava scheduler

On Sat, 2 Nov 2019 at 04:48, cnspring2002 <cnspring2002@aliyun.com> wrote:
>
> Does lava has roadmap to separate resource management to some open source mechenisim, so it could share resource with other framework?

I assume you know LAVA _is_ an open source project :) Do you have a
use case for what you ask for? Is there any software that can already
do what you propose? I see no reason to spend time on some abstract
concept without existing reason.

Having said that we're experimenting with labgrid
(https://github.com/labgrid-project) as board management layer. This
should work already with existing interfaces.

milosz

> Like spark/hadoop could use mesos/yarn to share resource.
> _______________________________________________
> Lava-users mailing list
> Lava-users@lists.lavasoftware.org
> https://lists.lavasoftware.org/mailman/listinfo/lava-users