Dimensioning model assumptions
The Dell Telecom Infrastructure Blocks for Red Hat dimensioning model consists of dimensioning the various types of clouds that are the building blocks for the deployment, including:
- Telecom Infrastructure Automation Suite infrastructure cloud
- Red Hat OpenShift Container Platform management cloud
- Workload clouds
The following assumptions were considered for the Telecom Infrastructure Blocks for Red Hat dimensioning model:
- All software components that are a part of the Telecom Infrastructure Blocks for Red Hat solution are considered, including assumptions for the cloud-native network function (CNF) workloads. For Telecom Infrastructure Blocks for Red Hat that includes:
- Telecom Infrastructure Automation Suite
- Red Hat components in the management cloud
- Workload clouds
- A deployment scaling model with an initial number of network domains, including the National Data Center (NDC), Regional Data Centers (RDCs), Local Data Centers (LDCs), and Cell Sites to accommodate a typical communications service provider (CSP) deployment, specifically:
- One NDC
- Two RDCs per NDC
- Two LDCs per RDC
- The number of CNFs in each cloud, and the number of clouds in the network domain. The initial distribution model considered was:
- One CNF for each workload cloud
- One cloud for each network domain, including NDC, RDC, LDC, and Cell Sites
- All servers in a cloud have the same hardware profile and have the same type and number of network interface controller (NIC) cards.
- A defined number of server nodes for each type of cloud, specifically:
- Three Infrastructure Automation nodes
- Six management cloud nodes
- Six workload cloud nodes, plus three more workload cloud nodes for Red Hat OpenShift Data Foundation
The dimensioning model is part of the Dell Professional Services practice. Based on the requirements of the CSP, Dell Professional Services can determine the appropriate network dimensioning using Telecom Infrastructure Blocks for Red Hat building blocks and the Telecom Infrastructure Blocks for Red Hat automation workflows.
Using the Telecom Infrastructure Blocks for Red Hat automation workflows, the initial Telecom Infrastructure Blocks for Red Hat dimensioning can be extrapolated, depending on the number of CNFs, the CNF distribution in each network domain and in clouds, and the CSP traffic profiles. The following scenarios can be considered to extend your calculations:
- Adding new network domains, RDCs, LDCs, and Cell Sites
- Adding new clouds to each network domain
- Adding new server nodes to a cloud
- Replacing hardware such as drives, NICs, and server nodes
Dimensioning model details
The following table describes the variables that are used for the dimensioning calculations:
Variable name | Description | Default value |
NDC_U1 | NDC management cluster unit. This is the number of nodes that are initially allocated for this cluster. | 3 |
NDC_U2 | NDC compute cluster unit This is the number of nodes that are initially allocated for this cluster. | 6 |
RDC_U1 | RDC management cluster unit. This is the number of nodes that are initially allocated for this cluster. | 3 |
RDC_U2 | RDC compute cluster unit. This is the number of nodes that are initially allocated for this cluster. | 6 |
LDC_U3 | Local Data Center compute cluster unit. This is the number of nodes that are initially allocated for this cluster. | 3 |
Cell_Site_U4 | Cell Site compute cluster unit. This is the number of nodes that are initially allocated for this cluster. | 1 |
T1 | The number of NDCs, where the NDC is the root node from a topology point of view. | 1 |
T2 | The number of RDCs sub-tended to one NDC. This describes the RDC topology deployment starting from the NDC. | 2 |
T3 | The number of LDCs sub-tended to one RDC. | 2 |
T4 | The number of Cell Sites sub-tended to one LDC. | 2 |
V1 | The number of clouds per NDC. | 1 |
V2 | The number of clouds per RDC. | 1 |
V3 | The number of clouds per LDC. | 1 |
V4 | The number of clouds per Cell Site. | 1 |
DTIB | Dell Telecom Infrastructure Blocks. | 1 |
The computational model allows you to change any variable when calculating the final sizing requirements. For example, V1 can equal 10 clusters for one 5G core, T3 can equal 10 sub-tended LDCs, and T4 can equal 100 Cell Sites. Based on the specific configuration and variables, the dimensioning model can be used to calculate:
- The initial number of serves for each cluster type, including the nodes allocated for Red Hat OpenShift Data Foundation storage
- The number of servers in each network domain
- The total number of serves for a given deployment for a specific customer deployment
Formulas
The following sample formulas show how to calculate for a deployment:
NDC total dimensioning(#servers) = 1 NDC_U1(#servers) + V1*NDC_U2(#servers)
RDC total dimensioning(#servers) = 1 RDC_U1(#servers) + V2*RDC_U2(#servers)
LDC total dimensioning(#servers) = V3*LDC_U3(#servers)
Cell Sites total dimensioning(#servers) = V4*Cell_Site_U4(#servers)
Telecom Infrastructure Blocks total deployment(#servers) = T1*NDC total dimensioning(#servers) + T2*RDC total dimensioning(#servers) +T3*LDC total dimensioning(#servers) + T4*Cell Sites total dimensioning(#servers)
Telecom Infrastructure Blocks for Red Hat automation workflows using these assumptions and calculations will allow CSPs to extend their initial deployments to meet their deployment expansion requirements.