action #43718
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #43706: [epic] Generate "download&use" docker image of openQA for SUSE QA
Docker image for webui and workers are versioned and uploaded to obs registry
Description
Motivation¶
To avoid QA employee getting blocked by a malfunctioning new openQA version, we should have container images available, ideally versioned so people can always use a known to be working openQA version.
Acceptance criteria¶
- AC1: (DONE) An x86-64 container image for the webui is available on OBS.
- AC2: (DONE) An x86-64 container image for the worker is available on OBS.
- AC3: (IMPLICIT IN OBS) Container images are versioned.
Suggestions¶
- Look into CI images https://build.opensuse.org/package/show/devel:openQA/openqa_dev
- Mention the available containers as part of documentation
Updated by szarate almost 6 years ago
- Subject changed from [functional[u] Docker image for webui and workers are versioned and uploaded to docker hub to [functional][u] Docker image for webui and workers are versioned and uploaded to docker hub / obs registry
- Description updated (diff)
I'd like to set this to a later milestone, there are upcomming changes to openQA that would help a lot with the containerization process, but with the openqa bootstrap scripts provided by poo#45365 there's already a start
Updated by szarate almost 6 years ago
- Related to action #43715: Update upstream dockerfiles to provide an easy to use docker image of workers added
Updated by szarate almost 6 years ago
- Related to deleted (action #43715: Update upstream dockerfiles to provide an easy to use docker image of workers)
Updated by okurz almost 6 years ago
good idea, can we relate these tickets then?
Updated by okurz almost 6 years ago
- Subject changed from [functional][u] Docker image for webui and workers are versioned and uploaded to docker hub / obs registry to Docker image for webui and workers are versioned and uploaded to docker hub / obs registry
- Category set to Feature requests
- Target version deleted (
Milestone 23)
As per #43718#note-5 , no response on the relations. I think it's a nice idea but currently out of scope for QSF-u.
Updated by okurz over 4 years ago
- Priority changed from Normal to Low
- Target version set to future
Updated by okurz over 4 years ago
- Related to action #43619: Improve workflow for dealing with openQA's dependencies added
Updated by livdywan about 4 years ago
- Description updated (diff)
- Assignee set to ilausuch
Updated by livdywan about 4 years ago
I created the devel:openQA:container packageproject, so we have a place to publish images there. And once that works we'll do the same for the web UI.
Updated by okurz about 4 years ago
please do not work on this ticket, it's not on our backlog. And I would really appreciate if we can resolve the other tickets first. Of course it's ok if you already have some intermediate steps. You can just keep them.
Updated by ilausuch about 4 years ago
Now https://build.opensuse.org/project/show/devel:openQA:container is configured properly and I created two packages
https://build.opensuse.org/package/show/devel:openQA:container/openQA_container_webUI
https://build.opensuse.org/package/show/devel:openQA:container/openQA_container_worker
For now, I didn't created the Load Balancer package, but I guess we'll need this in the future.
Both build the images.
obs://build.opensuse.org/devel:openQA:container/containers15.2/6912e7418a7fee7d67a96990f0970e63-openQA_container_webUI
obs://build.opensuse.org/devel:openQA:container/containers15.2/feae4bf90cfbc2366f76f357f21f7f60-openQA_container_worker
Now I am trying to adjust the configuration to publish the images in the public registry
Updated by ilausuch about 4 years ago
The container images are already in the registry
podman pull registry.opensuse.org/devel/openqa/container/containers15.2/openqa_webui:latest
podman pull registry.opensuse.org/devel/openqa/container/containers15.2/openqa_worker:latest
Updated by okurz about 4 years ago
good. I have not updated #43718 as it is not on our backlog but my suggestion (elsewhere) was to not have packages within the subproject ":container" to prevent the repeated word "container" in the URL. Can you please move the packages to devel:openQA directly?
EDIT: After that I suggest to remove the project again.
Updated by ilausuch about 4 years ago
The packages are moved to the https://build.opensuse.org/project/show/devel:openQA project
https://build.opensuse.org/package/show/devel:openQA/openQA_container_webUI
https://build.opensuse.org/package/show/devel:openQA/openQA_container_worker
And the devel:openQA:container project is deleted
Updated by okurz about 4 years ago
looks good. I can find the images on https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3Ddevel%3AopenQA
But when I try to run the worker image I get:
podman run --rm -it registry.opensuse.org/devel/openqa/containers15.2/openqa_worker
Trying to pull registry.opensuse.org/devel/openqa/containers15.2/openqa_worker...
Getting image source signatures
Copying blob 03155e773b90 done
Copying blob 9ae21f77663e done
Copying config 6083cf2534 done
Writing manifest to image destination
Storing signatures
Error: container_linux.go:349: starting container process caused "exec: \"/run_openqa_worker.sh\": permission denied": OCI runtime permission denied error
I assume the problem is that https://github.com/os-autoinst/openQA/pull/3547 works when building images locally but when we download a simple file within OBS then permissions of the file are lost. Sorry about that. I created https://github.com/os-autoinst/openQA/pull/3594 but now with a comment so that we know why we need that chmod call :)
Updated by okurz about 4 years ago
- Copied to action #80516: Docker image for webui and workers on docker hub reflect current state added
Updated by okurz about 4 years ago
- Subject changed from Docker image for webui and workers are versioned and uploaded to docker hub / obs registry to Docker image for webui and workers are versioned and uploaded to obs registry
- Description updated (diff)
- Target version changed from future to Ready
Updated by ilausuch about 4 years ago
- Description updated (diff)
As far as I know versioning is controlled directly by the OBS. When a merge is performed against the master, the image creation will be launched. The latest build made with the latest tag and indicating the date of publication will be published in the registry. So we can consider it taken for granted.
Updated by ilausuch about 4 years ago
In order to list where we can find the build images:
registry.opensuse.org/devel/openqa/containers15.2/openqa_webui:latest
registry.opensuse.org/devel/openqa/containers15.2/openqa_worker:latest
Updated by ilausuch about 4 years ago
Also Added Web UI Load Balancer build container package
https://build.opensuse.org/package/show/devel:openQA/openQA_container_webUI_loadbalancer
Updated by okurz about 4 years ago
- Description updated (diff)
- Due date set to 2020-12-02
- Status changed from Workable to Feedback
With my PR contribution https://github.com/os-autoinst/openQA/pull/3595 merged we prominently mention the Dockerfile based containers in our documentation. We sholud wait until this is deployed to open.qa/docs . More of announcements can be done as part of #80534 . Setting due to to 2020-12-02 as I assume at the latest until then the documentation should be published. Normally that should happen anyway tomorrow morning by an automatic circleCI job creating a PR.
Updated by ilausuch about 4 years ago
- Status changed from Feedback to Resolved
After checking that https://github.com/os-autoinst/openQA/pull/3595 is published then I put the status as resolved