OSDOCS-8210: Crated an OCI doc book for the AI install route

Author: dfitzmau

_attributes/common-attributes.adoc

@@ -244,8 +244,10 @@ endif::[]
 :vmw-full: VMware vSphere
 :vmw-short: vSphere
 //Oracle
-:oci-first: Oracle(R) Cloud Infrastructure
+:oci-first: Oracle(R) Cloud Infrastructure (OCI)
 :oci: OCI
+:ocid-first: Oracle(R) Cloud Identifier (OCID)
+:ocid: OCID
 :ocvs-first: Oracle(R) Cloud VMware Solution (OCVS)
 :ocvs: OCVS
 // Cluster Observability Operator

_topic_maps/_topic_map.yml

@@ -459,6 +459,12 @@ Topics:
     File: uninstalling-openstack-user
   - Name: Installation configuration parameters for OpenStack
     File: installation-config-parameters-openstack
+- Name: Installing on OCI
+  Dir: installing_oci
+  Distros: openshift-origin,openshift-enterprise
+# Topics:
+#  - Name: Using the Assisted Installer to install a cluster on OCI
+#  - File: installing-oci-assisted-installer
 - Name: Installing on vSphere
   Dir: installing_vsphere
   Distros: openshift-origin,openshift-enterprise

images/ingress_load_balancer_warning_message.png

@@ -0,0 +1 @@
+../../_attributes/

installing/installing_oci/_attributes

@@ -0,0 +1 @@
+../../images

installing/installing_oci/images

@@ -0,0 +1,34 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="installing-oci-assisted-installer"]
+= Using the Assisted Installer to install a cluster on OCI
+include::_attributes/common-attributes.adoc[]
+:context: installing-oci-assisted-installer
+
+toc::[]
+
+In {product-title} {product-version}, you can use the Assisted Installer to install a cluster on {oci-first} by using infrastructure that you provide.
+
+// The Assisted Installer and OCI overview
+//include::modules/installing-oci-about-assisted-installer.adoc[leveloffset=+1]
+////
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../installing/installing_platform_agnostic/installing-platform-agnostic.html#cluster-entitlements_installing-platform-agnostic[Internet access for {product-title}]
+* xref:../../installing/installing_on_prem_assisted/installing-on-prem-assisted.html#using-the-assisted-installer_installing-on-prem-assisted[Using the Assisted Installer]
+
+// Using the Assisted Installer to install a cluster on OCI
+include::modules/installing-using-assisted-installer-oci.adoc[leveloffset=+1]
+
+// Troubleshooting installation of a cluster on OCI
+include::modules/installing-troubleshooting-assisted-installer-oci.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../installing/installing_on_prem_assisted/installing-on-prem-assisted.adoc[Installing an on-premise cluster using the Assisted Installer]
+* link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform/2022/html-single/assisted_installer_for_openshift_container_platform/index[Assisted Installer for {product-title}]
+//* link:https://access.redhat.com/node/7038262[Using the Agent-based Installer to install a cluster on OCI]
+* link:https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Concepts/resourcemanager.htm#ariaid-title6[Ways to access Resource Manager]
+* [Creating a stack](https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Tasks/create-stack.htm#top) in the Oracle documentation.
+////

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

@@ -0,0 +1 @@
+../../modules/

installing/installing_oci/modules

@@ -0,0 +1 @@
+../../snippets/

installing/installing_oci/snippets

@@ -0,0 +1,24 @@
+// Module included in the following assemblies:
+//
+// * installing/installing_oci/installing-oci-assisted-installer.adoc [Using the Assisted Installer to install a cluster on OCI]
+
+:_mod-docs-content-type: CONCEPT
+[id="installing-oci-about-assisted-installer_{context}"]
+= The Assisted Installer and OCI overview
+
+From {product-title} {product-version} and later versions, you can install an {product-title} cluster on {oci-first} virtual machines (VMs) by using the Assisted Installer. You can run cluster workloads on infrastructure that supports dedicated, hybrid, public, and multiple cloud environments. Both Red Hat and Oracle test, validate, and supports running {oci} in an {product-title} cluster on {oci}.
+
+{oci} provides services that can meet your needs for regulatory compliance and performance and cost-effectiveness.
+
+[IMPORTANT]
+====
+To ensure the best performance conditions for your cluster workloads that operate on {oci}, ensure volume performance units (VPUs) for your block volume are sized for your workloads. The following list provides guidance for selecting the VPUs needed for specific performance needs:
+
+* Test or proof of concept environment: 100 GB, and 20 to 30 VPUs.
+* Basic environment: 500 GB, and 60 VPUs.
+* Heavy production environment: More than 500 GB, and 100 or more VPUs.
+
+Consider reserving additional VPUs to provide sufficient capacity for updates and scaling activities. For more information about VPUs, see Volume Performance Units in the Oracle documentation.
+====
+
+If you are unfamiliar with the {product-title} Assisted Installer, go to the links in the following _Additional resources_ section.

modules/installing-oci-about-assisted-installer.adoc

@@ -0,0 +1,31 @@
+// Module included in the following assemblies:
+//
+// * installing/installing_oci/installing-oci-assisted-installer.adoc [Using the Assisted Installer to install a cluster on OCI]
+
+:_mod-docs-content-type: PROCEDURE
+[id="installing-troubleshooting-assisted-installer-oci_{context}"]
+= Troubleshooting installation of a cluster on OCI
+
+If you experience issues with using the Assisted Installer to install an {product-title} cluster on {oci-first}, read the following sections to troubleshoot common problems.
+
+== The Ingress Load Balancer in OCI is not at a healthy status
+
+This issue is classed as a `Warning` as against an `Error`, because by using the Resource Manager to create a stack, you created a pool of compute nodes, 3 by default, that are automatically added as backend listeners for the Ingress Load Balancer. By default, the {product-title} deploys two router pods, which are based on the default values from the {product-title} manifest files. The `Warning` is expected because a mismatch exists with the number of router pods available, two, to run on the three compute nodes. 
+
+.Example of a `Warning` message that is under the **Backend set information** tab on {oci}: 
+image::ingress_load_balancer_warning_message.png[Example of an warning message that is under the Backend set information tab on OCI]
+
+You do not need to modify the Ingress Load Balancer's configuration. Instead, you can point the Ingress Load Balancer to specific compute nodes that operate in your cluster on {product-title}. To do this, you will need to use placement mechanisms, such as annotations, on {product-title} to ensure router pods only run on the compute nodes that you originally configured on the Ingress Load Balancer as backend listeners. 
+
+== OCI create stack operation fails with an Error: 400-InvalidParameter message
+
+On attempting to create a stack on {oci}, you identified that the **Logs** section of the job outputs an error message. For example:
+
+[source,terminal]
+----
+Error: 400-InvalidParameter, DNS Label oci-demo does not follow Oracle requirements
+Suggestion: Please update the parameter(s) in the Terraform config as per error message DNS Label oci-demo does not follow Oracle requirements
+Documentation: https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/core_vcn
+----
+
+Go to the https://console.redhat.com/openshift/assisted-installer/clusters/~new[**Install OpenShift with the Assisted Installer**] page on the Hybrid Cloud Console, and check the **Cluster name** field on the  **Cluster Details** step. Remove any special characters, such as a hyphen (`-`),  from the name, because these special characters are not compatible with the {oci} naming conventions.  For example, change `oci-demo` to `ocidemo`.