LAVA supports running a single test across multiple devices (of any type), combining those devices into a group. Devices within this MultiNode group can communicate with each other using the MultiNode API.
The test definitions used in MultiNode tests typically do not have to differ much from single-node tests, unless the tests need to support communication between devices in the same group. In fact, the recommended way to develop MultiNode tests is to start simple and build up complexity one step at a time. That’s what the examples here will show.
Note
When viewing MultiNode log files, the original YAML submitted to start the job is available as the MultiNode Definition. The other definition is the parsed content which was sent to each node within the MultiNode job to create a separate log file and test job for each node. It is not likely to be useful to submit the definition of one node of a MultiNode job as a separate job.
The first example is the simplest Multinode test job - the same job runs on two devices of the same type, without using any of the synchronisation calls.
Assuming that you have an already-working simple test job, the first changes to make are in device selection.
device_type
declaration in the job as
that only works for single devices.The MultiNode protocol defines roles. This example snippet creates
a group of three devices, two of the device_type
panda in the
client
role and one of the device_type
beaglebone-black in the
server
role.
protocols: lava-multinode: roles: client: device_type: qemu context: arch: amd64 count: 1 server: device_type: qemu context: arch: amd64 count: 1 timeout: minutes: 6
Note
The role is an arbitrary label - you may use whatever descriptive names you like for the different roles, so long as they are unique.
The role names defined here will be used later in the test job to determine which tests are run on which devices, and also inside the test shell definition to determine how the devices communicate with each other.
After just these changes, your test job will be enough to run a simple MultiNode test in LAVA. It will pick several devices for the test, then run exactly the same set of actions on each device independently.
The next thing to do is to modify the test job to use the roles. The next
example will show how to run different actions on each different device, this
first example uses both roles and so does the same things on two similar devices.
Each action in the test definition should now include the role
field and one or more
label(s) to match those defined roles
.
Here we deploy the same software to the server
and
client
machines by specifying each role in a list:
actions: - deploy: role: - server - client timeout: minutes: 5 to: tmpfs images: rootfs: image_arg: -drive format=raw,file={rootfs} url: http://images.validation.linaro.org/kvm-debian-wheezy.img.gz compression: gz os: debian root_partition: 1
We also use the same boot actions for all the devices:
- boot: role: - server - client method: qemu media: tmpfs prompts: - "root@debian:"
Tests in multinode jobs can run independently, in which case the test action is very similar to a singlenode job:
- test: role: - server - client timeout: minutes: 10 definitions: - repository: http://git.linaro.org/lava-team/lava-functional-tests.git from: git path: lava-test-shell/multi-node/multinode01.yaml name: multinode-basic - repository: git://git.linaro.org/qa/test-definitions.git from: git path: ubuntu/smoke-tests-basic.yaml name: smoke-tests
As well as running the same tasks on similar devices, MultiNode can run
the same tests across different types of devices. This uses the role
support to allocate one deploy
and/or boot
action to one role and a
different block to another role.
This second example will use two panda
devices and one beaglebone-black
device.
These devices need different files to deploy, different commands to boot and will
take different lengths of time to get to a login prompt. Therefore, this
second example also deals with synchronising devices within a multinode group.
To run this testjob, you will need at least one idle beaglebone-black
device
and at least two idle panda
devices.
The examples include details of how to deploy to devices using U-Boot
but the important elements from a Multinode perspective are the use of role
.
protocols: lava-multinode: roles: client: device_type: panda count: 2 server: device_type: beaglebone-black count: 1 timeout: minutes: 6
actions: - deploy: role: - server timeout: minutes: 2 to: tftp kernel: url: http://images.validation.linaro.org/functional-test-images/panda/uImage ramdisk: url: http://images.validation.linaro.org/functional-test-images/common/linaro-image-minimal-initramfs-genericarmv7a.cpio.gz.u-boot compression: gz header: u-boot add-header: u-boot os: oe dtb: url: http://images.validation.linaro.org/functional-test-images/am335x-boneblack.dtb - deploy: role: - client timeout: minutes: 2 to: tftp kernel: url: http://snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/1/vmlinuz ramdisk: url: http://snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/1/initramfs.cpio.gz compression: gz header: u-boot # the bootloader needs a u-boot header on the modified ramdisk add-header: u-boot modules: url: http://snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/1/modules.tar.gz compression: gz # despite this being a Debian initramfs, it is not a complete Debian rootfs, so use oe compatibility os: oe dtb: url: http://snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/1/dtbs/omap4-panda.dtb
A very common requirement in a MultiNode test is that a device (or devices) within the MultiNode group can be told to wait until another device in the group is at a particular stage. This can be used to ensure that a device running a server has had time to complete the boot and start the server before the device running the client tries to make a connection to the server, for example. The only way to be sure that the server is ready for client connections is to make every client in the group wait until the server confirms that it is ready.
Note
It is recommended to use inline definitions for the calls to the synchronisation helpers. This makes it much easier to debug when a synchronisation call times out and will allow the flow of the multinode job to be summarised in the UI.
Synchronisation is done using the MultiNode API and lava-wait. The
test definition specified for the role client
causes the device to
wait until the test definition specified for the role server
uses
lava-send to signal that the server is ready.
definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: client-wait description: "client waiting for server" os: - debian scope: - functional run: steps: - lava-wait server_installed from: inline name: client-wait path: inline/client-wait.yaml
The server
role would need to run an inline definition to
do some work and then tell the client that the server is ready:
definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: client-apache description: "server installation" os: - debian scope: - functional run: steps: - apt update - apt install apache2 - lava-send server_installed from: inline name: apache-client path: inline/apache-client.yaml
This means that each device using the role client
will wait until
any one device in the group sends a signal with the messageID of
server_installed
. The assumption here is that the group only has
one device with the label server
.
The Multinode protocol also provides support for using the Multinode API outside of the test shell definition - any action block can now access the protocol from within specific actions. This makes it possible to even block deployment or boot on one group of machines before others are fully up and running. There is a lot of flexibility here to allow for a wide range of test scenarios.
Each message sent using the MultiNode API uses a messageID which is a string, unique within the group. It is recommended to make these strings descriptive using underscores instead of spaces. The messageID will be included in the log files of the test.
If devices need to wait until all devices with a specified role send a signal, the devices which need to wait should instead use lava-wait-all.
If the expected messageID is never sent, the job will timeout when the default timeout expires. See Timeouts.
See also
Writing jobs using the MultiNode protocol for more information on how to call the Multinode API outside the test shell.
lava-send can be used to send data between devices. A device can send data at any time, and that data will be broadcast to all devices in the MultiNode group. The data can be downloaded by any device in the group using the messageID using lava-wait or lava-wait-all. Data is sent as key-value pairs.
Note
The message data is stored in a cache file which will be overwritten when the next synchronisation call is made. Ensure that your scripts make use of (or copy aside) any MultiNode cache data before calling any other MultiNode API helpers that may clear the cache.
For example, if a device raises a network interface and wants to make
data about that network connection available to other devices in the
group, the device can send the IP address using lava-send
:
run:
steps:
- lava-send ipv4 ip=$(./get_ip.sh)
The contents of get_ip.sh
is operating system specific.
On the receiving device, the test definition would include a call to
lava-wait
or lava-wait-all
with the same messageID:
run:
steps:
- lava-wait ipv4
- ipdata=$(cat /tmp/lava_multi_node_cache.txt | cut -d = -f 2)
Note
Although multiple key value pairs can be sent as a single message, the API is not intended for large amounts of data (messages larger than about 4KB are considered large). Use other transfer protocols like ssh or wget to send large amounts of data between devices.
LAVA provides some helper routines for common data transfer tasks and
more can be added where appropriate. The main MultiNode API calls are
intended to work on all POSIX systems, but some of the helper tools
like lava-network may be restricted to particular operating
systems or compatible shells due to a reliance on operating system
tools like ifconfig
.
It is also possible for devices to retrieve data about the group itself, including the role or name of the current device as well as the names and roles of other devices in the group. See MultiNode API for more information.
The MultiNode protocol defines the MultiNode group and also allows actions within the job Pipeline to make calls using the MultiNode API outside of a test definition.
The MultiNode protocol allows data to be shared between actions,
including data generated in one test shell definition being made
available over the protocol to a deploy or boot action of jobs with a
different role
.
The Multinode protocol can underpin the use of other tools without necessarily needing a dedicated protocol class to be written for those tools. Using the Multinode protocol is an extension of using the existing MultiNode API calls within a test definition. The use of the protocol is an advanced use of LAVA and relies on the test writer carefully planning how the job will work.