Hi Lava Team Can you assist me on this usecase that how i can share LXC data with DUT. We have LXC and DUT TEST defined in a Job. LXC Tests generates some data and logs which is required to be accessed by DUT TEST.
On 25 July 2017 at 12:13, Chetan Sharma chetan.sharma@timesys.com wrote:
Hi Lava Team Can you assist me on this usecase that how i can share LXC data with DUT. We have LXC and DUT TEST defined in a Job. LXC Tests generates some data and logs which is required to be accessed by DUT TEST.
Generally, no. This is not possible.
Please attach the test job submission.
The only way to communicate between DUTs is MultiNode and the LXC used to support deployments of devices is not a DUT. You could define a second LXC in a MultiNode job and then pass data between that LXC and the device. It is not possible to pass data to the LXC associated with the device - exactly the same as it is not possible to pass data directly to the worker using MultiNode.
On 25 July 2017 at 12:42, Neil Williams neil.williams@linaro.org wrote:
On 25 July 2017 at 12:13, Chetan Sharma chetan.sharma@timesys.com wrote:
Hi Lava Team Can you assist me on this usecase that how i can share LXC data with DUT. We have LXC and DUT TEST defined in a Job. LXC Tests generates some data and logs which is required to be accessed by DUT TEST.
Generally, no. This is not possible.
Please attach the test job submission.
The only way to communicate between DUTs is MultiNode and the LXC used to support deployments of devices is not a DUT. You could define a second LXC in a MultiNode job and then pass data between that LXC and the device. It is not possible to pass data to the LXC associated with the device - exactly the same as it is not possible to pass data directly to the worker using MultiNode.
This isn't exactly correct in all cases. Please check this job: https://staging.validation.linaro.org/scheduler/job/179904/definition
There is LXC and HiKey board. LXC is first used to provision the board. Than it usually sits idle. In this case I used the LXC to execute tests on HiKey with test-runner.py [1]. It won't work out of the box though. Communication between LXC and HiKey happens over SSH. So HiKey has to run SSH server, LXC needs to know the IP address of HiKey. This is done using device dictionary and DHCP configured the way HiKey always gets the same IP address.
This setup is probably not exactly what you need, but there is a way to do LXC - DUT communication without Multinode.
[1] https://git.linaro.org/qa/test-definitions.git/tree/automated/utils/test-run...
miilosz
On Tuesday 25 July 2017 05:50 PM, Milosz Wasilewski wrote:
There is LXC and HiKey board. LXC is first used to provision the board. Than it usually sits idle. In this case I used the LXC to execute tests on HiKey with test-runner.py [1]. It won't work out of the box though. Communication between LXC and HiKey happens over SSH. So HiKey has to run SSH server, LXC needs to know the IP address of HiKey. This is done using device dictionary and DHCP configured the way HiKey always gets the same IP address.
This setup is probably not exactly what you need, but there is a way to do LXC - DUT communication without Multinode.
Another way I could think of when the test job involves Android OS (on the DUT) is to push the data produced in the LXC to the DUT using 'adb push' and vice versa using 'adb pull'.
Thank You.
lava-users@lists.lavasoftware.org
-
Chetan Sharma -
Milosz Wasilewski -
Neil Williams -
Senthil Kumaran S