action #159651
Updated by jbaier_cz 6 months ago
## Motivation Apache in prefork mode uses a lot of resources to provide mediocre performance. After nginx is deployed on OSD we should ensure that nginx helps to improve performance either with our default config or with additional config tweaks ## Acceptance criteria * **AC1:** It is known if Nginx default config or rate limiting features help to prevent work for our use cases * **AC2:** Nginx has been deployed successfully on OSD unresponsiveness ## Suggestions * Follow what was done for Nginx deployment on OSD Make sure there is an easy way to switch back to Apache in #130636 and #159654 case something goes wrong * Take a look at what we already do or didn't want to do on o3, see See #129490 for results from O3 * Monitor performance over some time, in particular if Adapt O3 nginx config for HTTP response graphs from openQA directly still show unresponsiveness windows or not + HTTPS (O3 only requires HTTP) * Add changes to salt-states-openqa including monitoring: we have multiple panels regarding apache that need to be adapted for any nginx config tweaks ## Out of scope as applicable * Any major research or big config tweaks for rate limiting, just some very basics if necessary at all Ensure that we have no alerts regarding "oh no, apache is down" ;)