HCIDOCS-651-followup: Oracle Cloud C3 finalizing

Author: Talia Shwartzberg

installing/installing_oci/installing-c3-assisted-installer.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-With {oci-c3} (C3), you can run applications and middleware by using {oci-first} services on high performance cloud infrastructure in your data center. 
+With {oci-c3}, you can run applications and middleware by using {oci-first} services on high performance cloud infrastructure in your data center. 
 
 // Overview
 include::modules/c3-assisted-installer-overview.adoc[leveloffset=+1]
@@ -17,17 +17,11 @@ include::modules/c3-assisted-installer-preparing-bastion-server.adoc[leveloffset
 // Terraform script execution - part 1
 include::modules/c3-assisted-installer-running-script-via-home.adoc[leveloffset=+1]
 
-// Preparing the OpenShift image
-[id="c3-assisted-installer-preparing-image_{context}"]
-== Preparing the {oci} image 
+// Generating the OpenShift image
+include::modules/c3-assisted-installer-preparing-image-generating.adoc[leveloffset=+1]
 
-Generate the {product-title} ISO image in the {ai-full} on the Red{nbsp}Hat portal. Then, convert the image to an {oci-first-no-rt} compatible image and upload it to the *Custom Images* page of your {oci-c3-no-rt} environment. 
-
-You can generate, convert and upload the image on your laptop and not on the bastion server or within environments such as Oracle Solution Center. 
-
-include::modules/c3-assisted-installer-preparing-image-generating.adoc[leveloffset=+2]
-
-include::modules/c3-assisted-installer-preparing-image-converting.adoc[leveloffset=+2]
+// Converting and uploading the image
+include::modules/c3-assisted-installer-preparing-image-converting.adoc[leveloffset=+1]
 
 // Terraform script execution - part 2
 include::modules/c3-assisted-installer-running-script-via-region.adoc[leveloffset=+1]

modules/c3-assisted-installer-completing-installation-manifests.adoc

@@ -20,11 +20,13 @@ Create, modify, and upload the four mandatory custom manifests provided by Oracl
 
 .Prerequisites
 
-* Prepare the custom manifests. For details, see step 8 in the "Install the Cluster using the RH Assisted Installer UI" section of the link:https://www.oracle.com/a/otn/docs/compute_cloud_at_customer_assisted_installer.pdf?source=:em:nl:mt::::PCATP[Oracle documentation].
+* You have prepared the custom manifests. For details, see step 8 in the "Install the Cluster using the RH Assisted Installer UI" section of the link:https://www.oracle.com/a/otn/docs/compute_cloud_at_customer_assisted_installer.pdf?source=:em:nl:mt::::PCATP[Oracle documentation].
+
+* You have added NTP sources to failed hosts on the *Networking* page of the {ai-full} wizard.
 
 .Procedure
 
-. Navigate to the *Custom manifests* page.
+. In the {ai-full} wizard, navigate to the *Custom manifests* page.
 
 . Upload and save the `oci-ccm.yml` and `oci-csi.yml` manifest files:
 
@@ -36,7 +38,7 @@ Create, modify, and upload the four mandatory custom manifests provided by Oracl
 
 .. Select the *oci-ccm.yml* file from the `C3/custom_ manifest_C3/manifests` folder.
 
-.. Click *Add another manifest* and repeat the previous substeps for the `oci-csi.yml` file.
+.. Click *Add another manifest*. Then repeat the previous substeps for the `oci-csi.yml` file.
 
 . Upload and save the `machineconfig-ccm.yml` and `machineconfig-csi.yml` manifest files:
 
@@ -50,7 +52,7 @@ Create, modify, and upload the four mandatory custom manifests provided by Oracl
 
 .. Select the *machineconfig-ccm.yml* file from the `C3/custom_ manifest_C3/openshift` folder.
 
-.. Click *Add another manifest* and repeat the previous substeps for the `machineconfig-csi.yml` file.
+.. Click *Add another manifest*. Then repeat the previous substeps for the `machineconfig-csi.yml` file.
 
 . Click *Next* to save the custom manifests.
 

modules/c3-assisted-installer-completing-installation-networking.adoc

@@ -8,12 +8,18 @@
 
 On the *Networking* page, add the NTP sources for any hosts that display the `Some validations failed` status.
 
+.Prerequisites
+
+. You have deleted the disconnected hosts on the *Host discovery* page of the {ai-full} wizard.
+
 .Procedure
 
+. In the {ai-full} wizard, navigate to the *Networking* page.
+
 . In the *Host inventory* table, click the *Some validations failed* link for each host displaying this status.
 
 . Click *Add NTP sources*, and then add the IP address `169.254.169.254` for one of the nodes. 
 
-. Wait for 2 - 3 minutes until all the *Some validations failed* indicators disappear. 
+. Wait for 2 - 3 minutes until all of the *Some validations failed* indicators disappear. 
 
 . Select *Next*.

modules/c3-assisted-installer-completing-installation-nodes.adoc

@@ -8,17 +8,21 @@
 
 If the Terraform scripts completed successfully, twelve hosts are now listed for the cluster. Three control plane hosts and three compute hosts have the status "Disconnected". Three control plane hosts and three compute hosts have the status "Insufficient". 
 
-Delete the disconnected hosts and assign roles to the remaining hosts. 
+Delete the disconnected hosts and assign roles to the remaining hosts.
+
+.Prerequisites
+
+. You have created all infrastructure resources by running the Terraform script via the {oci-c3-short} region.
 
 .Procedure
 
 . From the link:https://console.redhat.com/openshift/assisted-installer/clusters[{ai-full} web console], select the cluster and navigate to the *Host discovery* page. 
 
-. Delete the six hosts with a "Disconnected" status, by clicking the option button for each host and selecting *Remove host*. The status of the remaining hosts changes from "Insufficient" to "Ready". This process can take up to three minutes.
+. Delete the six hosts with a "Disconnected" status by clicking the option button for each host and selecting *Remove host*. The status of the remaining hosts changes from "Insufficient" to "Ready". This process can take up to three minutes.
 
-. From the *Role* column, assign the *Control plane* role to the three nodes with a boot size of 1.10 TB. Assign the *Worker* role to the three nodes with boot size of 100 GB. 
+. From the *Role* column, assign the *Control plane* role to the three nodes with a boot size of 1.10 TB. Assign the *Worker* role to the three nodes with a boot size of 100 GB. 
 
-. Rename any hosts with a name shorter than 63 characters, by clicking the option button for the host and selecting *Change hostname*. Otherwise the cluster installation will fail. 
+. Rename any hosts with a name shorter than 63 characters by clicking the option button for the host and selecting *Change hostname*. Otherwise the cluster installation will fail. 
 
 . Click *Next*. 
 

modules/c3-assisted-installer-overview.adoc

@@ -6,7 +6,7 @@
 [id="c3-ai-overview_{context}"]
 = Overview
 
-You can install {product-title} on {oci-c3-no-rt} by using the {ai-full}. 
+You can install {product-title} on {oci-c3} by using the {ai-full}. 
 
 For an alternative installation method, see "Installing a cluster on {oci-c3} by using the Agent-based Installer".
 
@@ -32,15 +32,23 @@ The installation process subsequently provisions three control plane (master) no
 
 .Main steps
 
-The main steps of the procedure are as follows:
+The following workflow describes a high-level outline for installing an {product-title} on {oci-c3-short} using the {ai-full}:
 
-. Preparing the {oci-c3-short} bastion server.
+. Prepare the {oci-c3-short} bastion server (Oracle).
 
-. Running the Terraform script via the Home region. 
+. Run the Terraform script via the Home region (Oracle).
 
-. Preparing the {product-title} image for {oci-first-no-rt}. 
+. Generate the {product-title} image in the {ai-full} web console (Red Hat). 
 
-. Running the Terraform script via the {oci-c3-short} region.
+. Convert and upload the image to {oci-first-no-rt} (Oracle).
 
-. Installing the cluster by using the {ai-full} web console.
+. Run the Terraform script via the {oci-c3-short} region (Oracle).
+
+. Complete the cluster installation by using the {ai-full} web console (Red Hat):
+
+.. Assign node roles.
+
+.. Configure networking.
+
+.. Add custom manifests.
 

modules/c3-assisted-installer-preparing-bastion-server.adoc

@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="c3-ai-preparing-bastian-server_{context}"]
-= Preparing the {oci} bastion server
+= Preparing the bastion server in the {oci-first} home region
 
 By implementing a bastion host, you can securely and efficiently manage access to your {oci-c3-no-rt} resources, ensuring that your private instances remain protected and accessible only through a secure, controlled entry point.
 

