Merge pull request #70553 from alishaIBM/4.15-install-doc

OCP 4.15 Installation doc updates for IBM Power

Author: jab-rh

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

@@ -218,8 +218,13 @@ endif::restricted[]
 ----
 <1> The base domain of the cluster. All DNS records must be sub-domains of this base and include the cluster name.
 <2> The `controlPlane` section is a single mapping, but the `compute` section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the `compute` section must begin with a hyphen, `-`, and the first line of the `controlPlane` section must not. Only one control plane pool is used.
+ifndef::ibm-power[]
 <3> Specifies whether to enable or disable simultaneous multithreading (SMT), or hyperthreading. By default, SMT is enabled to increase the performance of the cores in your machines. You can disable it by setting the parameter value to `Disabled`. If you disable SMT, you must disable it in all cluster machines; this includes both control plane and compute machines.
-ifndef::ibm-z,ibm-z-kvm[]
+endif::ibm-power[]
+ifdef::ibm-power[]
+<3> Simultaneous multithreading (SMT) is not supported.
+endif::ibm-power[]
+ifndef::ibm-z,ibm-z-kvm,ibm-power[]
 +
 [NOTE]
 ====
@@ -230,7 +235,7 @@ Simultaneous multithreading (SMT) is enabled by default. If SMT is not enabled i
 ====
 If you disable `hyperthreading`, whether in the BIOS or in the `install-config.yaml` file, ensure that your capacity planning accounts for the dramatically decreased machine performance.
 ====
-endif::ibm-z,ibm-z-kvm[]
+endif::ibm-z,ibm-z-kvm,ibm-power[]
 ifdef::ibm-z,ibm-z-kvm[]
 +
 [NOTE]

modules/installation-load-balancing-user-infra.adoc

@@ -181,31 +181,31 @@ listen api-server-6443 <1>
   bind *:6443
   mode tcp
   server bootstrap bootstrap.ocp4.example.com:6443 check inter 1s backup <2>
-  server master0 master0.ocp4.example.com:6443 check inter 1s
-  server master1 master1.ocp4.example.com:6443 check inter 1s
-  server master2 master2.ocp4.example.com:6443 check inter 1s
+  server control-plane0 control-plane0.ocp4.example.com:6443 check inter 1s
+  server control-plane1 control-plane1.ocp4.example.com:6443 check inter 1s
+  server control-plane2 control-plane2.ocp4.example.com:6443 check inter 1s
 listen machine-config-server-22623 <3>
   bind *:22623
   mode tcp
   option  httpchk GET /readyz HTTP/1.0
   option  log-health-checks
   balance roundrobin
   server bootstrap bootstrap.ocp4.example.com:6443 verify none check check-ssl inter 10s fall 2 rise 3 backup <2>
-  server master0 master0.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3
-  server master1 master1.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3
-  server master2 master2.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3
+  server control-plane0 control-plane0.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3
+  server control-plane1 control-plane1.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3
+  server control-plane2 control-plane2.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3
 listen ingress-router-443 <4>
   bind *:443
   mode tcp
   balance source
-  server worker0 worker0.ocp4.example.com:443 check inter 1s
-  server worker1 worker1.ocp4.example.com:443 check inter 1s
+  server compute0 compute0.ocp4.example.com:443 check inter 1s
+  server compute1 compute1.ocp4.example.com:443 check inter 1s
 listen ingress-router-80 <5>
   bind *:80
   mode tcp
   balance source
-  server worker0 worker0.ocp4.example.com:80 check inter 1s
-  server worker1 worker1.ocp4.example.com:80 check inter 1s
+  server compute0 compute0.ocp4.example.com:80 check inter 1s
+  server compute1 compute1.ocp4.example.com:80 check inter 1s
 ----
 
 <1> Port `6443` handles the Kubernetes API traffic and points to the control plane machines.

modules/installation-user-infra-machines-static-network.adoc

@@ -293,7 +293,12 @@ Optional: You can bond multiple SR-IOV network interfaces to a dual port NIC int
 
 On each node, you must perform the following tasks:
 
+ifndef::installing-ibm-power[]
 . Create the SR-IOV virtual functions (VFs) following the guidance in link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/managing-virtual-devices_configuring-and-managing-virtualization#managing-sr-iov-devices_managing-virtual-devices[Managing SR-IOV devices]. Follow the procedure in the "Attaching SR-IOV networking devices to virtual machines" section.
+endif::installing-ibm-power[]
+ifdef::installing-ibm-power[]
+. Create the SR-IOV virtual functions (VFs).
+endif::installing-ibm-power[]
 
 . Create the bond, attach the desired VFs to the bond and set the bond link state up following the guidance in link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/configuring-network-bonding_configuring-and-managing-networking[Configuring network bonding]. Follow any of the described procedures to create the bond.
 

modules/nw-operator-cr.adoc

@@ -347,6 +347,10 @@ defaultNetwork:
     genevePort: 6081
     ipsecConfig: {}
 ----
+[IMPORTANT]
+====
+Using OVNKubernetes can lead to a stack exhaustion problem on {ibm-power-name}.
+====
 
 [discrete]
 [id="nw-operator-cr-kubeproxyconfig_{context}"]

modules/recommended-ibm-power-system-requirements.adoc

@@ -32,7 +32,7 @@ On your {ibm-power-name} instance, set up:
 == Network for the PowerVM guest virtual machines
 
 * Dedicated physical adapter, or SR-IOV virtual function
-* Available by the Virtual I/O Server using Shared Ethernet Adapter
+* Virtualized by the Virtual I/O Server using Shared Ethernet Adapter
 * Virtualized by the Virtual I/O Server using {ibm-name} vNIC
 
 [discrete]