Project

General

Profile

action #111377

coordination #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

Added by okurz about 1 month ago. Updated about 1 month ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-05-20
Due date:
% Done:

0%

Estimated time:
Difficulty:

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-update and check results, e.g. journalctl -e -u openqa-continuous-update and check for any unforeseen errors and such
  • Monitor the state of the systems after some hours
  • Monitor again on the next day

Related issues

Copied from openQA Project - action #105885: Continuous deployment of o3 workers - all the other o3 workers size:MResolved

History

#1 Updated by okurz about 1 month ago

  • Copied from action #105885: Continuous deployment of o3 workers - all the other o3 workers size:M added

#2 Updated by okurz about 1 month 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.

Also available in: Atom PDF