Recommended CPU specifications

The following sections provides information on the CPU specifications that have been validated as part of a Telco Blueprint, reason to consider them, and customization options.

Controller

HPE ProLiant DL360 Gen10 Servers with dual socket Gen2 Intel Xeon scalable family processors

Validated Configuration

  • HPE ProLiant DL360 Gen10 Server

  • 2 x 4216 Gen2 (16 cores)

  • Each CPU socket includes 16 cores, six DDR4 memory channels, and x48 PCIe IO lanes.

Blueprint design consideration

  • Optimum performance and flexibility​

  • Providing efficient performance at low power and NEBS compliance​

Customization option

For non-NEBS options, consider the following parameters while choosing between the Intel Gold or Silver CPU processors:

  • Power consumption

  • Core count

  • Support tenure availability

  • Cost effectiveness

You can choose from the list available in HPE ProLiant DL360 Gen10 Server QuickSpecs.

However, ensure that your choices meet the minimum requirements specified by Red Hat in Recommendations for Large Deployments document.

HPE ProLiant m510 Xeon Servers with single socket Intel Xeon scalable family processors

Validated Configuration

  • HPE ProLiant m510 Xeon servers

  • 1x Xeon D-1587 1.7GHz (16-core)

  • The CPU socket includes 16 cores, 2 channels per processor, 2 DIMMs per channel

Blueprint design consideration

  • Optimum performance and flexibility​

  • Providing efficient performance at low power and NEBS compliance​

Customization option

No customization options available.

NOTE:

Based on the number of compute nodes that you require, size your Undercloud node to ensure optimum performance. For more information on Undercloud sizing, see Recommendation for Undercloud sizing

Storage - Ceph

HPE ProLiant DL380 Gen10 Servers with dual socket Gen2 Intel Xeon scalable family processors.​

Validated Configuration

  • HPE ProLiant DL380 Gen10 Servers

  • 2x 4216 Gen2 (16 cores)

  • Each CPU socket includes 16 cores, six DDR4 memory channels, and x48 PCIe IO lanes.

Blueprint design consideration

  • Optimum performance and flexibility​

  • Providing efficient performance at low power and NEBS compliance​

  • In HPE ProLiant DL380 NEBS max = 16 drives, augmented by P816i-a SR array controller

Customization option

For non-NEBS options, consider the following parameters while choosing between the Intel Gold or Silver CPU processors:

  • Power consumption

  • Core count

  • Type of drives (HDD, SSD, or NVMe)

  • Support tenure availability

  • Cost effectiveness

You can choose from the list available in HPE ProLiant DL380 Gen10 Server QuickSpecs
NOTE:
  • If you opt for SSD or NVMe (drive types) as storage drives, then it is recommended to add higher CPU core. The expected drive to CPU core ratio is as follows:

    • Per HDD Drive you require minimum 1 CPU core

    • Per SSD Drive you require minimum 2 CPU cores

    • Per NVMe Drive you require minimum 4 CPU cores

  • It is recommended to allocate a minimum of 4% of total cluster OSD capacity with the high-speed drives for WAL/RocksDB.

  • DL380 non-NEBS can accommodate more than 16 drives. This option will require SAS enablement kit to support additional drives​​
    NOTE:

    Ensure the additional SSD drives are added as per the number of the storage HDD drives. The recommended HDD:SSD ratio is 6:1.

However, ensure that your choices meet the minimum requirements specified by Red Hat in Recommendations for Large Deployments document.

Compute

HPE ProLiant DL360 Gen10 Servers with dual socket Gen2 Intel Xeon scalable family processors.​

Validated Configuration

  • HPE ProLiant DL360 Gen10 Servers

  • 2 x 6252N Gen2 (24 cores) N: NFV optimized

  • Each CPU socket includes 24 cores, six DDR4 memory channels, and x48 PCIe IO lanes.

Blueprint design consideration

  • Optimum performance and flexibility​

  • Providing efficient performance at low power and NEBS compliance​

Customization option

For non-NEBS options, consider the following parameters while choosing between the Intel Platinum or Gold processors:

  • Power consumption

  • Core count based on workload requirements

  • Support tenure availability

  • Cost effectiveness

