Add IBM Z LPAR installation assembly

Author: SNiemann15

_topic_maps/_topic_map.yml

@@ -403,6 +403,8 @@ Topics:
     File: installing-ibm-z-kvm
   - Name: Restricted network IBM Z installation with RHEL KVM
     File: installing-restricted-networks-ibm-z-kvm
+  - Name: Installing a cluster in an LPAR on IBM Z and IBM LinuxONE
+    File: installing-ibm-z-lpar
   - Name: Installation configuration parameters for IBM Z and IBM LinuxONE
     File: installation-config-parameters-ibm-z
 - Name: Installing on IBM Power

installing/installing_ibm_z/installing-ibm-z-lpar.adoc

@@ -0,0 +1,142 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="installing-ibm-z-lpar"]
+= Installing a cluster in an LPAR on {ibm-z-title} and {ibm-linuxone-title}
+include::_attributes/common-attributes.adoc[]
+:context: installing-ibm-z-lpar
+
+toc::[]
+
+[role="_abstract"]
+In {product-title} version {product-version}, you can install a cluster in
+a logical partition (LPAR) on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
+
+[NOTE]
+====
+While this document refers only to {ibm-z-name}, all information in it also applies to {ibm-linuxone-name}.
+====
+
+[IMPORTANT]
+====
+Additional considerations exist for non-bare metal platforms. Review the information in the
+link:https://access.redhat.com/articles/4207611[guidelines for deploying {product-title} on non-tested platforms] before you install an {product-title} cluster.
+====
+
+== Prerequisites
+
+* You reviewed details about the xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update] processes.
+* You read the documentation on xref:../../installing/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
+* Before you begin the installation process, you must clean the installation directory. This ensures that the required installation files are created and updated during the installation process.
+* You provisioned xref:../../storage/persistent_storage/persistent-storage-ocs.adoc#persistent-storage-ocs[persistent storage using {rh-storage}] or other supported storage protocols for your cluster. To deploy a private image registry, you must set up persistent storage with `ReadWriteMany` access.
+* If you use a firewall, you xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configured it to allow the sites] that your cluster requires access to.
+
+[NOTE]
+====
+Be sure to also review this site list if you are configuring a proxy.
+====
+
+include::modules/cluster-entitlements.adoc[leveloffset=+1]
+
+[id="installation-requirements-user-infra-lpar_{context}"]
+== Requirements for a cluster with user-provisioned infrastructure
+
+For a cluster that contains user-provisioned infrastructure, you must deploy all
+of the required machines.
+
+This section describes the requirements for deploying {product-title} on user-provisioned infrastructure.
+
+include::modules/installation-machine-requirements.adoc[leveloffset=+2]
+include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]
+
+include::modules/minimum-ibm-z-system-requirements.adoc[leveloffset=+2]
+include::modules/preferred-ibm-z-system-requirements.adoc[leveloffset=+2]
+include::modules/csr-management.adoc[leveloffset=+2]
+include::modules/installation-network-user-infra.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+[id="additional-resources_ibmz_lpar-chrony-time-service"]
+.Additional resources
+
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+
+include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
+
+include::modules/installation-load-balancing-user-infra.adoc[leveloffset=+2]
+
+include::modules/installation-infrastructure-user-infra.adoc[leveloffset=+1]
+
+include::modules/installation-user-provisioned-validating-dns.adoc[leveloffset=+1]
+
+include::modules/ssh-agent-using.adoc[leveloffset=+1]
+
+include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
+
+include::modules/cli-installing-cli.adoc[leveloffset=+1]
+
+include::modules/installation-initializing-manual.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../installing/installing_ibm_z/installation-config-parameters-ibm-z.adoc#installation-config-parameters-ibm-z[Installation configuration parameters for {ibm-z-name}]
+
+include::modules/installation-bare-metal-config-yaml.adoc[leveloffset=+2]
+
+include::modules/installation-configure-proxy.adoc[leveloffset=+2]
+
+include::modules/installation-three-node-cluster.adoc[leveloffset=+2]
+
+include::modules/nw-operator-cr.adoc[leveloffset=+1]
+
+include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1]
+
+include::modules/ibmz-configure-nbde-with-static-ip.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+[id="additional-resources_configure-nbde-ibm-z-lpar"]
+.Additional resources
+
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-butane_installing-customizing[Creating machine configs with Butane]
+
+include::modules/installation-ibm-z-user-infra-machines-iso.adoc[leveloffset=+1]
+
+include::modules/installation-user-infra-machines-static-network.adoc[leveloffset=+2]
+
+include::modules/installation-installing-bare-metal.adoc[leveloffset=+1]
+
+include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
+
+include::modules/installation-approve-csrs.adoc[leveloffset=+1]
+
+include::modules/installation-operators-config.adoc[leveloffset=+1]
+
+include::modules/installation-registry-storage-config.adoc[leveloffset=+2]
+
+include::modules/registry-configuring-storage-baremetal.adoc[leveloffset=+3]
+
+include::modules/installation-registry-storage-non-production.adoc[leveloffset=+3]
+
+include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
+
+include::modules/cluster-telemetry.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+[id="additional-resources_ibmz-lpar-remote-health-monitoring"]
+.Additional resources
+
+* See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service
+
+* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within OpenShift4 nodes without SSH].
+
+[id="next-steps_ibmz-lpar"]
+== Next steps
+
+* xref:../../post_installation_configuration/machine-configuration-tasks.adoc#rhcos-enabling-multipath_post-install-machine-configuration-tasks[Enabling multipathing with kernel arguments on {op-system}].
+
+* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
+
+* If necessary, you can
+xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].

