Hi Milosz,

Sorry If I made you confuse.

Currently my Worker is running in a debian 12(bookworm) standalone machine not a docker container Image and along with lava-worker I am using the same machine for pytest run (without using the lava-worker interference).

So, as per multinode definition I have to create(will create a container) and boot this docker Image by using
- boot:
role:
- host
command: bash
method: docker
prompts: ['root@lava']

which acts as a docker -- (host) to a device

and my real Hardware :

Is my understanding correct? and Can i use only docker boot method of docker image with out deployment method on (docker01) using internal container information(pytest+ubuntu 23.04) already in place in the lava-worker standalone machine(debian 12).

Regards

Nagendra S

> timeout:
> minutes: 2

On Wed, Apr 10, 2024 at 10:51 PM Milosz Wasilewski <milosz.wasilewski@foundries.io> wrote:

On Wed, Apr 10, 2024 at 5:52 PM Singamsetty Nagendra
<mouli.nagendra@gmail.com> wrote:
>
> Hi Milosz,
>
> As suggested I have gone through the docker process in lava but I am a bit confused here. Our pytest suite required many packages to install and custom steps needed to perform in a linux machine before test runs using pytest.
>
> I am assuming this way please correct me if I am wrong,
>
> 1. Install custom docker image in worker and run the custom steps & requirements.txt. Now I am assuming the docker container is ready to perform the pytest suite operations.

you do it either beforehand or during the lava job.

> 2. Once the above setup is ready in the worker, Can i use this docker running in the worker host as DUT (as per your above suggestion) and our real board(which can execute & give response back via uart for pytest suite commands). Is my understanding correct?

I'm confused. You said pytest connects to your DUT from host. In lava
docker container will emulate the host. "worker host" is not what I
think DUT should be.

> becz according to this definition:
> actions:
> - deploy:
> role:
> - host
> repeat: 3
> image: chaseqi/standalone-fuego:1.4.0
> os: debian
> timeout:
> minutes: 10
> to: docker
>
> - boot:
> role:
> - host
> command: bash
> method: docker
> prompts: ['root@lava']
> timeout:
> minutes: 2
>
> docker image will clone, install and boot in a lava job for each run which makes confusing for me.

yes, you're correct. LAVA job setup is ephemeral - will be created
only for the duration of the test job.

Best Regards,
Milosz

>
> Thank you very much.
>
> Regards,
> Nagendra S
>
>
> On Mon, Apr 8, 2024 at 2:34 PM Milosz Wasilewski <milosz.wasilewski@foundries.io> wrote:
>>
>> On Tue, Apr 2, 2024 at 7:55 AM Singamsetty Nagendra
>> <mouli.nagendra@gmail.com> wrote:
>> >
>> > Hello everyone,
>> >
>> > I would like to integrate & run a bare metal custom tests suite(pytest) on lava. Currently I am executing manually from Host Machine(where pytest is configured and pytest suite will execute) and these commands are sent to DUT and results are collected on Host Machine.
>> >
>> > I am familiar with lava-interactive method but it looks like it will not suit this requirement(Run pytest on Host and collect logs from DUT).
>> >
>> > Does lava suits for this requirement? if someone could give me advice on this that would be great support.
>>
>> You could try using multinode, where one of the nodes is your DUT and
>> the other is docker running on your worker host. Please check Chase's
>> example here:
>> https://github.com/Linaro/test-definitions/blob/master/automated/linux/fuego-multinode/lava-multinode-job-example-fuego.yaml
>> Not quite what you need, but I think it's pretty close.
>>
>> Best Regards,
>> Milosz
>>
>> >
>> > Regards
>> > Nagendra S
>> > _______________________________________________
>> > lava-users mailing list -- lava-users@lists.lavasoftware.org
>> > To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org
>> > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s