Skip to content

Commit cce1a7b

Browse files
aireillyaireilly
committed
adding rhacm managed cluster maximums info
David's bandwidth tweak
1 parent d2eced9 commit cce1a7b

File tree

3 files changed

+110
-4
lines changed

3 files changed

+110
-4
lines changed

‎.vale/styles/Vocab/OpenShiftDocs/accept.txt

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
# Regex terms added to accept.txt are ignored by the Vale linter and override RedHat Vale rules.
22
# Add terms that have a corresponding incorrectly capitalized form to reject.txt.
33

4+
[Ff]ronthaul
5+
[Mm]idhaul
46
[Pp]assthrough
7+
[Rr]ealtime
58
Assisted Installer
69
Control Plane Machine Set Operator
710
custom resource
811
custom resources
12+
Mbps
913
MetalLB
1014
Operator
1115
Operators
12-
[Ff]ronthaul
13-
[Mm]idhaul
14-
[Rr]ealtime

‎modules/ztp-gitops-ztp-max-spoke-clusters.adoc

Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.adoc]
4+
5+
:_content-type: REFERENCE
6+
[id="ztp-gitops-ztp-max-spoke-clusters_{context}"]
7+
= Recommended hub cluster specifications and managed cluster limits for {ztp}
8+
9+
With {ztp-first}, you can manage thousands of clusters in geographically dispersed regions and networks.
10+
The Red Hat Performance and Scale lab successfully created and managed 3500 virtual {sno} clusters with a reduced DU profile from a single {rh-rhacm-first} hub cluster in a lab environment.
11+
12+
In real-world situations, the scaling limits for the number of clusters that you can manage will vary depending on various factors affecting the hub cluster.
13+
For example:
14+
15+
Hub cluster resources::
16+
Available hub cluster host resources (CPU, memory, storage) are an important factor in determining how many clusters the hub cluster can manage.
17+
The more resources allocated to the hub cluster, the more managed clusters it can accommodate.
18+
19+
Hub cluster storage::
20+
The hub cluster host storage IOPS rating and whether the hub cluster hosts use NVMe storage can affect hub cluster performance and the number of clusters it can manage.
21+
22+
Network bandwidth and latency::
23+
Slow or high-latency network connections between the hub cluster and managed clusters can impact how the hub cluster manages multiple clusters.
24+
25+
Managed cluster size and complexity::
26+
The size and complexity of the managed clusters also affects the capacity of the hub cluster.
27+
Larger managed clusters with more nodes, namespaces, and resources require additional processing and management resources.
28+
Similarly, clusters with complex configurations such as the RAN DU profile or diverse workloads can require more resources from the hub cluster.
29+
30+
Number of managed policies::
31+
The number of policies managed by the hub cluster scaled over the number of managed clusters bound to those policies is an important factor that determines how many clusters can be managed.
32+
33+
Monitoring and management workloads::
34+
{rh-rhacm} continuously monitors and manages the managed clusters.
35+
The number and complexity of monitoring and management workloads running on the hub cluster can affect its capacity.
36+
Intensive monitoring or frequent reconciliation operations can require additional resources, potentially limiting the number of manageable clusters.
37+
38+
{rh-rhacm} version and configuration::
39+
Different versions of {rh-rhacm} can have varying performance characteristics and resource requirements.
40+
Additionally, the configuration settings of {rh-rhacm}, such as the number of concurrent reconciliations or the frequency of health checks, can affect the managed cluster capacity of the hub cluster.
41+
42+
Use the following representative configuration and network specifications to develop your own Hub cluster and network specifications.
43+
44+
[IMPORTANT]
45+
====
46+
The following guidelines are based on internal lab benchmark testing only and do not represent a complete real-world host specification.
47+
====
48+
49+
.Representative three-node hub cluster machine specifications
50+
[cols=2*, width="90%", options="header"]
51+
|====
52+
|Requirement
53+
|Description
54+
55+
|{product-title} version
56+
|version 4.13
57+
58+
|{rh-rhacm} version
59+
|version 2.7
60+
61+
|{cgu-operator-first}
62+
|version 4.13
63+
64+
|Server hardware
65+
|3 x Dell PowerEdge R650 rack servers
66+
67+
|NVMe hard disks
68+
a|* 50 GB disk for `/var/lib/etcd`
69+
* 2.9 TB disk for `/var/lib/containers`
70+
71+
|SSD hard disks
72+
a|* 1 SSD split into 15 200GB thin-provisioned logical volumes provisioned as `PV` CRs
73+
* 1 SSD serving as an extra large `PV` resource
74+
75+
|Number of applied DU profile policies
76+
|5
77+
|====
78+
79+
[IMPORTANT]
80+
====
81+
The following network specifications are representative of a typical real-world RAN network and were applied to the scale lab environment during testing.
82+
====
83+
84+
.Simulated lab environment network specifications
85+
[cols=2*, width="90%", options="header"]
86+
|====
87+
|Specification
88+
|Description
89+
90+
|Round-trip time (RTT) latency
91+
|50 ms
92+
93+
|Packet loss
94+
|0.02% packet loss
95+
96+
|Network bandwidth limit
97+
|20 Mbps
98+
|====

‎scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.adoc

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,13 @@ To use {rh-rhacm} in a disconnected environment, create a mirror registry that m
1010

1111
include::modules/ztp-telco-ran-software-versions.adoc[leveloffset=+1]
1212

13+
include::modules/ztp-gitops-ztp-max-spoke-clusters.adoc[leveloffset=+1]
14+
15+
[role="_additional-resources"]
16+
.Additional resources
17+
18+
* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html/install/installing#single-node[Creating and managing {sno} clusters with {rh-rhacm}]
19+
1320
include::modules/ztp-acm-installing-disconnected-rhacm.adoc[leveloffset=+1]
1421

1522
[role="_additional-resources"]
@@ -43,4 +50,4 @@ include::modules/ztp-configuring-the-hub-cluster-to-use-unauthenticated-registri
4350

4451
include::modules/ztp-preparing-the-hub-cluster-for-ztp.adoc[leveloffset=+1]
4552

46-
include::modules/ztp-preparing-the-ztp-git-repository.adoc[leveloffset=+1]
53+
include::modules/ztp-preparing-the-ztp-git-repository.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)