action #76990
closed
coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
Improve documentation for redundant/load-balancing webui deployments of openQA
Added by okurz over 3 years ago.
Updated about 3 years ago.
Category:
Feature requests
Description
Motivation¶
We have a proof-of-concept of a redundant/load-balancing webui deployment based on docker-compose. To make that more visible we should cover it in documentation so that it shows up in https://open.qa/docs
Acceptance criteria¶
Suggestions¶
- Copied from action #69355: [spike] redundant/load-balancing webui deployments of openQA added
- Target version changed from future to Ready
- Parent task set to #80142
- Blocked by action #88187: Set the addresses in the "internal clients" configurable added
- Status changed from Workable to In Progress
PR: https://github.com/os-autoinst/openQA/pull/3819
As a first step I only did the improvements mentioned in the commit message. However, I have to note that the documentation is actually horrible to follow. Two different setups (Fedora and docker-compose) are explained in an interleaved way. It would make much more sense to use distinct sections. The documentation also uses way too many cross-references of the kind "do not follow instructions of that other section" or "follow instructions of that other section except for".
PR merged. Additional to the AC I suggest to crosscheck with "example users" if the new documentation structure is sufficient.
- Status changed from In Progress to Feedback
The documentation is now available under http://open.qa/docs/#containerizedsetup.
Additional to the AC I suggest to crosscheck with "example users" if the new documentation structure is sufficient.
I have already mentioned that I don't like the way the documentation is structured. At least the Fedora container and the docker-compose setup should be separated from each other. However, I'm not sure whether it makes much sense to improve it at this point.
- Status changed from Feedback to Resolved
It should be good enough for now. I've been following the instructions myself and was able to create a basic docker-compose setup. The documentation should of course be further extended as we improve the docker-compose setup itself.
Also available in: Atom
PDF