Project

General

Profile

action #33682

[sle][functional][s390-kvm][hard][u] Create a useful documentation for the automated LPAR setup/qnipl

Added by nicksinger over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
SUSE QA - Milestone 18
Start date:
Due date:
2018-08-28
% Done:

0%

Estimated time:

Description

#33223 showed us how to setup a SCSI-drive to kickstart a SLES installation from the initramfs by using kexec to chain-load several "bootloader" steps.
This knowledge now needs to be preserved for future in form of documentation. This includes ( ACs ):

Notes:

  • https://progress.opensuse.org/projects/openqav3/wiki#s390x-Test-Organisation would be maybe a good place to put all the info
  • Move dracut-qnipl into a non-private repo (maybe openQA org?)
  • bootstrap SCSI-disk is a shared medium between several LPARs and Infra/gschlotter is needed to link LPAR <-> SCSI-bootstrap-disk
  • Example cmd to start an LPAR remote (e.g. from a x86_64 host): snipl -f ./snipl.conf -s P0069A27-LP3 -A fa00 --wwpn_scsiload 500507630713d3b3 --lun_scsiload 4001401100000000 --ossparms_scsiload "install=http://openqa.suse.de/assets/repo/SLE-15-Installer-DVD-s390x-Build533.2-Media1 hostip=10.161.159.3/20 gateway=10.161.159.254 Nameserver=10.160.0.1 Domain=suse.de ssh=1 regurl=http://all-533.2.proxy.scc.suse.de"

Notes about the "magic" bootstrap disk:

linux-kboz:~ # lsblk
NAME                                        MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda                                           8:0    0   10G  0 disk  
  sda1                                        8:1    0   10G  0 part  
  36005076307ffd3b30000000000000111         254:0    0   10G  0 mpath 
    36005076307ffd3b30000000000000111-part1 254:1    0   10G  0 part  
sdb                                           8:16   0   10G  0 disk  
  sdb1                                        8:17   0   10G  0 part  
  36005076307ffd3b30000000000000111         254:0    0   10G  0 mpath 
    36005076307ffd3b30000000000000111-part1 254:1    0   10G  0 part
linux-kboz:/boot/zipl # sfdisk -d /dev/sda 
label: dos
label-id: 0x1323e80f
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=    20969472, type=83
linux-kboz:/tmp/test # mount /dev/mapper/36005076307ffd3b30000000000000111-part1 /tmp/test
linux-kboz:/tmp/test # find .
.
./zipl
./zipl/bootmap
./image_installer
./lost+found
./initrd_installer
./zipl.conf
./initrd_zipl
./image_4.12.14-16.2
./image_zipl
./custom_initramfs
./image_4.12.14-11.2
linux-kboz:/tmp/test # find .
.
./zipl
./zipl/bootmap
./image_installer
./lost+found
./initrd_installer
./zipl.conf
./initrd_zipl
./image_4.12.14-16.2
./image_zipl
./custom_initramfs
./image_4.12.14-11.2
linux-kboz:/tmp/test # file *
custom_initramfs:   XZ compressed data    <- generated by dracut with qnipl-module enabled
image_4.12.14-11.2: Linux S390
image_4.12.14-16.2: Linux S390
image_installer:    Linux S390
image_zipl:         Linux S390
initrd_installer:   XZ compressed data
initrd_zipl:        XZ compressed data
lost+found:         directory
zipl:               directory
zipl.conf:          ASCII text             <- IIRC needed for `zipl` to generate/write the z-bootloader
linux-kboz:/tmp/test # cat zipl.conf 
## This file was written by 'grub2-install/grub2-zipl-setup'
## filling '/etc/default/zipl2grub.conf.in' as template
## with values from '/etc/default/grub'.
## In-place modifications will eventually go missing!

[defaultboot]
defaultmenu = menu

[custom]
    target = /mnt/network_boot/zipl
    ramdisk = /mnt/network_boot/custom_initramfs
    image = /mnt/network_boot/image_4.12.14-16.2
    parameters = "rd.break=initqueue TERM=dumb plymouth.enable=0 "

:menu
    target = /mnt/network_boot/zipl
    timeout = 0
    default = 1
    prompt = 1
    1 = custom

History

#2 Updated by nicksinger over 3 years ago

  • Subject changed from [sle][functional][s390-kvm][u] Create a useful documentation for the automated LPAR setup/qnipl to [sle][functional][s390-kvm][hard][u] Create a useful documentation for the automated LPAR setup/qnipl

