Hello Neil,
Please, hold your horses. I am very new to all this, and I need some time to get to the Lava architecture, meaning to get in proper ways. In the sense, I'll try to rephrase the questions, and the working context, since your answers make me more confused than bring the viable solutions... :-(
After reading your email, there are the major addendums to this context, so let me rephrase/rework my initial email. _______
My aim is to use Lava V2 (since Lava V1 is not supported anymore). Let it be.
As I mentioned, I would like to use Beagle Bone Black (BBB) to Lava worker, and from Lava apache to set the proper context for testing BBB HW.
But also, for the starters (seems the step in between) I can do QEMU (the problem is I have no idea how to do this outside of YOCTO Project).
What version of LAVA are you running? On Debian Jessie or Debian Stretch?
I am running Lava v2017/7. Which supports ONLY V1. On Virtual Machine Debian Stretch (using VBox as VMM).
root@stretch:/home/vagrant# uname -a Linux stretch 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 GNU/Linux root@stretch:/home/vagrant# dpkg-query -W -f '${version}\n' 'lava-server' 2017.07
My problem here is that I can build the newest version of the Hashicorp debian/stretch64 using vagrant: https://app.vagrantup.com/debian/boxes/stretch64
But I am NOT able to include the newest Lava into this setup, since apt-get install Lava (and components) is bringing me Lava V1 (even very old version 2016.12-2)???
Q1: how I can bring here the newest Lava 2018.01 (only Version 2 compliant)? What the apt-get install Lava-2018.01 or similar command (I am Fedora monkey, as considering my host setup. Lava I am bringing/installing into the VM over VBox VMM)?
In other words, what is the specific command I need to use in scripts to bring proper Lava 2018.01??? Or any another command? Here is what is now used: sudo DEBIAN_FRONTEND=noninteractive apt-get -y install lava -t stretch-backports
Jinja is V2 - so things are already getting confused. You can use the U-Boot that comes with the BBB but you will need to account for any changes in prompts etc. in the device configuration.
I already use the newest 2017.11 BBB U-Boot, so anyway I need to tap (and change some strings) into the following files (as of my best understanding): root@stretch:/# find . -name base-uboot.jinja2 ./etc/lava-server/dispatcher-config/device-types/base-uboot.jinja2 root@stretch:/# find . -name beaglebone-black.jinja2 ./etc/lava-server/dispatcher-config/device-types/beaglebone-black.jinja2 root@stretch:/# find . -name qemu.jinja2 ./etc/lava-server/dispatcher-config/device-types/qemu.jinja2 root@stretch:/#
Q2: I need here some examples, if they exist. How I can build these scripts, or should I use existing? Or to do something more to hook Lava to ser2net?
I already know: interrupt_prompt: {{ interrupt_prompt|default('Hit any key to stop autoboot') }} <<===== String MUST be changed for U-Boot 2017.11!
Q3: I see that base-uboot.jinja2 is a base file. Should I include it it other .jinja2 files using: {% extends 'base-uboot.jinja2' %}
That looks like you have to manage the power control using a graphical interface and that's not going to work...
Let us skip for now this question (I would like to simplify). PDU is for now not of importance. Focusing to make minimalistic approach to work.
That will show up in /dev/serial/by-id/ and that becomes part of the ser2net configuration.
The whole ttyUSB0 using ser2net TCP is done already, works like a charm. In VM, as pass-through device.
Q4: do I need to use something special here to hook ser2net terminal to Lava?
root@stretch:/# cd /dev/serial root@stretch:/dev/serial# ls -al total 0 drwxr-xr-x 4 root root 80 Feb 9 11:29 . drwxr-xr-x 19 root root 3140 Feb 9 11:32 .. drwxr-xr-x 2 root root 60 Feb 9 11:29 by-id drwxr-xr-x 2 root root 60 Feb 9 11:29 by-path root@stretch:/dev/serial#
That is all managed by LAVA in the test job submission. TFTP is already configured.
in.tftp works like a charm (tftp-ing from VM to U-Boot BBB), as well as dhcpd (dnsmasq, also from VM). So, I have to trust you if you say that I do not need to do anything on that.
Typically, for the BBB, we use the mainline U-Boot that comes from Debian. https://packages.debian.org/stretch/u-boot-omap
In fact, this was not my question (I have latest 2017.11 U-Boot there on mmcblk1 which is /boot partition, works perfectly).
Q5: I wanted to know do I need to set up U-Boot scripts in some ways (as /etc/lava-server/dispatcher-config/device-types/beaglebone-black.jinja2 suggests, as example)??? In other words, make U-Boot environment more as .jinja2 suggests?
Start with QEMU, make sure that's working and get an understanding of how that works with the device dictionary, test job submission, test shell definitions and general LAVA UI usage.
Q6: So, what I need to do here? I use YOCTO project to build all BBB embedded Linux ingredients, uImage, .dtb and root tree, how I can use QEMU from YOCTO as independent .exe in Lava context??? Or, maybe, after all, I can try real image?!
I apologize for the long email. Some features are already solved (tftp, edhcp, ser2net), so we do not need to include them further (as I now understand).
Thank you, Zoran _______
On Fri, Feb 9, 2018 at 10:23 AM, Neil Williams neil.williams@linaro.org wrote:
On 9 February 2018 at 09:00, Zoran S zoran.stojsavljevic.de@gmail.com wrote:
Hello to the Lava users,
I am the new Lava user. My aim is to use Lava (for now V1)
Welcome. Please take care with terminology. V1 is already dead, please don't start there. We will be unable to help you with your V1 setup. Your later comments refer to elements from V2, so please take care with which bits of documentation you are following.
What version of LAVA are you running? On Debian Jessie or Debian Stretch?
setup for my testing, from the beginning just to hook-up my Beagle Bone Black (BBB) to Lava worker, and from Lava apache to set the proper context for testing BBB HW.
As I am reading Lava framework, I got the following impression about the test suite: [1] I need to prepare BBB's U-Boot for the Lava U-Boot jinja2 setup;
Jinja is V2 - so things are already getting confused. You can use the U-Boot that comes with the BBB but you will need to account for any changes in prompts etc. in the device configuration.
[2] I need to hook-up my EG-PMS2-LAN (energenie) to the Lava (to PO and POFF HW platform);
That looks like you have to manage the power control using a graphical interface and that's not going to work. You'll need to investigate how to control that unit using the command line only. Does it have a telnet API or other serial API? That will all be down to you to configure. You might want to look at using an APC PDU instead as those already have support in lavapdu (or can use SNMP if you configure the worker appropriately).
[3] I need to hook-up ser2net interface (which I already have working over TCP) to the Lava. so Lava can control it;
That goes into the device dictionary, as per the docs. Do you have the FTDI cable to attach to the BBB to get the serial connection? That will show up in /dev/serial/by-id/ and that becomes part of the ser2net configuration.
[4] I need to hook-up uImage, .dtb and ramdisk images to the Lava (which will be FTPed and set in memory for board setup and testing).
TFTP, not FTP.
That is all managed by LAVA in the test job submission. TFTP is already configured.
Question 1: Does manual have some Beagle Bone Black U-Boot default scripts, which should be provisioned to the BBB U-Boot for the correct Lava U-Boot behavior?
Typically, for the BBB, we use the mainline U-Boot that comes from Debian. https://packages.debian.org/stretch/u-boot-omap
Question 2: How do I do [1], [2], [3] and [4], does Lava manual have some explanation as working example how to do these points?
Those are mostly specific to your local setup.
Question 3: Anything else I missed for the proper Lava test setting?
Start with QEMU, make sure that's working and get an understanding of how that works with the device dictionary, test job submission, test shell definitions and general LAVA UI usage.
Thank you in advance, Zoran
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/