| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The lava-docker infrastructure have now splitted master and slave.
So there are no reason to keep tftp/lava-slave on master.
|
|
The start.sh will now be stored in lava-master.
This will help for migrating to official LAVA docker images
|
|
|
|
lava-server manage users list does not display inactive users.
Furthermore the return code of this action is not tested.
lava-server manage users list display also firstname/lastname and this
need to be filtered.
This patch fix thoses problem.
|
|
The current way to do backup assume that slave will be restarted after
each master maintainance.
If master is restarted from backup without slaves restarting bring to
devices files missing.
By backuping devices, a master can be restored from backup without
needing slaves worker to be restarted.
|
|
For storing backups to be restored, it is better to use /root/backup/
instead of /
|
|
When there are no group, the grep return non-0 and setup.sh exits.
This patch fix by doing the filter in two step.
Fixes: e489f60b449b ("lava-master: skip creation of already existing groups")
|
|
When restoring a backup, it is not possible to create a group which
already exists.
This patch adds detection for this case and skip the creation when the
group exists.
|
|
This patch adds support for creating groups
|
|
|
|
|
|
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.
|
|
When restoring a database, token are restored and so cannot be re-created.
|
|
This patch add an easy way to backup postgresql database and needed data stored in filesystem.
In the mean time, a way to restore backup during start is added
|
|
Until now, each docker-compose down will loose all data (jobs, devices, etc...).
By creating a docker volume, the database will now be persistent other restart.
Due to a risk of the lava package reseting the password, it is always reseted at start.
This patch add also another volume for job output which are stored in the filesystem and not in database.
|
|
This patch remove the use of setup.sh during build.
So setup.sh is now ran during startup.
Since setup.sh could ran multiple times (start -> stop -> start) against
the same database, we need to handle already existing objects (user,
devices,...)
So all "add objects" are done only after a check that this object is not
already present.
|
|
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
|
|
This patch add two user options staff and superuser.
This will permit to create users with thoses flag in LAVA.
In the process remove the hardcoded admin user from Dockerfile and move
it in tokens.yaml
|
|
Device-type are jinja2 files and not yaml files and so a have a
different filename.
So this patch correct the handling of custom device-types.
|
|
This commit add suppot for generated files by lalalab-gen.py.
|
|
|
Corentin LABBE