[OSDOCS-17003] IBM Z CQA work

installing/installing_ibm_z/ibmz-post-install.adoc

@@ -6,14 +6,15 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 After installing {product-title}, you can configure additional devices for your cluster in an {ibm-z-name} or {ibm-linuxone-name} environment, which is installed with z/VM. The following devices can be configured:
 
 * Fibre Channel Protocol (FCP) host
 * FCP LUN
 * DASD
 * qeth
 
-You can configure devices by adding udev rules using the Machine Config Operator (MCO) or you can configure devices manually.
+You can configure devices by adding udev rules by using the Machine Config Operator (MCO) or you can configure devices manually.
 
 [NOTE]
 ====
@@ -27,7 +28,8 @@ The procedures described here apply only to z/VM installations. If you have inst
 
 include::modules/ibm-z-configure-devices-mco.adoc[leveloffset=+1]
 
-.Next steps
+[role="_additional-resources"]
+.Additional resources
 
 * xref:../../storage/persistent_storage_local/persistent-storage-local.adoc#persistent-storage-using-local-volume[Install and configure the Local Storage Operator]
 * xref:../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#k8s-nmstate-updating-node-network-config[Observing and updating the node network state and configuration]
@@ -37,17 +39,16 @@ include::modules/ibm-z-configure-devices-manually.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* link:https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev[chzdev - Configure {ibm-z-name} devices] ({ibm-name} Documentation)
+* link:https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev[chzdev - Configure {ibm-z-name} devices ({ibm-name} Documentation)]
 
-* link:https://www.ibm.com/docs/en/linux-on-systems?topic=linuxonibm/com.ibm.linux.z.ludd/ludd_c_perscfg.html[Persistent device configuration] ({ibm-name} Documentation)
+* link:https://www.ibm.com/docs/en/linux-on-systems?topic=linuxonibm/com.ibm.linux.z.ludd/ludd_c_perscfg.html[Persistent device configuration ({ibm-name} Documentation)]
 
-[id="roce-network-cards"]
-== RoCE network Cards
-RoCE (RDMA over Converged Ethernet) network cards do not need to be enabled and their interfaces can be configured with the Kubernetes NMState Operator whenever they are available in the node. For example, RoCE network cards are available if they are attached in a z/VM environment or passed through in a {op-system-base} KVM environment.
+include::modules/ibm-z-roce-network-cards.adoc[leveloffset=+1]
 
 include::modules/ibm-z-enable-multipathing-fcp-luns.adoc[leveloffset=+1]
 
-.Next steps
+[role="_additional-resources"]
+.Additional resources
 
 * xref:../../storage/persistent_storage_local/persistent-storage-local.adoc#persistent-storage-using-local-volume[Install and configure the Local Storage Operator]
 * xref:../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#k8s-nmstate-updating-node-network-config[Observing and updating the node network state and configuration]

installing/installing_ibm_z/installation-config-parameters-ibm-z.adoc

@@ -7,6 +7,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 Before you deploy an {product-title} cluster, you provide a customized `install-config.yaml` installation configuration file that describes the details for your environment.
 
 [NOTE]

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

@@ -6,7 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-You can install an {product-title} cluster on {ibm-z-name} and {ibm-linuxone-name} using a variety of different installation methods.
+[role="_abstract"]
+You can install an {product-title} cluster on {ibm-z-name} and {ibm-linuxone-name} by using a variety of different installation methods.
 Each method has qualities that can make them more suitable for different use cases, such as installing a cluster in a disconnected environment or installing a cluster with minimal configuration and provisioning.
 
 //moved prerequisites to ibm z cluster installation assemblies zvm, lpar, kvm
@@ -21,9 +22,9 @@ While this document refers only to {ibm-z-name}, all information in it also appl
 
 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}.
+* *Interactive*: You can deploy a cluster with the web-based {ai-full}. This method requires no setup for the installation program, and is ideal for connected environments such as {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]. 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 disconnected networks.
+* *Local Agent-based*: You can deploy a cluster locally with the Agent-based Installer. It provides many of the benefits of the {ai-full}, but you must download and configure the Agent-based Installer first. Configuration is done with a command-line interface (CLI). This approach is ideal for disconnected networks.
 
 * *Full control*: You can deploy a cluster on infrastructure that you prepare and maintain, which provides maximum customizability. You can deploy clusters in connected or disconnected environments.
 
@@ -36,31 +37,31 @@ The {product-title} installation program offers the following methods for deploy
 |{ibm-z-name} with z/VM
 |✓
 |✓
-|xref:../../installing/installing_ibm_z/upi/installing-ibm-z.adoc#installing-ibm-z[✓]
+|✓
 |
 
 |Restricted network {ibm-z-name} with z/VM
 |
 |✓
-|xref:../../installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[✓]
+|✓
 |
 
 |{ibm-z-name} with {op-system-base} KVM
 |✓
 |✓
-|xref:../../installing/installing_ibm_z/upi/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[✓]
+|✓
 |
 
 |Restricted network {ibm-z-name} with {op-system-base} KVM
 |
 |✓
-|xref:../../installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[✓]
+|✓
 |
 
 |{ibm-z-name} in an LPAR
 |✓
 |✓
-|xref:../../installing/installing_ibm_z/upi/installing-ibm-z-lpar.adoc#installing-ibm-z-lpar[✓]
+|✓
 |
 
 |Restricted network {ibm-z-name} in an LPAR
@@ -70,7 +71,7 @@ The {product-title} installation program offers the following methods for deploy
 |
 |===
 
