LAVA V1 - deprecated¶
[ Help Overview] [ Help Pipeline (V2)] [ Home ] [ Dashboard ] [ Scheduler ] [ API ]
LAVA V1 is the collective name for the LAVA support which involves JSON submissions,
deploy_linaro_kernel
and associated actions, Bundles, BundleStreams, Filters
and Image Reports (including Image Reports 2.0).
End Of Life for LAVA V1¶
Migration to V2 started with the 2016.2 release as the new codebase grew and improved. We are now reaching the end of this long process. As announced, LAVA V1 is now (September 2017) being retired, in the following steps:
- 2017.9 is the last release of LAVA which will support running V1 test jobs.
- 2017.10 will not support running V1 test jobs, but will include support for providing a read-only archive of V1 test data.
- 2017.11 will be the first release of LAVA which is V2 only. It will contain no support for accessing V1 data and this V1 documentation will be removed.
- 2017.12 will permanently delete all V1 test data from the database upon installation.
See also
- Logging In
- Authentication Tokens
- lava-tool overview
- Bundle Stream Overview
- Submitting your first job
- Glossary of terms
- Getting support
- LAVA Installation
- Writing a LAVA test definition
- Writing commands to run on the device
- Best practices for writing a LAVA job
- Writing MultiNode tests
- Features specific to LAVA V1
- Submitting a JSON job
- Writing a LAVA test using JSON
- Best practices for writing a LAVA JSON job
- Writing MultiNode JSON tests
- JSON Hacking Sessions
- JSON Multinode
- External measurements
- Actions to be run for a LAVA test
- Actions to be run to simply deploy without tests
- Examples
- Distributed deployment
- Migrating LAVA instances from deployment_tool
- Test definitions in version control
- Filters
- Image Reports
- Image Reports 2.0
- Writing Health Checks for device types
- MultiNode Use Cases
- Virtual Machine Groups
- Development process
- What do you want from LAVA - FAQs
LAVA Test Developer Guide¶
- Introduction to the LAVA Test Developer Guide
- List of available JSON dispatcher actions
- LAVA Test Shell
- LAVA Hacking Sessions (JSON)
- Multi-Node LAVA (JSON)
- Virtual Machine Groups
- Boot Management
- Building and manipulating images
- Deploying a Bootloader Device
- Hooks, Signals and External Measurement
- Exporting data out of LAVA
- LAVA-LMP Test Guide
LAVA Administrator Guide¶
- Configuration files for lava-dispatcher
- Running LAVA Scheduler
- Identifying device types
- Hidden device type
- Cache Proxy Setting Up
- 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
- PDU Daemon
- Deploying a KVM (x86_64) Device
- Adding a KVM device to LAVA
- Submitting a KVM Job
- Deploying an ipmi/pxe-boot Device
- Deploying dummy devices
- Deploying an iPXE (x86) device
- Switch / Hijack User
Other Topics¶
- 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