modules/c3-assisted-installer-preparing-image-converting.adoc

@@ -6,8 +6,11 @@
 [id="c3-assisted-installer-preparing-image-converting_{context}"]
 = Converting and uploading the image to {oci-c3-no-rt}
 
-Convert the ISO image to an {oci} image and upload it to your {oci-c3-short} system from your OCI Home Region Object 
-Store.
+Convert the ISO image to an {oci} image and upload it to your {oci-c3-short} system from your {oci-first} Home Region Object Store. You can perform this step on your laptop, rather than on the bastion server or within environments such as Oracle Solution Center.
+
+.Prerequisites
+
+* You have generated the {product-title} Discovery ISO in the {ai-full} web console, and saved the file to your local system.
 
 .Procedure
 

modules/c3-assisted-installer-preparing-image-generating.adoc

@@ -4,9 +4,13 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="c3-assisted-installer-preparing-image-generating_{context}"]
-= Generating the image in the {ai-full}
+= Generating the image in the Red Hat {ai-full}
 
-Create a cluster and download the discovery ISO image.
+Create a cluster and generate the {product-title} Discovery ISO image in the {ai-full} on the Red{nbsp}Hat portal. You can perform this step on your laptop, rather than on the bastion server or within environments such as Oracle Solution Center.
+
+.Prerequisites
+
+* You have run the `createInfraResources.tf` Terraform script to create the Dynamic Group Identity resources on your {oci-first-no-rt} Home region.
 
 .Procedure
 
