Actions
action #111377
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #80908: [epic] Continuous deployment (package upgrade or config update) without interrupting currently running openQA jobs
Continuous deployment of osd workers - similar as on o3 size:M
Status:
Rejected
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-05-20
Due date:
% Done:
0%
Estimated time:
Description
Acceptance criteria¶
- AC1: All osd workers automatically deploy after every update to os-autoinst or openQA-worker but only if o3 is fine
Suggestions¶
- Read how #105885 was done
- Ensure to have a check for "o3 is fine" included as we already have in our osd-deployment
- Enable the timer for "openqa-continuous-update.service" with salt
- For checking call
systemctl status openqa-continuous-updateand check results, e.g.journalctl -e -u openqa-continuous-updateand check for any unforeseen errors and such - Monitor the state of the systems after some hours
- Monitor again on the next day
Updated by okurz over 2 years ago
- Copied from action #105885: Continuous deployment of o3 workers - all the other o3 workers size:M added
Updated by okurz over 2 years ago
- Status changed from New to Rejected
- Assignee set to okurz
Actually I think we shouldn't need that. For the time being we can stay on daily deployment on OSD and continuous on O3.
Actions