Hello,
I'm quite new to Lava. As a companion device for a network test I need to just boot up a device (raspberry), login (ssh) and start a tool. No deployment is needed. The switch on/off is still working. As far as I understood my device dictionary needs to extend ssh.jinja, isn't it? Beside the power commands - which parameter I need to define here? And what do I need to define in the Lava test job? I assume something like this is still solved. Is there probably an example available?
Best regards, Thomas
On Mon, 26 Mar 2018 13:19:23 +0000 Thomas Klaehn Thomas.Klaehn@u-blox.com wrote:
Hello,
I'm quite new to Lava. As a companion device for a network test I need to just boot up a device (raspberry), login (ssh) and start a tool. No deployment is needed. The switch on/off is still working. As far as I understood my device dictionary needs to extend ssh.jinja, isn't it? Beside the power commands - which parameter I need to define here? And what do I need to define in the Lava test job? I assume something like this is still solved. Is there probably an example available?
Please read the docs on avoiding simplistic testing - deployment will be needed for this to be a part of a CI process. Please avoid thinking of ssh as a shortcut. Primary SSH is not recommended.
https://staging.validation.linaro.org/static/docs/v2/simple-admin.html#probl...
As a second device involved in a test, then you could just manage the SSH operations from within the test shell definition and use the pi as a network device, not a test device. Then ensure that you handle *all* the complications of persistence and locking on the pi which is then left running as a piece of infrastructure, like a packet switch or PDU. Configure the keys yourself, give the pi a static IP and use it that way.
BTW - you may find that the lava-users mailing list is more suitable for this kind of enquiry.
linaro-validation@lists.linaro.org