Age | Commit message (Collapse) | Author | Files | Lines |
|
This patch permit to add a group on boards
|
|
By default LAVA give owning of boards to admin, this patch permit to
give board to a specific user.
|
|
|
|
This patch permits to add tags to device
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>
|
|
Current ser2net present in debian is too old, we need at least the 3.2
release for having the multiple connection support.
This patch download, compile and install ser2net 3.5
|
|
When trying to detect if master is up, we have set a timeout of 60s.
This is good for most of the time, but when the master is restoring a
database, 60s is not enougth.
This patch increase timeout to 300s.
|
|
When re-adding devices to a worker, setup.sh re-add them with UNKNOWN
status.
This patch prevent this for RETIRED/MAINTENANCE status and keep it.
|
|
Instead of calling devices/device-types list for each device, call them
once.
|
|
|
|
The process of building LAVA is hard to maintain.
But since we need to be able to go back in time
(or just stay longer with a specific version)
we need a way to keep a LAVA version.
For achieving this, we build a minimal image with just LAVA
and tag it with the version of LAVA inside.
|
|
This patch add support for using ZMQ auth.
Basicly adding "zmq_auth: True" to a master is sufficient to enable it.
Since "ZMQ certificates" are using a custom format (vs X509 classic), we need to use the custom generator.
For helping with that a temporary docker is generated which handle generating thoses files.
|
|
This patch add support for using screen instead of conmux-console.
screen can be used by adding "use_screen: True" to uart.
screen is necessary for some board with internal uart which have a micro
cut when switching power (like DRA7-EVM and M3ULCB)
|
|
This patch add support for ser2net.
ser2net can be used by adding "use_ser2net: True" to uart.
|
|
This patch upgrade lava-docker to LAVA 2018.4
|
|
This patch implement multiple slave support.
Instead of having a maximum of one master and one slave in one docker
image, it is now possible to have multiple slave accross several docker
host.
For helping this change, a new boards.yaml format is introduced (See
README.md for details)
Note that tokens.yaml is also squashed in boards.yaml
|
|
Starting lava-slave too early is dangerous since some services it needs
are not started yet.
Always start lava-slave in last.
|
|
Since nothing depends on them, copy them at last step.
This prevents rebuild of all docker steps when changing them.
|
|
qemu-kvm is not availlable on ARM.
Install it only on supported x86/x86_64
|
|
On some OS, the rights/user from host are not duplicated on guest.
So the tty is owned by root and cu could not read it.
Force the owning of all tty by uucp
|
|
Recent lavapdu is unpackaged and buggy.
Remove it and replace with a generic PDU command line wrapper
|
|
Since LAVA packages are ephemeral, this patch permit to build a know release of LAVA.
Introducing scripts/build-lava which builds from source any LAVA
compoments from any version tag.
In the same time, stick to 2017.11 as its a know working release for
lava-docker.
|
|
Libguestfs actions are done by the dispatcher, so the slave must be able
to do them.
In the same time, add a TODO for setting volumes as read_only.
|
|
Some boards need cu > 1.07-24
It exists only in debian testing, so add a hack for getting it.
|
|
Under Linux, dynamic port range is 32768-60999, so a clash is possible
with XNBD port range.
Furthermore XNBD constants file have changed in 2017.11
|
|
|
|
|
|
|