On Friday 24 June 2016 11:31 PM, Sandeep Chawla wrote:
I didn't quite understand how LXC will help with fastboot.
In V2 when a fastboot device is requested a transparent LXC device could be created automatically. Think of this transparent LXC device like an intermediate dispatcher, where all the commands that used to run from the dispatcher directly, now runs via LXC (ie., contained). This gives the flexibility of choosing your own operating system (currently only Debian and Ubuntu are supported) and java versions to communicate with the DUT. adb daemon is started within the LXC container in order to communicate with the device, similarly the deployment happens via fastboot commands within the container. Once the job finishes the transparent LXC container gets destroyed.
See https://git.linaro.org/lava-team/refactoring.git/blob/HEAD:/nexus9-simple.ya... for a sample job definition in V2 that exercises the above.
A sample job run with nexus9 that demonstrates the above is here - https://staging.validation.linaro.org/scheduler/job/151871
My understanding of LXC was that it replaces KVM for a multinode setup as it is more lightweight and supports usb for things like adb over USB.
We are moving towards dropping multinode for running tests on fastboot devices. The above job is one such example. Also, shortly we will add support for devices such as Hikey, DragonBoard and whatever that uses fastboot and adb.
Thank You.