summaryrefslogtreecommitdiffstats
path: root/lava-master
AgeCommit message (Collapse)AuthorFilesLines
2021-02-10Upgrade to 2021.01Corentin LABBE1-1/+1
2020-11-04Fix device-types patcherCorentin LABBE1-0/+2
The device-types patchs were not used since 9918419127b ("Handle the change of device-type storage"). The patch was correctly modified with path hacks, but not applied.
2020-08-18Increase LAVA version to 2020.07Corentin LABBE1-1/+1
Signed-off-by: Corentin LABBE <clabbe@baylibre.com>
2020-07-13Do not apply backup twiceCorentin LABBE1-21/+26
If we use persistend_db, a restart with an image containing a backup will re-apply the backup and so overrun current DB. So when backup is used, apply a flag to not reuse it.
2020-07-13Permit to set the postgres lavaserver passwordCorentin LABBE2-2/+7
By setting pg_lava_password, the final lavaserver password will be set to this value.
2020-06-01Handle the change of device-type storageCorentin LABBE2-2/+15
device-types are now in /usr/share/lava-server/device-types/ and so device-type-patch does not work anymore. This patch support both location
2020-06-01Support 2020.05Corentin LABBE1-1/+7
LAVA has changed the place of DB password from instance.conf to a yaml file.
2020-03-03Update LAVA to 2020.02Corentin LABBE2-26/+1
2020-03-02Merge pull request #111 from montjoie/pr-2020.01Kevin Hilman1-0/+2
Pr 2020.01
2020-01-16master: handle migrationsCorentin LABBE1-0/+2
This patch permits to handle migrations when upgrading.
2019-12-06Allow using different folder than /tmp for tar operationsPhilippe Mazet1-0/+4
When backup size grows to several GB, tar operation can fail with "no space left on device" error. This is because of the limited size of /tmp on certain machines This changes allows using a different folder. This can be done by simply adding such line in Dockerfile: ENV TMPDIR /wherever/tmp
2019-10-09lava-master: patch: Add fix for visibility issueCorentin LABBE1-0/+25
This patch backport a LAVA patch which fix an issue with lavacli commands.
2019-09-27lava-master: automaticaly agree on DB migrationCorentin LABBE1-1/+1
2019-09-27Upgrade to 2019.09Corentin LABBE1-2/+1
2019-08-26Upgrade to 2019.07Corentin LABBE3-42/+15
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
2019-06-26Permit to modify apache2 configurationCorentin LABBE2-0/+2
This patch permits to copy configurations files in lava-master/apache2/, there will be copied over in the /etc/apache2 directory of master.
2019-06-25lava-master: remove tftp/lava-slaveCorentin LABBE3-11/+1
The lava-docker infrastructure have now splitted master and slave. So there are no reason to keep tftp/lava-slave on master.
2019-06-25lava-master: move the start.sh from lava-master-base to lava-masterCorentin LABBE2-0/+41
The start.sh will now be stored in lava-master. This will help for migrating to official LAVA docker images
2019-06-04Permit to host healtchecksCorentin LABBE1-0/+1
This patch adds an optional container which host healthchecks images.
2019-05-09lava-master: Ensure that device-types are owned by LAVACorentin LABBE1-0/+1
Like for health-checks, device-types must be owned by lavaserver
2019-04-03lava-master: fix the applying of patchs against LAVACorentin LABBE1-3/+4
Lava patch which contains device-type changes are ignored since final device-types are already in /etc/lava-server/device-types/ So for fixing this, we apply lava-patch before device-type patch and synchronize them.
2019-04-01lava-master: warning when overwriting existing device-typesCorentin LABBE1-0/+4
2019-04-01Use 2019.03Corentin LABBE1-1/+1
Since 2019.03 is ready, use it
2019-03-19lava-master: handle order of LAVA patchsCorentin LABBE1-1/+1
The current way to add patchs is non-determinist and could lead to failure to build. This patch made the order determinist by using sort
2019-01-14Permit to choose loglevelCorentin LABBE2-0/+2
By default, all process use the DEBUG loglevel, this could be too much for a production server. This patch permits to tune the loglevel.
2019-01-14lava-master: better check of already existing usersCorentin LABBE1-2/+14
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.
2018-12-18Use 2018.11Corentin LABBE1-1/+1
This patch made lava-docker use a known to work dockerhub tag. Keep the latest tag for internal work.
2018-12-11backup: backup also devices filesCorentin LABBE1-0/+6
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.
2018-12-11lava-master: use /root/backup/ for storing backupsCorentin LABBE2-6/+7
For storing backups to be restored, it is better to use /root/backup/ instead of /
2018-12-05lava-master: fix group handlingCorentin LABBE1-1/+2
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")
2018-11-27lava-master: skip creation of already existing groupsCorentin LABBE1-5/+15
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.
2018-11-02lavalab-gen.py: permit to set env settings on slaveCorentin LABBE2-4/+2
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.
2018-10-31lava-master: fix permissions on health-checksPatryk Mungai1-0/+1
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>
2018-10-17Permit to create groupsCorentin LABBE2-0/+25
This patch adds support for creating groups
2018-09-18README: enhance documentation on dependencies and CSRF issuesCorentin LABBE1-1/+0
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.
2018-07-26Permit to configure email for LAVA usersCorentin LABBE1-0/+4
2018-07-26Permit to choose the FQDN printed in emailCorentin LABBE2-0/+8
2018-07-25Split dockerfile in two imagesCorentin LABBE7-508/+1
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.
2018-07-24lavalab-gen.py: token is optional for usersCorentin LABBE1-0/+2
2018-07-23Handle ZMQ authCorentin LABBE3-0/+11
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.
2018-07-20Do not add already existing tokenCorentin LABBE1-2/+7
When restoring a database, token are restored and so cannot be re-created.
2018-07-20Permit to backup/restore lavaserver databaseCorentin LABBE3-0/+16
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
2018-07-19Made the database persistentCorentin LABBE1-0/+7
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.
2018-07-12Exit if device-types patch does not applyCorentin LABBE1-1/+1
2018-07-12Add device-types and tokens at startupCorentin LABBE3-8/+20
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.
2018-07-12Permit to have backported LAVA patchCorentin LABBE2-0/+3
If backporting LAVA patch is necessary, this patch add an easy way to do it.
2018-07-12Do not copy start/stop scripts twiceCorentin LABBE1-4/+0
It is unnecessary to copy start/stop twice during build
2018-06-05Permit to access LAVA webadmin via httpsCorentin LABBE1-16/+0
This patch permits to access LAVA webadmin via HTTPS. Resolve SPEC-1493
2018-06-05Allow to have device-types-patchCorentin LABBE2-0/+3
2018-06-05Upgrade to 2018.4Corentin LABBE7-14/+419
This patch upgrade lava-docker to LAVA 2018.4