DAOS Set-Up on RHEL and Clones¶
The following instructions detail how to install, set up and start DAOS servers and clients on two or more nodes. This document includes instructions for EL8 and CentOS 7. The process is identical for CentOS Linux 7 and EL 8, except for the location of the DAOS RPM repository. For setup instructions on OpenSuse, refer to OpenSuse setup.
For more details, including the prerequisite steps before installing DAOS, reference the DAOS administration guide.
Requirements¶
The following steps require two or more hosts which will be divided up into admin, client, and server roles. One node can be used for multiple roles. For example the admin role can reside on a server, on a client, or on a dedicated admin node.
All nodes must have:
-
sudo access configured
-
password-less ssh configured
-
pdsh installed (or some other means of running multiple remote commands in parallel)
In addition the server nodes should also have IOMMU enabled.
For the use of the commands outlined on this page the following shell variables will need to be defined:
- ADMIN_NODES
- CLIENT_NODES
- SERVER_NODES
- ALL_NODES
For example, if you want to use admin-1 as the admin node, client-1 and client-2 as client nodes, and server-[1-3] as server nodes, these variables would be defined as:
ADMIN_NODES="admin-1"
CLIENT_NODES="client-1,client-2"
SERVER_NODES="server-1,server-2"
ALL_NODES="$ADMIN_NODES,$CLIENT_NODES,$SERVER_NODES"
Note
If a client node is also serving as an admin node, exclude
$ADMIN_NODES from the ALL_NODES assignment to prevent duplication.
For example: ALL_NODES=$CLIENT_NODES,$SERVER_NODES
RPM Installation¶
In this section the required RPMs will be installed on each of the nodes based upon their role. Admin and client nodes require the installation of the daos-client RPM and the server nodes require the installation of the daos-server RPM.
-
Configure access to the DAOS package repository, using the subdirectory that matches the EL/CentOS version of the nodes:
For CentOS7:
pdsh -w $ALL_NODES 'sudo wget -O /etc/yum.repos.d/daos-packages.repo https://packages.daos.io/v2.2/CentOS7/packages/x86_64/daos_packages.repo'For EL8:
pdsh -w $ALL_NODES 'sudo wget -O /etc/yum.repos.d/daos-packages.repo https://packages.daos.io/v2.2/EL8/packages/x86_64/daos_packages.repo' -
Import GPG key on all nodes:
pdsh -w $ALL_NODES 'sudo rpm --import https://packages.daos.io/RPM-GPG-KEY' -
Install epel-release on all nodes:
pdsh -w $ALL_NODES 'sudo yum install -y epel-release' -
Install the
daos-adminRPMs on the admin nodes:pdsh -w $ADMIN_NODES 'sudo zypper install -y daos-admin' -
Install the
daos-serverRPMs on the server nodes:pdsh -w $SERVER_NODES 'sudo yum install -y daos-server' -
Install the
daos-clientRPMs on the client nodes:pdsh -w $CLIENT_NODES 'sudo yum install -y daos-client'
Hardware Provisioning¶
In this section, PMem (Intel(R) Optane(TM) persistent memory) and NVME SSDs will be prepared and configured to be used by DAOS.
-
Prepare the pmem devices on Server nodes:
daos_server storage prepare --scm-onlySample Script:
Preparing locally-attached SCM... Memory allocation goals for SCM will be changed and namespaces modified, this will be a destructive operation. Please ensure namespaces are unmounted and locally attached SCM & NVMe devices are not in use. Please be patient as it may take several minutes and subsequent reboot maybe required. Are you sure you want to continue? (yes/no) yes A reboot is required to process new SCM memory allocation goals. -
Reboot the server node.
-
Run the prepare cmdline again:
daos_server storage prepare --scm-onlySample Script:
Preparing locally-attached SCM... SCM namespaces: SCM Namespace Socket ID Capacity ------------- --------- -------- pmem0 0 3.2 TB pmem1 0 3.2 TB -
Prepare the NVME devices on Server nodes:
daos_server storage prepare --nvme-only -u root Preparing locally-attached NVMe storage... -
Scan the available storage on the Server nodes:
daos_server storage scan Scanning locally-attached storage... NVMe PCI Model FW Revision Socket ID Capacity -------- ----- ----------- --------- -------- 0000:81:00.0 INTEL SSDPE2KE016T8 VDV10170 0 1.6 TB 0000:83:00.0 INTEL SSDPE2KE016T8 VDV10170 1 1.6 TB SCM Namespace Socket ID Capacity ------------- --------- -------- pmem0 0 3.2 TB pmem1 1 3.2 TB
Generate certificates¶
In this section certificates will be generated and installed for encrypting the DAOS control plane communications.
Administrative nodes require the following certificate files:
-
CA root certificate (daosCA.crt) owned by the current user
-
Admin certificate (admin.crt) owned by the current user
-
Admin key (admin.key) owned by the current user
Client nodes require the following certificate files:
-
CA root certificate (daosCa.crt) owned by the current user
-
Agent certificate (agent.crt) owned by the daos_agent user
-
Agent key (agent.key) owned by the daos_agent user
Server nodes require the following certificate files:
-
CA root certificate (daosCA.crt) owned by the daos_server user
-
Server certificate (server.crt) owned by the daos_server user
-
Server key (server.key) owned by the daos_server user
-
A copy of the Client certificate (client.crt) owned by the daos_server user
See Certificate Configuration for more information.
Note
The following commands are run on one of the $ADMIN_NODES.
-
Generate a new set of certificates:
cd /tmp /usr/lib64/daos/certgen/gen_certificates.shNote
These files should be protected from unauthorized access and preserved for future use.
-
Copy the certificates to a common location on each node in order to move them to the final location:
pdsh -S -w $ALL_NODES -x $(hostname -s) scp -r $(hostname -s):/tmp/daosCA /tmp -
Copy the certificates to their default location (/etc/daos) on each admin node:
pdsh -S -w $ADMIN_NODES sudo cp /tmp/daosCA/certs/daosCA.crt /etc/daos/certs/. pdsh -S -w $ADMIN_NODES sudo cp /tmp/daosCA/certs/admin.crt /etc/daos/certs/. pdsh -S -w $ADMIN_NODES sudo cp /tmp/daosCA/certs/admin.key /etc/daos/certs/.Note
If the /etc/daos/certs directory does not exist on the admin nodes then use the following command to create it:
pdsh -S -w $ADMIN_NODES sudo mkdir /etc/daos/certs -
Copy the certificates to their default location (/etc/daos) on each client node:
pdsh -S -w $CLIENT_NODES sudo cp /tmp/daosCA/certs/daosCA.crt /etc/daos/certs/. pdsh -S -w $CLIENT_NODES sudo cp /tmp/daosCA/certs/agent.crt /etc/daos/certs/. pdsh -S -w $CLIENT_NODES sudo cp /tmp/daosCA/certs/agent.key /etc/daos/certs/.Note
If the /etc/daos/certs directory does not exist on the client nodes, use the following command to create it:
pdsh -S -w $CLIENT_NODES sudo mkdir /etc/daos/certs -
Copy the certificates to their default location (/etc/daos) on each server node:
pdsh -S -w $SERVER_NODES sudo cp /tmp/daosCA/certs/daosCA.crt /etc/daos/certs/. pdsh -S -w $SERVER_NODES sudo cp /tmp/daosCA/certs/server.crt /etc/daos/certs/. pdsh -S -w $SERVER_NODES sudo cp /tmp/daosCA/certs/server.key /etc/daos/certs/. pdsh -S -w $SERVER_NODES sudo cp /tmp/daosCA/certs/agent.crt /etc/daos/certs/clients/agent.crt -
Cleanup the temp directory
pdsh -S -w $ALL_NODES sudo rm -rf /tmp/daosCA -
Set the ownership of the admin certificates on each admin node:
pdsh -S -w $ADMIN_NODES sudo chown $USER:$USER /etc/daos/certs/daosCA.crt pdsh -S -w $ADMIN_NODES sudo chown $USER:$USER /etc/daos/certs/admin.\* -
Set the ownership of the client certificates on each client node:
pdsh -S -w $CLIENT_NODES sudo chown $USER:$USER /etc/daos/certs/daosCA.crt pdsh -S -w $CLIENT_NODES sudo chown daos_agent:daos_agent /etc/daos/certs/agent.\* -
Set the ownership of the server certificates on each server node:
pdsh -S -w $SERVER_NODES sudo chown daos_server:daos_server /etc/daos/certs/daosCA.crt pdsh -S -w $SERVER_NODES sudo chown daos_server:daos_server /etc/daos/certs/server.\* pdsh -S -w $SERVER_NODES sudo chown daos_server:daos_server /etc/daos/certs/clients/agent.crt pdsh -S -w $SERVER_NODES sudo chown daos_server:daos_server /etc/daos/certs/clients
Create Configuration Files¶
In this section the daos_server, daos_agent, and dmg command configuration files will be defined.
Examples are available on github.
-
Determine the addresses for the NVMe devices on the server nodes:
pdsh -S -w $SERVER_NODES sudo lspci | grep -i nvmeNote
Save the addresses of the NVMe devices to use with each DAOS server, e.g. \"81:00.0\", from each server node. This information will be used to populate the \"bdev_list\" server configuration parameter below.
-
Create a server configuration file by modifying the default
/etc/daos/daos_server.ymlfile on the server nodes.An example of the daos_server.yml is presented below. Copy the modified server yaml file to all the server nodes at `/etc/daos/daos_server.yml.
name: daos_server access_points: - server-1 port: 10001 transport_config: allow_insecure: false client_cert_dir: /etc/daos/certs/clients ca_cert: /etc/daos/certs/daosCA.crt cert: /etc/daos/certs/server.crt key: /etc/daos/certs/server.key provider: ofi+verbs;ofi_rxm control_log_mask: DEBUG control_log_file: /tmp/daos_server.log helper_log_file: /tmp/daos_admin.log engines: - pinned_numa_node: 0 targets: 8 nr_xs_helpers: 2 fabric_iface: ib0 fabric_iface_port: 31316 log_mask: INFO log_file: /tmp/daos_engine_0.log env_vars: - CRT_TIMEOUT=30 storage: - class: dcpm scm_mount: /mnt/daos0 scm_list: - /dev/pmem0 - class: nvme bdev_list: - "0000:81:00.0" - pinned_numa_node: 1 targets: 8 nr_xs_helpers: 2 fabric_iface: ib1 fabric_iface_port: 31416 log_mask: INFO log_file: /tmp/daos_engine_1.log env_vars: - CRT_TIMEOUT=30 storage: - class: dcpm scm_mount: /mnt/daos1 scm_list: - /dev/pmem1 - class: nvme bdev_list: - "0000:83:00.0" -
Copy the modified server yaml file to all the server nodes at
/etc/daos/daos_server.yml. -
Create an agent configuration file by modifying the default
/etc/daos/daos_agent.ymlfile on the client nodes. The following is an exampledaos_agent.yml. Copy the modified agent yaml file to all the client nodes at/etc/daos/daos_agent.yml.name: daos_server access_points: - server-1 port: 10001 transport_config: allow_insecure: false ca_cert: /etc/daos/certs/daosCA.crt cert: /etc/daos/certs/agent.crt key: /etc/daos/certs/agent.key log_file: /tmp/daos_agent.log -
Create a dmg configuration file by modifying the default
/etc/daos/daos_control.ymlfile on the admin node. The following is an example of thedaos_control.yml.name: daos_server port: 10001 hostlist: - server-1 - server-2 transport_config: allow_insecure: false ca_cert: /etc/daos/certs/daosCA.crt cert: /etc/daos/certs/admin.crt key: /etc/daos/certs/admin.key
Start the DAOS Servers¶
-
Start daos engines on server nodes:
pdsh -S -w $SERVER_NODES "sudo systemctl daemon-reload" pdsh -S -w $SERVER_NODES "sudo systemctl start daos_server" -
Check status and format storage:
# check status pdsh -S -w $SERVER_NODES "sudo systemctl status daos_server" # if you see following format messages (depending on number of servers), proceed to storage format server-1: Dec 16 00:12:11 server-1.test.hpdd.intel.com daos_server[290473]: SCM format required on instance 1 server-1: Dec 16 00:12:11 server-1.test.hpdd.intel.com daos_server[290473]: SCM format required on instance 0 # format storage dmg storage format -l $SERVER_NODES # can use --force if needed -
Verify that all servers have started:
# system query from ADMIN_NODES dmg system query -v # all the server ranks should show 'Joined' STATE Rank UUID Control Address Fault Domain State Reason ---- ---- --------------- ------------ ----- ------ 0 604c4ffa-563a-49dc-b702-3c87293dbcf3 10.8.1.179:10001 /server-1.test.hpdd.intel.com Joined 1 f0791f98-4379-4ace-a083-6ca3ffa65756 10.8.1.179:10001 /server-1.test.hpdd.intel.com Joined 2 745d2a5b-46dd-42c5-b90a-d2e46e178b3e 10.8.1.189:10001 /server-2.test.hpdd.intel.com Joined 3 ba6a7800-3952-46ce-af92-bba9daa35048 10.8.1.189:10001 /server-2.test.hpdd.intel.com Joined
Start the DAOS Agents¶
-
Start the daos agents on the client nodes:
# start agents pdsh -S -w $CLIENT_NODES "sudo systemctl start daos_agent" -
(Optional) Check daos_agent status:
# check status pdsh -S -w $CLIENT_NODES "cat /tmp/daos_agent.log" # Sample output depending on number of client nodes client-1: agent INFO 2022/05/05 22:38:46 DAOS Agent v2.2 (pid 47580) listening on /var/run/daos_agent/daos_agent.sock client-2: agent INFO 2022/05/05 22:38:53 DAOS Agent v2.2 (pid 39135) listening on /var/run/daos_agent/daos_agent.sock