Changes addressing follow-up PR comments

SNiemann15 · SNiemann15 · commit 92d98c755d0e · 2025-01-16T14:51:00.000+01:00
diff --git a/installing/installing_ibm_z/upi/installing-ibm-z-kvm.adoc b/installing/installing_ibm_z/upi/installing-ibm-z-kvm.adoc
@@ -15,15 +15,9 @@ In {product-title} version {product-version}, you can install a cluster on
 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.
-====
-
+[id="prerequisites-ibm-z-kvm_{context}"]
 == Prerequisites
 
-
 * 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].
@@ -102,9 +96,9 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .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
+* 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 OpenShift4 nodes without SSH].
+* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]
 
 [id="next-steps_ibm-z-kvm"]
 == Next steps
diff --git a/installing/installing_ibm_z/upi/installing-ibm-z-lpar.adoc b/installing/installing_ibm_z/upi/installing-ibm-z-lpar.adoc
@@ -14,12 +14,7 @@ In {product-title} version {product-version}, you can install a cluster in a log
 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.
-====
-
+[id="prerequisites-ibm-z-lpar_{context}"]
 == Prerequisites
 
 * 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].
@@ -84,9 +79,9 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .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
+* 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 OpenShift4 nodes without SSH].
+* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]
 
 [id="next-steps_installing-ibm-z-lpar"]
 == Next steps
diff --git a/installing/installing_ibm_z/upi/installing-ibm-z.adoc b/installing/installing_ibm_z/upi/installing-ibm-z.adoc
@@ -15,12 +15,7 @@ In {product-title} version {product-version}, you can install a cluster on
 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.
-====
-
+[id="prerequisites-ibm-z_{context}"]
 == Prerequisites
 
 * 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].
@@ -35,62 +30,8 @@ link:https://access.redhat.com/articles/4207611[guidelines for deploying {produc
 Be sure to also review this site list if you are configuring a proxy.
 ====
 
-// moved to upi-ibm-z-preparing-to-install include::modules/cluster-entitlements.adoc[leveloffset=+1]
-
-// 4.17 and later Installation requirements in new assembly installing-ibm-z-requirements.adoc
-// [id="installation-requirements-user-infra_{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
-
-//link to 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]
-
-//[role="_additional-resources"]
-//[id="additional-resources_ibmz-requirements"]
-//.Additional resources
-
-//* See link:https://www.ibm.com/docs/en/zvm/latest?topic=networks-bridging-hipersockets-lan-zvm-virtual-switch[Bridging a HiperSockets LAN with a z/VM Virtual Switch] in {ibm-name} Documentation.
-
-//* See link:https://public.dhe.ibm.com/software/dw/linux390/perf/zvm_hpav00.pdf[Scaling HyperPAV alias devices on Linux guests on z/VM] for performance optimization.
-
-//* See link:https://www.vm.ibm.com/library/presentations/lparperf.pdf[Topics in LPAR performance] for LPAR weight management and entitlements.
-
-//link to Recommended host practices for {ibm-z-name} & {ibm-linuxone-name} environments
-
-//include::modules/installation-network-user-infra.adoc[leveloffset=+2]
-
-//[role="_additional-resources"]
-//[id="additional-resources_ibmz-chrony-time-service"]
-//.Additional resources
-
-//link to 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]
 
-// moved to upi-ibm-z-preparing-to-install include::modules/installation-user-provisioned-validating-dns.adoc[leveloffset=+1]
-
-// moved to upi-ibm-z-preparing-to-install include::modules/ssh-agent-using.adoc[leveloffset=+1]
-
-// moved to upi-ibm-z-preparing-to-install include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
-
-// moved to upi-ibm-z-preparing-to-install include::modules/cli-installing-cli.adoc[leveloffset=+1]
-
 include::modules/installation-initializing-manual.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
@@ -139,9 +80,9 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .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
+* 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 OpenShift4 nodes without SSH].
+* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]
 
 [id="next-steps_ibm-z-vm"]
 == Next steps
diff --git a/installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z-kvm.adoc b/installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z-kvm.adoc
@@ -15,12 +15,7 @@ In {product-title} version {product-version}, you can install a cluster on
 While this document refers to only {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.
-====
-
+[id="prerequisites-ibm-z-kvm-restricted_{context}"]
 == Prerequisites
 
 * 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].
@@ -109,7 +104,7 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH].
+* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]
 
 [id="next-steps_ibm-z-kvm-restricted"]
 == Next steps
diff --git a/installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z-lpar.adoc b/installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z-lpar.adoc
@@ -14,12 +14,7 @@ In {product-title} version {product-version}, you can install a cluster in a log
 While this document refers to only {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.
-====
-
+[id="prerequisites-ibm-z-lpar-restricted_{context}"]
 == Prerequisites
 
 * 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].
@@ -42,11 +37,6 @@ Be sure to also review this site list if you are configuring a proxy.
 
 include::modules/installation-about-restricted-network.adoc[leveloffset=+1]
 
-include::modules/minimum-ibm-z-system-requirements.adoc[leveloffset=+2]
-
-[role="_additional-resources"]
-.Additional resources
-
 include::modules/installation-infrastructure-user-infra.adoc[leveloffset=+1]
 
 include::modules/installation-initializing-manual.adoc[leveloffset=+1]
@@ -97,7 +87,7 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH].
+* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]
 
 [id="next-steps_ibm-z-lpar-restricted"]
 == Next steps
