Merge pull request #49290 from tmulquee/BZ1979956

BZ1979956: review terminology of provisioning

Author: abrennan89

images/210_OpenShift_Baremetal_IPI_Deployment_updates_0122_1.png

@@ -4,19 +4,25 @@
 include::_attributes/common-attributes.adoc[]
 :context: ipi-install
 
-Installer-provisioned installation provides support for installing {product-title} on bare metal nodes. This guide provides a methodology to achieving a successful installation.
-
-During installer-provisioned installation on bare metal, the installation program on the bare metal node labeled as `provisioner` creates a bootstrap virtual machine (VM). The role of the bootstrap VM is to assist in the process of deploying an {product-title} cluster. The bootstrap VM connects to the `baremetal` network and to the `provisioning` network, if present, via the network bridges.
+Installer-provisioned installation on bare metal nodes deploys and configures the infrastructure that a {product-title} cluster runs on. This guide provides a methodology to achieving a successful installer-provisioned bare-metal installation. The following diagram illustrates the installation environment in phase 1 of deployment.
 
 image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_1.png[Deployment phase one]
 
-The provisioning node can be removed after the installation.
+For the installation, the key elements in the previous diagram are:
+
+- **Provisioner**: A physical machine that runs the installation program and hosts the bootstrap VM that deploys the controller of a new {product-title} cluster.
+- **Bootstrap VM**: A virtual machine that assists in the process of deploying an {product-title} cluster.
+- **Network bridges**: The bootstrap VM connects to the bare-metal network and to the provisioning network, if present, via network bridges, `eno1` and `eno2`.
+
+In phase 2 of the deployment, the provisioner destroys the bootstrap VM automatically and moves the virtual IP addresses (VIPs) to the appropriate nodes. The API VIP moves to the control plane nodes and the Ingress VIP moves to the worker nodes.
 
-When the installation of {product-title} is complete and fully operational, the installation program destroys the bootstrap VM automatically and moves the virtual IP addresses (VIPs) to the appropriate nodes accordingly. The API VIP moves to the control plane nodes and the Ingress VIP moves to the worker nodes.
+The following diagram illustrates phase 2 of deployment.
 
 image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_2.png[Deployment phase two]
 
+After this point, the node used by the provisioner can be removed or repurposed. From here, all additional provisioning tasks are carried out by controllers.
+
 [IMPORTANT]
 ====
-The `provisioning` network is optional, but it is required for PXE booting. If you deploy without a `provisioning` network, you must use a virtual media BMC addressing option such as `redfish-virtualmedia` or `idrac-virtualmedia`.
-====
+The provisioning network is optional, but it is required for PXE booting. If you deploy without a provisioning network, you must use a virtual media baseboard management controller (BMC) addressing option such as `redfish-virtualmedia` or `idrac-virtualmedia`.
+====

images/210_OpenShift_Baremetal_IPI_Deployment_updates_0122_2.png

@@ -8,14 +8,14 @@ toc::[]
 
 Installer-provisioned installation of {product-title} requires:
 
-ifdef::openshift-origin[. One provisioner node with {op-system-first} installed. The provisioning node can be removed after installation.]
-ifndef::openshift-origin[. One provisioner node with {op-system-base-full} 8.x installed. The provisioning node can be removed after installation.]
-. Three control plane nodes.
-. Baseboard management controller (BMC) access to each node.
+ifdef::openshift-origin[. One provisioner node with {op-system-first} installed. The provisioner can be removed after installation.]
+ifndef::openshift-origin[. One provisioner node with {op-system-base-full} 8.x installed. The provisioner can be removed after installation.]
+. Three control plane nodes
+. Baseboard management controller (BMC) access to each node
 . At least one network:
 .. One required routable network
-.. One optional network for provisioning nodes; and,
-.. One optional management network.
+.. One optional provisioning network
+.. One optional management network
 
 Before starting an installer-provisioned installation of {product-title}, ensure the hardware environment meets the following requirements.
 

installing/installing_bare_metal_ipi/ipi-install-overview.adoc

@@ -10,15 +10,15 @@ You can use installer-provisioned installation to install {product-title} on IBM
 
 [IMPORTANT]
 ====
