LAVA V2 - pipeline model¶
[ Help Overview] [ Help V1] [ Home ] [ Results ] [ Scheduler ] [ API ]
LAVA V2 is the collective name for the pipeline model for the dispatcher, YAML job submissions, Results, Queries and Charts. It includes major changes to the architecture of LAVA which will improve how a distributed LAVA instance is installed, configured and used for running test jobs.
Migration to V2 started with the 2016.2 release.
- Logging In
- Authentication Tokens
- lava-tool overview
- Submitting your first job
- Glossary of terms
- Getting support
- LAVA Installation
- Migrating to the Pipeline Dispatcher
- Writing a LAVA test definition
- Writing commands to run on the device
- Best practices for writing a LAVA job
- Using Protocols
- Test definitions in version control
- Writing Health Checks for device types
- Exporting data out of LAVA
- Development process
- What do you want from LAVA - FAQs
LAVA Test Developer Guide¶
- Introduction to the LAVA Test Developer Guide
- Refactoring Use Cases
- Pipeline schema
- Writing YAML files for the refactored dispatcher
- LAVA Test Shell
- Refactored Dispatcher Actions
- Protocols
- LAVA Hacking Sessions
- Multi-Node LAVA (JSON)
- MultiNode API
- lava-self
- lava-role
- lava-group
- lava-send
- lava-wait
- lava-wait-all
- lava-sync
- lava-network
- Example 1: simple client-server multi-node test
- Example 2: iperf client-server test
- Example 3: variable number of clients
- Example 4: peer-to-peer application
- Example 5: using lava-network
- Using a flow table to plan the job
- MultiNode Use Cases
- Building and manipulating images
- VLANd support in LAVA test jobs
LAVA Administrator Guide¶
- Setting up a LAVA pipeline instance
- Administrator use cases
- Worked example of migrating a known device
- Identifying device types
- Hidden device type
- Cache Proxy Setting Up
- PDU Daemon
- Deploying a Galaxy Nexus phone
- Deploying an ipmi/pxe-boot Device
- Deploying an iPXE (x86) device
- Deploying LXC devices
- Switch / Hijack User
- LAVA Migrate Management Command
- Administering VLANd support in LAVA
Other Topics¶
- Lava Dispatcher Usage
- Device Capabilities Support
- Packaging lava-server for distributions
- Debian-based distributions
- LAVA Scheduler summary help
- Detailed device information in LAVA Scheduler
- Device type information in LAVA Scheduler
- Job submission failure help
- LAVA job failures, errors, comments and tags
- Lava tool summary help
Developer guides¶
- LAVA development
- Debugging LAVA test definitions
- Convert Multi-Node jobs to single node
- Always use set -x in wrapper scripts
- Avoid using shell operators in YAML lines
- Check that your message ID labels are consistent
- Test your result parsers
- Be obsessive about paths and scripts
- A failed test is not necessarily a bug in the test
- Check your JSON files
- Developing LAVA on Debian
- Lava Dispatcher Design
- Testing the new design
- Compatibility with the old dispatcher LavaTestShell
- Logical actions
- Connections, Actions and the SignalDirector
- Using debug logs
- Debugging on the slave dispatcher
- Adding new classes
- Pre-boot deployment manipulation
- LAVA result visualization