Packaging lava-server for distributions

Packaging lava-server for distributions


This chapter discusses a model of deployment which is being superceded by the pipeline model.

Apache distribution support


Aimed at apache2.4 with comments for apache2.2 usage. Edit where necessary and then enable and restart apache to use.

Instance name

  1. Only one instance can be running at any one time.
  2. Instance templates share a common folder: /usr/share/lava-server/templates

LAVA Components

lava meta-package for single instance setup
lava-server apache and WSGI settings and HTML content
lava-dispatcher dispatches jobs to devices

Daemon renaming

The main scheduler daemon is now explicitly named and only restarts the scheduler daemon:

$ sudo service lava-server restart

The web application itself is handled within apache, so to refresh the code running behind the front end, use:

$ sudo apache2ctl restart

The LAVA_SYS_USER has also been renamed from an instance-specific name to lavaserver. lava-server manage can also be run as a normal user or by root. The system user is used just for the filesystem permissions.

WSGI debugging help

If you get a 502 bad gateway, the uwsgi is probably not setup.