diff --git a/installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z.adoc b/installing/installing_ibm_z/upi/installing-restricted-networks-ibm-z.adoc
@@ -15,12 +15,7 @@ In {product-title} version {product-version}, you can install a cluster on
 While this document refers to only {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.
-====
-
+[id="prerequisites-ibm-z-restricted_{context}"]
 == Prerequisites
 
 * 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].
@@ -94,7 +89,7 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH].
+* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]
 
 [id="next-steps_ibm-z-restricted"]
 == Next steps
diff --git a/modules/installation-requirements-ibm-z.adoc b/modules/installation-requirements-ibm-z.adoc
@@ -7,7 +7,7 @@
 // = Minimum resource requirements for cluster installation
 // Do a regular check for changes in modules/installation-minimum-resource-requirements.adoc
 
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="minimum-ibm-z-system-requirements_{context}"]
 = Minimum {ibm-z-title} system environment
 
@@ -62,22 +62,21 @@ The following {ibm-name} hardware is supported with {product-title} version {pro
 2. The {op-system-base} KVM host in your environment must meet certain requirements to host the virtual machines that you plan for the {product-title} environment. See link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/getting-started-with-virtualization-in-rhel-8_configuring-and-managing-virtualization[Getting started with virtualization].
 
 [discrete]
+[id="ibm-z-hardware-requirements_{context}"]
 == Hardware requirements
 
 * The equivalent of six Integrated Facilities for Linux (IFL), which are SMT2 enabled, for each cluster.
 * At least one network connection to both connect to the `LoadBalancer` service and to serve data for traffic outside the cluster.
 
-[NOTE]
-====
-You can use dedicated or shared IFLs to assign sufficient compute resources. Resource sharing is one of the key strengths of {ibm-z-name}. However, you must adjust capacity correctly on each hypervisor layer and ensure sufficient resources for every {product-title} cluster.
-====
-
 [IMPORTANT]
 ====
-Since the overall performance of the cluster can be impacted, the LPARs that are used to set up the {product-title} clusters must provide sufficient compute capacity. In this context, LPAR weight management, entitlements, and CPU shares on the hypervisor level play an important role.
+* You can use dedicated or shared IFLs to assign sufficient compute resources. Resource sharing is one of the key strengths of {ibm-z-name}. However, you must adjust the capacity correctly on each hypervisor layer and ensure that there are sufficient resources for every {product-title} cluster.
+
+* Since the overall performance of the cluster can be impacted, the LPARs that are used to set up the {product-title} clusters must provide sufficient compute capacity. In this context, LPAR weight management, entitlements, and CPU shares on the hypervisor level play an important role. For more information, see "Recommended host practices for {ibm-z-title} & {ibm-linuxone-title} environments".
 ====
 
 [discrete]
+[id="ibm-z-operating-system-requirements_{context}"]
 == {ibm-z-title} operating system requirements
 
 
@@ -113,6 +112,7 @@ Since the overall performance of the cluster can be impacted, the LPARs that are
 |===
 
 [discrete]
+[id="ibm-z-network-connectivity_{context}"]
 == {ibm-z-title} network connectivity
 
 .Network connectivity requirements
@@ -148,6 +148,7 @@ See link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/
 
 
 [discrete]
+[id="ibm-z-disk-storage_{context}"]
 === Disk storage
 
 .Disk storage requirements
diff --git a/modules/preferred-installation-requirements-ibm-z.adoc b/modules/preferred-installation-requirements-ibm-z.adoc
@@ -7,16 +7,17 @@
 // = Minimum resource requirements for cluster installation
 // Do a regular check for changes in modules/installation-minimum-resource-requirements.adoc
 
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="preferred-ibm-z-system-requirements_{context}"]
 = Preferred {ibm-z-title} system environment
 
 The preferred system environment for running {product-title} version {product-version} on {ibm-z-name} hardware is as follows:
 
 [discrete]
+[id="preferred-ibm-z-hardware-requirements_{context}"]
 == Hardware requirements
 
-* Three LPARS that each have the equivalent of six IFLs, which are SMT2 enabled, for each cluster.
+* Three logical partitions (LPARs) that each have the equivalent of six Integrated Facilities for Linux (IFLs), which are SMT2 enabled, for each cluster.
 * Two network connections to both connect to the `LoadBalancer` service and to serve data for traffic outside the cluster.
 * HiperSockets that are attached to a node directly as a device. To directly connect HiperSockets to a node, you must set up a gateway to the external network via a {op-system-base} 8 guest to bridge to the HiperSockets network.
 +
@@ -26,6 +27,7 @@ When installing in a z/VM environment, you can also bridge HiperSockets with one
 ====
 
 [discrete]
+[id="preferred-ibm-z-operating-system-requirements_{context}"]
 == {ibm-z-title} operating system requirements
 
 
@@ -59,6 +61,6 @@ When installing in a z/VM environment, you can also bridge HiperSockets with one
 |One machine
 
 |===
-1.To ensure the availability of integral components in an overcommitted environment, increase the priority of the control plane by using the CP command `SET SHARE`. Do the same for infrastructure nodes, if they exist. See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-set-share[SET SHARE] in {ibm-name} Documentation.
+1. To ensure the availability of integral components in an overcommitted environment, increase the priority of the control plane by using the CP command `SET SHARE`. Do the same for infrastructure nodes, if they exist. See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-set-share[SET SHARE] ({ibm-name} Documentation).
 
 //Alex: Two Infrastructure nodes
