Project

General

Profile

Actions
Copy link

action #90362

closed

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 over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
Ready
Start date:
2021-03-19
Due date:
% Done:

0%

Estimated time:

Description

Motivation

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 registry.opensuse.org/devel/openqa/....

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

Related issues 1 (0 open — 1 closed)

Related to openQA Project - action #106999: os-autoinst: Document the use of custom openQA backend commands to test os-autoinst changes on production workers size:MResolvedokurz2022-02-14

Actions
Actions
Copy link
 #1

Updated by okurz over 3 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by openqa_review over 3 years ago

  • Due date set to 2021-04-03

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

Actions
Copy link
 #3

Updated by okurz over 3 years ago

  • Status changed from In Progress to Resolved

https://github.com/os-autoinst/openQA/pull/3804 is merged, deployed and effective in a way that given right permissions it works as designed. During the work on https://hackweek.suse.com/20/projects/automated-test-for-game-plus-only-web-based-dev-plus-python-openqa 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.

Actions
Copy link
 #4

Updated by livdywan over 3 years ago

  • Due date deleted (2021-04-03)

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

Actions
Copy link
 #5

Updated by okurz over 2 years ago

  • Related to action #106999: os-autoinst: Document the use of custom openQA backend commands to test os-autoinst changes on production workers size:M added
Actions
Copy link

Also available in: Atom PDF