Writing documentation is always hard for devs…

#5 Updated by nicksinger over 3 years ago

  • Due date deleted (2018-04-10)
  • Start date deleted (2018-03-28)

#6 Updated by okurz over 3 years ago

  • Due date set to 2018-04-24

#7 Updated by nicksinger over 3 years ago

  • Status changed from In Progress to Workable

huh… forgot to set back to workable after writing the README.md from qnipl.

#8 Updated by okurz over 3 years ago

  • Due date deleted (2018-04-24)
  • Assignee deleted (nicksinger)
  • Target version changed from Milestone 15 to Milestone 16

how do you feel about https://progress.opensuse.org/issues/33682 in the current sprint? I will move it but if you think someone will really commit to accomplishing it in S15 we can move it back

#9 Updated by okurz over 3 years ago

  • Due date set to 2018-06-05

#10 Updated by SLindoMansilla over 3 years ago

  • Due date changed from 2018-06-05 to 2018-06-19

Not enough capacity during sprint 18

#11 Updated by okurz over 3 years ago

  • Target version changed from Milestone 16 to Milestone 17

That's M17 by now then

#12 Updated by mgriessmeier over 3 years ago

  • Due date changed from 2018-06-19 to 2018-07-03

note down first steps, what was already done - to have a better starting point later on

#13 Updated by okurz over 3 years ago

  • Description updated (diff)

#14 Updated by riafarov over 3 years ago

Missing step: link it to wiki or some other place which is visible for people who are not aware about the specific repo.

#15 Updated by nicksinger over 3 years ago

  • Description updated (diff)

#16 Updated by nicksinger over 3 years ago

  • Description updated (diff)

#17 Updated by nicksinger over 3 years ago

  • Description updated (diff)

#18 Updated by nicksinger over 3 years ago

  • Description updated (diff)

#19 Updated by nicksinger over 3 years ago

  • Description updated (diff)

#20 Updated by nicksinger about 3 years ago

  • Status changed from Workable to In Progress

Topic now documented at the progress-s390x-wiki. Assigning to mgriessmeier to cross-check it.

#21 Updated by nicksinger about 3 years ago

  • Status changed from In Progress to Feedback
  • Assignee set to mgriessmeier

#22 Updated by nicksinger about 3 years ago

I also tried to find the right place to host the github repo:

12:47 <nsinger> I'm looking for the right place to put https://github.com/nicksinger/dracut-qnipl . coolo, okurz would you say https://github.com/os-autoinst is the appropriate org for it? Or is there a better org for such things?
13:47 <okurz> nsinger: it does not depend on os-autoinst or openQA, right? Then I guess openSUSE namespace could work
13:48 <okurz> nsinger: I guess rbrown is happy to create a repo for you within https://github.com/openSUSE if you like
13:57 <nsinger> okurz: well it is not only restricted to openQA but the whole use-case arises out of that context. However, I like the idea of using openSUSE and will follow up on that

and therefore have asked rbrown about a new repo:

13:58 <nsinger> hey there. Would you be so kind to create a repo inside the openSUSE org on github where I could move https://github.com/nicksinger/dracut-qnipl to?
13:58 <nsinger> I can also write a short mail if required. Just let me know :)

#23 Updated by nicksinger about 3 years ago

Got access to the openSUSE org. I've created a "secret" openqa-users group in there to transfer the repo to this team. Wiki-links already updated.

#24 Updated by okurz about 3 years ago

  • Project changed from SUSE QA to QA

#25 Updated by okurz about 3 years ago

  • Due date changed from 2018-07-03 to 2018-07-31
  • Target version changed from Milestone 17 to Milestone 18

We do not understand right now what is missing for resolution.

#26 Updated by okurz about 3 years ago

  • Due date changed from 2018-07-31 to 2018-08-28

mgriessmeier please crosscheck with nsinger what is the current state and if there is anything missing from your point of view. I suggest to also use a "test person" to see if he can find the LPAR documentation with only a little hint and considers the documentation "useful" enough.

#27 Updated by mgriessmeier about 3 years ago

okurz wrote:

We do not understand right now what is missing for resolution.

permission to close this still missing

#28 Updated by okurz about 3 years ago

  • Status changed from Feedback to Resolved

so I assume you want to set it to "Resolved" then. I will try to manage the users for the progress project better.

Also available in: Atom PDF