GitLab

Add apertis distro scripts to the manifest

See merge request !35

Add test shell scripts for Apertis

See merge request !33

For the apertis deployment data add the same test shell script as are
used on Debian and Ubuntu
Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>

qemu fixes

See merge request !32

The vland block allows setting device_ip (among other things). This is
just a useful for qemu based devices as normal ones.
Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>

prepare_guestfs simply removed the top-level directory from the overlay
tarball; Which is fine if the test results directory is meant to be in /,
but not so much if the directory is a few level deep.

Correct that by directly taking the mountpoint directly into account.

Add apertis as deployment type

See merge request !31

Add apertis as deployment type

See merge request !30

Apertis is a Debian derivative with images that typically do *not* have
bash and often the rootfs is mounted read-only as well

Create a new deployment type which differs in these two aspects from
Debian (sh as shell, /var/lib the location that can be assumed writable

collabora: ensure docs are properly installed

See merge request !29

The base docker image we use configures dpkg to not install most files
to /usr/share/doc/, which makes sense in general. However, it is from
there that LAVA obtains the files it uses to show for its 'Help'
section, so we override the configuration to include the files
installed by lava-server-doc.

Add dell-latitude-5400-sarien device type template

See merge request !17

Add a template for the dell-latitude-5400-sarien x86_64 Chromebook
device type using Depthcharge.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

Add helmchart and Ci based deployment

See merge request !28

Only deploy it from the staging branch though; As that will get an
actual dispatcher attached and our development cluster isn't big enough
for a lot of deployments...

Misc improvements discussed with sjoerd

See merge request !27

re-integrate debian package building CI rules

See merge request !26

At startup we can simply add all of the device types that are supported,
rather than requiring users to go through that additional step when adding
a new device.

Rather than sending the logs to a file in /var/log, make them all go
through stderr (the default used by logging.StreamHandler), so that
it can all be seen by using docker logs.

At startup, we now create the directories used by configuration for when
the setup is not using an overlaid docker volume, but an empty host
directory. The commands are idempotent so should always work.

Dockerization CI and publishing of the lava-server image

See merge request !18

Merge upstream release 2021.05

See merge request !25

For testing publishing docker images from all branches is quite useful;
So make the naming be specific rather then one general name

The new publish stage builds only the lava-server image and publishes
it to the registry.

This tests our containerized lava-server based on the Debian packages by
firing it up, setting up a dispatcher container and a lavacli container
alongside it and then:

- creating a super user
- adding the qemu device type and a qtest device of that type
- using lavacli to set the device dictionary and health test
- running a regular job
- making sure both the health check and the regular job succeeded

This is a very basic definition for just the LAVA service that can
be used along with an override file to properly wire the dispatcher
configuration directories and the database.

A sample override to start the server with a containerized db is
also included, along with a sample env file to specify all the
required configuration through the environment.

LAVA Software 2021.05 release

device-types: fix broken xilinx-zcu102 device-type

See merge request lava/lava!1519

Add asus-C523NA-A20057-coral device type template

See merge request lava/lava!1512

device-types: add BeagleBone Enhanced

See merge request lava/lava!1511