installing/installing_ibm_z/preparing-to-install-on-ibm-z.adoc

@@ -23,12 +23,18 @@ While this document refers only to {ibm-z-name}, all information in it also appl
 [id="choosing-an-method-to-install-ocp-on-ibm-z"]
 == Choosing a method to install {product-title} on {ibm-z-title} or {ibm-linuxone-title}
 
+The {product-title} installation program offers the following methods for deploying a cluster on {ibm-z-name}:
+
+* *Interactive*: You can deploy a cluster with the web-based link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform[{ai-full}]. This method requires no setup for the installer, and is ideal for connected environments like {ibm-z-name}.
+
+* *Local Agent-based*: You can deploy a cluster locally with the xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#preparing-to-install-with-agent-based-installer[agent-based installer] for air-gapped or restricted networks. It provides many of the benefits of the {ai-full}, but you must download and configure the link:https://console.redhat.com/openshift/install/ibmz/agent-based[agent-based installer] first. Configuration is done with a command line interface (CLI). This approach is ideal for air-gapped or restricted networks.
+//agent-based link for IBM Z not available yet needs to be verified shortly before GA
+* *Full control*: You can deploy a cluster on xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[infrastructure that you prepare and maintain], which provides maximum customizability. You can deploy clusters with both connected or air-gapped or restricted networks.
+
 You can install {product-title} with the link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform[{ai-full}]. This method requires no setup for the installer, and is ideal for connected environments like {ibm-z-name}.
 See xref:../../installing/installing_on_prem_assisted/installing-on-prem-assisted.adoc#installing-on-prem-assisted[Installing an on-premise cluster using the {ai-full}] for additional details.
 
-You can also install {product-title} on infrastructure that you provide. If you do not use infrastructure that the installation program provisions, you must manage and maintain the cluster resources yourself.
-
-See the xref:../../architecture/architecture-installation.adoc#installation-process_architecture-installation[Installation process] for more information about Assisted Installer and user-provisioned installation processes.
+See the xref:../../architecture/architecture-installation.adoc#installation-process_architecture-installation[Installation process] for more information about the installation processes.
 
 [IMPORTANT]
 ====
@@ -46,3 +52,5 @@ User-provisioned infrastructure requires the user to provision all resources req
 * **xref:../../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[Installing a cluster with RHEL KVM on {ibm-z-name} and {ibm-linuxone-name}]**: You can install {product-title} with KVM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
 
 * **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[Installing a cluster with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name} in a restricted network]**: You can install {product-title} with {op-system-base} KVM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted or disconnected network, by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.
+
+* **xref:../../installing/installing_ibm_z/installing-ibm-z-lpar.adoc#installing-ibm-z-lpar[Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name}]**: You can install {product-title} in a logical partition (LPAR) on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.

modules/installation-ibm-z-user-infra-machines-iso.adoc

@@ -1,12 +1,30 @@
 // Module included in the following assemblies:
 //
 // * installing/installing_ibm_z/installing-ibm-z.adoc
+// * installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc
+// * installing/installing_ibm_z/installing-ibm-z-lpar.adoc
+
+
+ifeval::["{context}" == "installing-ibm-z"]
+:ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-restricted-networks-ibm-z"]
+:ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-ibm-z-lpar"]
+:ibm-z-lpar:
+endif::[]
 
 :_mod-docs-content-type: PROCEDURE
 [id="installation-user-infra-machines-iso-ibm-z_{context}"]
 = Installing {op-system} and starting the {product-title} bootstrap process
 
+ifdef::ibm-z[]
 To install {product-title} on {ibm-z-name} infrastructure that you provision, you must install {op-system-first} on z/VM guest virtual machines. When you install {op-system}, you must provide the Ignition config file that was generated by the {product-title} installation program for the type of machine you are installing. If you have configured suitable networking, DNS, and load balancing infrastructure, the {product-title} bootstrap process begins automatically after the {op-system} z/VM guest virtual machines have rebooted.
+endif::ibm-z[]
+ifndef::ibm-z[]
+To install {product-title} on {ibm-z-name} infrastructure that you provision, you must install {op-system-first} in an LPAR. When you install {op-system}, you must provide the Ignition config file that was generated by the {product-title} installation program for the type of machine you are installing. If you have configured suitable networking, DNS, and load balancing infrastructure, the {product-title} bootstrap process begins automatically after the {op-system} guest machines have rebooted.
+endif::ibm-z[]
 
 Complete the following steps to create the machines.
 
