LAVA Manual¶
[ Home ] [ Dashboard ] [ Scheduler ] [ API ]
Note
Migrations from the current dispatcher to the pipeline are beginning and will continue as more devices and new deployment methods gain support in the refactoring. Please subscribe to the Mailing lists for information and support. Migrations are expected to take most of 2016 to complete. Support for the current dispatcher will be removed at a point after the completion of the migrations. See the guide to migrating to the pipeline. See also docs for the deprecated JSON features.
- LAVA Overview
- Using tables in LAVA
- 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
- Image Reports 2.0
- Writing Health Checks for device types
- Development process
- What do you want from LAVA - FAQs
Deprecated features¶
All features of the current dispatcher and some features of the server UI which are bound to features of the current dispatcher are deprecated in favour of the pipeline. Support for these features will be removed in a future release.
- Deprecated features
- List of available JSON dispatcher actions
- Filters
- Image Reports
- Virtual Machine Groups
- Migrating from lava-deployment-tool to packages
- Multi-Node LAVA (JSON)
- MultiNode Use Cases
- Boot Management
- Deploying a Bootloader Device
- Hidden device type
- Exporting data out of LAVA
- LAVA-LMP Test Guide
- Configuration files for lava-dispatcher
- Running LAVA Scheduler
- Deploying a board in LAVA
- Writing device information for a new board
- Adding known devices using the LAVA admin helpers
- Adding initial data manually
- Deploying a QEMU Device
- Deploying a KVM (x86_64) Device
- Adding a KVM device to LAVA
- Submitting a KVM Job
- Deploying dummy devices
- LAVA development (Deprecated model)
- Dashboard Bundle Schema
LAVA Test Developer Guide¶
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¶
- Adding Extensions to LAVA Server
- Lava Dispatcher Usage
- Using the ARM Energy Probe
- 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¶
- Developing LAVA on Debian or Ubuntu
- 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