LAVA integration

LMS allows to automatically and remotely configure the LAVA worker running on the LAA and to connect it to the right LAVA server.

Server configuration

LMS allows admins to configure the LAVA instance that the LAA should connect to. LMS will automatically create the right LAVA worker on the LAVA instance server and forward the configuration to the LAA.

The LAA will then automatically start a LAVA worker with the right configuration and the right LAVA version.

When no LAVA instance is configured, LMS will display:

LAVA not configured

Click on the pencil in front of Instances to browse to a list of available LAVA instances.

LAVA instances

Select the right LAVA instance (staging in this screenshot) and click select:

LAVA instance configured

Multiple LAVA instances

It is possible to select multiple LAVA instances. LMS will configure every select LAVA instances servers and forward the configurations to the LAA that will start multiple LAVA workers.

While possible, we discourage this as you will need to properly set LAVA DUT health manually.

DUT configuration

LMS also allows admin to select the DUT attached to an LAA. LMS will automatically configure the LAVA server to use the LAA and the attached DUT with the right device dictionary.

Click on the pencil in front of DUT to browse to a list of supported device-types.

Device-type selection

Select the right device-type (qemu in the screenshot) and click on select.

LAVA configured

Server upgrade

If the LAVA instance server is upgraded (or downgraded), the LAA LAVA worker will automatically match the local version to the server version.

Running LAVA jobs

Before restarting the LAVA worker process, the LAA will wait for the local LAVA job to finish.