coordination #28630
open[qe-core] setup for LPAR installation (manual + automatic)
65%
Description
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.
Updated by okurz almost 7 years ago
I created this ticket because I do not know of any other progress ticket about the use of s390x LPARs for testing and questions surrounding that topic come up from time to time. I suggest to use this ticket to collect all requirements, e.g. in subtickets, linked tickets, comments, etc.
I assume we won't have all the points done before M16, mid of next year. Everyone else is welcome to provide the share of view and according requirements here.
Updated by mgriessmeier almost 7 years ago
AC1 will be done by me, once I can login again to intra.microfocus
meanwhile I had a first quick look on the tool to automate communication with the zHMC which looks very promising
Updated by mgriessmeier almost 7 years ago
I've set up s390P7 for now to not block manual testing
I don't plan to integrate it in openQA in the near future, most likely not this year anymore
Alice and Leon are aware of how to use it and hopefully can perform manual testing here
Updated by cachen almost 7 years ago
- Subject changed from [sle][functional][migration][virtualization][tools][s390x][epic] setup for LPAR installation (manual + automatic) to [sle][functional][migration][virtualization][s390x][tools][epic] setup for LPAR installation (manual + automatic)
Updated by mgriessmeier almost 7 years ago
- Subject changed from [sle][functional][migration][virtualization][s390x][tools][epic] setup for LPAR installation (manual + automatic) to [sle][functional][migration][virtualization][s390-kvm][s390x][tools][epic] setup for LPAR installation (manual + automatic)
Updated by mgriessmeier almost 7 years ago
- Due date changed from 2017-12-19 to 2018-01-02
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-01-02 to 2018-04-24
due to changes in a related task
Updated by mgriessmeier over 6 years ago
- Subject changed from [sle][functional][migration][virtualization][s390-kvm][s390x][tools][epic] setup for LPAR installation (manual + automatic) to [sle][functional][migration][virtualization][s390-kvm][s390x][tools][saga] setup for LPAR installation (manual + automatic)
changed to [saga] because one subticket is also an [epic]
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-04-24 to 2018-03-27
due to changes in a related task
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-03-27 to 2018-04-10
due to changes in a related task
Updated by okurz over 6 years ago
- Target version changed from Milestone 16 to Milestone 17
Updated by okurz over 6 years ago
- Target version changed from Milestone 17 to Milestone 18
it's M18 actually
Updated by okurz over 6 years ago
- Target version changed from Milestone 18 to Milestone 19
that's actually M19
Updated by okurz about 6 years ago
- Subject changed from [sle][functional][migration][virtualization][s390-kvm][s390x][tools][saga] setup for LPAR installation (manual + automatic) to [sle][functional][u][migration][virtualization][s390-kvm][s390x][tools][saga] setup for LPAR installation (manual + automatic)
- Target version changed from Milestone 19 to Milestone 21
hm, I doubt we can finish this in M19, trying again until M21 after subtasks are done which are planned for M20.
Updated by okurz almost 6 years ago
- Due date changed from 2018-11-07 to 2018-03-27
due to changes in a related task
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21 to Milestone 25+
-> #33916
Updated by okurz over 5 years ago
- Status changed from New to Blocked
- Assignee set to okurz
blocked by subtickets (refined enough)
Updated by okurz over 5 years ago
- Due date changed from 2018-03-27 to 2019-12-31
due to changes in a related task
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 25+ to Milestone 26
Updated by okurz over 5 years ago
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
Updated by mgriessmeier about 5 years ago
- Target version changed from Milestone 26 to Milestone 29
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 29 to Milestone 35+
Updated by SLindoMansilla over 4 years ago
- Subject changed from [sle][functional][u][migration][virtualization][s390-kvm][s390x][tools][saga] setup for LPAR installation (manual + automatic) to [sle][functional][migration][virtualization][s390-kvm][s390x][tools][saga] setup for LPAR installation (manual + automatic)
Updated by okurz about 4 years ago
- Subject changed from [sle][functional][migration][virtualization][s390-kvm][s390x][tools][saga] setup for LPAR installation (manual + automatic) to [sle][functional][migration][virtualization][s390-kvm][s390x][saga] setup for LPAR installation (manual + automatic)
I don't see the need for the SUSE QA Tools team (which ignored that issue so far anyway) so far. I am sure you will be able to find us in case of specific backend problems where you need support :)
Updated by szarate about 4 years ago
- Tracker changed from action to coordination
- Status changed from Blocked to New
Updated by szarate about 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
Updated by szarate over 2 years ago
- Target version changed from Milestone 35+ to future
Updated by szarate over 1 year ago
- Tags set to platform-team
- Project changed from 46 to openQA Project
- Subject changed from [sle][functional][migration][virtualization][s390-kvm][s390x][saga] setup for LPAR installation (manual + automatic) to [qe-core] setup for LPAR installation (manual + automatic)
- Category set to Feature requests
- Status changed from New to Blocked
- Assignee changed from mgriessmeier to szarate
I'm missing a backend
category... Oli, If you don't want it in this project, move it to the openQA tests one, but we'll handle this on QE-Core.
Updated by okurz over 1 year ago
szarate wrote:
I'm missing a
backend
category...
please do not add that. Ticket categories are not technical components. It's a different axis.
Oli, If you don't want it in this project, move it to the openQA tests one, but we'll handle this on QE-Core.
It's good.
Updated by szarate over 1 year ago
okurz wrote:
szarate wrote:
I'm missing a
backend
category...please do not add that. Ticket categories are not technical components. It's a different axis.
:), is not added - for now <insert evil laugh>
-
Updated by mgriessmeier 4 months ago
(updated subtasks)
as follow-up of https://bugzilla.suse.com/show_bug.cgi?id=1226215 - this task should be revisited and re-evaluated