Supported operating system

Use an operating system that is supported by DPOD as described in Hardware and Software Requirements. Verify the installed OS using the following command:

cat /etc/redhat-release

CPU and RAM

Allocate CPU and RAM according to the chosen deployment profile as listed in Hardware and Software Requirements. Verify the allocated resources using the following commands:

free -h
lscpu

Disks

DPOD requires at least 3 disks (LUNs / physical / virtual):

• 1 disk for the operating system

• 1 disk for the application and logs

• At least 1 disk for the data

The sizes of the disks are described in Hardware and Software Requirements. Some configurations, such as the Cell environment, require multiple disks for the data.

You may verify the existence of the disks using the following command (e.g: look for sda, sdb and sdc):

lsblk

Mount points, file systems and logical volumes

DPOD requires specific mount points / file systems in the different disks.
See Table 1 below for the list of mount points / file systems and their sizes.
It is strongly recommended to use logical volume manager (LVM) - particularly for the data disk(s). See Example: Creating File Systems using LVM.
Once configured, you may verify the configuration using the following command:

lsblk

Tip: To use LVM in AWS EC2 instances with RHEL 8.x and EBS disks, first execute dnf install lvm2 to install the LVM package, and use gdisk to create a partition. For more information, see https://aws.amazon.com/premiumsupport/knowledge-center/create-lv-on-ebs-partition/.

Privileged user

The installation must be performed by the root user or by using sudo.

• Do not use script command during the login sequence to make a typescript of the terminal session for audit, as this will cause various scripts to hang.

• Do not use trap command to clear the terminal on session close, as this will cause various scripts to get extra characters as their input and fail.

• Do not print a disclaimer in .bashrc, as this will cause various scripts to get the disclaimer as their input and fail.

Non-privileged OS user and group

The DPOD services require a non-privileged dedicated OS user and group to run. Consider executing the following command:

groupadd dpodsvcg && useradd -g dpodsvcg -md /home/dpodsvc -s /bin/bash dpodsvc

OS locale

The supported OS locale is en_US.UTF-8. Check the OS Locale Configuration and change it if necessary.

Network requirements

Ensure you have at least one network interface installed and configured with full access to network services, such as DNS and NTP.
Some configurations, such as the Cell environment, require 2 network interfaces.
See Firewall Requirements for more details.

Setup DNS

It is highly recommended to setup DNS - your network admin may need to assist you with this action.

Using dnf on RedHat

For RedHat only: Your system might need to be registered and subscribed to the Red Hat Customer Portal to be able to install all prerequisites using dnf.
Registration and subscription may differ between organizations and RHEL versions, so consider the following commands just as an example:

subscription-manager register
subscription-manager attach --auto

• For RHEL 8.x

  subscription-manager repos --enable rhel-8-for-x86_64-baseos-rpms
  subscription-manager repos --enable rhel-8-for-x86_64-appstream-rpms

• For RHEL 9.x

  subscription-manager repos --enable=rhel-9-for-x86_64-baseos-rpms
  subscription-manager repos --enable=rhel-9-for-x86_64-appstream-rpms

Setup hosts file

Verify that the /etc/hosts file includes an entry with your server name mapped to your external server IP.
To display your server name, you may execute the command hostname.
To display your server’s IP address, you may execute the command ip a.

Required RPMs

Verify the existence of the following RPMs from the official Red Hat/Rocky Linux yum repositories:

• httpd version 2.4.6-67 and above (together with the following dependencies: mailcap, apr, httpd_tools)

• mod_ssl

• curl

• wget

• unzip

• initscripts

• xmlstarlet

• lz4

• jansson

• cjose

• chrony

• iptables-services

• bc

• fontconfig

• mailcap

• policycoreutils-python-utils

• numactl

• tuned

• nmon

• hiredis

The installation is usually performed by executing dnf. If the command fails to find the packages, you should manually download the RPM files and install them.

dnf install httpd
dnf install mod_ssl
dnf install curl
dnf install wget
dnf install unzip
dnf install initscripts
dnf install xmlstarlet
dnf install lz4
dnf install jansson
dnf install cjose
dnf install chrony
dnf install iptables-services
dnf install bc
dnf install fontconfig
dnf install mailcap
dnf install policycoreutils-python-utils
dnf install numactl
dnf install tuned
dnf install nmon
dnf install hiredis

The following RPMs are recommended for system maintenance and troubleshooting, and are optional: telnet client, net-tools, iftop, tcpdump, netcat

Ensure the httpd service is enabled and started by executing the command:

systemctl enable httpd.service && systemctl start httpd.service && systemctl status httpd.service

Disk 1: Operating System (e.g.: sda)

For this disk, use your organization’s standards for the operating system, or use the default sizes that are created automatically when the operating system is installed.

Disk 2: Application and Logs (e.g.: sdb)

/app

30 GB

LVM

XFS

/app/tmp

8 GB

LVM

XFS

/installs

30 GB

LVM

XFS

/logs

15 GB

LVM

XFS

/shared

1 GB

LVM

XFS

Data Disk(s) (e.g.: sdc, sdd, sde...)

/data

As described in Hardware and Software Requirements or according to the sizing spreadsheet in case one was provided by the DPOD support team. Minimum of 100 GB.

LVM

XFS

[Required only for cell members]
/data2, /data22, /data222, /data3, /data33, /data333, /data4, /data44, /data444

Only for cell members, according to the sizing spreadsheet provided by DPOD support team. See Setup a Cell Environment for information about these disks/mount points.

LVM

XFS