You can choose from the list available in HPE ProLiant DL360 Gen10 Server QuickSpecs
NOTE:

For computes, minimum Intel Gold series CPUs must be used.

However, ensure that your choices meet the minimum requirements specified by Red Hat in Recommendations for Large Deployments document.

Hyperconverged Infrastructure

HPE ProLiant DL380 Gen10 Servers with dual socket Gen2 Intel Xeon scalable family processors​ (Intel-based)

Validated Configuration

  • HPE ProLiant DL380 Gen10 Servers

  • 2x 6252 Gen1 (24 cores)

  • Each CPU socket includes 24 cores, six DDR4 memory channels, and x48 PCIe IO lanes.

Blueprint design consideration

  • Optimum performance and flexibility​

  • Providing efficient performance at low power and NEBS compliance​

Customization option

For non-NEBS options, consider the following parameters while choosing between the Intel Platinum, Gold or Silver CPU processors:

  • Power consumption

  • Core count based on workload requirements

  • Support tenure availability

  • Cost effectiveness

  • Types of drives required (HDD or SSD or NVMe)

You can choose from the list available in HPE ProLiant DL380 Gen10 Server QuickSpecs
NOTE:

For computes, minimum Intel Gold series CPUs must be used.

NOTE:
  • If you opt for SSD or NVMe (drive types) as storage drives, then it is recommended to add higher CPU core. The expected drive to CPU core ratio is as follows:

    • Per HDD Drive you require minimum 1 CPU core

    • Per SSD Drive you require minimum 2 CPU cores

    • Per NVMe Drive you require minimum 4 CPU cores

  • It is recommended to allocate a minimum of 4% of total cluster OSD capacity with the high-speed drives for WAL/RocksDB.

However, ensure that your choices meet the minimum requirements specified by Red Hat in Recommendations for Large Deployments document.

HPE ProLiant DL385 Gen 10 Servers with dual socket AMD EPYC family processors (AMD-based)

Validated Configuration

  • HPE ProLiant DL385 Gen10 

  • EPYC™ 7601 Dual AMD Server - The first-generation AMD EPYC processor offered up to 32 cores with NEBS compliance.

Blueprint design consideration

  • Optimum performance and flexibility​

  • Providing efficient performance at low power and NEBS compliance.

Customization option

For non-NEBS options, consider the following parameters while appropriate AMD processor:

  • Power consumption

  • Core count based on workload requirements

  • Support tenure availability

  • Cost effectiveness

  • Types of drives required (HDD or SSD or NVMe)

You can choose from the list available in HPE ProLiant DL385 Gen10 Server QuickSpecs
NOTE:
  • If you opt for SSD or NVMe (drive types) as storage drives, then it is recommended to add higher CPU core. The expected drive to CPU core ratio is as follows:

    • Per HDD Drive you require minimum 1 CPU core

    • Per SSD Drive you require minimum 2 CPU cores

    • Per NVMe Drive you require minimum 4 CPU cores

  • It is recommended to allocate a minimum of 4% of total cluster OSD capacity with the high-speed drives for WAL/RocksDB.

However, ensure that your choices meet the minimum requirements specified by Red Hat in Recommendations for Large Deployments document.

HPE ProLiant e910 Xeon Servers with single socket Intel Xeon scalable family processors (Intel-based)

Validated Configuration

  • HPE ProLiant e910 Xeon Servers

  • 1x Xeon-Gold 6212U (24-core)

  • Each CPU socket includes 24 cores, six DDR4 memory channel

Blueprint design consideration

  • Optimum performance and flexibility​

  • Providing efficient performance at low power and NEBS compliance.

Customization option

For non-NEBS options, consider the following parameters while choosing between the Intel Gold or Silver CPU processors:

  • Power consumption

  • Core count

  • Support tenure availability

  • Cost effectiveness

You can choose from the list available in HPE ProLiant e910 Server Blade.

However, ensure that your choices meet the minimum requirements specified by Red Hat in Recommendations for Large Deployments document.