action #4654

deprecate workers.ini

Added by coolo over 5 years ago. Updated 6 months ago.

Status:ResolvedStart date:12/11/2014
Priority:NormalDue date:
Assignee:-% Done:


Category:Feature requests
Target version:QA - future


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.

Related issues

Related to openQA Project - action #6602: move worker credentials to workers.ini Rejected 10/03/2015


#1 Updated by oholecek over 5 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 over 5 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 about 5 years ago

with it's no longer necessary to configure it

#4 Updated by coolo about 5 years ago

I wish that was true.

To setup a remote worker, you need to:

  1. install the packages
  2. setup the NFS mount
  3. configure the host you just mounted from /etc/openqa/workers.ini
  4. 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.

#5 Updated by okurz over 3 years ago

  • Related to action #6602: move worker credentials to workers.ini added

#6 Updated by okurz about 3 years ago

  • Target version set to future

#7 Updated by okurz over 1 year ago

  • Target version changed from future to future

#8 Updated by okurz 6 months ago

  • Status changed from New to Resolved

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?

#9 Updated by coolo 6 months ago

not really no. But then I again, I don't care so much about the future atm

Also available in: Atom PDF