Hardware and Software Requirements

This section provides the hardware and software requirements to install the DX Platform:
dxp10
This section provides the hardware and software requirements to install the DX Platform:
Hardware Requirements
This section describes the hardware requirements for the Application Service Layer, Kubernetes Master Layer, and Elasticsearch Layer:
Application Service Layer
The Application Service Layer requires the following hardware:
  • CPU, Memory and Storage:
     Based on the sizing recommendation.
  • Processor: 
    2.5GHz Intel Xeon processor or 2.5GHz AMD server processor 
  • Network Speed:
     NIC 10 GB/s between the nodes 
  • We recommend using hosts with 16 cores, and 32-GB or higher
Kubernetes Master Layer
The Kubernetes Master Layer requires the following hardware:
  • Network speed 10 Gb/s between all nodes
  • 8 Cores
  • 16-GB RAM
  • 200 GB non-OS space
Elasticsearch Layer
The Elasticsearch Layer requires the following hardware:
  • Elasticsearch Hot Node:
     Locally attached SSDs (NVMe preferred or high-end SATA SSD, IOPS - random 90K for read/write operations, throughput - sequential read 540 MB/s and write 520 MB/s, 4K block size, NIC 10 GB/s
  • Elasticsearch Warm Node:
     Locally attached or network storage with a minimum speed of 220 MB/s for read/write operations, 4K block size, NIC 10 GB/s
  • Network Speed:
     NIC 10 GB/s between the nodes 
Software Requirements for Kubernetes and the Install System
Kubernetes is a prerequisite for the 
DX Platform
 installation. The following software is required for the Kubernetes cluster instances:
Supported Operating Systems
The following table lists the supported operating systems and their versions: 
Operating System
Version
Red Hat Enterprise Linux
7.3, 7.4, 7.5, 7.6
CentOS
7.3, 7.4, 7.5, 7.6
Supported Containerization Systems
The following table lists the supported containerization systems: 
Containerization Systems
Version
Kubernetes
1.10.11, 1.11.7, 1.12.5, 1.13.2
Docker Engine
1.13.1
Nginx Ingress Controller
0.23.0 or higher
This version of 
DX Platform
 installer supports only Nginx Ingress Controller. For more information about Nginx Ingress Controller installation, see the  documentation.
To use other Ingress Controllers, contact the
Broadcom Support
.
 Additional requirements for Kubernetes:
  • Disable the scheduling pods on the master node. This prevents the application services from being deployed on the master node. For example, if node 1 is the master in the Kubernetes cluster, run the following command to disable scheduling of pods in the master:
    kubectl taint node node1 node-role.kubernetes.io/master=true:NoSchedule
  • Cluster admin role. Run the installer in the validation mode to confirm that the access privileges are met. 
Required External Services
The following external services are required:
  • NFS Service that is accessible from all nodes
  • (Optional) SMTP Server that is accessible from all nodes
  • (Optional) MacOS Server for Desymbolication in DX App Experience Analytics
Ports Reference
The following table lists all the ports that need to be open:
If you open the ports after DX APM is already installed, ensure to restart all the pods. Run the following command to start all the pods at once:
kubectl delete pods --all -n <namespace> --force --grace-period=0
Server
Port Number
Description
Kubernetes Master
6443
2379-2380
10250-10255
179
5473
4789
Open the following ports:
firewall-cmd --permanent --add-port=6443/tcp firewall-cmd --permanent --add-port=2379-2380/tcp firewall-cmd --permanent --add-port=10250-10255/tcp firewall-cmd --permanent --add-port=179/tcp firewall-cmd --permanent --add-port=5473/tcp firewall-cmd --permanent --add-port=4789/udp
Kubernetes Nodes
10250
10255
30000-32767
6783
179
5473
4789
Open the following ports:
firewall-cmd --permanent --add-port=10250/tcp firewall-cmd --permanent --add-port=10255/tcp firewall-cmd --permanent --add-port=30000-32767/tcp firewall-cmd --permanent --add-port=6783/tcp firewall-cmd --permanent --add-port=179/tcp firewall-cmd --permanent --add-port=5473/tcp firewall-cmd --permanent --add-port=4789/udp
Docker Registry
5000
Open the following port on the registry-proxy pod:
firewall-cmd --permanent --add-port=5000/tcp
Ingress Controller Master
80
443
Open the following ports:
firewall-cmd --permanent --add-port=80/tcp firewall-cmd --permanent --add-port=443/tcp For more information, see the Pre-Installation Tasks section.
NFS Master
111
2049
20048
Open these ports for communication with the NFS:
firewall-cmd --permanent --add-port=111/tcp firewall-cmd --permanent --add-port=2049/tcp firewall-cmd --permanent --add-port=20048/tcp firewall-cmd --permanent --add-port=20048/udp Open the following services: firewall-cmd --permanent --add-service=mountd firewall-cmd --permanent --add-service=nfs firewall-cmd --permanent --add-service=rpc-bind