action #132134
Updated by okurz over 1 year ago
## Motivation
New hardware was ordered to serve as openQA workers for o3, both x86_64 and aarch64. We can connect those machines to the o3 webUI VM instance regardless if o3 running still from NUE1 or from PRG2.
## Acceptance criteria
* **AC1:** o3 multi-machine jobs run successfully on new PRG2 openQA workers
* **AC2:** All o3 workers have the same relevant downgrades and package locks as others, e.g. see w19+w21 as reference for kernel-default, linked to https://bugzilla.suse.com/show_bug.cgi?id=1214537
## Suggestions
* Track https://jira.suse.com/browse/ENGINFRA-2347 "DMZ-OpenQA implementation" so that the o3 network is available
* Track https://jira.suse.com/browse/ENGINFRA-2379 "PRG2 IPMI for QA" to be able to remote control
* Track https://jira.suse.com/browse/ENGINFRA-2155 "Install Additional links to DMZ-CORE from J12 - openQA-DMZ", something about cabling
* Track https://jira.suse.com/browse/ENGINFRA-1742 "Build OpenQA Environment" which is the neighboring story of the o3 VM being migrated
* Wait for Eng-Infra to inform us about the availability of the network and machines
* Ensure we can connect over IPMI
* Include IPMI contact details in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls
* Follow https://progress.opensuse.org/projects/openqav3/wiki/#Setup-guide-for-new-machines for o3 to install OS and openQA worker, connect to o3
* Ensure configuration is equivalent to what existing o3 machines can do
* Ensure that o3 can work without relying on any physical machine in NUE1 (if problems found then feel free to delegate into a new, specific ticket)
## Out of scope
* aarch64: #134123
* w26,w27,w28: #134126