diff options
| author |   Corentin LABBE <clabbe@baylibre.com> | 2018-07-04 14:45:58 +0200 |
|---|---|---|
| committer | Corentin LABBE <clabbe@baylibre.com> | 2018-07-23 16:20:48 +0200 |
| commit | d42030d39800b930634dba1efafcf43959c40205 (patch) | |
| tree | dd9bc68db2a8e763fc1032503a85ec9342568185 /README.md | |
| parent | 0f09e5c9b89cee21a6ee39db9daf8e17525dd493 (diff) | |
Handle ZMQ auth
This patch add support for using ZMQ auth.
Basicly adding "zmq_auth: True" to a master is sufficient to enable it.
Since "ZMQ certificates" are using a custom format (vs X509 classic), we need to use the custom generator.
For helping with that a temporary docker is generated which handle generating thoses files.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -215,6 +215,9 @@ masters: - name: lava-master name of the master host: name name of the host running lava-master (default to "local") webadmin_https: Does the LAVA webadmin is accessed via https + zmq_auth: True/False Does the master requires ZMQ authentication. + zmq_auth_key: optional path to a public ZMQ key + zmq_auth_key_secret: optional path to a private ZMQ key persistent_db: True/False (default False) Is the postgres DB is persistent over reboot users: - name: LAVA username @@ -229,6 +232,8 @@ masters: slaves: - name: lab-slave-XX The name of the slave (where XX is a number) host: name name of the host running lava-slave-XX (default to "local") + zmq_auth_key: optional path to a public ZMQ key + zmq_auth_key_secret: optional path to a private ZMQ key dispatcher_ip: the IP where the slave could be contacted. In lava-docker it is the host IP since docker proxify TFTP from host to the slave. remote_master: the name of the master to connect to remote_address: the FQDN or IP address of the master (if different from remote_master) |