On Mon, 18 Jan 2016 19:13:09 +0100 Alexander Couzens lynxis@fe80.eu wrote:
Hi,
I'm trying to setup a pipeline lava instances and the documentation is a bit unclear to me.
You're a bit ahead of the docs at this point. ;-)
But what does it exactly means with "Pipeline devices need the worker hostname to be set manually in the database". ???
Either an existing worker (registered over XMLRPC using the existing scheduler daemon and distributed deployment setup) OR a worker created using the django administration interface - well, once I've tweaked the admin page to do that or created a helper. The issue is that manually entered workers are unlikely to work with the old scheduler, so there needs to be a warning about that. i.e. Devices assigned to this worker need to be "exclusive" to the pipeline.
https://validation.linaro.org/static/docs/glossary.html?highlight=exclusive#...
In the database I can only see a worker_id. Or does it just means, I have to set the worker within django?
Pipeline-only workers would need to be added on the command line currently:
$ sudo lava-server manage shell
from lava_scheduler_app.models import Worker new_worker = Worker.objects.create(hostname='host.domain') new_worker.save()
Rather than changing the admin page, it might be better to provide a command line helper to do this - and the device assignment for that worker.
note: if this worker is already running lava-slave, the worker will be able to start jobs immediately that any devices are assigned to this worker.
To assign devices, use the administration interface and set the worker host for the specified device.
My goal is to setup a lava master and a slave using the new pipeline framework. The master is setted up on a debian jessie 8.2 using lava production repository as well as backports.
I connected the slave to the master using the .service file. tcpdump shows some 'PING' and 'PONG' traffic between the two hosts. Should I see the slave somewhere in django application? On the Admin/worker view I only see the master.
master: lava-server 2015.12-3~bpo8+1 slave: lava-dispatcher@c391b53231fba978532327d2bdff5173fcb55db4
Check the /var/log/lava-scheduler/lava-master.log and /var/log/lava-dispatcher/lava-slave.log on the master and slave respectively.
... and let us know if there are problems.