# Solution Components
This solution describes the deployment of the HPE Ezmeral Runtime Enterprise, the creation of a Kubernetes cluster with the native HPE Ezmeral Data Fabric for Kubernetes, and an app modernization use case using KubeDirector. HPE Ezmeral Runtime Enterprise Controllers, Gateway servers, and Kubernetes cluster nodes are configured to achieve high availability. This section outlines the hardware, software, and service components utilized in this solution.
# Solution Physical Components
# Hardware
The HPE Ezmeral Runtime Enterprise environment is built around HPE ProLiant Gen11 Servers using a deployment setup consisting of HPE ProLiant DL360 Gen11 nodes, three (3) of which are deployed as HPE Ezmeral Runtime Enterprise Controllers in a highly available configuration, two (2) are deployed as gateway Load Balancer server, five (5) HPE DL 380 Gen11 nodes are used to create the HPE Ezmeral Data Fabric for Kubernetes and finally six (6) HPE ProLiant DL360 Gen 11 nodes are deployed as Kubernetes compute cluster.
Figure 5 shows the physical layout of the server, storage, and network used for the solution.
Figure 5. Front view of 16x HPE ProLiant DL360 & DL380 Gen11 Servers in the solution
The installation user has the flexibility to customize the HPE components throughout this stack in accordance with the unique IT and workload requirements or to build the solution with individual components.
Table 1 highlights the individual components and their quantities as deployed within the solution.
Table 1. Components utilized in the creation of this solution.
| Component | Qty | Description |
|---|---|---|
| HPE ProLiant DL360 Gen11 Servers | 11 | Three for HPE Ezmeral Runtime Enterprise Controller + Two for HPE Ezmeral Runtime Enterprise Gateway + Three for HPE Ezmeral Data Fabric K8 Master Nodes + Six for HPE Ezmeral Runtime Enterprise K8s Compute Cluster |
| HPE ProLiant DL380 Gen11 Servers | 5 | Five Data Fabric worker nodes. |
| HPE Aruba 8325-32C BF | 2 | Each switch contains either 40/100GbE (QSFP+/QSFP28) or 1/10/25GbE (SFP/SFP+/SFP28) |
# Disk requirement
A minimum of two (2) raw disks of 500 GB or higher in addition to the 500 GB OS disk per node is required.
# Software
HPE Ezmeral Runtime Enterprise 5.6.x.
# Operating System installation
Installs the SUSE Linux Enterprise Server 15 SP3 and ensures that the system has appropriate licensing in place using SUSE subscription. Installs the latest patches using zypper and ensures that the prerequisites have been met for each server.
The operating system installation and prerequisites for the deployment are automated as part of this solution. More details can be found further in the document in OS deployment section.
Table 2 describes the software versions utilized in the creation of this solution. The installation user should ensure that they download or have access to this software. Ensure that the appropriate subscription and licensing are in place to use within the planned time frame.
Table 2. Major software versions used in the creation of this solution
| Component | Version | Description |
|---|---|---|
| HPE Ezmeral Runtime Enterprise | 5.6.x | Control Plane deployed on three server nodes |
| SUSE Linux Enterprise Server | 15 SP3 | OS for all compute modules with SP1 update minimum |
| HPE Gateway Load Balancer | 5.6.x | Configured automatically by HPE Ezmeral Runtime Enterprise |
| Kubernetes | 1.23 | Kubernetes version installed as a part of the solution |
| Docker | 19.03.15 | Docker server & client version |
| HPE External Ezmeral Data Fabric | 7.2 | HPE Ezmeral Data Fabric for tenant persistent volume |
Table 3. Software installed on the installer machine
| Component | Version |
|---|---|
| Ansible | 2.9 |
| Python | 3.6 |
| Java | 1.8 |
NOTE
The latest sub-version of each component listed in Table 2 and 3 should be installed.
# Services
This document is built with assumptions about services and network ports available within the implementation environment. This section discusses those assumptions.
Table 4 disseminates the services required in this solution and provides a high-level explanation of their function.
Table 4. Services used in the creation of this solution.
| Service | Description |
|---|---|
| DNS | Provides name resolution on management and data center networks |
| NTP | Ensures consistent time across the solution stack. |