Page Comparison

Operating system version

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 usually 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 number of disks and sizes are described in the Hardware and Software Requirements. Some configurations, such as the Cell environment, requiremultiple disks for the data, while others, such as the Developer Edition, require only one.

You may verify the number of installed 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 each disk. It is strongly recommended to use logical volume manager (LVM) - particularly for the data disk(s).
See Table 1 below for the list of mount points / file systems and their sizes.
See Example: Creating File Systems using LVM for creating the mount points / file systems via the command line.
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 a user capable of running the sudo command.

• 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 using the following example:

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

OS locale

The OS locale must be configured to en_US.UTF-8. You may verify the OS locale using the following command:

localectl status

If the locale is not en_US.UTF-8, set the locale using the following command:

localectl set-locale LANG=en_US.UTF-8

Network interfaces and firewall

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.

DNS

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

Hosts file

Verify that the /etc/hosts file includes an entry with your server name mapped to your external server IP address (the IP address used to access the Web Console).
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.

Using dnf on RHEL

If you are using Red Hat Enterprise Linux (RHEL), 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 as an example:

subscription-manager register
subscription-manager attach --auto

• For RHEL 8.x:

  Code Block
  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:

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

Packages (RPMs)

Make sure the following packages (RPMs) are installed and up-to-date from the official Red Hat/Rocky Linux repositories:
bc, chrony, cjose, curl, fontconfig, hiredis, httpd, initscripts, jansson, lz4, mailcap, mod_ssl, nmon, numactl, policycoreutils-python-utils, tuned, unzip, wget, xmlstarlet.

Note: The EPEL repository (e.g.: dnf install epel-release) may be required to install the packages hiredis and nmon.

The installation is usually performed by executing dnf:

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

If the command fails to find the packages, you may manually download the RPM files and install them.

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

Web server (httpd)

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

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