diff --git a/content/patterns/multicloud-gitops/mcg-cluster-sizing.adoc b/content/patterns/multicloud-gitops/mcg-cluster-sizing.adoc index 6419e382b..a69a2ad86 100644 --- a/content/patterns/multicloud-gitops/mcg-cluster-sizing.adoc +++ b/content/patterns/multicloud-gitops/mcg-cluster-sizing.adoc @@ -8,19 +8,6 @@ aliases: /multicloud-gitops/mcg-cluster-sizing/ :imagesdir: /images :_content-type: ASSEMBLY include::modules/comm-attributes.adoc[] +include::modules/multicloud-gitops/metadata-multicloud-gitops.adoc[] -include::modules/mcg-about-cluster-sizing.adoc[leveloffset=+1] - -//include::modules/mcg-support-matrix.adoc[leveloffset=+1] - -include::modules/mcg-hub-cluster-sizing.adoc[leveloffset=+2] - -// This is what we might probably need - need to discuss this with the team -include::modules/mcg-managed-cluster-sizing.adoc[leveloffset=+2] - - -//include::modules/mcg-aws-instance-types.adoc[leveloffset=+1] - -//include::modules/mcg-azure-instance-types.adoc[leveloffset=+1] - -//include::modules/mcg-gcp-instance-types.adoc[leveloffset=+1] +include::modules/cluster-sizing-template.adoc[] diff --git a/modules/mcg-about-cluster-sizing.adoc b/modules/mcg-about-cluster-sizing.adoc deleted file mode 100644 index 7acac993c..000000000 --- a/modules/mcg-about-cluster-sizing.adoc +++ /dev/null @@ -1,35 +0,0 @@ - -:_content-type: CONCEPT -:imagesdir: ../../images - -[id="about-openshift-cluster-sizing-mcg"] -= About OpenShift cluster sizing for the Multicloud GitOps Pattern - -The minimum requirements for an {ocp} cluster depend on your installation platform, for example: - -* For AWS, see link:https://docs.openshift.com/container-platform/4.16/installing/installing_aws/preparing-to-install-on-aws.html#requirements-for-installing-ocp-on-aws[Installing {ocp} on AWS]. - -* For bare-metal, see link:https://docs.openshift.com/container-platform/4.16/installing/installing_bare_metal/installing-bare-metal.html#installation-minimum-resource-requirements_installing-bare-metal[Installing {ocp} on bare metal]. - -To understand cluster sizing requirements for the Multicloud GitOps pattern, consider the following components that the Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster: - -|=== -| Name | Kind | Namespace | Description - -| multicloud-gitops-hub -| Application -| multicloud-gitops-hub -| Hub GitOps management - -| Red Hat Advanced Cluster Management -| Operator -| open-cluster-management -| Advance Cluster Management - -| Red Hat OpenShift GitOps -| Operator -| openshift-operators -| OpenShift GitOps -|=== - -The Multicloud GitOps pattern also includes the Red Hat Advanced Cluster Management (RHACM) supporting operator that is installed by OpenShift GitOps using Argo CD. \ No newline at end of file diff --git a/modules/mcg-aws-instance-types.adoc b/modules/mcg-aws-instance-types.adoc deleted file mode 100644 index 778c8b5a7..000000000 --- a/modules/mcg-aws-instance-types.adoc +++ /dev/null @@ -1,106 +0,0 @@ -:_content-type: REFERENCE -:imagesdir: ../../images - -[id="aws-instance-types"] -= Amazon Web Services (AWS) instance types - -The Multicloud GitOps pattern was tested with the highlighted AWS instances. With the OpenShift installer, you can determine whether an AWS instance type meets the minimum requirements for a cluster. - -.Example output -[source,text] ----- -INFO Credentials loaded from default AWS environment variables -FATAL failed to fetch Metadata: failed to load asset "Install Config": [controlPlane.platform.aws.type: Invalid value: "m4.large": instance type does not meet minimum resource requirements of 4 vCPUs, controlPlane.platform.aws.type: Invalid value: "m4.large": instance type does not meet minimum resource requirements of 16384 MiB Memory] ----- - -Below you can find a list of the AWS instance types that can be used to deploy the Multicloud GitOps pattern. - -[cols="^,^,^,^,^"] -|=== -| Instance type | Default vCPUs | Memory (GiB) | Datacenter | Factory/Edge - -| -| -| -| 3x3 OCP Cluster -| 3 Node OCP Cluster - -| m4.xlarge -| 4 -| 16 -| N -| N - -| *m4.2xlarge* -| 8 -| 32 -| Y -| Y - -| m4.4xlarge -| 16 -| 64 -| Y -| Y - -| m4.10xlarge -| 40 -| 160 -| Y -| Y - -| m4.16xlarge -| 64 -| 256 -| Y -| Y - -| *m5.xlarge* -| 4 -| 16 -| Y -| N - -| *m5.2xlarge* -| 8 -| 32 -| Y -| Y - -| m5.4xlarge -| 16 -| 64 -| Y -| Y - -| m5.8xlarge -| 32 -| 128 -| Y -| Y - -| m5.12xlarge -| 48 -| 192 -| Y -| Y - -| m5.16xlarge -| 64 -| 256 -| Y -| Y - -| m5.24xlarge -| 96 -| 384 -| Y -| Y -|=== - -The OpenShift cluster is made of 4 Control Plane nodes and 3 Workers for the Datacenter and the Edge/managed data center cluster are made of 3 Control Plane and 3 Worker nodes.For the node sizes, use the m5.xlarge on AWS and ensure this instance type meets the minimum requirements to deploy the Multicloud GitOps pattern successfully on the Datacenter hub. For the managed data center cluster, use the m5.xlarge because the minimum cluster consists of 3 nodes. - -[role="_additional-resources"] -.Additional resources -* xref:modules/mcg-azure-instance-types.adoc#ms-azure-instance-types[Microsoft Azure instance types] -* xref:modules/mcg-gcp-instance-types.adoc#gcp-instance-types[Google Cloud Platform (GCP) instance types] \ No newline at end of file diff --git a/modules/mcg-azure-instance-types.adoc b/modules/mcg-azure-instance-types.adoc deleted file mode 100644 index 87b010aee..000000000 --- a/modules/mcg-azure-instance-types.adoc +++ /dev/null @@ -1,46 +0,0 @@ -:_content-type: REFERENCE -:imagesdir: ../../images - -[id="ms-azure-instance-types"] -= Microsoft Azure instance types - -The Multicloud GitOps pattern was also deployed on Azure using the *Standard_D8s_v3* VM size. Below is a table of different VM sizes available for Azure. Keep in mind that due to limited access to Azure we only used the *Standard_D8s_v3* VM size. - -The OpenShift cluster is made of 3 Control Plane nodes and 3 Workers for the Datacenter cluster. - -The OpenShift cluster is made of 3 Control Plane nodes and 3 or more workers for each of the managed data center clusters. - -|=== -| Type | Sizes | Description - -| https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-general[General purpose] -| B, Dsv3, Dv3, Dasv4, Dav4, DSv2, Dv2, Av2, DC, DCv2, Dv4, Dsv4, Ddv4, Ddsv4 -| Balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers. - -| https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-compute[Compute optimized] -| F, Fs, Fsv2, FX -| High CPU-to-memory ratio. Good for medium traffic web servers, network appliances, batch processes, and application servers. - -| https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory[Memory optimized] -| Esv3, Ev3, Easv4, Eav4, Ev4, Esv4, Edv4, Edsv4, Mv2, M, DSv2, Dv2 -| High memory-to-CPU ratio. Great for relational database servers, medium to large caches, and in-memory analytics. - -| https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-storage[Storage optimized] -| Lsv2 -| High disk throughput and IO ideal for Big Data, SQL, NoSQL databases, data warehousing and large transactional databases. - -| https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-gpu[GPU] -| NC, NCv2, NCv3, NCasT4_v3, ND, NDv2, NV, NVv3, NVv4 -| Specialized virtual machines targeted for heavy graphic rendering and video editing, as well as model training and inferencing (ND) with deep learning. Available with single or multiple GPUs. - -| https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-hpc[High performance compute] -| HB, HBv2, HBv3, HC, H -| Our fastest and most powerful CPU virtual machines with optional high-throughput network interfaces (RDMA). -|=== - - -[role="_additional-resources"] -.Additional resources -* <> -* <> -* link:https://docs.microsoft.com/en-us/azure/virtual-machines/sizes[Sizes for virtual machines in Azure] diff --git a/modules/mcg-gcp-instance-types.adoc b/modules/mcg-gcp-instance-types.adoc deleted file mode 100644 index 88d675a0a..000000000 --- a/modules/mcg-gcp-instance-types.adoc +++ /dev/null @@ -1,39 +0,0 @@ -:_content-type: REFERENCE -:imagesdir: ../../images - -[id="gcp-instance-types"] -= Google Cloud Platform (GCP) instance types - -The Multicloud GitOps pattern was also deployed on GCP using the *n1-standard-8* VM size. Below is a table of different VM sizes available for GCP. Keep in mind that due to limited access to GCP we only used the *n1-standard-8* VM size. - -The OpenShift cluster is made of 3 Control Plane and 3 Workers for the Datacenter cluster. - -The OpenShift cluster is made of 3 Nodes combining Control Plane/Workers for the Edge/managed data center cluster. - -The following table provides VM recommendations for different workloads. - -|=== -| *General purpose* | *Workload optimized* | | | | - -| Cost-optimized | Balanced | Scale-out optimized | Memory-optimized | Compute-optimized | Accelerator-optimized - -| E2 -| N2, N2D, N1 -| T2D -| M2, M1 -| C2 -| A2 - -| Day-to-day computing at a lower cost -| Balanced price/performance across a wide range of VM shapes -| Best performance/cost for scale-out workloads -| Ultra high-memory workloads -| Ultra high performance for compute-intensive workloads -| Optimized for high performance computing workloads -|=== - -[role="_additional-resources"] -.Additional resources -* <> -* <> -* link:https://cloud.google.com/compute/docs/machine-resource[Machine families resource and comparison guide]. \ No newline at end of file diff --git a/modules/mcg-hub-cluster-sizing.adoc b/modules/mcg-hub-cluster-sizing.adoc deleted file mode 100644 index f2f4434e5..000000000 --- a/modules/mcg-hub-cluster-sizing.adoc +++ /dev/null @@ -1,27 +0,0 @@ -:_content-type: CONCEPT -:imagesdir: ../../images - - -[id="mcg-openshift-datacenter-hub-cluster-size"] -= Multicloud GitOps pattern with OpenShift datacenter hub cluster size - -The Multicloud GitOps pattern has been tested with a defined set of specifically tested configurations that represent the most common combinations that Red Hat OpenShift Container Platform customers are using or deploying for the x86_64 architecture. - -The datacenter hub OpenShift cluster uses the following the AWS deployment configuration: - -[cols="<,^,<,<"] -|=== -| Node Type | Number of nodes | Cloud Provider | Instance Type - -| Control Plane -| 4 -| Amazon Web Services -| m5.xlarge - -| Worker -| 3 -| Amazon Web Services -| m5.xlarge -|=== - -The datacenter hub OpenShift cluster needs to be a bit bigger than the Factory/Edge clusters because this is where the developers will be running pipelines to build and deploy the Multicloud GitOps pattern on the cluster. The above cluster sizing is close to a minimum size for a Datacenter HUB cluster. In the next few sections we take some snapshots of the cluster utilization while the Multicloud GitOps pattern is running. Keep in mind that resources will have to be added as more developers are working building their applications. diff --git a/modules/mcg-managed-cluster-sizing.adoc b/modules/mcg-managed-cluster-sizing.adoc deleted file mode 100644 index afd3ccc90..000000000 --- a/modules/mcg-managed-cluster-sizing.adoc +++ /dev/null @@ -1,24 +0,0 @@ -[id="mcg-openshift-managed-datacenter-cluster-size-cluster-sizing"] -= Multicloud GitOps pattern with OpenShift managed datacenter cluster size - -The standard datacenter deployment of an OpenShift cluster is 3 control plane nodes and 3 or more worker nodes. - -[cols="^,^,^,^"] -|=== -| Node Type | Number of nodes | Cloud Provider | Instance Type - -| Control Plane/Worker -| 3 -| Google Cloud -| n1-standard-8 - -| Control Plane/Worker -| 3 -| Amazon Cloud Services -| m5.2xlarge - -| Control Plane/Worker -| 3 -| Microsoft Azure -| Standard_D8s_v3 -|=== diff --git a/modules/mcg-support-matrix.adoc b/modules/mcg-support-matrix.adoc deleted file mode 100644 index 38acd3f46..000000000 --- a/modules/mcg-support-matrix.adoc +++ /dev/null @@ -1,26 +0,0 @@ -:_content-type: REFERENCE -:imagesdir: ../../images - -[id="support-matrix-for-multicloud-gitops-pattern-cluster-sizing"] -= Support matrix for the Multicloud GitOps pattern - -The Multicloud GitOps pattern has been tested in the following Certified Cloud Providers. - -|=== -| Certified Cloud Providers | 4.8 | 4.9 | 4.10 - -| Amazon Web Services -| -|✓ -| - -| Microsoft Azure -| -|✓ -| - -| Google Cloud Platform -|✓ -| -| -|===