For 2019.04 version, we see next:
Job context
-----------
The schema validator is now checking the content of the `context` dictionary. Only the following keys are now allowed:
* `arch`, `boot_console`, `boot_root`, `cpu`, `extra_options`, `guestfs_driveid`, `guestfs_interface`, `guestfs_size`, `machine`, `memory`, `model`, `monitor`, `netdevice`, `serial`, `vga`
* `bootloader_prompt`, `console_device`, `extra_kernel_args`, `extra_nfsroot_args`, `kernel_loglevel`, `kernel_start_message`, `lava_test_results_dir`, `menu_interrupt_prompt`, `mustang_menu_list`, `test_character_delay`, `tftp_mac_address`
Jobs using keys that are not listed in this list will be rejected.
We usually set an customized context in job, and in device-type jinja2, use this context to just different value to set proper parameters.
After this limit, all things break!
So, my question is:
lava could be designed to as a framework to give freedom to users to do their things as in the past, why we now enhance so many limits to users?
And additional, and workaround for my scenario?
Regards,
Larry
Dear users,
I'd like to add metrics to scale my test farm. Basically I would like to check the occupation rate of the active boards in my farm, to be able to decide whether I need to add extra ones or not.
Do you know if there is a simple way to do it?
Best regards,
Denis
The multinode function of "pass data between devices".Note:
"The message data is stored in a cache file which will be overwritten when
the next synchronisation call is made. Ensure that your scripts make use of
(or copy aside) any MultiNode cache data before calling any other MultiNode
API helpers that may clear the cache."
Does it mean follow example:
roler1:
..
steps:
- lava-send ipv4 ip=192
- lava-send ipv4 ip=193
..
roler2:
step2:
- lava-wait ipv4
- ipdata=$(cat /tmp/lava_multi_node_cache.txt | cut -d = -f 2)
..
After run, is content of roler2 ipdata 193?
In trying to run lava-dispatcher inside a docker container and connect a FRDM-K64F board ran into some issues related to the fact that udev events aren’t seen inside the container since we aren’t typically running systemd/udevd there.
I came across this project that will forward udev events from the host to a container that worked pretty well:
https://github.com/eiz/udevfw
I’ve re-implemented this in python for easier development (added some docker awareness):
https://git.lavasoftware.org/galak/docker-compose/blob/lite/contrib/udev-fo…
Right now running udev-forward.py is kinda kludgy. Wanted to get input on how people think this should work, should we make a daemon out of it? Should there be some kinda of config file? Do we think we need to filter events (and if so how)? Need to look at support for multicasting (support sending to multiple dispatchers). Where should this live, in docker-compose repo?
Other thoughts.
- k
Hello,
I have a remote worker that needs to add a new device-type on the
master.
The remote worker has an auth token with admin/staff/superuser
privileges, and lavacli configured with that token, but when I attempt
to set the new template, I get permission denied:
# lavacli device-types template set da850-lcdk /tmp/new-device-type.jinja2
Unable to call 'device-types.template': <Fault 400: 'Unable to write device-type configuration: Permission denied'>
What permissions am I missing?
Kevin
Hi!
I'm seeing the following issue with lavasoftware/lava-server:2019.04:
http://localhost/static/docs/v2/ gives "Forbidden". Apache log shows the
following:
[Mon May 06 17:57:42.206713 2019] [autoindex:error] [pid 766:tid 140404225701632] [client 172.18.0.1:46780] AH01276: Cannot serve directory /usr/share/lava-server/static/docs/v2/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive, referer: http://localhost/
The easiest way to reproduce is to run:
$ docker run --rm -p 80:80 -it lavasoftware/lava-server:2019.04
And load http://localhost/static/docs/v2/
Change 2019.04 to 2019.03 and it works fine.
I didn't see anything about this mentioned in the release announcement.
I guess the apache config needs some update?
Thanks!
Dan
The name of the action for http download uses a hyphen, not an
underscore. Fix the typos.
Signed-off-by: Kevin Hilman <khilman(a)baylibre.com>
---
doc/v2/timeouts.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/v2/timeouts.rst b/doc/v2/timeouts.rst
index c330f9d89548..50070766abe0 100644
--- a/doc/v2/timeouts.rst
+++ b/doc/v2/timeouts.rst
@@ -259,7 +259,7 @@ block override.
timeouts:
actions:
- http_download:
+ http-download:
minutes: 2
.. _individual_connection_timeout_overrides:
@@ -275,7 +275,7 @@ specific connection timeout which can be longer or shorter than the default.
timeouts:
connections:
- http_download:
+ http-download:
minutes: 2
.. _action_block_timeout_overrides:
--
2.21.0
Hello everyone,
the current LAVA version in stretch-backports is still 2018-11. Is there a reason why it has not been updated since then?
Will newer releases go into buster only? Or will there be updates in stretch-backports in the future?
For stretch users, do you recommend using the LAVA repositories to upgrade to the latest version?
Or should production systems keep using 2018-11 at this moment?
Mit freundlichen Grüßen / Best regards
Tim Jaacks
DEVELOPMENT ENGINEER
Garz & Fricke GmbH
Tempowerkring 2
21079 Hamburg
Direct: +49 40 791 899 - 55
Fax: +49 40 791899 - 39
tim.jaacks(a)garz-fricke.com
www.garz-fricke.com<http://www.garz-fricke.com/>
WE MAKE IT YOURS!
[cid:image001.jpg@01D4FF4A.A2ED9910]
Sitz der Gesellschaft: D-21079 Hamburg
Registergericht: Amtsgericht Hamburg, HRB 60514
Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
