Pre-deployment checks

更新时间:
复制 MD 格式

Before you install a privacy computing node, you must check the node environment. This topic describes the required machine configurations and server operations.

Machine configuration recommendations

This section provides recommendations for machine configurations, including single-node resource configurations and operating system requirements.

Single-node resource configuration

The following table lists the resource configuration requirements for a single privacy computing node.

Service

Node environment

Node type

Server configuration

Quantity

Notes

MPC

Test

Training node

8-core 16 GB, with 500 GB or more of disk space

1

If you want to perform parallel training for multiple models, add more machines.

Prediction node

1

-

Production

Training node

1

If the feature dimension is 100 or more, upgrade the configuration.

Prediction node

≥2

-

FL

Test

Training node

1

-

Production

Training node

≥1

-

SCQL

Test

Analysis node

1

-

Production

Analysis node

≥1

-

PSI

Test

Analysis node

1

-

Production

Analysis node

≥1

-

Operating system requirements

The server's operating system must be CentOS Linux release 7.5 or later. If you use a different operating system version, contact the helpdesk to confirm whether the operating system is supported.

Server operations

Log on to the node server to sync the system time, install dependencies, and manage users. The procedure is as follows:

  1. On the node client, confirm that the system time is synchronized. If the system time is not synchronized, manually calibrate it or use the Network Time Protocol (NTP) service to calibrate it automatically.

  2. Run the following command to install the required dependencies.

    yum install -y docker docker-compose
  1. If you install the node as a regular user, add the user to the docker group. The procedure is as follows:

    1. Run the following command to create the docker group.

      groupadd docker
    2. Run the following command to restart the Docker service.

      systemctl restart docker
    3. Run the following command to view information about the docker.sock file.

      ls -l /var/run/docker.sock

      The command returns a message similar to the following. Confirm that the user group for the /var/run/docker.sock file is docker.

      srw-rw---- 1 root docker 0 Mar 23 17:20 /var/run/docker.sock
    4. Run the following command to add the regular user to the docker group. Replace ${USER} with the username of the regular user.

      usermod -a -G docker ${USER}