@@ -113,6 +131,7 @@ rd.zfcp=0.0.19C7,0x50050763071bc5e3,0x4008400B00000000
 +
 Write all options in the parameter file as a single line and make sure you have no newline characters.
 
+ifdef::ibm-z[]
 . Transfer the initramfs, kernel, parameter files, and {op-system} images to z/VM, for example with FTP. For details about how to transfer the files with FTP and boot from the virtual reader, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-installing-zvm-s390[Installing under Z/VM].
 . Punch the files to the virtual reader of the z/VM guest virtual machine that is to become your bootstrap node.
 +
@@ -132,4 +151,21 @@ $ ipl c
 +
 See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-ipl[IPL] in IBM Documentation.
 +
+endif::ibm-z[]
+ifndef::ibm-z[]
+. Transfer the initramfs, kernel, parameter files, and {op-system} images to the LPAR, for example with FTP. For details about how to transfer the files with FTP and boot, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_8_installation/installing-in-an-lpar_installing-rhel[Installing in an LPAR].
+
+. Boot the machine
+endif::ibm-z[]
+
 . Repeat this procedure for the other machines in the cluster.
+
+ifeval::["{context}" == "installing-ibm-z"]
+:!ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-restricted-networks-ibm-z"]
+:!ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-ibm-z-lpar"]
+:!ibm-z-lpar:
+endif::[]

modules/minimum-ibm-z-system-requirements.adoc

@@ -2,6 +2,17 @@
 //
 // * installing/installing_ibm_z/installing-ibm-z.adoc
 // * installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc
+// * installing/installing_ibm_z/installing-ibm-z-lpar.adoc
+
+ifeval::["{context}" == "installing-ibm-z"]
+:ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-restricted-networks-ibm-z"]
+:ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-ibm-z-lpar"]
+:ibm-z-lpar:
+endif::[]
 
 :_mod-docs-content-type: CONCEPT
 [id="minimum-ibm-z-system-requirements_{context}"]
@@ -31,31 +42,66 @@ Since the overall performance of the cluster can be impacted, the LPARs that are
 [discrete]
 == Operating system requirements
 
+ifdef::ibm-z[]
 * One instance of z/VM 7.2 or later
 
 On your z/VM instance, set up:
 
 * Three guest virtual machines for {product-title} control plane machines
 * Two guest virtual machines for {product-title} compute machines
 * One guest virtual machine for the temporary {product-title} bootstrap machine
+endif::ibm-z[]
+ifndef::ibm-z[]
+* Five logical partitions (LPARs)
+** Three LPARs for {product-title} control plane machines
+** Two LPARs for {product-title} compute machines
+* One machine for the temporary {product-title} bootstrap machine
+endif::ibm-z[]
 
 [discrete]
 == {ibm-z-title} network connectivity requirements
 
+ifdef::ibm-z[]
 To install on {ibm-z-name} under z/VM, you require a single z/VM virtual NIC in layer 2 mode. You also need:
 
 *   A direct-attached OSA or RoCE network adapter
 *   A z/VM VSwitch set up. For a preferred setup, use OSA link aggregation.
+endif::ibm-z[]
+ifndef::ibm-z[]
+To install on {ibm-z-name} in an LPAR, you need:
+
+*   A direct-attached OSA or RoCE network adapter
+*   For a preferred setup, use OSA link aggregation.
+endif::ibm-z[]
 
 [discrete]
-=== Disk storage for the z/VM guest virtual machines
+=== Disk storage
+// We might need two headings:
+// === Disk storage for the z/VM guest virtual machines
+// === Disk storage for the LPARs
 
+ifdef::ibm-z[]
 * FICON attached disk storage (DASDs). These can be z/VM minidisks, fullpack minidisks, or dedicated DASDs, all of which must be formatted as CDL, which is the default. To reach the minimum required DASD size for {op-system-first} installations, you need extended address volumes (EAV). If available, use HyperPAV to ensure optimal performance.
 * FCP attached disk storage
+endif::ibm-z[]
+ifndef::ibm-z[]
+* FICON attached disk storage (DASDs). This can be dedicated DASDs that must be formatted as CDL, which is the default. To reach the minimum required DASD size for {op-system-first} installations, you need extended address volumes (EAV). If available, use HyperPAV to ensure optimal performance.
+* FCP attached disk storage
+endif::ibm-z[]
 
 [discrete]
 === Storage / Main Memory
 
 * 16 GB for {product-title} control plane machines
 * 8 GB for {product-title} compute machines
 * 16 GB for the temporary {product-title} bootstrap machine
+
+ifeval::["{context}" == "installing-ibm-z"]
+:!ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-restricted-networks-ibm-z"]
+:!ibm-z:
+endif::[]
+ifeval::["{context}" == "installing-ibm-z-lpar"]
+:!ibm-z-lpar:
+endif::[]