action #130636
Updated by jbaier_cz 25 days ago
## Motivation Apache in prefork mode uses a lot of resources to provide mediocre performance. ## Acceptance criteria * **AC1:** It is known if Nginx rate limiting features work for our use cases * **AC2:** Nginx has been deployed successfully on OSD * **AC2:** No alerts regarding "oh no, apache is down" ;) ## Suggestions * Make sure there is an easy way to switch back to Apache in case something goes wrong * See #129490 for results from O3 * Adapt OSD O3 nginx config for HTTP + HTTPS (O3 only requires HTTP) * We can prepare the deployment of nginx in parallel Add changes to apache, salt-states-openqa including monitoring: we have it deployed and at any time decide when multiple panels regarding apache that need to switch by just disabling/enabling services accordingly. The deployment needs to consider dehydrated+nginx as well. We can switch OSD to be adapted for nginx to gather realtime data before we suggest to use nginx as default in our openQA documentation and CI infrastructure. applicable * Add changes to salt-states-openqa excluding monitoring * Ensure that we have no alerts regarding "oh no, apache is down" ;) * If there are any bigger issues observed then just revert and note down in follow-up tickets what needs to be solved first (to limit the ticket to size:S) ## Out of scope * It is known if Nginx rate limiting features work for our use cases * Full monitoring integration