action #109734
Updated by okurz about 2 years ago
## Motivation
Multiple times we have found users trying to start the systemd-services `openqa-worker@` when instead we are running `openqa-worker-auto-restart@`. Last instance when that happened was in #109055. We should try to find a better way which is less confusing to users. At best we should have only `openqa-worker@` and use configuration to solve the auto-restart requirement.
## Acceptance criteria
* **AC1:** We have an unambiguous solution for providing both variants of worker modes which are not confusing users
* **AC2:** Ensure documentation covers the updated way
## Suggestions
* DONE: Research about systemd service best practices
* DONE: Research why we chose to have separate systemd service at the time -> Likely because we need different settings on systemd level
* DONE: Conduct a brainstorming session together, different ideas:
* Replace openqa-worker@ by a symlink pointing to the real solution, e.g. "openqa-worker-auto-restart" and "openqa-worker-plain", similar to "network.service" which for us is a symlink in /etc/systemd/system pointing to e.g. /usr/lib/systemd/system/NetworkManager.service or /usr/lib/systemd/system/wicked.service
* Alternative: just provide a drop-in file instead of separate systemd service file
* Alternative: Potentially provide the drop-in file in an openSUSE package
* Alternative: Solve it within a process itself so that systemd is not involved, e.g. same as hypnotoad or nginx
* Should the services be actual "conflicts" on the level of systemd? -> Likely yes, but not a full solution. Could be done on top
* Update documentation