The pipeline design designates the machine running Django and PostgreSQL as the lava-master and all other machines connected to that master which will actually be running the jobs are termed lava-slave machines.
If this slave has no devices which will be used by the current dispatcher, only by the pipeline, just install lava-dispatcher:
$ sudo apt install lava-dispatcher
Change the init script for lava-slave (/etc/init.d/lava-slave) to point at the relevant lava-master.
Change the port numbers, if required, to match those in use on the lava-master.
Restart lava-slave once the changes are complete:
$ sudo service lava-slave restart
The administrator of the master will then be able to allocate pipeline devices to this slave.
Note
For security reasons, the slave does not declare the devices connected to it to the master. The slave actually needs no knowledge of what is connected or where. All this information is stored solely in the database of the master. Once this data is entered by the admin of the master, the slave then needs to connect and the admin can then select that slave for the relevant devices. Once selected, the slave can immediately start running pipeline jobs on those devices.
The administrator of the master will require the following information about the devices attached to each slave:
This information contains specific information about the local network setup of the slave and will be transmitted between the master and the slave in clear text over ZMQ. Any encryption would need to be arranged separately between the slave and the master. Information typically involves the hostname of the PDU, the port number of the device on that PDU and the port number of the serial connection for that device. The slave is responsible for ensuring that these ports are only visible to that slave. There is no need for any connections to be visible to the master.
On an existing remote worker, a lava-master daemon will already be running on localhost (doing nothing). Once the migration to the pipeline is complete, the lava-server package can be removed from all workers, so the above information relates to this endpoint. In the meantime, remote workers should have lava-master disabled on localhost once the slave has been directed at the real master as above.
Warning
Only do this on the remote worker but make sure it is done on all remote workers before submitting pipeline jobs which would need the devices on those workers.
If a new worker does not need to run jobs using the current dispatcher, i.e. if all devices on this worker are exclusive, then lava-server does not need to be installed and there is no lava-master daemon to disable.
For existing workers, pipeline jobs will be likely be mixed with JSON jobs. This leads to lava-server being installed on the workers (solely to manage the JSON jobs). On such workers, lava-master should be disabled once lava-slave has been reconfigured:
$ sudo invoke-rc.d lava-master stop
$ sudo update-rc.d lava-master remove
$ sudo chmod a -x /etc/init.d/lava-master
$ sudo service lava-master status
lava-master: unrecognized service
Removing the executable bits stops the lava-master being re-enabled when the packages are updated.