The device-type aliases feature has been totally redesigned. You can
now define multiple aliases for a given device-type. In a job
definition, users can use either the device-type or any of its
New supported devices:
It is now possible to override the setting resets_after_flash in the
device dictionary, to support newer firmwares.
Fix the dtb and ramdisk addresses:
dtb: 0x01070000 (was 0x0107f000)
ramdisk: 0x08000000 (was 0x04000000)
Move the ramdisk load address to 0x02200000 (was 0x02100000)
to allow more space for the kernel image and avoid them overlapping.
Allow to use zImage.
This new version creates several database migrations to:
remove TestJob.admin_notifications field
improve DeviceType aliases
replace some CharField types with TextField to remove unnecessary
These may incur a small amount of downtime during the upgrade process
as database migrations happen. A goal for the LAVA development team is
to reduce the frequency of database migrations to reduce this cost as
much as possible. The next planned set of database migrations is
in the 2019.08 release, in August.
The dashboard_app (holding v1 results) has been fully removed,
Due to some limitation in the docker registry embedded in GitLab, we
are no longer building and providing multiarch docker images for every
commit. Multiarch images will still be available on docker
hub for every release.
The dispatcher docker image now includes docker-ce-cli. This will
allow lava to control docker containers from within a lava-dispatcher
container, helping admins to participate in lavafed.
The USE_TEMPLATE_CACHE setting variable has been removed. On newer
Django versions, this option is no longer useful and might even cause
Compressing job logs
Support has been added for compressing log files on the server, using
xz (lzma) compression. Logs will be stored uncompressed as jobs are
running, but they may later be compressed by admins to reduce the
amount of space needed.
The lava-server manage jobs compress command
includes options to allow for management of this. Admins can use this
in cronjobs to automatically compress job logs older than 30 days, or
similar (lava-server manage jobs compress --older-than 30d --slow).
LAVA will automatically decompress old compressed logs on the fly if
they are ever needed again in future.
Job definition schema
The lava-server manage jobs validate command can now send a mail to
the admin when an invalid job is found.
To make use of this, admins can setup a regular cronjob that will call:
lava-server manage jobs validate --mail-admins
The schema validator is now checking the content of the context
dictionary for both single and multinode jobs.
Two new allowed keys have been added: uboot_extra_error_message and