-Red Hat supports IPMI and PXE on the `provisioning` network only. Red Hat has not tested Red Fish, virtual media, or other complementary technologies such as Secure Boot on IBM Cloud deployments. The `provisioning` network is required.
+Red Hat supports IPMI and PXE on the provisioning network only. Red Hat has not tested Red Fish, virtual media, or other complementary technologies such as Secure Boot on IBM Cloud deployments. A provisioning network is required.
 ====
 
 Installer-provisioned installation of {product-title} requires:
 
-* One provisioner node with {op-system-first} 8.x installed
+* One node with {op-system-first} 8.x installed, for running the provisioner
 * Three control plane nodes
 * One routable network
-* One network for provisioning nodes
+* One provisioning network
 
 Before starting an installer-provisioned installation of {product-title} on IBM Cloud, address the following prerequisites and requirements.
 

installing/installing_bare_metal_ipi/ipi-install-prerequisites.adoc

@@ -161,4 +161,4 @@ You can reconfigure the control plane nodes to act as NTP servers on disconnecte
 [id='network-requirements-out-of-band_{context}']
 == Port access for the out-of-band management IP address
 
-The out-of-band management IP address is on a separate network from the node. To ensure that the out-of-band management can communicate with the provisioning node during installation, the out-of-band management IP address must be granted access to port `80` on the bootstrap host and port `6180` on the {product-title} control plane hosts.
+The out-of-band management IP address is on a separate network from the node. To ensure that the out-of-band management can communicate with the provisioner during installation, the out-of-band management IP address must be granted access to port `80` on the bootstrap host and port `6180` on the {product-title} control plane hosts.

installing/installing_ibm_cloud/install-ibm-cloud-prerequisites.adoc

@@ -94,13 +94,13 @@ $ ssh [email protected]
 
 If you are not successful logging in to the bootstrap VM, you have likely encountered one of the following scenarios:
 
-* You cannot reach the `172.22.0.0/24` network. Verify network connectivity on the provisioner host specifically around the `provisioning` network bridge. This will not be the issue if you are not using the `provisioning` network.
-
+* You cannot reach the `172.22.0.0/24` network. Verify the network connectivity between the provisioner and the `provisioning` network bridge. This issue may occur if you are using a `provisioning` network.
+`
 * You cannot reach the bootstrap VM through the public network. When attempting
 to SSH via `baremetal` network, verify connectivity on the
 `provisioner` host specifically around the `baremetal` network bridge.
 
 * You encountered `Permission denied (publickey,password,keyboard-interactive)`. When
 attempting to access the bootstrap VM, a `Permission denied` error
 might occur. Verify that the SSH key for the user attempting to log
-into the VM is set within the `install-config.yaml` file.
+in to the VM is set within the `install-config.yaml` file.

modules/ipi-install-network-requirements.adoc

@@ -9,7 +9,7 @@
 [role="_abstract"]
 The {product-title} installation completes when the following installation health checks are successful:
 
-* The provisioning host can access the {product-title} web console.
+* The provisioner can access the {product-title} web console.
 
 * All control plane nodes are ready.
 
@@ -18,9 +18,9 @@ The {product-title} installation completes when the following installation healt
 [NOTE]
 ====
 After the installation completes, the specific cluster Operators responsible for the worker nodes continuously attempt to provision all worker nodes. It can take some time before all worker nodes report as `READY`. For installations on bare metal, wait a minimum of 60 minutes before troubleshooting a worker node. For installations on all other platforms, wait a minimum of 40 minutes before troubleshooting a worker node. A `DEGRADED` state for the cluster Operators responsible for the worker nodes depends on the Operators' own resources and not on the state of the nodes.
-==== 
+====
 
-After your installation completes, you can continue to monitor the condition of the nodes in your cluster using the following steps. 
+After your installation completes, you can continue to monitor the condition of the nodes in your cluster by using the following steps.
 
 .Prerequisites
 * The installation program resolves successfully in the terminal.
@@ -67,4 +67,4 @@ openshift-machine-api   example-zbbt6-worker-0-25bhp   Running
 openshift-machine-api   example-zbbt6-worker-0-8b4c2   Running                              49m
 openshift-machine-api   example-zbbt6-worker-0-jkbqt   Running                              49m
 openshift-machine-api   example-zbbt6-worker-0-qrl5b   Running                              49m
-----
+----