Cluster requirements for CLM

CLM VM hardware requirements

CLM deployments are server- and vendor-agnostic, but must meet all CLM hardware criteria and performance targets. Server-class hardware is required; desktop hardware is inadequate. Processor support is limited to specific Intel Xeon-based x86-64 and AMD Epyc x86-64 CPUs that have the required minimum CPU core speed listed in Table 2-4, VM processor requirements.

Table 2-4: VM processor requirements

Processor microarchitecture	Minimum CPU core speed	Supported deployments
Intel Xeon Haswell or Broadwell	2.4 GHz	Supported for all CLM deployments
Intel Skylake or newer	2.0 GHz	Supported for all CLM deployments
AMD Epyc Zen 3 or newer	2.0 GHz	Supported for all CLM deployments

Provisioned CPU resources are based upon threaded CPUs. The CLM platform requirements will specify a minimum number of vCPUs to be assigned to the VM. VMs are recommended to be configured with all vCPUs on one virtual socket.

A host system requires CPU, memory and disk resources after resources for CLM VMs have been allocated. Contact the hypervisor provider for requirements and best practices related to the hosting environment.

You must provide information about the provisioned VMs to Nokia support. You can provide the information through read-only hypervisor access, or make the information available upon request. Failure to provide the information may adversely affect CLM support.

CLM cluster storage-layer requirements

The storage layer of a CLM cluster requires a minimum read/write IOPS based on deployment type, network size and storage type. Deployments with customer provided storage also have storage capacity requirements for database backups.

The following minimum CLM cluster IOPS requirement applies:

• Minimum storage-layer read/write IOPS for local storage: 2000

Note: IOPS performance can vary in a cloud environment and may degrade over time. Degraded IOPS performance may affect CLM performance. Customers are advised to monitor IOPS performance over time.

Minimum and production platform requirements

WARNING Service Degradation Risk

The CLM deployer host is a crucial element of a CLM system that holds the required container images and Helm repositories for deployment to the CLM cluster VM. If the CLM deployer host is unavailable, cluster recovery in the event of a failure may be compromised.

Ensure that the CLM deployer host remains operational and reachable by the CLM cluster after the cluster deployment.

Each deployment requires one deployer node and one cluster node.

The minimum requirements are as follows:

• CLM deployer node

  • 4 vCPU

  • 8 GB memory

  • 400 GB disk

• CLM cluster node

  • 4 vCPU

  • 32 GB memory

  • 710 GB disk

VM memory

The virtual memory configuration of each CLM cluster VM requires a parameter change to support Centralized Logging.

The following command entered as the root user displays the current setting:

sysctl -a | grep “vm.max_map_count”

If the setting is not at least 26 2144, you must enter the following command before you deploy the CLM:

sysctl -w vm.max_map_count=262144

nsp system user

The CLM deployer and cluster nodes require a system user account named nsp that must have uid 1000. If a user other than nsp is already assigned to uid 1000, then that user needs to be deleted or modified before CLM can be installed.

Using hostnames

The hostname of CLM must meet the following criteria:

• include only alphanumeric ASCII characters and hyphens

• not begin or end with a hyphen

• if an FQDN, FQDN components are delimited using periods

• hostname FQDN does not exceed 63 characters

Note: If you use hostnames or FQDNs to identify CLM in the configuration, the hostnames or FQDNs must be resolvable using DNS.