|
4 | 4 |
|
5 | 5 | :_mod-docs-content-type: CONCEPT
|
6 | 6 | [id="installing-oci-about-assisted-installer_{context}"]
|
7 |
| -= The {ai-full} and {oci} overview |
| 7 | += About the {ai-full} and {oci} integration |
8 | 8 |
|
9 | 9 | You can run cluster workloads on {oci-first} infrastructure that supports dedicated, hybrid, public, and multiple cloud environments. Both Red{nbsp}Hat and Oracle test, validate, and support running {oci} in an {product-title} cluster on {oci}.
|
10 | 10 |
|
11 |
| -The {ai-full} supports the {oci} platform, and you can use the {ai-full} to access an intuitive interactive workflow for the purposes of automating cluster installation tasks on {oci}. |
| 11 | +This section explains how to use the {ai-full} to install an {product-title} cluster on the {oci} platform. The installation deploys cloud-native components such as {oci-ccm-full} and {oci-csi-full}, and integrates your cluster with {oci} API resources such as instance node, load balancer, and storage. |
12 | 12 |
|
13 |
| -.Workflow for using the {ai-full} in a connected environment to install a cluster on {oci} |
| 13 | +The installation process uses the {product-title} discovery ISO image provided by Red Hat, together with the scripts and manifests provided and maintained by {oci}. |
14 | 14 |
|
15 |
| -image::684_OpenShift_Installing_on_OCI_0724_assisted.png[Image of a high-level workflow for using the Assisted Installer in a connected environment to install a cluster on {oci}] |
| 15 | +[id="installing-oci-preinstallation-considerations_{context}"] |
| 16 | +== Preinstallation considerations |
16 | 17 |
|
17 |
| -{oci} provides services that can meet your needs for regulatory compliance, performance, and cost-effectiveness. You can access {oci} Resource Manager configurations to provision and configure {oci} resources. |
| 18 | +Before installing {product-title} on {oci-first-no-rt}, you must consider the following configuration choices. |
18 | 19 |
|
19 |
| -[IMPORTANT] |
20 |
| -==== |
21 |
| -The steps for provisioning {oci} resources are provided as an example only. You can also choose to create the required resources through other methods; the scripts are just an example. Installing a cluster with infrastructure that you provide requires knowledge of the cloud provider and the installation process on {product-title}. You can access {oci} Resource Manager configurations to complete these steps, or use the configurations to model your own custom script. |
22 |
| -==== |
| 20 | +.Deployment platforms |
23 | 21 |
|
24 |
| -Follow the steps in the _Installing a cluster on {oci-first-no-rt} by using the Assisted Installer_ document to understand how to use the {ai-full} to install a {product-title} cluster on {oci}. This document demonstrates the use of the {oci} Cloud Controller Manager (CCM) and Oracle’s Container Storage Interface (CSI) objects to link your {product-title} cluster with the {oci} API. |
| 22 | +The integration between {product-title} and {oci-first-no-rt} is certified on both virtual machines (VMs) and bare-metal (BM) machines. Bare-metal installations using iSCSI boot drives require a secondary vNIC that is automatically created in the Terraform stack provided by Oracle. |
| 23 | + |
| 24 | +Before you create a virtual machine (VM) or bare-metal (BM) machine, you must identify the relevant {oci} shape. For details, see the following resource: |
| 25 | + |
| 26 | +* link:https://catalog.redhat.com/cloud/detail/216977[Cloud instance types (Red{nbsp}Hat Ecosystem Catalog portal)]. |
| 27 | + |
| 28 | +.VPU sizing recommendations |
25 | 29 |
|
26 |
| -[IMPORTANT] |
27 |
| -==== |
28 | 30 | To ensure the best performance conditions for your cluster workloads that operate on {oci}, ensure that 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:
|
29 | 31 |
|
30 | 32 | * Test or proof of concept environment: 100 GB, and 20 to 30 VPUs.
|
31 | 33 | * Basic environment: 500 GB, and 60 VPUs.
|
32 | 34 | * Heavy production environment: More than 500 GB, and 100 or more VPUs.
|
33 | 35 |
|
34 |
| -Consider reserving additional VPUs to provide sufficient capacity for updates and scaling activities. For more information about VPUs, see Volume Performance Units (Oracle documentation). |
35 |
| -==== |
| 36 | +Consider reserving additional VPUs to provide sufficient capacity for updates and scaling activities. For more information about VPUs, see link:https://docs.oracle.com/en-us/iaas/Content/Block/Concepts/blockvolumeperformance.htm#vpus[Volume Performance Units (Oracle documentation)]. |
| 37 | + |
| 38 | +.Instance sizing recommendations |
| 39 | + |
| 40 | +Find recommended values for compute instance CPU, memory, VPU, and volume size for {product-title} nodes. For details, see link:https://docs.oracle.com/en-us/iaas/Content/openshift-on-oci/installing-agent-about-instance-configurations.htm[Instance Sizing Recommendations for {product-title} on {oci} Nodes (Oracle documentation)]. |
| 41 | + |
| 42 | +[id="installing-oci-workflow_{context}"] |
| 43 | +== Workflow |
| 44 | + |
| 45 | +//// |
| 46 | +Diagram will be updated and replace steps in a future task: |
| 47 | +
|
| 48 | +The procedure for using the {ai-full} in a connected environment to install a cluster on {oci} is illustrated in the diagram below. |
| 49 | +
|
| 50 | +image::684_OpenShift_Installing_on_OCI_0724_assisted.png[Image of a high-level workflow for using the Assisted Installer in a connected environment to install a cluster on {oci}] |
| 51 | +//// |
| 52 | + |
| 53 | +The procedure for using the {ai-full} in a connected environment to install a cluster on {oci} is outlined below: |
| 54 | + |
| 55 | +. In the {oci} console, configure an {oci} account to host the cluster: |
36 | 56 |
|
37 |
| -If you are unfamiliar with the {product-title} {ai-full}, see "Assisted Installer for {product-title}". |
| 57 | +.. Create a new child compartment under an existing compartment. |
| 58 | + |
| 59 | +.. Create a new object storage bucket or use one provided by {oci}. |
| 60 | + |
| 61 | +.. Download the stack file template stored locally. |
| 62 | + |
| 63 | +. In the {ai-full} console, set up a cluster: |
| 64 | + |
| 65 | +.. Enter the cluster configurations. |
| 66 | + |
| 67 | +.. Generate and download the discovery ISO image. |
| 68 | + |
| 69 | +. In the {oci} console, create the infrastructure: |
| 70 | + |
| 71 | +.. Upload the discovery ISO image to the {oci} bucket. |
| 72 | + |
| 73 | +.. Create a Pre-Authenticated Request (PAR) for the ISO image. |
| 74 | + |
| 75 | +.. Upload the stack file template, and use it to create and apply the stack. |
| 76 | + |
| 77 | +.. Copy the custom manifest YAML file from the stack. |
| 78 | + |
| 79 | +. In the {ai-full} console, complete the cluster installation: |
| 80 | + |
| 81 | +.. Set roles for the cluster nodes. |
| 82 | + |
| 83 | +.. Upload the manifests provided by Oracle. |
| 84 | + |
| 85 | +.. Install the cluster. |
| 86 | + |
| 87 | +[IMPORTANT] |
| 88 | +==== |
| 89 | +The steps for provisioning {oci} resources are provided as an example only. You can also choose to create the required resources through other methods; the scripts are just an example. Installing a cluster with infrastructure that you provide requires knowledge of the cloud provider and the installation process on {product-title}. You can access {oci} configurations to complete these steps, or use the configurations to model your own custom script. |
| 90 | +==== |
0 commit comments