diff options
author | Corentin LABBE <clabbe@baylibre.com> | 2019-05-10 11:32:15 +0200 |
---|---|---|
committer | Corentin LABBE <clabbe@baylibre.com> | 2019-05-13 11:10:12 +0200 |
commit | 4ae24270f6e8e853ca97cdd1f926da486a39a387 (patch) | |
tree | 8221dc796dac83375fc93c9bbaa5cefe061a0879 /README.md | |
parent | d6ac516eed6fcf2caab00ecf03b12fa4482e278d (diff) |
lava-slave: support lava-coordinator
This patchs adds a new flag "lava-coordinator" for slave which enables
the generation of a lava-coordinator.conf file.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -219,6 +219,7 @@ masters: zmq_auth_key: optional path to a public ZMQ key zmq_auth_key_secret: optional path to a private ZMQ key slave_keys: optional path to a directory with slaves public key. Usefull when you want to create a master without slaves nodes in boards.yaml. + lava-coordinator: Does the master should ran a lava-coordinator and export its port persistent_db: True/False (default False) Is the postgres DB is persistent over reboot http_fqdn: The FQDN used to access the LAVA web interface. This is necessary if you use https otherwise you will issue CSRF errors. allowed_hosts: A list of FQDN used to access the LAVA master @@ -267,6 +268,7 @@ slaves: bind_dev: Bind /dev from host to slave. This is needed when using some HID PDU use_nfs: Does the LAVA dispatcher will run NFS jobs arch: The arch of the worker (if not x86_64), only accept arm64 + lava-coordinator: Does the slave should ran a lava-coordinator expose_ser2net: Do ser2net ports need to be available on host expose_ports: Expose port p1 on the host to p2 on the worker slave. - p1:p2 |