Hi Neil,
I'm replying to this older thread regarding questions that came up for me in a recent mail: https://lists.lavasoftware.org/pipermail/lava-users/2019-February/001693.htm... and the issue you linked: https://git.lavasoftware.org/lava/lava/issues/114
On 24.01.19 16:06, Neil Williams wrote:
Don't obsess about the LXC either. With upcoming changes for docker support, we could remove the presence of the LXC entirely. The LXC with android devices only exists as a unit of isolation for the benefit of the dispatcher. It has useful side effects but the reason for the LXC to exist is to separate the fastboot operations from the dispatcher operations.
What exactly is the envisioned approach for AOSP testing in LAVA? Is it that LXC gets replaced by (user) docker containers? In earlier messages I got the impression that the containers are removed entirely. If not, will there still be one container per test job (thus per DUT)? How is isolation and scalability achieved for fastboot and adb, especially regarding the issues listed here: https://master.lavasoftware.org/static/docs/v2/integrate-fastboot.html ? Do you expect that changes on the test jobs/shells/scripts will be required to be compatible with the new approach, especially for MultiNode testing?
Thanks, Karsten