action #160436
openopenQA Project (public) - coordination #105624: [saga][epic] Reconsider how openQA handles secrets
openQA Project (public) - coordination #157537: [epic] Secure setup of openQA test machines with secure network+secure authentication
Use s390zl19+s390zl1a in production size:S
0%
Description
Motivation¶
There are two s390x LPARs, s390zl19+s390zl1a, that were originally prepared to run as openQA qemu workers for #159063 but so far os-autoinst-distri-opensuse based tests do not run on such environment which is why s390zl19+s390zl1a are currently unused. We should ensure that both LPARs are put to good use, e.g. just run the same setup as on s390zl12+13 though with more limited ressources.
Acceptance criteria¶
- AC1: Both s390zl19+s390zl1a are used in production
Suggestions¶
- Ensure both s390zl19+s390zl1a are used in production just like s390zl12+13
- Just login over ssh
- Look into #159063-3 regarding the storage and maybe mount points
- Then maybe simply follow https://gitlab.suse.de/openqa/salt-states-openqa instructions using the same approach as for s390zl12+13
- Also set the newly introduced grain "roles: external_openqa_hypervisor", see https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/top.sls?ref_type=heads#L59
- If both instances are not really usable then free the resources again coordinating with mgriessmeier
Updated by okurz 8 months ago
- Copied from action #159063: s390x qemu backend host within SUSE networks added
Updated by mgriessmeier 7 months ago
I will use ZL1A for manual testing and debugging purposes for the time being.
please let me know if you need it re-installed to continue with this ticket