that you have to set your own HOST in workers.ini is very unintuitive. Especially if we have more workers, we need the scheduler to tell the workers the hostname for openQA without additional requirements.
#1 Updated by oholecek almost 7 years ago
I don't get this. How ie. remote worker will get openQA hostname? Do you mean some kind of zeroconf support (which, assuming avahi, AFAIK works as far as multicast is routed, so even there some backup should be supported)?
But I must admit that one thing I really loved on maintenance's mtui tool is that it works right after the installation. Install, run, done - that level of functionality would be super cool for spreading the message of openQA :)
#2 Updated by coolo almost 7 years ago
Well, once you have the file system mounted on the remote worker, there shouldn't be any more setup necessary. All the necessary information should be gatherable for the worker from the scheduler.
Right now you need to provide the worker with the file system (so far easy as only local workers supported) and provide a workers.ini on every node giving the resolvable name of the UI.
#3 Updated by coolo almost 7 years ago
with https://github.com/os-autoinst/os-autoinst/pull/123 it's no longer necessary to configure it
#4 Updated by coolo almost 7 years ago
I wish that was true.
To setup a remote worker, you need to:
- install the packages
- setup the NFS mount
- configure the host you just mounted from /etc/openqa/workers.ini
- copy the API keys into /etc/openqa/client.conf
IMO the secrets should be read from the NFS share and skip step 3 and 4.