Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2021-02-23 | Add custom rpi4HEADquillback_16.93.0quillback_16.92.0quillback_16.91.1quillback_16.91.0quillback/16.93.0quillback/16.92.0quillback/16.91.1quillback/16.91.0pike_16.0.4pike_16.0.3pike_16.0.2pike_16.0.1pike_16.0.0pike_15.92.0pike_15.91.1pike_15.91.0pike/16.0.4pike/16.0.3pike/16.0.2pike/16.0.1pike/16.0.0pike/15.92.0pike/15.91.1pike/15.91.0octopus_15.0.5octopus_15.0.4octopus_15.0.3octopus_15.0.2octopus_15.0.1octopus_15.0.0octopus_14.94.0octopus_14.93.0octopus_14.92.0octopus_14.91.0octopus/15.0.5octopus/15.0.4octopus/15.0.3octopus/15.0.2octopus/15.0.1octopus/15.0.0octopus/14.94.0octopus/14.93.0octopus/14.92.0octopus/14.91.0needlefish_14.0.5needlefish_14.0.4needlefish_14.0.3needlefish_14.0.2needlefish_14.0.1needlefish_14.0.0needlefish_13.93.0needlefish_13.92.0needlefish_13.91.0needlefish/14.0.5needlefish/14.0.4needlefish/14.0.3needlefish/14.0.2needlefish/14.0.1needlefish/14.0.0needlefish/13.93.0needlefish/13.92.0needlefish/13.91.0marlin_13.0.3marlin_13.0.2marlin_13.0.1marlin_13.0.0marlin_12.93.0marlin_12.92.0marlin_12.91.0marlin_12.90.1marlin_12.90.0marlin/13.0.3marlin/13.0.2marlin/13.0.1marlin/13.0.0marlin/12.93.0marlin/12.92.0marlin/12.91.0marlin/12.90.1marlin/12.90.0lamprey_12.1.6lamprey_12.1.5lamprey_12.1.4lamprey_12.1.3lamprey_12.1.2lamprey_12.1.12lamprey_12.1.1lamprey_12.1.0lamprey_12.0.1lamprey_12.0.0lamprey_11.93.0lamprey_11.92.0lamprey_11.91.0lamprey/12.1.6lamprey/12.1.5lamprey/12.1.4lamprey/12.1.3lamprey/12.1.2lamprey/12.1.12lamprey/12.1.1lamprey/12.1.0lamprey/12.0.1lamprey/12.0.0lamprey/11.93.0lamprey/11.92.0lamprey/11.91.0koi_11.0.5koi_11.0.4koi_11.0.3koi/11.0.5koi/11.0.4koi/11.0.3jellyfish_10.0.3jellyfish/10.0.316.93.016.92.016.91.116.91.016.0.416.0.316.0.216.0.116.0.015.92.015.91.115.91.015.0.515.0.415.0.315.0.215.0.115.0.014.94.014.93.014.92.014.91.014.0.514.0.414.0.314.0.214.0.114.0.013.93.013.92.013.91.013.0.313.0.213.0.113.0.012.93.012.92.012.91.012.90.112.90.012.1.612.1.512.1.412.1.312.1.212.1.1212.1.112.1.012.0.112.0.011.93.011.92.011.91.011.0.511.0.411.0.310.0.3master | 1 | -0/+31 | ||
2021-02-23 | Add r8a7795-agl-refhw | 1 | -0/+8 | ||
2021-02-23 | device-type-patch: fix rcar address | 1 | -0/+35 | ||
2021-02-22 | Merge pull request #135 from montjoie/upgrade-to-2021.01 | 3 | -2/+5 | ||
Upgrade to 2021.01 | |||||
2021-02-10 | Fix rigths on /etc/lava-server/dispatcher-config | 1 | -0/+3 | ||
When using persistent /etc/lava-server, a device-type could be copied without proper rights. But the fix of rights is done during docker build and at that time, volume are not setup, so not fixed. So the rigths fix need to be done at run time. | |||||
2021-02-10 | Upgrade to 2021.01 | 2 | -2/+2 | ||
2021-02-08 | Merge pull request #134 from montjoie/prepare-2021.x | 4 | -20/+27 | ||
Prepare 2021.x | |||||
2021-02-08 | Merge pull request #133 from montjoie/fix-license | 1 | -0/+458 | ||
Add license | |||||
2021-02-05 | Permit to set worker token in boards.yaml | 3 | -7/+27 | ||
LAVA 2020.09 dropped ZMQ and use now a token to authenticate worker against master. lava-docker already handle this by getting token via lavacli. But we need to support to set token in boards.yaml, this patch permits this. Furthermore, the token was given to worker via --token, but this is bad since token can be found by anyone running ps. A better secure way is to use --token-file. | |||||
2021-02-05 | wanted ser2net and cu are in buster | 1 | -13/+0 | ||
The version of cu/ser2net we want are already in buster now, so no need to play with testing/sid. Furthermore, sid give a new ser2net with incompatible config file. | |||||
2021-01-26 | Add license | 1 | -0/+458 | ||
We missed to add a license, fix that. Closes: #132 | |||||
2021-01-04 | Merge pull request #130 from montjoie/support-2020.09plus | 7 | -38/+46 | ||
Support 2020.09plus | |||||
2020-11-23 | Fixes python warning | 1 | -1/+1 | ||
This patch fixes the warning: SyntaxWarning: "is" with a literal. Did you mean "=="? | |||||
2020-11-23 | Add dockcomp_add_cap helper | 1 | -2/+6 | ||
Add an helper to add caps | |||||
2020-11-23 | Handle 2020.09+ workers | 3 | -0/+35 | ||
Since 2020.09, workers does not use ZMQ anymore but use a token. This patch permit our setup to detecte when we use LAVA 2020.09+ and retrieve it from master. | |||||
2020-11-23 | check if envdir exists before creating it | 1 | -1/+2 | ||
If envdir already exists, lavalab-gen.py fail | |||||
2020-11-23 | Remove screen support | 5 | -34/+2 | ||
When I have added screen support, it was a hack for made M3ulcb serial console works. But for a long time ser2net works on m3ulcb. So lava-docker discouraged usage of screen and now it is time to remove it. | |||||
2020-11-04 | Merge pull request #129 from montjoie/no-tftp-ipv6 | 1 | -1/+1 | ||
Disable IPV6 for tftp | |||||
2020-11-04 | Merge pull request #125 from montjoie/fix-2020.07 | 2 | -0/+4 | ||
Fix 2020.07 | |||||
2020-11-04 | lavalab-gen.py: Name workers images with version tag | 1 | -0/+2 | ||
If version is specified, we can generate docker images with tags set to it. | |||||
2020-11-04 | Fix device-types patcher | 1 | -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-11-04 | Disable IPV6 for tftp | 1 | -1/+1 | ||
There is no need to listen on ipv6 inside docker. Furtheremore, this break lava-docker on non-ipv6 machine. | |||||
2020-09-04 | Merge pull request #127 from montjoie/misc-09-2020 | 3 | -8/+35 | ||
Misc 09 2020 | |||||
2020-09-04 | README: add more ZMQ documentation | 1 | -0/+25 | ||
This patch adds more ZMQ documentation | |||||
2020-09-04 | README: add lava-dispatcher-host in prerequisites | 1 | -0/+2 | ||
For fastboot/docker, lava-dispatcher-host could be necessary | |||||
2020-09-04 | deploy.sh: Remove udev rules in a more restrictive way | 1 | -2/+2 | ||
Now lava-dispatcher-host package exists, we should not remove its udev rules. So remove only only lava-docker rules. | |||||
2020-09-04 | backup.sh: do not allocate tty | 1 | -6/+6 | ||
For backuping we dont need a tty. Furthermore, this break AGL cron backup. | |||||
2020-08-18 | Merge pull request #124 from montjoie/BumptoLAVA-2020.07 | 2 | -2/+2 | ||
Increase LAVA version to 2020.07 | |||||
2020-08-18 | Increase LAVA version to 2020.07 | 2 | -2/+2 | ||
Signed-off-by: Corentin LABBE <clabbe@baylibre.com> | |||||
2020-07-17 | Merge pull request #123 from Rosepeter/master | 1 | -1/+1 | ||
[Fix] Ensure proper filename of public master key | |||||
2020-07-14 | [Fix] Ensure proper filename of public master key | 1 | -1/+1 | ||
Currently, the public master key is references as $LAVA_MASTER.key in e.g. scripts/setup.sh. If the key is named master.key it is copied to $LAVA_MASTER.key by scripts/setup.sh. However, no nameing convention for the public master key provided to lavalab-gen.py is documented, so the worker simply will not start if the key is stored as e.g. master-public.key. Running into such error scenarios could simply be prevented by copying the public master key to an appropriatly named file in lavalab-gen.py. This is done here. | |||||
2020-07-13 | Merge pull request #122 from montjoie/postgres-fix | 4 | -25/+75 | ||
Postgres fix | |||||
2020-07-13 | Merge pull request #121 from aliceinwire/handle_upper_case | 1 | -4/+4 | ||
Fix upper case on boards.yaml | |||||
2020-07-13 | Do not apply backup twice | 1 | -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-13 | Persistent DB need /etc/lava-server to be kept. | 1 | -0/+3 | ||
Since the LAVA DB password is set in /etc/lava-server/, we need to keep it accross restart. So put /etc/lava-server on a volume. This will also permit to keep some live configuration like dispatcher IP. | |||||
2020-07-13 | Permit to set the postgres lavaserver password | 4 | -3/+16 | ||
By setting pg_lava_password, the final lavaserver password will be set to this value. | |||||
2020-07-13 | Sort master/workers keywords | 1 | -2/+31 | ||
The keyword list is too long, so split it in multiline, one letter per line. | |||||
2020-07-13 | Fix upper case on boards.yaml | 1 | -4/+4 | ||
Fixes #29 Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com> | |||||
2020-07-10 | Merge pull request #120 from aliceinwire/fix_documentation | 1 | -1/+1 | ||
healthcheck need a supported url protocol scheme to work | |||||
2020-07-10 | healthcheck need a supported url protocol scheme to work | 1 | -1/+1 | ||
Job error: Unsupported url protocol scheme: healthcheck Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com> | |||||
2020-07-09 | Merge pull request #119 from aliceinwire/add_build_args | 2 | -2/+12 | ||
Add option to add docker build args | |||||
2020-07-09 | Merge pull request #117 from Rahix/hws/tftp-binding | 1 | -1/+4 | ||
Make docker bind the TFTP server to the correct interface | |||||
2020-07-01 | Add build_args option explanation to the README file | 1 | -0/+6 | ||
Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com> | |||||
2020-07-01 | Add option to add docker build arguments | 1 | -2/+6 | ||
Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com> | |||||
2020-06-20 | Merge pull request #118 from montjoie/support_2020.05 | 4 | -4/+25 | ||
Support 2020.05 | |||||
2020-06-01 | Handle the change of device-type storage | 2 | -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-01 | Support docker | 1 | -1/+3 | ||
docker need some more bind mounts. | |||||
2020-06-01 | Support 2020.05 | 1 | -1/+7 | ||
LAVA has changed the place of DB password from instance.conf to a yaml file. | |||||
2020-05-20 | Make docker bind the TFTP server to the correct interface | 1 | -1/+4 | ||
With UDP, docker sometimes can't route UDP packets to the correct address because the source address gets mangled [1]. This happens indeterministically because by default the kernel uses some heuristics to decide which interface to use. But in some rare circumstances, those can fail and a wrong source address is used. This can be worked around by explicitly binding to a concrete interface instead of 0.0.0.0. [1]: https://github.com/moby/libnetwork/issues/1729 Signed-off-by: Harald Seiler <hws@denx.de> | |||||
2020-04-28 | Merge pull request #116 from montjoie/misc-04-2020 | 2 | -3/+5 | ||
Misc 04 2020 |