| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Be more clear on how to upgrade
|
|
Fix 09 2018
|
|
default_slave was not in valid keyword and thus generate a warning.
This patch set it as valid and document it in the mean time.
|
|
In the board loop, the slave name is stored in slave_name, but some code
after use worker_name.
This works when only one slave exists, but fail when it exists multiple
slave.
This patch replace slave_name by worker_name for being consistent with
the naming used in the rest of code.
|
|
|
|
lava-slave: increase connect to master timeout
|
|
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.
|
|
Csrf fix
|
|
lava-logs and lava-server-gunicorn init script fail to restart.
This is due to a missing --make-pidfile option.
|
|
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.
|
|
When login on LAVA via https, a CSRF failure is done.
This is due to missing CSRF_TRUSTED_ORIGINS.
|
|
Miscfix 07 2018b
|
|
Splitimage
|
|
|
|
|
|
|
|
|
|
The current script just check for zmq_auth presence and does not check
if it is set to false.
this patch fix that!
|
|
|
|
We no longer build LAVA from source, so all build-lava stuff must go.
|
|
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.
|
|
lavalab-gen.py: token is optional for users
|
|
|
|
Zmq auth
|
|
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.
|
|
Persistantdb pr
|
|
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.
|
|
Fix072018
|
|
|
|
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.
|
|
If backporting LAVA patch is necessary, this patch add an easy way to do
it.
|
|
It is unnecessary to copy start/stop twice during build
|
|
This patch warnings the user when using lavalab-gen.py with unknow
keywords in boards.yaml.
|
|
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)
|
|
lavalab-gen: add \n between custom options
|
|
This patch add support for ser2net.
ser2net can be used by adding "use_ser2net: True" to uart.
|
|
If a board has mutliple custom options, they need to be separated by a newline.
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
|
|
Multi slave 2018 x
|
|
This patch permits to access LAVA webadmin via HTTPS.
Resolve SPEC-1493
|
|
|
|
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
|
|
Miscfix03
|
|
Some board need some jinja options (ex: nanopik2 need use_vendor_uboot) but
adding all possible options is not worth the cost.
So this patch adds a custom way to add option to board file.
|
|
For clarify the use of macaddr, rename it to uboot_macaddr.
|
|
Some boards have broken uboot dhcp, so we need to set a static ip in
uboot.
This patch add a way to specify such IP via uboot_ipaddr.
|
|
Some generated files are not cleaned, add them to the toclean list
|
khilman
Corentin LABBE
Kevin Hilman