@@ -27,10 +31,10 @@ Create a cluster and download the discovery ISO image.
 |Field |Action required
 
 |*Cluster name*
-|Specify the name of your {product-title} cluster. This name is the same name you used to create the resource via the Terraform scripts. The name must be between 1-54 characters. It can use lowercase alphanumeric characters or hyphen (-), but must start and end with a lowercase letter or a number.
+|Specify the name of your {product-title} cluster. This name is the same name you used to create the resource via the Terraform scripts. The name must be between 1-54 characters. It can use lowercase alphanumeric characters and hyphens (-), but must start and end with a lowercase letter or a number.
 
 |*Base domain*
-|Specify the base domain of the cluster. This is the value used for the `zone_dns` variables in the Terraform scripts that run on {oci-c3-short}. Make a note of the value.
+|Specify the base domain of the cluster. This is the value used for the `zone_dns` variables in the Terraform scripts that run on {oci-c3-short}. Make a note of the value for later use.
 
 |*OpenShift version*
 | Select *OpenShift 4.16.20*. If it is not immediately visible, scroll to the end of the dropdown menu, select *Show all available versions*, and type the version in the search box.
@@ -52,19 +56,21 @@ After you specify this value, the *Include custom manifests* checkbox is selecte
 The minimal ISO image is the mandatory *Provisioning type* for the {oci-first-no-rt}, and cannot be changed.
 ====
 
-.. In the *SSH public key* field, add the SSH public key by copying the output of the following command: 
+.. Create the SSH public key by running the following command:
 +
 [source,terminal]
 ----
 $ cat ~/.ssh/id_rsa.put
 ----
