action #90362

coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

coordination #90359: [epic] Customizable worker engine

Allow to customize worker engine by configuration

Added by okurz 7 months ago. Updated 6 months ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:



Working on os-autoinst/os-autoinst#1558 this
idea came back to mind. I had already thought about doing something
similar couple of times, also based on requests by other users to be
able to test os-autoinst changes more easily. With this change it
should be possible to execute an arbitrary command within the worker
based on a job setting. For example the use case I envision is to
build a container image from a still open pull request of os-autoinst
and execute tests on a production instance without harmful impact of
the general environment, e.g.
podman run --rm -it

This could also be helpful for customized backend environments needed
to access other, more exotic hardware and such.

Acceptance criteria

  • AC1: "isotovideo" is not hardcoded as only choice within the openQA worker engine


#1 Updated by okurz 7 months ago

  • Description updated (diff)
  • Status changed from New to In Progress

#2 Updated by openqa_review 7 months ago

  • Due date set to 2021-04-03

Setting due date based on mean cycle time of SUSE QE Tools

#3 Updated by okurz 7 months ago

  • Status changed from In Progress to Resolved is merged, deployed and effective in a way that given right permissions it works as designed. During the work on I tried it out on openqaworker7 and have adjusted apparmor a bit locally. However likely we need to tweak further so that the user _openqa-worker can do more as well, e.g. execute podman. I will leave this for the parent epic though.

#4 Updated by cdywan 6 months ago

  • Due date deleted (2021-04-03)

Resetting the due date in an attempt to remove it from the parent ticket

Also available in: Atom PDF