-For more information about the installation process, see the xref:../../architecture/architecture-installation.adoc#installation-process_architecture-installation[Installation process].
+For more information about the installation process, see Installation process in the Additional resources section.
 
 == User-provisioned infrastructure installation of {product-title} on {ibm-z-title}
 
@@ -81,14 +82,38 @@ User-provisioned infrastructure requires the user to provision all resources req
 The steps for performing a user-provisioned infrastructure installation are provided as an example only. Installing a cluster with infrastructure you provide requires knowledge of the {ibm-z-name} platform and the installation process of {product-title}. Use the user-provisioned infrastructure installation instructions as a guide; you are free to create the required resources through other methods.
 ====
 
-* **xref:../../installing/installing_ibm_z/upi/installing-ibm-z.adoc#installing-ibm-z[Installing a cluster with z/VM on {ibm-z-name} and {ibm-linuxone-name}]**: You can install {product-title} with z/VM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
+* *Installing a cluster with z/VM on {ibm-z-name} and {ibm-linuxone-name}*: You can install {product-title} with z/VM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
+
+* *Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title} in a disconnected environment*: You can install {product-title} with z/VM 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.
+
+* *Installing a cluster with {op-system-base} 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.
+
+* *Installing a cluster with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name} in a disconnected environment*: 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.
+
+* *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.
+
+* *Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name} in a disconnected environment*: You can install {product-title} in an LPAR 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.
+
+[role="_additional-resources"]
+[id="additional-resources_{context}"]
+== Additional resources
+
+* link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform[{ai-full}]
+
+* xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#preparing-to-install-with-agent-based-installer[Preparing to install with the Agent-based Installer]
+
+* link:https://console.redhat.com/openshift/install/ibmz/agent-based[Agent-based Installer for {ibm-z-name}]
+
+* xref:../../architecture/architecture-installation.adoc#installation-process_architecture-installation[Installation process]
+
+* xref:../../installing/installing_ibm_z/upi/installing-ibm-z.adoc#installing-ibm-z[Installing a cluster with z/VM on {ibm-z-name} and {ibm-linuxone-name}]
 
-* **xref:../../installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title} in a disconnected environment]**: You can install {product-title} with z/VM 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/upi/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title} in a disconnected environment]
 
-* **xref:../../installing/installing_ibm_z/upi/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/upi/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[Installing a cluster with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name}]
 
-* **xref:../../installing/installing_ibm_z/upi/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 disconnected environment]**: 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/upi/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 disconnected environment]
 
-* **xref:../../installing/installing_ibm_z/upi/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.
+* xref:../../installing/installing_ibm_z/upi/installing-ibm-z-lpar.adoc#installing-ibm-z-lpar[Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name}]
 
-* **xref:../../installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z-lpar.adoc#installing-restricted-networks-ibm-z-lpar[Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name} in a disconnected environment]**: You can install {product-title} in an LPAR 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/upi/installing-restricted-networks-ibm-z-lpar.adoc#installing-restricted-networks-ibm-z-lpar[Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name} in a disconnected environment]

installing/installing_ibm_z/upi/installing-ibm-z-kvm.adoc

@@ -7,29 +7,22 @@ include::_attributes/common-attributes.adoc[]
 toc::[]
 
 [role="_abstract"]
-In {product-title} version {product-version}, you can install a cluster on
-{ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
+In {product-title} version {product-version}, you can install a cluster 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}.
 ====
 
-[id="prerequisites-ibm-z-kvm_{context}"]
-== Prerequisites
+include::modules/prereqs-ibm-z-kvm-upi.adoc[leveloffset=+1]
 
-* You have completed the tasks in xref:../../../installing/installing_ibm_z/upi/upi-ibm-z-preparing-to-install.adoc#upi-ibm-z-preparing-to-install[Preparing to install a cluster on {ibm-z-title} using user-provisioned infrastructure].
-* 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/overview/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-module_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.
-====
-* You provisioned a {op-system-base} Kernel Virtual Machine (KVM) system that is hosted on the logical partition (LPAR) and based on {op-system-base} 8.6 or later. See link:https://access.redhat.com/support/policy/updates/errata#RHEL8_and_9_Life_Cycle[Red Hat Enterprise Linux 8 and 9 Life Cycle].
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../installing/installing_ibm_z/upi/upi-ibm-z-preparing-to-install.adoc#upi-ibm-z-preparing-to-install[Preparing to install a cluster on {ibm-z-title} using user-provisioned infrastructure]
+* xref:../../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
+* xref:../../../installing/overview/installing-preparing.adoc#installing-preparing[Selecting a cluster installation method and preparing it for users]
+* xref:../../../storage/persistent_storage/persistent-storage-ocs.adoc#persistent-storage-ocs[Persistent storage using {rh-storage}]
+* xref:../../../installing/install_config/configuring-firewall.adoc#configuring-firewall-module_configuring-firewall[Configuring your firewall]
 
 include::modules/installation-infrastructure-user-infra.adoc[leveloffset=+1]
 
@@ -119,15 +112,13 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
 include::modules/cluster-telemetry.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
-.Additional resources
+[id="additional-resources_{context}"]
+== Additional resources
 
 * xref:../../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring]
 
 * link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]
 
 * xref:../../../support/remote_health_monitoring/remote-health-reporting.adoc#remote-health-reporting[Remote health reporting]
 
-[id="next-steps_ibm-z-kvm"]
-== Next steps
-
 * xref:../../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster]