QA » openQA Project » openQA Infrastructure

Motivation¶

After #127286 we should have continously released os-autoinst+openQA so we should be able to switch OSD to deploy from SLE+packagehub instead of custom OBS repo devel:openQA which allows for a bit more stabilization and also helps with other requirements, e.g. #168439 where one requirement might be that CC-relevant SUSE services are only produced by fully SUSE controlled platforms, i.e. using SLE+packagehub which is fully IBS built instead of devel:openQA with no explicit approval of only SUSE employees before packages are available from there

Acceptance criteria¶

• AC1: The complete OSD infrastructure does not rely on devel:openQA anymore
• AC2: Periodic deployment of os-autoinst+openQA and dependencies in OSD infrastructure from most recent possible packages

Suggestions¶

• Wait for #127286
• Change https://gitlab.suse.de/openqa/salt-states-openqa to not use devel:openQA repos anymore at all
• Consider the impact on https://gitlab.suse.de/openqa/osd-deployment/ as so far we distinguish exactly when packages come from devel:openQA or not to define what is part of nightly automatic OS upgrades and what is part of "osd deployment"
• Adapt https://gitlab.suse.de/openqa/osd-deployment/ where needed
• Try out the change role by role, e.g. individual workers first, then all workers, then other roles, then webUI
• Ensure devel:openQA is not present and not used anymore on any OSD salt controlled machine
• Monitor
• Ensure our documentation is up-to-date: https://gitlab.suse.de/suse/wiki/-/blob/main/openqa.md already does not mention devel:openQA at all which is good but it mentions osd-deployment so make sure to review that