Added by coolo over 9 years ago. Updated over 4 years ago.
0%
Description
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.
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)?
Offtopic:
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 :)
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.
with https://github.com/os-autoinst/os-autoinst/pull/123 it's no longer necessary to configure it
I wish that was true.
To setup a remote worker, you need to:
IMO the secrets should be read from the NFS share and skip step 3 and 4.
well, we did not deprecate workers.ini but I guess the mentioned problems are mostly solved so I guess we can call the ticket "Resolved", right?
not really no. But then I again, I don't care so much about the future atm