Merge pull request #27386 from openshift-cherrypick-robot/cherry-pick-27298-to-enterprise-4.7

[enterprise-4.7] power ibm z updates

_topic_map.yml

@@ -226,13 +226,13 @@ Topics:
     File: installing-ibm-z
   - Name: Restricted network IBM Z installation
     File: installing-restricted-networks-ibm-z
-- Name: Installing on IBM Power
+- Name: Installing on IBM Power Systems
   Dir: installing_ibm_power
   Distros: openshift-enterprise,openshift-webscale
   Topics:
-  - Name: Installing a cluster on IBM Power
+  - Name: Installing a cluster on IBM Power Systems
     File: installing-ibm-power
-  - Name: Restricted network IBM Power installation
+  - Name: Restricted network IBM Power Systems installation
     File: installing-restricted-networks-ibm-power
 - Name: Installing on OpenStack
   Dir: installing_openstack

installing/installing_ibm_power/installing-ibm-power.adoc

@@ -1,17 +1,17 @@
 [id="installing-ibm-power"]
-= Installing a cluster on IBM Power
+= Installing a cluster on IBM Power Systems
 include::modules/common-attributes.adoc[]
 :context: installing-ibm-power
 
 toc::[]
 
 In {product-title} version {product-version}, you can install a cluster on
-IBM Power infrastructure that you provision.
+IBM Power Systems infrastructure that you provision.
 
 [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.
+link:https://access.redhat.com/articles/4207611[guidelines for deploying {product-title} on non-tested platforms] before you install an {product-title} cluster.
 ====
 
 .Prerequisites
@@ -59,7 +59,7 @@ include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[lev
 [id="creating-machines-bare-metal-power"]
 == Creating {op-system-first} machines
 
-Before you install a cluster on IBM Power infrastructure that you provision,
+Before you install a cluster on IBM Power Systems infrastructure that you provision,
 you must create {op-system} machines for it to use. Follow either the steps
 to use an ISO image or network PXE booting to create the machines.
 

installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc

@@ -1,12 +1,12 @@
 [id="installing-restricted-networks-ibm-power"]
-= Installing a cluster on IBM Power in a restricted network
+= Installing a cluster on IBM Power Systems in a restricted network
 include::modules/common-attributes.adoc[]
 :context: installing-restricted-networks-ibm-power
 
 toc::[]
 
 In {product-title} version {product-version}, you can install a cluster on
-IBM Power infrastructure that you provision in a restricted network.
+IBM Power Systems infrastructure that you provision in a restricted network.
 
 [IMPORTANT]
 ====
@@ -67,7 +67,7 @@ include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[lev
 [id="creating-machines-ibm-power-restricted-network"]
 == Creating {op-system-first} machines
 
-Before you install a cluster on IBM Power infrastructure that you provision,
+Before you install a cluster on IBM Power Systems infrastructure that you provision,
 you must create {op-system} machines for it to use. Follow either the steps
 to use an ISO image or network PXE booting to create the machines.
 

modules/installation-bare-metal-config-yaml.adoc

@@ -30,7 +30,7 @@ ifdef::ibm-z[]
 = Sample `install-config.yaml` file for IBM Z
 endif::ibm-z[]
 ifdef::ibm-power[]
-= Sample `install-config.yaml` file for IBM Power
+= Sample `install-config.yaml` file for IBM Power Systems
 endif::ibm-power[]
 
 You can customize the `install-config.yaml` file to specify more details about
@@ -159,7 +159,7 @@ configure load balancers and routers to manage the traffic.
 configuration variables for
 ifndef::ibm-z,ibm-power[bare metal]
 ifdef::ibm-z[IBM Z]
-ifdef::ibm-power[IBM Power]
+ifdef::ibm-power[IBM Power Systems]
 infrastructure.
 <11> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
 ifndef::restricted[]

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

@@ -53,7 +53,7 @@ The rootfs image is the same for FCP and DASD.
 Example parameter file, `bootstrap-0.parm`, for the bootstrap machine:
 +
 ----
-rd.neednet=1 console=ttysclp0 coreos.inst.install_dev=dasda coreos.inst.image_url=ftp://
+rd.neednet=1 console=ttysclp0 coreos.inst.install_dev=dasda coreos.live.rootf_url=ftp://
 cl1.provide.example.com:8080/assets/rhcos-live-rootfs.s390x.img
 coreos.inst.ignition_url=ftp://cl1.provide.example.com:8080/ignition-bootstrap-0
 ip=172.18.78.2::172.18.78.1:255.255.255.0:::none nameserver=172.18.78.1

modules/installation-requirements-user-infra.adoc

@@ -181,6 +181,7 @@ On your z/VM instances, set up:
 * 3 guest virtual machines for {product-title} control plane machines, one per z/VM instance
 * At least 6 guest virtual machines for {product-title} compute machines, distributed across the z/VM instances
 * 1 guest virtual machine for the temporary {product-title} bootstrap machine
+* To ensure the availability of integral components in an overcommitted environment, increase the priority of the control plane using the CP command `SET SHARE`. Do the same for infrastructure plane machines if they exist. See link:https://www.ibm.com/support/knowledgecenter/en/SSB27U_7.1.0/com.ibm.zvm.v710.hcpb7/setshare.htm[SET SHARE] in the IBM Knowledge Center.
 
 [discrete]
 === Disk storage for the z/VM guest virtual machines

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

@@ -16,7 +16,7 @@ endif::[]
 
 Before you install a cluster on
 ifndef::ibm-power[bare metal]
-ifdef::ibm-power[IBM Power]
+ifdef::ibm-power[IBM Power Systems]
 infrastructure that you provision, you must create
 {op-system} machines for it to use. You can use an ISO image to create the
 machines.

modules/registry-configuring-storage-baremetal.adoc

@@ -29,7 +29,7 @@ ifdef::ibm-z[]
 = Configuring registry storage for IBM Z
 endif::ibm-z[]
 ifdef::ibm-power[]
-= Configuring registry storage for IBM Power
+= Configuring registry storage for IBM Power Systems
 endif::ibm-power[]
 
 As a cluster administrator, following installation you must configure your
@@ -42,7 +42,7 @@ registry to use storage.
 * A cluster on
 ifndef::ibm-z,ibm-power[bare metal.]
 ifdef::ibm-z[IBM Z.]
-ifdef::ibm-power[IBM Power.]
+ifdef::ibm-power[IBM Power Systems.]
 ifndef::ibm-z[* Persistent storage provisioned for your cluster, such as Red Hat OpenShift Container Storage.]
 ifdef::ibm-z[* Persistent storage provisioned for your cluster.]
 +