action #33223
closed
coordination #28630: [qe-core] setup for LPAR installation (manual + automatic)
coordination #28869: [sle][functional][virtualization][s390-kvm][s390x][epic] Automated installation on LPAR & integration to openQA
[sle][functional][virtualization][s390-kvm][s390x][tools][u][research] Learn how to use snipl to install and configure an LPAR
Added by mgriessmeier about 6 years ago.
Updated about 1 year ago.
Target version:
SUSE QA - Milestone 15
Description
User story¶
There is a cli tool called snipl (Simple Network IPL), which can be used to communicate with the zHMC from the console.
Goal here is to learn how this cli works and how it can be used to communicate with our SUSE zHMC to interact with a given LPAR (e.g. start, stop, install)
Acceptance criteria¶
- AC1: Learn how snipl works in our environment
- AC2: Come up with a proof of concept how the automation of a LPAR installation can be done
- Precedes action #33226: [sle][functional][virtualization][s390-kvm][s390x][medium] Add a simple testsuite which uses the "new" LPAR backend added
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][u] Learn how to use snipl to install and configure an LPAR to [sle][functional][virtualization][s390-kvm][s390x][tools][u][research] Learn how to use snipl to install and configure an LPAR
- Status changed from New to Workable
- Status changed from Workable to In Progress
sooo, after first research, I can use snipl to control a LPAR to some extend (start, stop, activate, deactivate)
unfortunately I didn't find a way yet to trigger installation. apparently we need to boot from a scsi disk where some kind of bootloader exists which then can boot the actual installation system.
I've requested the required disks and try to come up with something which works for us to trigger the installation
- Assignee changed from mgriessmeier to nicksinger
nick is mainly working on this atm
We came up with a new dracut module: https://github.com/nicksinger/dracut-qnipl
This module was already able to chain-load the installer initrd/kernel. We need now to come up with a way to provide all the additional parameters to the SUSE installer while respecting the maximum character limit of "ossparms_scsiload".
- Copied to action #33682: [sle][functional][s390-kvm][hard][u] Create a useful documentation for the automated LPAR setup/qnipl added
- Copied to deleted (action #33682: [sle][functional][s390-kvm][hard][u] Create a useful documentation for the automated LPAR setup/qnipl)
- Precedes action #33682: [sle][functional][s390-kvm][hard][u] Create a useful documentation for the automated LPAR setup/qnipl added
- Status changed from In Progress to Resolved
First manual installation with an automatically started LPAR was successful so we can conclude here with the experiment and push forward into production as described by the followup tickets.
Also available in: Atom
PDF