coordination #28630
Updated by mgriessmeier over 6 years ago
## Motivation
SLE needs to support installation on s390x so we need a way to test it. Also, we have at least one LPAR available for SUSE QA SLE and should make use it for it, be it solely for manual testing or also for automatic testing including the possibility to have virtual machines (z/VM or suse-kvm) on that LPAR installation
## Acceptance criteria
* **AC1:** The LPAR instance(s) that are available for QA SLE are documented, e.g. on https://wiki.microfocus.net/index.php/OpenQA -> https://progress.opensuse.org/issues/28860
* **AC2:** There is a documented workflow how to use that LPAR or description how it's used -> https://progress.opensuse.org/issues/28863
* **AC3:** The LPAR is used for manual and/or automatic testing on a regular base -> https://progress.opensuse.org/issues/28869
* **AC4:** Redefine machines on openQA, right now we have s390x-kvm for s390p8 which is the sle12sp3 lpar, we need to add one for s390p7, the sle15 lpar -> https://progress.opensuse.org/issues/28967
## Further details
### short summary, not providing a full documentation
* we have currently three LPARs which openQA is using
* s390pb: zKVM hypervisor which we don't touch directly and only using to install guests via virsh
* s390p8: SLE-12SP3 KVM Hypervisor which we need to always update to the latest maintenance updates automatically but not reinstall
* s390p7: SLE-15 KVM Hypervisor which we need to reinstall with every build and on top of that install guests by using virsh
* zHMC
* our LPARs are controlled via zHMC (z Hardware Management Console -> https://zhmc.suse.de)
* there is one dedicated QAP account which is at the moment restricted to me only, I need to clarify how we can handle this, because stuff can really break if some misclick happens here ;)
* TODO documentation, other wiki pages, other tickets, meeting minutes, etc.