Architectures/PowerPC/Infrastructure

These are not the droids you're looking for
This information is for the Fedora for Power and Fedora Infrastructure teams only. Access to these systems is highly restricted

Fedora for Power currently has all of its infrastructure located on two physical hosts, each running multiple LPARs:

ppc-comm03

• Hypervisor: PowerVM
• VIOS: ppc-comm03.qa.fedoraproject.org
• ASM: ppc-comm03-mgmt.qa.fedoraproject.org

IBM 8231-E2B

Hostname	LPAR Name	LPAR ID
ppc-hub.qa	hub	3
ppc-composer.qa	composer	4
ppc-builder1.qa	builder1	2
ppc-builder2.qa	builder2	5
ppc-builder3.qa	builder3	6
ppc-builder4.qa	builder4	7

• Note that builder4 is a configured LPAR, but is normally turned off and inactive to allow the rest of the hosts on the system to have more CPU and I/O bandwidth.

ppc-comm04

• Hypervisor: PowerVM
• VIOS: ppc-comm04.qa.fedoraproject.org
• ASM: ppc-comm04-mgmt.qa.fedoraproject.org

Hostname	LPAR Name	LPAR ID
ppc-builder5.qa	builder5	2
ppc-builder6.qa	builder6	3
ppc-builder7.qa	builder7	4
ppc-builder8.qa	builder8	5
ppc-releng.qa	releng	6

• The builder8 lpar exists but has not been installed to
• releng is a not a production "system", it's used for install testing and miscellaneous tasks as needed.

ppc-comm05

• Hypervisor: PowerVM
• VIOS: ppc-comm05.qa.fedoraproject.org
• ASM: ppc-comm05-mgmt.qa.fedoraproject.org

Hostname	LPAR Name	LPAR ID
ppc-le-hub.qa	ppc-le-hub	2

ppc-comm06

• Hypervisor: Fedora/KVM
• ASM: ppc-comm06-mgmt.qa.fedoraproject.org

Hostname
ppc-le-builder1.qa.fedoraproject.org

ppc-comm07

• Hypervisor: Fedora/KVM
• ASM: ppc-comm07-mgmt.qa.fedoraproject.org

Hostname
ppc-le-builder2.qa.fedoraproject.org

ppc-comm08

• Hypervisor: Fedora/KVM
• ASM: ppc-comm08-mgmt.qa.fedoraproject.org

Hostname
ppc-le-builder3.qa.fedoraproject.org

ppc8-01

• Hypervisor: None
• RAID: Needs to be raid'd
• ASM: ppc8-01-fsp.qa.fedoraproject.org

ppc8-02

• Hypervisor: None
• ASM: ppc8-02-fsp.qa.fedoraproject.org
• RAID: Needs to be raid'd

Hostname

ppc8-03

• Hypervisor: None
• ASM: ppc8-03-fsp.qa.fedoraproject.org
• RAID: Needs to be raid'd

Hostname

ppc8-04

• Hypervisor: None
• ASM: ppc8-04-fsp.qa.fedoraproject.org
• RAID: Needs to be raid'd

Hostname

Handy VIOS Commands

• Immediately restart a system:

chsysstate -o shutdown -r lpar --immed --restart -n [LPAR name]

• Attach a serial console:

mkvt -id [LPAR ID]

To quit the console while you're in it, use "~.[ENTER]"

• Unattach someone else's serial console:

rmvt -id [LPAR ID]

• List all LPARs on the system (and only display LPAR name and ID):

lssyscfg -r lpar -F lpar_id,name

• Create virtual media from an ISO and attach it to a system:

mkvopt -name Fedora-18-20120830-Hamzy-ppc64-DVD -file Fedora-18-20120830-Hamzy-ppc64-DVD.iso -ro
loadopt -disk Fedora-18-20120830-Hamzy-ppc64-DVD -vtd vtopt4 -release

Use 'lsmap -all' to figure out which LPAR has which vtopt device.

Fedora/KVM Notes

• Any time the host is power cycled, SMT must be manually disabled:

  ppc64_cpu --smt=off

• Each guest on the KVM hosts currently uses nearly all of the CPU resources on that system.
• After the ppc-le-hub is retired, we may want to convert ppc-comm05 to be a KVM host. It has hardware RAID so we likely want to use it for high-value guests (hub, composers) before builders.
• Guests on the KVM hosts each have 'start-foo.sh' scripts in /root, e.g:

#!/bin/bash
ppc64_cpu --smt=off
qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER7 -smp 14 -m 16G -nographic -nodefaults -monitor stdio -serial pty -device spapr-vscsi -device spapr-vlan,netdev=net1,mac=12:34:56:78:9A:BF -netdev bridge,br=br0,id=net1 -append "rw root=/dev/sda" -kernel /home/kvm/vmlinuz-3.14.0-0.rc8.git0.1.fc21.ppc64le -initrd /home/kvm/initrd-3.14.0-0.rc8.git0.1.fc21.img -drive file=/home/kvm/ppc-le-builder3.img

Hostname