| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
When doing a qemu-only slave, there are no need of NBD.
This patch adds a use_nbd option.
|
|
When doing a qemu-only slave, there are no need of TFTP.
This patch adds a use_tftp option.
|
|
On my gentoo, using yaml.load now give:
Traceback (most recent call last):
raise RuntimeError("Unsafe load() call disabled by Gentoo. See bug #659348")
RuntimeError: Unsafe load() call disabled by Gentoo. See bug #659348
Note that on recent ubuntu, a warning appears also.
YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
This is due to a security risk of using yaml.load()
Since we didnt rely on any behavour provided by load(), let's convert the call to safe_load().
|
|
This patch adds support for the device-type aliases.
|
|
This patch upgrade LAVA to 2019.07 via their official docker images.
Along with the change of the baseimage from our lava-xx-base to official
2019.07, some minor changes are needed:
- Activate the en_US.UTF-8 locale needed for postgresql
- chown to lavaserver all copied device-types
- Fix the start scripts for using the official entrypoints
|
|
When a custom way of getting serial is set, we should not defaulting to
ser2net.
This is the case for hsdk which use a spetial console handler via connection_command.
|
|
The README mentions using localhost in the quickstart guide, but it
doesn't work if only 127.0.0.1 is in that list.
|
|
This patch adds an optional container which host healthchecks images.
|
|
Since bind_dev could be set to false, just testing its presence is
wrong.
This patch made lavalab-gen.py check its value.
|
|
The NFS code produce a working docker-compose.yml but this file is
dumped before this modification.
This patch moves the docker-compose.yml dump after last modifications of
the dockcomp variable.
|
|
Enabling TAP devices is global to a whole worker.
So having the flag on devices is wrong.
This patchs move the flag "tap" at worker level.
|
|
|
|
This patchs adds a new flag "lava-coordinator" for slave which enables
the generation of a lava-coordinator.conf file.
|
|
This patch permit to adds extra devices (like a USB relay) in the slave
|
|
Currently arm64 workers need to modify at hand the from in the
dockerfile for using arm64 images.
This patch automate this;
|
|
This patch adds an helper for doing NFS jobs
|
|
Since 2019.03 , ALLOWED_HOSTS is mandatory in settings.conf.
Without it all requests are denied with code 500.
|
|
Misc
|
|
By default, all process use the DEBUG loglevel, this could be too much
for a production server.
This patch permits to tune the loglevel.
|
|
For full networking capacity, qemu need to access TAP devices.
This patch adds the choice of use it via the tap keyword.
|
|
If two qemu with KVM enabled are on the same node, the device map
"/dev/kvm:/dev/kvm" will be present twice.
This patch adds an helper for preventing this.
This will also clean the code later which adds serial device.
|
|
Adding custom options for LAVA often requires specific formatting for
the LAVA jinja2 files, including single or double quotes. Rather than
also using quotes in the boards.yaml file, use YAML "plain style"[1]
avoids the need to add extra quotes or escapes.
When using the "|-" for plain style, the custom_options will appear to
lavalab-gen as a one long string, rather than a list of options, so
here we modify lavalab-gen to handle strings slightly differently than
a list.
[1] https://yaml.org/spec/1.2/spec.html#id2788859
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
|
|
When someone want to use screen/conmux for a board, the current situation imply
to adds use_ser2net = False.
This patchs remove this need.
|
|
This patch makes ser2net the default uart handler.
|
|
When using a PDU with crelay, we need to access the whole content /dev/hid/ and so need to bind the whole /dev/
This is also necessary when using the HSDK board which have a serial
which appears only when board is powered.
|
|
|
|
lavalab-gen.py: Remove udev template for support of interfacenum
|
|
The current udev templating is bad since adding a new optional keyword
lead to numerous ifelse and templates.
This patch simply generate a udev line part by part.
This made adding interfacenum easier.
This will also permit to mix devpath/serial/etc.. without any problem
|
|
This patch adds missing newline after overrides.
Without them, the generated file is not a valid yaml file
|
|
Since some setup use distinct boards.yaml for master and slave, a way to
set env settings for a slave via the master node is needed.
|
|
This patch permits to add some env settings on slave.
The primary goal of this is to permits to add a proxy for a specific slave.
|
|
When creating a split boards.yaml with only one master which uses ZMQ,
no way to adds slave key exists.
This patch fix that by adding a way to copy all slave keys.
|
|
This patch adds an easy way to choose an alternate file than
boards.yaml.
|
|
This patch permit to add a group on boards
|
|
This patch adds support for creating groups
|
|
By default LAVA give owning of boards to admin, this patch permit to
give board to a specific user.
|
|
This patch rename export_ser2net to expose_ser2net.
The old export_ser2net is still handled but we now print a deprecating
message.
|
|
This patch adds a way to choose a number of ports to be exposed from
host to slave.
|
|
This patch permits to add tags to device
Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
|
|
This patch permits to have a boards.yaml without the master node.
In the same time, it permit to have also only a master node without
slave.
Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
|
|
The ZMQ key file names are expected to have specific names in the
containers (e.g. $LAVA_MASTER.key). However, when using existing key
files, they are simply copied into the containers, and if they don't
match the exact requirements, encryption will silently fail.
Fix this by allowing arbitrary filenames for existing keys, but ensure
they are copied into the container with the expected filenames.
Related, when using auto-generated keys, the generated master key is
simply "master.key" in the slave. Fix this by ensuring that
"master.key" is copied to $LAVA_MASTER.key when the slave container
starts.
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
|
|
This patch add a ser2net max-connections for all boards
|
|
ser2net port range started from 60000 which is between the Linux dynamic port range: 32768-60999
This patch changes it outside of this range to 63001.
|
|
default_slave was not in valid keyword and thus generate a warning.
This patch set it as valid and document it in the mean time.
|
|
In the board loop, the slave name is stored in slave_name, but some code
after use worker_name.
This works when only one slave exists, but fail when it exists multiple
slave.
This patch replace slave_name by worker_name for being consistent with
the naming used in the rest of code.
|
|
When login on LAVA via https, a CSRF failure is done.
This is due to missing CSRF_TRUSTED_ORIGINS.
|
|
|
|
The current script just check for zmq_auth presence and does not check
if it is set to false.
this patch fix that!
|
|
|
|
We no longer build LAVA from source, so all build-lava stuff must go.
|
Corentin LABBE
Tobias Olausson
khilman
Kevin Hilman