Installing the PowerVM NovaLink software on a Red Hat Enterprise Linux partition

1. You must have a web server to host your RHEL install media and kickstart file. This can be a Linux, AIX, or any operating system that has a running web server.
2. Mount the RHEL 7 ISO to a network location such that the vmlinuz file and the initrd.img file are accessible over HTTP or HTTPS protocol at the following locations: <mount location>/ppc/ppc64/vmlinuz and <mount location>/ppc/ppc64/initrd.img. The installer should be able to copy the vmlinuz file and the initrd.img file to a local location to start the RHEL installation.
3. Configure your kickstart file for automated installation. For more details about the configuration, see the sample kickstart file. Complete the following steps to configure the kickstart file:
   • Verify that all of the storage and network information matches your environment.
   • In the "# Setup your yum repository for Red Hat Enterprise Linux" section of the sample kickstart file, complete all YUM repository setup, Red Hat subscription management, and registration that is required to perform YUM installation of RHEL packages. For more information about setting up your YUM repository, see the Setting up the YUM Repository section.
4. Mount your kickstart file to a network location that is accessible over http or https.
5. In the last page of the install wizard, select the option to install RHEL and add the appropriate Installation Source and Kickstart File location. The values selected in the wizard can be automated by using the PowerVM NovaLink install configuration file.
6. Complete the installation, and after the Virtual I/O Servers are installed, the system performs a network boot to your RHEL installation source, and the installation proceeds, depending on the settings that are specified in the kickstart file.

• After the Virtual IO Servers are created and installed, the system reboots to the SMS menu.
• You can now point to a network boot server that has RHEL images, and reinstall RHEL on the PowerVM NovaLink partition by using the sample kickstart file.

# This is a sample kickstart file for installing NovaLink and its dependent
# packages on Red Hat Enterprise Linux.
# Modify this file as needed to match your site's configuration. You must setup
# your yum subscription management registration for the new system before NovaLink
# or any extended packages can install. Look at the example in the post install
# settings for more information.

# Firewall configuration
firewall --disabled

# Install OS instead of upgrade
install

# Define the repository for Extra Packages for Enterprise Linux (EPEL)
# If this repository cannot be reached, the installation of NovaLink
# will fail due to dependent packages from EPEL.
# Follow instructions at https://fedoraproject.org/wiki/EPEL
# after the system reboots to setup the EPEL repo, then install NovaLink again.
repo --name=epel --baseurl=http://download.fedoraproject.org/pub/epel/7/ppc64le

# Default root password "passw0rd" encrypted using python one liner:
# python -c 'import crypt,base64,os; print(crypt.crypt("passw0rd", "$6$" + 
base64.b64encode(os.urandom(6))))'
# The default password will be used when the base OS is installed. It will be
# changed later in post installation based on what is specified as the NovaLink user password.
rootpw --iscrypted $6$F5jDDW3B$Vf3th7JxE2nfwozOnbrl6moBeEanQbRqZRjvWeC03nJIumI3
intYOm4JUnl9Hg0uEncViM.snO5Dkq.zC3yo70

# Password hashing algorithm
auth  --passalgo=sha512

# Use text mode install
text

# System keyboard
keyboard us

# System language
lang en_US

# SELinux configuration
selinux --disabled

# Do not configure the X Window System
skipx
services --enabled=sshd

# Installation logging level. Possible values are info, debug, warning, error,
# or critical
logging --level=info

# System timezone
timezone  America/New_York

# Clear the Master Boot Record
zerombr

# Storage data and setup below. By default, this kickstart file
# assumes 2 disks: sda and sdb, to be on a RAID. A sample single
# disk setup is also provided. Set this up to properly reflect your
# environment.

# 1 DISK SETUP START
# Uncomment everything until "1 DISK SETUP END"
# if configuring single disk with no redundant VIOS
# Also, you must edit the PreP partition setting in
# the post install at the end of this file if using
# a single drive environment.

# bootloader --driveorder=sda
# part None --fstype prepboot --ondrive=sda --size 8
# part /boot --size 300 --fstype ext4 --ondisk /dev/sda
# part pv.01 --size 1 --grow --ondisk /dev/sda
# volgroup pvmvg pv.01
# logvol / --vgname=pvmvg --name=root --size=9216
# logvol /var --vgname=pvmvg --name=var --size=10240
# logvol /tmp --vgname=pvmvg --name=tmp --size=1024
# logvol swap --vgname=pvmvg --name=swap --fstype swap --size=4096
# logvol /home --vgname=pvmvg --name=home --size=1 --grow
# clearpart --drives=sda --all --initlabel

# 1 DISK SETUP END

# 2 DISK WITH RAID SETUP START
# Comment everything until "2 DISK WITH RAID SETUP END"
# if configuring single disk with no redundant VIOS

