coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
Set the addresses in the "internal clients" configurable
The listening addresses are hardcoded to localhost within the different "internal clients" (e.g. lib/OpenQA/Scheduler/Client.pm and lib/OpenQA/WebSockets/Client.pm).
This limitation prevents running the different parts of the web UI on different hosts, e.g. a load balanced environment because the different components (scheduler, websockets, …) cannot communicate witch each other.
Read an environment variable like OPENQA_SCHEDULER_HOST. This environment variable needs then be supplied to all other containers.
Note: It looks like the livehandler and gru don't have a client. That likely means it is no necessary to care about them as no other services access them (via HTTP).
AC1: The addresses in the "internal clients" are configurable
- Category set to Feature requests
- Target version set to Ready
Sounds useful. Please follow the template from https://progress.opensuse.org/projects/openqav3/wiki#Feature-requests