Age | Commit message (Collapse) | Author | Files | Lines |
|
base-images: permit to install LAVA 2018.11
|
|
|
|
Ser2net options
|
|
|
|
|
|
lavalab-gen.py: Remove udev template for support of interfacenum
|
|
README: add contact informations
|
|
lavalab-gen.py: Add missing newline after overrides
|
|
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
|
|
lavalab-gen.sh: Handle arguments
|
|
This patch mades lavalab-gen.sh pass all arguments to lavalab-gen.py
Cleaning in the process the non-needed "rm build-lava"
|
|
Allow seeting ENV variables from YAML config.
|
|
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.
|
|
Permit to have backported LAVA patch on slave
|
|
backup: Create a symlink to recent backup
|
|
Previoulsy it was possible to backport LAVA patch only on master, this patch permits it on
slave.
|
|
backup will now create a backup-latest symlink to the backup just being
made.
|
|
Misc. fixes for oct sprint
|
|
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.
|
|
extra_actions is broken since commit f3d53d64922d ("lava-slave/Dockerfile: copy all scripts in one actions")
It is not anymore copied in /root but in /usr/local/bin/
|
|
This patch adds missing documentation on how to choose the slave owing a
device.
|
|
Changing the ownership of /etc/lava-server/dispatcher-config/health-c…
|
|
This fix allows users to add healthcheck files via API by changing
ownership from root to lavaserver. Without it users encounter a
permissions error.
Signed-off-by: Patryk Mungai <patryk.mungai-ndungu.kx@renesas.com>
|
|
README: add documentation on how to add patch for LAVA and device-type
|
|
lava-docker can patch LAVA and add/modify device-types, but the
documentation was lacking on how to do it.
|
|
lavalab-gen: permit to choose alternate boards.yaml
|
|
This patch adds an easy way to choose an alternate file than
boards.yaml.
|
|
Permit to give board to user
|
|
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.
|
|
lavalab-gen.py: Permit to customize exported ports to a slave
|
|
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.
|
|
lava-slave/Dockerfile: copy all scripts in one actions
|
|
|
|
README: enhance documentation on dependencies and CSRF issues
|
|
This patch add documentation on how to use lava-docker on arm64.
|
|
This patch add the missing pyyaml requirement in the documentation,
fixing issue #31 in the process.
Note that this patch adds also a requirements.txt for easy pip install.
This patch also a note on http_fqdn stating this option as necessary
when using https.
|
|
Permit to add tags to devices
|
|
This patch permits to add tags to device
Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
|
|
lavalab-gen.py: permit to have no master in boards.yaml
|
|
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>
|
|
lavalab-gen: fiz zmq key filename assumptions
|
|
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>
|
|
Ser2net multiconnections
|
|
This patch add a ser2net max-connections for all boards
|