Hi folks,

The 2022.08 tag has been pushed to master on git.lavasoftware.org. .deb packages have been built in GitLab CI and are published at

https://apt.lavasoftware.org/release

Docker images for amd64 and arm64 have been built in GitLab CI and are available from

https://hub.lavasoftware.org/

and

https://hub.docker.com/u/lavasoftware

Changes in this release ==================

## New device-types

New supported devices:

* aaeon-UPN-EHLX4RE-A10-0864 * imx8ulp-evk * imx93-11x11-evk * mt8192-asurada-spherion-r0 * synquacer-uboot

## Grub based device-types

Allow device-type to easily disable interrupting boot. This is not required if grub is build to always drop to a shell.

In the device-type template or device dictionary, add: ```jinja {% set grub_needs_interrupt = false %} ```

## UUU and BCU

Add support for [BCU](https://github.com/NXPmicro/bcu#readme) to the UUU based device-types. This utility allows changing the board's boot configuration (mainly SD card, eMMC or USB Serial Download Protocol) through a serial interface.

In the device dictionary, add:

```jinja {% set bcu_board_id = '2-1.3' %} ```

Then in the job definition, you can use bcu directly:

```yaml - boot: method: uuu commands: - bcu: reset usb - uuu: -b emmc {boot} - bcu: set_boot_mode emmc timeout: minutes: 20 ```

The support has been enabled for imx8dxl-evk imx8ulp-evk imx8mp-evk and imx93-11x11-evk device-types.

## OpenID connect

LAVA server can now support OpenID connect (for instance Azure ID or Keycloack) to authenticate users.

In roder to use this feature, you should install `mozilla-django-oidc` and add to the settings:

```yaml AUTH_OIDC: OIDC_RP_CLIENT_ID: "1" OIDC_RP_CLIENT_SECRET: "bd01adf93cfb" OIDC_OP_AUTHORIZATION_ENDPOINT: "http://testprovider:8080/openid/authorize " OIDC_OP_TOKEN_ENDPOINT: "http://testprovider:8080/openid/token" OIDC_OP_USER_ENDPOINT: "http://testprovider:8080/openid/userinfo" ```

See [mozilla-django-oidc]( https://mozilla-django-oidc.readthedocs.io/en/stable/settings.html) for the full list of options.

## Transfer Overlay

For device-type where the base OS does not provide tools to download over http (like wget or curl), the transfer overlay action can now use NFS.

In order to use this, the job definition would look like:

```yaml - boot: [...] transfer_overlay: transfer_method: nfs download_command: mount -t nfs -o nolock unpack_command: cp -rf ```

Rgds