Gustavo Noronha Silva authored Jun 26, 2021 and Paweł Wieczorek committed Jun 30, 2022

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.

Sjoerd Simons authored Jun 25, 2021 and Paweł Wieczorek committed Jun 30, 2022

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...

Gustavo Noronha Silva authored Jun 08, 2021 and Paweł Wieczorek committed Jun 30, 2022

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.

Gustavo Noronha Silva authored Jun 08, 2021 and Paweł Wieczorek committed Jun 30, 2022

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.

Gustavo Noronha Silva authored Jun 08, 2021 and Paweł Wieczorek committed Jun 30, 2022

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.

Sjoerd Simons authored Jun 04, 2021 and Paweł Wieczorek committed Jun 30, 2022

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

Gustavo Noronha Silva authored Apr 29, 2021 and Paweł Wieczorek committed Jun 30, 2022

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

Gustavo Noronha Silva authored Apr 01, 2021 and Paweł Wieczorek committed Jun 30, 2022

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

Gustavo Noronha Silva authored Apr 01, 2021 and Paweł Wieczorek committed Jun 30, 2022

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.

Gustavo Noronha Silva authored Mar 24, 2021 and Paweł Wieczorek committed Jun 30, 2022

The Dockerfile uses the debian packages as the basis, with a few files
patched so that it can work without PostgreSQL on the same system,
giving us more flexibility on how the db is set up.

Signed-off-by: Rémi Duraffort <remi.duraffort@linaro.org>

Fix "lava-server manage devices" crashes: is_public field has been removed

See merge request lava/lava!1798

device-types: add bcm2835-rpi-b-rev2

See merge request lava/lava!1797

Also revert "Fix `device add` and `device copy` ignoring --private option"

This reverts commit d528dfd5

.

Signed-off-by: Rémi Duraffort <remi.duraffort@linaro.org>

Add a device type template for bcm2836-rpi-2-b.

Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

callbacks: allow to receive a callback for both running and finished state

See merge request lava/lava!1796

Fix unused variable in lava_server/management/commands/sync.py

See merge request lava/lava!1795

Fix unused import, line length and sort imports in lava_scheduler_app/api/__init__.py

See merge request lava/lava!1793

Signed-off-by: Rémi Duraffort <remi.duraffort@linaro.org>

Fix a bug introduced in 41672fee



Signed-off-by: Rémi Duraffort <remi.duraffort@linaro.org>

Fix line length in lava_scheduler_app/views.py

See merge request lava/lava!1790

Introduce `REQUIRE_LOGIN` setting and document it

See merge request lava/lava!1787

Fix `device add` and `device copy` ignoring --private option

See merge request lava/lava!1794

It will activate the require login middleware if set to true.

device-types: sc7180-trogdor: remove base_kernel_args

See merge request lava/lava!1726

Create `LavaRequireLoginMiddleware` middleware

See merge request lava/lava!1784

Fixed unused variable warning in lava_scheduler_app/api/

See merge request lava/lava!1792

Fix variable unused warning in lava_scheduler_app/views.py

See merge request lava/lava!1791

It will make it a requirement to be logged in for any page
other than home "/", static files "/static/" or login page
"/accounts/login".

The middleware can be activated by altering `MIDDLEWARE`
configuration variable.

For example:

File: `/etc/lava-server/settings.d/middleware.yaml`

Contents:
```yaml
---
MIDDLEWARE:
  - django.middleware.security.SecurityMiddleware
  - whitenoise.middleware.WhiteNoiseMiddleware
  - django.contrib.sessions.middleware.SessionMiddleware
  - django.middleware.common.CommonMiddleware
  - django.middleware.csrf.CsrfViewMiddleware
  - django.contrib.auth.middleware.AuthenticationMiddleware
  - django.contrib.messages.middleware.MessageMiddleware
  - django.middleware.clickjacking.XFrameOptionsMiddleware
  - lava_server.security.LavaRequireLoginMiddleware
```

Fix lava_scheduler_app/checks.py unused variable warning

See merge request lava/lava!1789

Revert "Add helper for structlog to set it up with LOGGING config value"

See merge request lava/lava!1777