diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 34 |
1 files changed, 33 insertions, 1 deletions
@@ -219,8 +219,12 @@ 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 + - "fqdn1" + - "fqdn2" loglevel: lava-logs: DEBUG/INFO/WARN/ERROR (optional) select the loglevel of lava-logs (default to DEBUG) lava-slave: DEBUG/INFO/WARN/ERROR (optional) select the loglevel of lava-slave (default to DEBUG) @@ -262,6 +266,10 @@ slaves: remote_proto: http(default) or https default_slave: Does this slave is the default slave where to add boards (default: lab-slave-0) 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 + use_tap: Does TAP netdevices could be used + 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 @@ -270,13 +278,18 @@ slaves: env: - line1 A list of line to set as environment (See /etc/lava-server/env.yaml for examples) - line2 + devices: A list of devices which need UDEV rules + - name: The name of the device + vendorid: The VID of the UART (Formated as 0xXXXX) + productid: the PID of the UART (Formated as 0xXXXX) + serial: The serial number of the device if the device got one + devpath: The UDEV devpath to this device if more than one is present boards: - name: devicename Each board must be named by their device-type as "device-type-XX" (where XX is a number) type: the LAVA device-type of this device slave: (optional) Name of the slave managing this device. Default to first slave found or default_slave if set. kvm: (For qemu only) Does the qemu could use KVM (default: no) - tap: (For qemu only) Does the qemu could use TAP devices (default: no) uboot_ipaddr: (optional) a static IP to set in uboot uboot_macaddr: (Optional) the MAC address to set in uboot custom_option: (optional) All following strings will be directly append to devicefile @@ -402,6 +415,12 @@ For building an arm64 lava-docker, some little trick are necesssary: For building lava-xxx-base images - replace "bitnami/minideb" by "arm64v8/debian" on lava-master-base/lava-slave-base dockerfiles. +# How to ran NFS jobs +You need to se use_nfs: True on slave that will ran NFS jobs. +A working NFS server must be working on the host. +Furthermore, you must create a /var/lib/lava/dispatcher/tmp directory on the host and export it like: +/var/lib/lava/dispatcher/tmp 192.168.66.0/24(no_root_squash,rw,no_subtree_check) + ## How to add custom LAVA patchs You can add custom or backported LAVA patchs in lava-master/lava-patch Doing the same for lava-slave will be done later. @@ -419,6 +438,19 @@ slave: env: - "http_proxy: http://dns:port" +## How to use a board which uses PXE ? +All boards which uses PXE, could be used with LAVA via grub. +But you need to add a configuration in your DHCP server for that board. +This configuration need tell to the PXE to get GRUB for the dispatcher TFTP. +EXample for an upsquare and a dispatcher availlable at 192.168.66.1: +``` + host upsquare { + hardware ethernet 00:07:32:54:41:bb; + filename "/boot/grub/x86_64-efi/core.efi"; + next-server 192.168.66.1; + } +``` + ## Bugs, Contact The prefered way to submit bugs are via the github issue tracker You can also contact us on #lava-docker on the freenode IRC network |