Project

General

Profile

Actions

coordination #28630

open

[qe-core] setup for LPAR installation (manual + automatic)

Added by okurz over 6 years ago. Updated about 1 year ago.

Status:
Blocked
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2017-12-05
Due date:
2019-12-31 (over 4 years late)
% Done:

81%

Estimated time:
(Total: 0.00 h)

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

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.


Subtasks 8 (4 open4 closed)

action #28860: [sle][functional][virtualization][s390-kvm][s390x][easy] Documentation of LPARs used in QA SLEResolvedmgriessmeier2017-12-052017-12-19

Actions
action #28863: [sle][functional][virtualization][s390-kvm][s390x][medium] Documentation of LPAR usage/installation workflowResolvedmgriessmeier2017-12-052017-12-19

Actions
coordination #28869: [sle][functional][virtualization][s390-kvm][s390x][epic] Automated installation on LPAR & integration to openQANewmgriessmeier2018-03-142019-12-31

Actions
action #33223: [sle][functional][virtualization][s390-kvm][s390x][tools][u][research] Learn how to use snipl to install and configure an LPARResolvednicksinger2018-03-142018-03-27

Actions
action #33226: [sle][functional][virtualization][s390-kvm][s390x][medium] Add a simple testsuite which uses the "new" LPAR backendBlockedmgriessmeier2020-01-01

Actions
action #33232: [sle][functional][virtualization][s390-kvm][s390x] Execute useful LPAR installation testcases in the SLE Functional job groupNewmgriessmeier2020-01-02

Actions
action #33916: [sle][virtualization][s390x][hard] Implement simple backend which uses snipl/qnipl for automated LPAR installationBlockedmgriessmeier2018-03-142019-12-31

Actions
action #28967: [sle][functional][virtualization][s390x][s390-kvm][easy] Adapt Machines for s390-kvm (add for sle15, rename for sle12sp3)Resolvedmgriessmeier2017-12-062018-01-02

Actions
Actions #1

Updated by okurz over 6 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.

Actions #2

Updated by mgriessmeier over 6 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

Actions #3

Updated by mgriessmeier over 6 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

Actions #4

Updated by mgriessmeier over 6 years ago

  • Description updated (diff)

Added subtasks for each AC

Actions #5

Updated by mgriessmeier over 6 years ago

  • Description updated (diff)
Actions #6

Updated by mgriessmeier over 6 years ago

  • Description updated (diff)
Actions #7

Updated by sebchlad over 6 years ago

  • Due date set to 2017-12-19

due to changes in a related task

Actions #8

Updated by cachen over 6 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)
Actions #9

Updated by mgriessmeier over 6 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)
Actions #10

Updated by mgriessmeier over 6 years ago

  • Due date changed from 2017-12-19 to 2018-01-02

due to changes in a related task

Actions #11

Updated by okurz about 6 years ago

  • Due date changed from 2018-01-02 to 2018-04-24

due to changes in a related task

Actions #12

Updated by mgriessmeier about 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]

Actions #13

Updated by mgriessmeier about 6 years ago

  • Due date changed from 2018-04-24 to 2018-03-27

due to changes in a related task

Actions #14

Updated by mgriessmeier about 6 years ago

  • Due date changed from 2018-03-27 to 2018-04-10

due to changes in a related task

Actions #15

Updated by okurz about 6 years ago

  • Target version changed from Milestone 16 to Milestone 17
Actions #16

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 18

it's M18 actually

Actions #17

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 18 to Milestone 19

that's actually M19

Actions #18

Updated by okurz over 5 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.

Actions #19

Updated by okurz over 5 years ago

  • Due date changed from 2018-11-07 to 2018-03-27

due to changes in a related task

Actions #20

Updated by okurz over 5 years ago

  • Target version changed from Milestone 21 to Milestone 25+

-> #33916

Actions #21

Updated by okurz over 5 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz

blocked by subtickets (refined enough)

Actions #22

Updated by okurz about 5 years ago

  • Due date changed from 2018-03-27 to 2019-12-31

due to changes in a related task

Actions #23

Updated by mgriessmeier about 5 years ago

  • Target version changed from Milestone 25+ to Milestone 26
Actions #24

Updated by okurz about 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.

Actions #25

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 26 to Milestone 29
Actions #26

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 29 to Milestone 35+
Actions #27

Updated by SLindoMansilla about 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)
Actions #28

Updated by okurz over 3 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 :)

Actions #29

Updated by szarate over 3 years ago

  • Tracker changed from action to coordination
  • Status changed from Blocked to New
Actions #31

Updated by szarate about 2 years ago

  • Target version changed from Milestone 35+ to future
Actions #32

Updated by szarate about 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.

Actions #33

Updated by okurz about 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.

Actions #34

Updated by szarate about 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> -

Actions

Also available in: Atom PDF