This is the last call for comments for the review of debconf templates for lava-server. The reviewed templates will be sent on Friday, July 25, 2014 to this bug report and a mail will be sent to this list with "[BTS]" as a subject tag. --
Template: lava-server/master Type: boolean Default: true _Description: Is this a standalone master instance of LAVA? LAVA can be set up in either of two ways: as a single standalone master instance with attached devices, or in a distributed configuration with a central master instance and remote dispatchers providing (more) devices. . Configuration of remote dispatchers is currently experimental, so the standalone configuration is recommended. Template: lava-server/db-port Type: string Default: 5432 _Description: Port number of the PostgreSQL database: Please enter the port number for the PostgreSQL database. Template: lava-server/worker-note Type: note _Description: This install looks like a remote worker You asked for this system to be set up as master instance for a distributed configuration, but this system looks like a remote worker. You can either go back and change your answer or proceed with reconfiguring this system as specified. . Note that you will have to ensure that the lava-coordinator configuration is correct. Template: lava-server/master-note Type: note _Description: This install looks like a master instance You asked for this system to be set up as a remote worker for a distributed configuration, but this system looks like a master instance. You can either go back and change your answer or proceed with reconfiguring this system as specified. . Note that you will have to ensure that the lava-coordinator configuration is changed to point to the master instance for this remote worker. You can then remove the lava-coordinator package from the remote worker. Template: lava-server/instance-name Type: string Default: default _Description: Name for this LAVA instance: LAVA servers need to have an instance name. If this is a new instance, you can safely use the default name. If this is an upgrade of a previous LAVA instance, specify the instance name here to upgrade the database or use a different name to start fresh with a new database. Template: lava-server/missingname Type: error _Description: Missing LAVA instance name An instance name must be specified for LAVA-server. Using the instance name "default". Template: lava-worker/master-instance-name Type: string Default: default _Description: Name for the master instance for this worker: LAVA servers need to have an instance name. Each remote worker must be given the instance name of the master LAVA server which it will poll for new jobs to run on the devices attached to the worker. Template: lava-worker/db-server Type: string _Description: Master scheduler for this worker: Each remote worker needs to connect to a master scheduler running lava-server. This hostname or IP address will be used to connect to the master database. . To work with remote nodes, the master needs to be configured to allow the database to listen to the workers. An SSH key also needs to be generated on the worker and added to the master list of authorized_keys. Ensure that the master allows remote access from workers before submitting jobs or health checks. . You can continue setting up the worker, as long as remote database access is enabled before jobs are submitted. Template: lava-worker/db-name Type: string _Description: Name of the database on the master: Please enter the name of the database on the master scheduler running lava-server. The worker will use this name to contact the database. Template: lava-worker/db-user Type: string _Description: Username for the database on the master: Please enter the username for the database on the master scheduler running lava-server. The worker will use this username to contact the database. Template: lava-worker/db-port Type: string Default: 5432 _Description: Port number of the database on the master: Please enter the database port number for the database on the master scheduler running lava-server. The worker will use this port to contact the database. Template: lava-worker/db-pass Type: string _Description: Password for the database on the master: Please enter the password for the database on the master scheduler running lava-server. The worker will use this username to contact the database. Template: lava-server/missingip Type: error _Description: Missing server IP address The host name or IP address of the master scheduler must be specified.
Source: lava-server
Section: net
Priority: optional
Maintainer: Debian LAVA team <pkg-linaro-lava-devel@lists.alioth.debian.org>
Uploaders: Antonio Terceiro <terceiro@debian.org>,
Neil Williams <codehelp@debian.org>,
Fathi Boudra <fabo@debian.org>, Jordi Mallach <jordi@debian.org>
Build-Depends: debhelper (>= 8.0.0),
python | python-all | python-dev | python-all-dev,
python-sphinx (>= 1.0.7+dfsg) | python3-sphinx, po-debconf,
python-mocker, python-setuptools (>= 3)
X-Python-Version: 2.7
XS-Testsuite: autopkgtest
Standards-Version: 3.9.5
Homepage: http://www.linaro.org/projects/test-validation/
Vcs-Git: https://github.com/Linaro/pkg-lava-server.git
Vcs-Browser: https://github.com/Linaro/pkg-lava-server
Package: lava-server
Architecture: all
Provides: lava-scheduler, lava-dashboard, linaro-django-xmlrpc
Conflicts: lava-scheduler, lava-dashboard, linaro-django-xmlrpc
Replaces: lava-scheduler, lava-dashboard, linaro-django-xmlrpc
Depends: apache2, adduser, diffstat, fuse, iproute2,
libapache2-mod-uwsgi, libapache2-mod-wsgi, lshw,
python-daemon, python-dateutil, python-django-auth-openid (>= 0.5-2),
python-setuptools,
libjs-jquery-cookie, libjs-jquery-flot (>= 0.8.2), openssh-client,
postgresql, postgresql-client, postgresql-common,
${python:Depends}, ${misc:Depends}
Recommends: ntp, lava-coordinator, lava-server-doc
Description: Linaro Automated Validation Architecture - server
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
Tests can be simple boot testing, bootloader testing, and system
level testing, although extra hardware may be required for some
system tests. Results are tracked over time and data can be
exported for further analysis.
.
This package provides the Apache and WSGI configuration and LAVA
support files to run the validation server on the local Apache
instance as a lava-server virtual host as well as running the
scheduler and dispatcher.
.
This package can be configured as the master scheduler or as a
remote worker, although design limitations mean that it always
installs a database (unused on a remote worker).
Package: lava
Architecture: all
Section: metapackages
Depends: lava-server, lava-server-doc, lava-dispatcher, lava-coordinator,
lava-dev, lava-tool, lavapdu-client, linaro-image-tools, ntp | ntpdate,
tftpd-hpa, vmdebootstrap, ${misc:Depends}
Recommends: lavapdu-daemon
Description: Linaro Automated Validation Architecture - metapackage
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
Tests can be simple boot testing, bootloader testing, and system
level testing, although extra hardware may be required for some
system tests. Results are tracked over time and data can be
exported for further analysis.
.
This metapackage brings in all LAVA components on a single
machine. Some dependencies require the Linaro Tools PPA.
Package: lava-dev
Architecture: all
Section: devel
Depends: ca-certificates, devscripts, dpkg-dev, debhelper (>= 8.0.0),
fakeroot, git, libdistro-info-perl, django-testscenarios,
python | python-all | python-dev | python-all-dev,
python-sphinx (>= 1.0.7+dfsg) | python3-sphinx, po-debconf,
python-mocker, python-setuptools, python-versiontools,
${misc:Depends}
Recommends: sbuild
Description: Linaro Automated Validation Architecture - developer support
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
.
This package provides a helper script to build LAVA packages
from local Git working copies, and support for running the
LAVA unit tests locally.
Package: lava-server-doc
Architecture: all
Section: doc
Depends: ${sphinxdoc:Depends}, ${misc:Depends}
Conflicts: linaro-dashboard-bundle-doc
Provides: linaro-dashboard-bundle-doc
Replaces: linaro-dashboard-bundle-doc
Description: Linaro Automated Validation Architecture - server documentation
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
Tests can be simple boot testing, bootloader testing, and system
level testing, although extra hardware may be required for some
system tests. Results are tracked over time and data can be
exported for further analysis.
.
This package contains an offline copy of the LAVA
Manual available on each instance running LAVA server:
.
* an overview of LAVA;
* help on installing and configuring LAVA;
* test developer guide to writing LAVA tests;
* use cases and examples;
* administrator guide for managing a LAVA lab;
* developer guide.
Attachment:
signature.asc
Description: Digital signature