On Tue, 20 Aug 2019 at 12:33, Fedusiv Ilya fedusivilya@gmail.com wrote:
Thank you for your answer!! It became more clearly for me.
Also want ask about archive and compression. As I read, each file could be compressed. But what to do, if I have one tarball with all required images. I want to untar folder with all images for fastboot.
Is it possible? Or I need work directly with each image?
If you want to reuse existing LAVA code each partition should have it's own download. However you can do a single file download but that gets you to the territory of modifying downloaded file inside 'lxc'. For prototyping device support I would stick to separate images. Once you get this part working it should be fairly easy to add a few lines that decompress the single tarball inside lxc.
milosz
Ilya
On Tue, 20 Aug 2019 at 11:58, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Tue, 20 Aug 2019 at 09:28, Fedusiv Ilya fedusivilya@gmail.com wrote:
Dispatcher is running on docker container. https://github.com/kernelci/lava-docker
You were right, I miss lxc installation to lava-slave. I passed this step.
In this case you probably need lava-lxc-mocker which fakes all lxc-* calls inside the container. This isn't well documented unfortunately. AFAIK kernelci don't use any LXC for their test jobs. Maybe with exception of lab-bayliblre but that only started recently and they're still struggling a bit with some bugs in LAVA on that front.
And next questions appears:
- Do you have some manual about parameters description in job, cause I have not found it on your website?
flash_cmds_order fastboot_sequence and etc.
If you didn't find that in the docs I'm afraid you're out of luck. There are some bits in LAVA that aren't documented. In this case it's what it says on the cover: flash_cmds_order = the sequence of partitions that fastboot will flash fastboot_sequence = additional parameters to pass to fastboot (like -u to avoid erasing partitions)
- If I'm using local files ( file:// ) where is root directory?
honestly I don't know. Might be the root of dispatcher docker container you're using. In such setup I usually use a local webserver to host the files and avoid this question :)
- Just to be sure, lxc deploys on dispatcher, not on device
I'm not sure what you mean by that. LXC runs on the dispatcher and executes commands there but fastboot flashes files to the target, not to lxc itself.
milosz
Best regards, Ilya Fedusiv
On Tue, 20 Aug 2019 at 10:39, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Tue, 20 Aug 2019 at 08:33, Fedusiv Ilya fedusivilya@gmail.com wrote:
It appears always, right from the start of the job. lxc is installed on my dispatcher.
how about lxc-templates? This is also a dependency for dispatcher.
milosz
Job description https://pastebin.com/5g15YrWy
DUT description: https://pastebin.com/bTKdaM5i
these look OK. If it's not package dependencies, maybe it's the privileges of the user running dispatcher process. This should be root IIRC. Are running dispatcher on metal or in container?
milosz
I know dut description is not full, but I want do step by step, firstly run lxc on device.
Maybe you can give some advice about DUT desc. I'm using fastboot flash for few partitions after that fastboot reboot
flash_cmds_order - it is order of flashing partition fastboot_sequence - what is it?
Do you have some manual about this parameters description, cause have not found it on your website.
And one more question, lxc deployed on dispatcher, right?
Best regards, Ilya Fedusiv
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users