DOKK / manpages / debian 10 / lava-server / lava-server.1.en
LAVA-SERVER(1) General Commands Manual LAVA-SERVER(1)
" "LAVA"

lava-server - lava-server command line support

lava-server is a command-line management interface to a LAVA instance, and the Django database management tools for that instance.

lava-server manage subcommand [options] [args]

Most of these options are imported from django and more information can be found in the django documentation.

These options are supported for all subcommands.

Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output
The Python path to a settings module, e.g. "myproject.settings.main". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used.
A directory to add to the Python path, e.g. "/home/djangoprojects/myproject".
Print traceback on exception
show program's version number and exit
show this help message and exit



Type lava-server manage help <subcommand> for help on a specific subcommand.

Type lava-server manage <subcommand> -h for help on an option available to a specific subcommand.

Change a user's password for django.contrib.auth.
lava-server manage changepassword [options]
Specifies the database to use. Default is "default".


Used to create a superuser.
lava-server manage createsuperuser [options]
Specifies the username for the superuser.
Specifies the email address for the superuser.
Tells Django to NOT prompt the user for input of any kind. You must use --username and --email with --noinput and superusers created with --noinput will not be able to log in until they are given a valid password.
Specifies the database to use. Default is default.




django

django functions change with releases of the django package. See the documentation for python-django.


lava_scheduler_app

Manage devices
{add, details, list, set}
add Add a device
hostname Hostname of the device
show this help message and exit
Device type
Device description
Device dictionary
Create a v1 device (v2 by default)
Create the device offline (online by default)
Make the device private (public by default)
The name of the worker

--tags TAG1 TAG2 List of tags for the device




copy Copy an existing device as a new device

optional arguments:
show this help message and exit
Hostname of the existing device
Hostname of the device to create
Create the device offline (online by default)
Make the device private (public by default)
The name of the worker
Set all the tags of the original device on the target device





details Details about a device

positional arguments:
hostname Hostname of the device




list List the installed devices

Show all devices, including retired ones
{OFFLINE, IDLE, RUNNING, OFFLINING, RETIRED, RESERVED} Show only devices with this status
Print as csv




hostname Hostname of the device
show this help message and exit
Set the description
Device dictionary
make the device public
Make the device private
{OFFLINE, IDLE, RUNNING, OFFLINING, RETIRED, RESERVED} Set the device status
{UNKNOWN, PASS, FAIL, LOOPING} Set the device health status
Set the worker




Manage device types according to which templates are available and which device-types are defined in the database. When counting the number of devices, Retired devices are included.
{add, list} Sub commands
add Add V2 device type(s) to the database.

show this help message and exit

health check:
Only supported when creating a single device-type
--health-check HEALTH_CHECK
The health check (filename) for the given device type.

--health - frequency HEALTH_FREQUENCY
How often to run health checks.

--health-denominator
{hours, jobs} Initiate health checks by hours or by jobs.




show this help message and exit
Show all device types in the database, including types not currently installed.
Print as csv







Export device state transitions in either yaml or csv format. Output can be filtered by old_state and new_state field values.
positional arguments:
{export} Sub commands
Fields exported: created_on, created_by, device, job, old_state, new_state, message Available states are: RETIRED, IDLE, RUNNING, OFFLINING, RESERVED, OFFLINE Not all combinations of states will exist. Not all fields are populated for all transitions. Example: To see transitions where an admin put the device back online, use: lava-server manage device-transition export --old-state OFFLINE --new-state IDLE Note: exporting all transitions will produce a lot of output, it is recommended to always specify --old-state and --new-state.


optional arguments:

show this help message and exit

— csv Print as csv --old-state Filter output by old device status --new-state Filter output by new device status










pipeline-worker

Hostname of the new worker
optional description of the new worker
prevent pipeline jobs running on this worker.


Runs the test suite for the specified applications, or the entire site if no apps are specified.
lava-server manage test [options] [appname ...]
Tells Django to NOT prompt the user for input of any kind.
Tells Django to stop running the test suite after first failed test.
Tells Django to use specified test runner class instead of the one specified by the TEST_RUNNER setting.
Overrides the default address where the live server (used with LiveServerTestCase) is expected to run from. The default value is localhost:8081.





If your bug relates to a specific type of device, please include all configuration details for that device type as well as the job submission JSON and as much of the LAVA test job log file as you can (e.g. as a compressed file attached to the bug report).

If your device type is not one found on existing LAVA instances, please supply as much information as you can on the board itself.

If you, or anyone on your team, would like to register with Linaro directly, this will allow you to file an upstream bug, submit code for review by the LAVA team, etc. Register at the following url:

https://register.linaro.org/

If you are considering large changes, it is best to register and also to subscribe to the Linaro Validation mailing list at:

http://lists.linaro.org/mailman/listinfo/linaro-validation

Also talk to us on IRC:

irc.freenode.net
#linaro-lava


Linaro Validation Team

2010-2019, Linaro Limited

March 31, 2019 2019.01