QA » openQA Project

In principle I see this already fulfilled by https://github.com/os-autoinst/openQA/blob/master/docker/worker/Dockerfile but I want to clarify that your request is completely covered.

• I assume when you say "SUSE repositories" that "openSUSE" is ok?
• Can you clarify on "AC3: An automated way is provided to fill the database with necessary tables and schemas, and a predefined set of test data": What do you want to achieve with that and what do you mean with "predefined set of test data" in particular?
• Can you clarify on "AC4: Non-static data is stored on container volumes, if possible": Do you mean something like an external temporary directory passed into the container as the worker's cache and/or pool directory?

@plorinc can you please look into the questions from #73450#note-1

plorinc wrote:

okurz wrote:

In principle I see this already fulfilled by https://github.com/os-autoinst/openQA/blob/master/docker/worker/Dockerfile but I want to clarify that your request is completely covered.

The Dockerfile looks good. Do you have any guide on how to start a container from the image?

Yes, see https://github.com/os-autoinst/openQA/blob/master/docs/Installing.asciidoc#container-based-setup or simply:

podman run --rm -it registry.opensuse.org/devel/openqa/containers15.2/openqa_worker:latest

• Can you clarify on "AC3: An automated way is provided to fill the database with necessary tables and schemas, and a predefined set of test data": What do you want to achieve with that and what do you mean with "predefined set of test data" in particular?

The image will also be used in test/training scenarios completely isolated from the production system.
In these use cases we needed to put the system into a predefined state, for example by filling the database with a snapshot or a prepared dataset.

I have commented to a similar question regarding the webUI in #73447. The worker only needs simple command line parameters or configuration files which can be linked into the container.

• Can you clarify on "AC4: Non-static data is stored on container volumes, if possible": Do you mean something like an external temporary directory passed into the container as the worker's cache and/or pool directory?

Persistent data should be stored on mounted docker volumes so if the container gets restarted (e.g. because of redeployment or software upgrade) the data won't lost.
Basically: configuration is stored inside the container, state is stored outside.

The worker forwards all relevant output data to the web UI. The only relevant data for the worker is the configuration mentioned above. So I don't see this as problem.

Let's see if we can cover the ACs:

• AC1: Container started based on this image is able to run on the Docker engine

DONE: We tested with both "docker" and "podman". https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3Ddevel%3AopenQA lists the containers along with example commands based on podman as well as docker.

• AC2: Full Green Stack: All software components are available in the (open)SUSE repositories

DONE: Available in openSUSE Tumbleweed as well as build.opensuse.org/project/show/devel:openQA

• AC3: An automated way is provided to fill the database with necessary tables and schemas, and a predefined set of test data

DONE: N/A for the openQA worker

• AC4: Non-static data is stored on container volumes, if possible

DONE: N/A for the openQA worker

• AC5: Deliverable is an image stored in a registry, a Dockerfile (with instructions on how to create a container from the image) or a Compose file

DONE: All of that with https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3Ddevel%3AopenQA and https://github.com/os-autoinst/openQA/tree/master/docker

Same as in #73447 setting @ilausuch as he was the main driver in the latest work, I am just collecting facts as result :)