Home > Communication Service Provider Solutions > Converged Core > Guides > Dell Technologies 5G Core Solution with Affirmed and Red Hat OpenShift Container Platform Ref Arch Guide > Requirements planning
This section describes how to size an OpenShift-based container ecosystem cluster by using a sample cloud native application. Memory, CPU core, I/O bandwidth, and storage requirement estimates are indicative of resource requirements at peak load times. The following two tables show the estimated and overall resource requirements for a cloud native inventory management application with a customized quotation generation system workload.
Application type |
Number of pods |
Maximum memory (GB) |
CPU cores |
Typical IOPS: Kb/s @ block size (KB) |
Persistent storage (GB) |
Apache web application |
150 |
0.5 |
0.5 |
10 @ 0.5 |
1 |
Python-based application |
50 |
0.4 |
0.5 |
55 @ 0.5 |
1 |
JavaScript runtime |
220 |
1 |
1 |
80 @ 2.0 |
1 |
Database |
100 |
16 |
2 |
60 @ 8.0 |
15 |
Java-based tools |
110 |
1.2 |
1 |
25 @ 1.0 |
1.5 |
Totals per pod |
630 |
19.1 |
5 |
N/A |
19.5 |
Pods |
CPU cores |
RAM |
Storage |
Aggregate network bandwidth |
630 |
630 |
2,047 GB |
1.9 TB |
130 Gbps |
Our calculations using the workload information from Table 3 account for the following considerations:
At a minimum, we recommend the control-plane node configuration is a PowerEdge R640 server with dual Intel® Xeon® Gold 6238 scalable processors and 192 GB RAM. As the Red Hat resource requirements show, this node is large enough for a 250-node cluster and higher. Dell Technologies recommends that you do not scale beyond 200 nodes, which means that the proposed reference design is sufficient for nearly all deployments. The following table shows the sizing recommendations:
Number of compute nodes |
CPU cores* |
Memory (GB) |
25 |
4 |
16 |
100 |
8 |
32 |
*Does not include provisioning of at least four cores per node for infrastructure I/O handling.