# Set drive boot order
bootloader --driveorder=sda,sdb

# RAID1 2 disk partition recipe using LVM over RAID
# Second disk needs to have PreP partition created
part None --fstype prepboot --ondrive=sdb --size 8

# Setup RAID
part raid.00 --size 256 --asprimary --ondrive=sda
part raid.10 --size 256 --asprimary --ondrive=sdb
part raid.01 --size 29696 --asprimary --ondrive=sda
part raid.11 --size 29696 --asprimary --ondrive=sdb

raid /boot --fstype ext4 --device raid1-boot --level=RAID1 raid.00 raid.10
raid pv.01 --device raid1-pv --level=RAID1 raid.01 raid.11

# Build out volume group and logical volumes.
volgroup pvmvg pv.01

logvol / --vgname=pvmvg --name=root --size=9216
logvol /var --vgname=pvmvg --name=var --size=10240
logvol /tmp --vgname=pvmvg --name=tmp --size=1024
logvol swap --vgname=pvmvg --name=swap --fstype swap --size=4096
logvol /home --vgname=pvmvg --name=home --size=1 --grow

# Partition clearing information
clearpart --drives=sda,sdb --all --initlabel

# 2 DISK WITH RAID SETUP END

# reqpart will take care of PreP partition on first disk
reqpart

# Reboot the lpar after install completes
reboot

%packages
kernel-headers
kernel-devel
openssh*
parted*
net-tools*
@base
epel-release
telnet
%end

%post
curTTY=$(tty)
exec < $curTTY > $curTTY 2> $curTTY
echo "Running post configuration"
clear
set -x

# Setup your yum repository for Red Hat Enterprise Linux
# NOTE: YOU MUST SET THIS UP BEFORE ANYTHING ELSE CAN INSTALL BELOW.
# An example of setting this up programmatically:
# subscription-manager register --username <username> --password <password> --auto-attach

# Setup  NovaLink's yum repository
cat > /etc/yum.repos.d/pvm.repo <<EOF
[novalink]
name=NovaLink
baseurl=http://public.dhe.ibm.com/systems/virtualization/Novalink/rhel/73/novalink_1.0.0/
failovermethod=priority
enabled=1
gpgcheck=0
EOF

# Setup yum repository for IBM's RSCT.
cat > /etc/yum.repos.d/ibm-power.repo <<EOF
[IBM_Power_Tools]
name=IBM Power Tools
baseurl=http://public.dhe.ibm.com/software/server/POWER/Linux/yum/OSS/RHEL/7/ppc64le
enabled=1
gpgcheck=0
[IBM_Power_SDK_Tools]
name=IBM Power SDK Tools
baseurl=http://public.dhe.ibm.com/software/server/POWER/Linux/yum/SDK/RHEL/7/ppc64le
enabled=1
gpgcheck=0
[Advance_Toolchain]
name=Advance Toolchain
baseurl=ftp://ftp.unicamp.br/pub/linuxpatch/toolchain/at/redhat/RHEL7
enabled=1
gpgcheck=0
EOF

# Create the user from the NovaLink configuration file or entered
# into the NovaLink install wizard.
useradd `nvram --print-config=nv-user`
usermod -p `nvram --print-config=nv-pass` `nvram --print-config=nv-user`

# Set the root's password to be the same as the NovaLink user. Remove
# the line below if you don't want the root password to be the same
# as the NovaLink's user password
usermod -p `nvram --print-config=nv-pass` root

# Install python positional & NovaLink
yum --assumeyes install pvm-novalink python-positional

# Add NovaLink user to pvm_admin group
usermod -G pvm_admin `nvram --print-config=nv-user`

# Setup firewall rule for RSCT
cat > /etc/firewalld/services/rmc.xml <<EOF
<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>RMC</short>
  <description>
Reliable Scalable Cluster Technology (RSCT) is a set of software components that together 
provide a comprehensive clustering environment for AIX®, Linux, Solaris, and Windows 
operating systems. RSCT is the infrastructure used by a variety of IBM® products to provide 
clusters with improved system availability, scalability, and ease of use.</description>
<port protocol="tcp" port="657"/>
 <port protocol="udp" port="657"/>
</service>
EOF
systemctl enable firewalld.service
firewall-offline-cmd --add-service=rmc

# nvram cleanup
nvram -p common --update-config nv-pass=
nvram -p common --update-config nv-user=

# Make sure PreP partitions are mirrored
# 2 DISK START
dd if=/dev/sda1 of=/dev/sdb1
parted /dev/sda set 1 boot on
parted /dev/sdb set 1 boot on
# 2 DISK END

# 1 DISK START
# parted /dev/sda set 1 boot on
# 1 DISK END
%end