-+
-The SSH public key will be installed on all {product-title} control plane and compute nodes.
+
+.. Copy the output from the previous step into the *SSH public key* field. The SSH public key will be installed on all {product-title} control plane and compute nodes.
 
 .. Click the *Show proxy settings* checkbox.
 
 .. Add the proxy variables from the `/etc/environment` file of the bastion server that you configured earlier:
 +
+.Proxy variables
++
 [source,terminal]
 ----
 http_proxy=http://www-proxy.<your_domain>.com:80 
@@ -73,6 +79,6 @@ no_proxy=localhost,127.0.0.1,1,2,3,4,5,6,7,8,9,0,.<your_domain>.com
 #(ie.oracle.com,.oraclecorp.com) 
 ---- 
 
-.. Click *Generate Discovery ISO* to generate the discovery ISO image file.
+.. Click *Generate Discovery ISO* to generate the Discovery ISO image file.
 
-. Click *Download Discovery ISO* to save the file to your local system. After you download the ISO file, you can rename it as required, for example `discovery_image_<your_cluster_name>.iso`.
+. Click *Download Discovery ISO* to save the file to your local system. After you download the Discovery ISO file, you can rename it as required, for example `discovery_image_<your_cluster_name>.iso`.

modules/c3-assisted-installer-running-script-via-home.adoc

@@ -4,12 +4,14 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="c3-ai-running-script-via-home_{context}"]
-= Running the Terraform script via the Home region
+= Running the Terraform script via the {oci-first-no-rt} Home region
 
-Copy the Terraform scripts `createInfraResources.tf` and `terraform.tfvars` onto the bastion server. Then run the `createInfraResources.tf` script to create the Dynamic Group Identity resources on your {oci-c3-short} {oci} Home Region. These resources include dynamic groups, policies, and tags.
+Copy the Terraform scripts `createInfraResources.tf` and `terraform.tfvars` onto the bastion server. Then run the `createInfraResources.tf` script to create the Dynamic Group Identity resources on your {oci-first-no-rt} Home region. These resources include dynamic groups, policies, and tags.
 
 .Prerequisites
 
+* You have prepared the bastion server in the {oci-first-no-rt} home region.
+
 * You have tenancy privileges to create Dynamic Groups and Policies. If not, you can manually provision them during this procedure.
 
 .Procedure
@@ -20,7 +22,7 @@ Copy the Terraform scripts `createInfraResources.tf` and `terraform.tfvars` onto
 
 . Copy the `createInfraResources.tf` and `terraform.tfvars` files from the C3_PCA GitHub repository into the `createResourceOnHomeRegion` folder.
 
-. Ensure that you have access to the source environment, and that your C3 certificate has been exported.
+. Ensure that you have access to the source environment, and that your {oci-c3-short} certificate has been exported.
 
 . Run the `createInfraResources.tf` Terraform script.
 

modules/c3-assisted-installer-running-script-via-region.adoc

@@ -4,17 +4,21 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="c3-ai-running-script-via-region_{context}"]
-= Running the Terraform script via the C3 region
+= Running the Terraform script via the {oci-c3-short} region
 
 Run the `terraform.tfvars` Terraform script to create all infrastructure resources on {oci-c3-short}. These resources include the {product-title} VCN, public and private subnets, load balancers, internet GW, NAT GW, and DNS server.
 
 This procedure deploys a cluster consisting of three control plane (master) and three compute (worker) nodes. After deployment, you must rename and reboot the nodes. This process temporarily duplicates nodes, requiring manual cleanup in the next procedure.
 
+.Prerequisites
+
+* You have converted and uploaded the image to {oci-first-no-rt}.
+
 .Procedure
 
 . Connect to the bastion server via SSH.
 
-. Set the C3 Certificate location and export the certificate. 
+. Set the {oci-c3-short} Certificate location and export the certificate. 
 
 . Run the `terraform.tfvars` script to create three control plane nodes and three compute nodes.