Confirming Server Configuration of the FineBI Project

App node: a single business node (not highly available)

DAU: 0 to 50 

Maximum rows in an analysis table: 0 to 5 million

Number of tables: 0 to 500

Note:

This scheme is intended for customers with minimal business usage only. All components of FineBI and FineOps are deployed on one server.

1. One main application server: 16-core CPU, 64 GB of memory, and 500 GB of disk space

It is used to deploy one FineBI - Application Node component, one Engine - Calculation Node component, one Engine - Metadata Node component, and one FineBI MinIO component.

It is used to deploy the following components:  Nginx, MySQL, Elasticsearch, and the cluster component.

It is used to deploy all FineOps components.

App node: a single business node (not highly available)

DAU: 0 to 300  

Maximum rows in an analysis table: 0 to 10 million

Number of tables: 0 to 2000

1. FineBI main application server: 16-core CPU, 64 GB of memory, and 500 GB of disk space

It is used to deploy one FineBI - Application Node component, one Engine - Calculation Node component, one Engine - Metadata Node component, and one FineBI MinIO component.             

2. Server for FineBI components and FineOps: 8-core CPU, 32 GB of memory, and 500 GB of disk space

It is used to deploy the following components:  Nginx, MySQL, Elasticsearch, and the cluster component.

It is used to deploy all FineOps components.

App node: a single business node (not highly available)

DAU: 0 to 600

Maximum rows in an analysis table: 0 to 100 million

Number of tables: 0 to 10 thousand

1. FineBI main application server: 32-core CPU, 128 GB of memory, and 2 TB of disk space

It is used to deploy one FineBI - Application Node component, one Engine - Calculation Node component, one Engine - Metadata Node component, and one FineBI MinIO component.          

2. Server for FineBI components and FineOps: 16-core CPU, 64 GB of memory, and 500 GB of disk space

It is used to deploy the following components:  Nginx, MySQL, Elasticsearch, and the cluster component.

It is used to deploy all FineOps components.

App node: multiple application nodes (highly available)

DAU: 0 to 600

Maximum rows in an analysis table: 0 to 10 million

Number of tables: 0 to 2000

1. FineBI main application server one: 16-core CPU, 64 GB of memory, and 500 GB of disk space

It is used to deploy one FineBI - Application Node component, one Engine - Calculation Node component, one Engine - Metadata Node component, and one FineBI MinIO component.

2. FineBI main application server two: 16-core CPU, 64 GB of memory, and 200 GB of disk space

It is used to deploy one FineBI - Application Node component and one Engine - Calculation Node component.

3. Server for FineBI components and FineOps: 8-core CPU, 32 GB of memory, and 500 GB of disk space

It is used to deploy the following components:  Nginx, MySQL, Elasticsearch, and the cluster component.

It is used to deploy all FineOps components.

App node: multiple application nodes (highly available)

DAU: 0 to 1200

Maximum rows in an analysis table: 0 to 100 million

Number of tables: 0 to 10 thousand

1. FineBI main application server one: 32-core CPU, 128 GB of memory, and 2 TB of disk space

It is used to deploy one FineBI - Application Node component, one Engine - Calculation Node component, one Engine - Metadata Node component, and one FineBI MinIO component.

2. FineBI main application server two: 32-core CPU, 128 GB of memory, and 500 GB of disk space

It is used to deploy one FineBI - Application Node component and one Engine - Calculation Node component.

3. Server for FineBI components and FineOps: 16-core CPU, 64 GB of memory, and 500 GB of disk space

It is used to deploy the following components:  Nginx, MySQL, Elasticsearch, and the cluster component.

It is used to deploy all FineOps components.

Component to be installed

It is used to install all components of FineBI and FineOps.

1. For details about the role of FineBI components, see Understanding the Roles of O&M Project Components.

Note:

1. You are advised to prepare and use the S3 service for data storage. 

2. If you use S3 to replace the data storage component FineBI MinIO and the file storage component MinIO, prepare at least two buckets to store the content of each component separately.

• FineBI - Application Node, Engine - Calculation Node, and Engine - Metadata Node

• FineBI MinIO (Self-provided S3 is recommended.)

• Filebeat, OPS Agent, and Nginx

• Elasticsearch (The self-provided service is recommended.)

• MinIO (The self-provided service is recommended.)

• MySQL (The self-provided service is recommended.)

• Redis (The self-provided service is recommended.)

2. For details about the role of FineOps components, see Understanding the Roles of FineOps Components.

Note:

If you have installed FineOps, skip this part. 

• OPS, Nginx, and OPS Agent

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and SkyWalking OAP

• Registry (The self-provided service is recommended.)

Supported:

Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) 

CentOS 7.3 to 7.9

Red Hat 7.6 and later releases 

Rocky Linux 8.8 to 9.4

Note:

1. Since CentOS is discontinued, you are advised to use Ubuntu. 

2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content.

CPU clock speed

Remaining free physical memory

64 GB   

Note:

Registration and authentication must be completed after project deployment.

• For the intranet environment that can be connected to the FanRuan cloud or the extranet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

• For the pure intranet environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration. 

The server shall have a partition with remaining free space of more than 500 GB.

Note:

There must be a single partition that meets the condition.

Disk type

If you have not prepared a data storage component, the FineBI MinIO component must be deployed, and the recommended disk type is XFS.

MinIO high-availability mode relies on the O_DIRECT feature, which is natively supported by the XFS file system. If you use an XFS-type disk, no additional operation is required when you scale MinIO for high availability in the future.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

The disk read/write speed must be greater than 100 MB/s, meaning the disk can handle at least 100 MB of data per second.

The random IOPS (4K) must be greater than 500, meaning the disk can perform at least 500 read/write operations on 4 KB data blocks per second.

Mounting directory preparation

For details, see FineBI Mounting Directory Preparation.

For details, see FineOps Mounting Directory Preparation.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has the tar command installed.

The tar command is a commonly used tool for packaging and compressing files.

FineOps requires this command for file extraction.

Ensure the server has the sed command installed.     

The sed command is used for text processing. 

FineOps requires this command for text processing.

Ensure the user you use can connect to the FineOps server via the SSH protocol.

Ensure the password used for SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

1. Using the root user (superuser) for project deployment and operation is preferred.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

On Ubuntu, the default root user is not a superuser. Ensure that the user privileges meet the requirements.

At least 1000 Mbps (125 MB/s)

Note:

You are advised to increase the intranet bandwidth accordingly if you need to add nodes to the project in the future.

Component-used port and component port interconnection

For details, see FineBI Server Network Confirmation.

For details, see FineOps Server Preparation.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Component to be installed

It is used to install the BI business and engine components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

Note:

1. You are advised to prepare and use the S3 service for data storage. 

2If you use S3 to replace the data storage component FineBI MinIO and the file storage component MinIO, prepare at least two buckets to store the content of each component separately.

• FineBI - Application Node

• Engine - Calculation Node

• Engine - Metadata Node

• FineBI MinIO (Self-provided S3 is recommended.)

• Filebeat

• OPS Agent

1. It is used to install the BI cluster, log, and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• Nginx

• Elasticsearch (The self-provided service is recommended.)

• MinIO (The self-provided service is recommended.)

• MySQL (The self-provided service is recommended.)

• Redis (The self-provided service is recommended.)

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of O&M Project Components. 

Note:

If you have installed FineOps, skip this part. 

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and SkyWalking OAP

• Registry (The self-provided service is recommended.)

• OPS Agent

The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds.

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Time zone consistency

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Supported:

Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) 

CentOS 7.3 to 7.9

Red Hat 7.6 and later releases 

Rocky Linux 8.8 to 9.4

Note:

1. Since CentOS is discontinued, you are advised to use Ubuntu. 

2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content.

CPU clock speed

Remaining free physical memory

64 GB   

32 GB  

Note:

Registration and authentication must be completed after project deployment.

• For the intranet environment that can be connected to the FanRuan cloud or the extranet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

• For the pure intranet environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration. 

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 300 GB (meaning that 200 GB of free disk space on the server is enough).

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB.

Disk type

If you have not prepared a data storage component, the FineBI MinIO component must be deployed, and the recommended disk type is XFS.

MinIO high-availability mode relies on the O_DIRECT feature, which is natively supported by the XFS file system. If you use an XFS-type disk, no additional operation is required when you scale MinIO for high availability in the future.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

If you have not prepared a file server, the MinIO component must be deployed, and the recommended disk type is XFS.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second.

Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second.

Mounting directory preparation

For details, see FineBI Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /, /usr, /root, /usr/local directories. You can create folders at these locations for mounting.

For details, see FineBI Mounting Directory Preparation.

For details, see FineOps Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /, /usr, /root, /usr/local directories. You can create folders at these locations for mounting.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has the tar command installed.                                               

The tar command is a commonly used tool for packaging and compressing files.

FineOps requires this command for file extraction.

Ensure the server has the sed command installed.     

The sed command is used for text processing. 

FineOps requires this command for text processing.

Ensure the password used for SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

1. Using the root user (superuser) for project deployment and operation is preferred.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

On Ubuntu, the default root user is not a superuser. Ensure that the user privileges meet the requirements.

Component-used port and component port interconnection

For details, see FineBI Server Network Confirmation.

For details, see FineOps Server Preparation.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Component to be installed

It is used to install the BI business and engine components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

Note:

1. You are advised to prepare and use the S3 service for data storage. 

2If you use S3 to replace the data storage component FineBI MinIO and the file storage component MinIO, prepare at least two buckets to store the content of each component separately.

• FineBI - Application Node

• Engine - Calculation Node

• Engine - Metadata Node

• FineBI MinIO (Self-provided S3 is recommended.)

• Filebeat

• OPS Agent

1. It is used to install the BI cluster, log, and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• Nginx

• Elasticsearch (The self-provided service is recommended.)

• MinIO (The self-provided service is recommended.)

• MySQL (The self-provided service is recommended.)

• Redis (The self-provided service is recommended.)

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components. 

Note:

If you have installed FineOps, skip this part. 

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and SkyWalking OAP

• Registry (The self-provided service is recommended.)

• OPS Agent

The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds.

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Time zone consistency

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Supported:

Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) 

CentOS 7.3 to 7.9

Red Hat 7.6 and later releases 

Rocky Linux 8.8 to 9.4

Note:

1. Since CentOS is discontinued, you are advised to use Ubuntu. 

2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content.

CPU clock speed

Remaining free physical memory

64 GB  

Note:

Registration and authentication must be completed after project deployment.

• For the intranet environment that can be connected to the FanRuan cloud or the extranet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

• For the pure intranet environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration.  

The server shall have a partition with remaining free space of more than 2 TB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 1.5 TB (meaning that 500 GB of free disk space on the server is enough).

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB.

Disk type

If you have not prepared a data storage component, the FineBI MinIO component must be deployed, and the recommended disk type is XFS.

MinIO high-availability mode relies on the O_DIRECT feature, which is natively supported by the XFS file system. If you use an XFS-type disk, no additional operation is required when you scale MinIO for high availability in the future.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

If you have not prepared a file server, the MinIO component must be deployed, and the recommended disk type is XFS.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second.

Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second.

Mounting directory preparation

For details, see FineBI Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /,/usr, /root, /usr/local directories. You can create folders at these locations for mounting.

For details, see FineBI Mounting Directory Preparation.

For details, see FineOps Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /, /usr, /root, /usr/local directories. You can create folders at these locations for mounting.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has the tar command installed.

The tar command is a commonly used tool for packaging and compressing files.

FineOps requires this command for file extraction.

Ensure the server has the sed command installed.     

The sed command is used for text processing. 

FineOps requires this command for text processing.

Ensure the password used for SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

1. Using the root user (superuser) for project deployment and operation is preferred.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

On Ubuntu, the default root user is not a superuser. Ensure that the user privileges meet the requirements.

Component-used port and component port interconnection

For details, see FineBI Server Network Confirmation.

For details, see FineOps Server Preparation.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Absence of Kingsoft Antivirus

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Component to be installed

It is used to install the BI business and engine components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

Note:

1. You are advised to prepare and use the S3 service for data storage. 

2If you use S3 to replace the data storage component FineBI MinIO and the file storage component MinIO, prepare at least two buckets to store the content of each component separately.

• FineBI - Application Node

• Engine - Calculation Node

• Engine - Metadata Node

• FineBI MinIO (Self-provided S3 is recommended.)

• Filebeat

• OPS Agent

It is used to install the BI business and engine components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineBI - Application Node

• Engine - Calculation Node

• Filebeat

• OPS Agent

1. It is used to install the BI cluster, log, and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• Nginx

• Elasticsearch (The self-provided service is recommended.)

• MinIO (The self-provided service is recommended.)

• MySQL (The self-provided service is recommended.)

• Redis (The self-provided service is recommended.)

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components. 

Note;

If you have installed FineOps, skip this part. 

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and SkyWalking OAP

• Registry (The self-provided service is recommended.)

• OPS Agent

The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds.

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Time zone consistency

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Supported:

Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) 

CentOS 7.3 to 7.9

Red Hat 7.6 and later releases 

Rocky Linux 8.8 to 9.4

Note:

1. Since CentOS is discontinued, you are advised to use Ubuntu. 

2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content.

CPU clock speed

Remaining free physical memory

32 GB  

Note:

Registration and authentication must be completed after project deployment.

• For the intranet environment that can be connected to the FanRuan cloud or the extranet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

• For the pure intranet environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration.

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 300 GB (meaning that 200 GB of free disk space on the server is enough).

The server shall have a partition with remaining free space of more than 200 GB.

Note:

There must be a single partition that meets the condition.

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB.

Disk type

If you have not prepared a data storage component, the FineBI MinIO component must be deployed, and the recommended disk type is XFS.

MinIO high-availability mode relies on the O_DIRECT feature, which is natively supported by the XFS file system. If you use an XFS-type disk, no additional operation is required when you scale MinIO for high availability in the future.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

If you have not prepared a file server, the MinIO component must be deployed, and the recommended disk type is XFS.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second.

Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second.

Mounting directory preparation

For details, see FineBI Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /,/usr, /root, /usr/local directories. You can create folders at these locations for mounting.

For details, see FineBI Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /,/usr, /root, /usr/local directories. You can create folders at these locations for mounting.

For details, see FineBI Mounting Directory Preparation.

For details, see FineOps Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /, /usr, /root, /usr/local directories. You can create folders at these locations for mounting.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has the tar command installed.                  

The tar command is a commonly used tool for packaging and compressing files.

FineOps requires this command for file extraction.

Ensure the server has the sed command installed.     

The sed command is used for text processing. 

FineOps requires this command for text processing.

Ensure the password used for SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

1. Using the root user (superuser) for project deployment and operation is preferred.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

On Ubuntu, the default root user is not a superuser. Ensure that the user privileges meet the requirements.

Component-used port and component port interconnection

For details, see FineBI Server Network Confirmation.

For details, see FineOps Server Preparation.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Absence of Kingsoft Antivirus

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Component to be installed

It is used to install the BI business and engine components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

Note:

1. You are advised to prepare and use the S3 service for data storage. 

2If you use S3 to replace the data storage component FineBI MinIO and the file storage component MinIO, prepare at least two buckets to store the content of each component separately.

• FineBI - Application Node

• Engine - Calculation Node

• Engine - Metadata Node

• FineBI MinIO (Self-provided S3 is recommended.)

• Filebeat

• OPS Agent

It is used to install the BI business and engine components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineBI - Application Node

• Engine - Calculation Node

• Filebeat

• OPS Agent

1. It is used to install the BI cluster, log, and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• Nginx

• Elasticsearch (The self-provided service is recommended.)

• MinIO (The self-provided service is recommended.)

• MySQL (The self-provided service is recommended.)

• Redis (The self-provided service is recommended.)

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components. 

Note:

If you have installed FineOps, skip this part. 

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and SkyWalking OAP

• Registry (The self-provided service is recommended.)

• OPS Agent

The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds.

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Time zone consistency

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

Supported:

Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) 

CentOS 7.3 to 7.9

Red Hat 7.6 and later releases 

Rocky Linux 8.8 to 9.4

Note:

1. Since CentOS is discontinued, you are advised to use Ubuntu. 

2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content.

CPU clock speed

Remaining free physical memory

64 GB  

Note:

Registration and authentication must be completed after project deployment.

• For the intranet environment that can be connected to the FanRuan cloud or the extranet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

• For the pure intranet environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration. 

The server shall have a partition with remaining free space of more than 2 TB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 1.5 TB (meaning that 500 GB of free disk space on the server is enough).

The server shall have a partition with remaining free space of more than 500 GB.

Note:

There must be a single partition that meets the condition.

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB.

Disk type

If you have not prepared a data storage component, the FineBI MinIO component must be deployed, and the recommended disk type is XFS.

MinIO high-availability mode relies on the O_DIRECT feature, which is natively supported by the XFS file system. If you use an XFS-type disk, no additional operation is required when you scale MinIO for high availability in the future.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

If you have not prepared a file server, the MinIO component must be deployed, and the recommended disk type is XFS.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second.

Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server.

The disk should at least be a SATA solid-state drive (SSD).

The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second.

The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second.

Mounting directory preparation

For details, see FineBI Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /,/usr, /root, /usr/local directories. You can create folders at these locations for mounting.

For details, see FineBI Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /,/usr, /root, /usr/local directories. You can create folders at these locations for mounting.

For details, see FineBI Mounting Directory Preparation.

For details, see FineOps Mounting Directory Preparation.

Note:

It is forbidden to mount projects/FineOps in /, /usr, /root, /usr/local directories. You can create folders at these locations for mounting.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has the tar command installed.                        

The tar command is a commonly used tool for packaging and compressing files.

FineOps requires this command for file extraction.

Ensure the server has the sed command installed.     

The sed command is used for text processing. 

FineOps requires this command for text processing.

Ensure the password used for SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

1. Using the root user (superuser) for project deployment and operation is preferred.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

On Ubuntu, the default root user is not a superuser. Ensure that the user privileges meet the requirements.

Component-used port and component port interconnection

For details, see FineBI Server Network Confirmation.

For details, see FineOps Server Preparation.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Absence of Kingsoft Antivirus

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

FineBI - Application Node

Server memory/4 

64 GB at most

5/8 Container memory - 2 

32766 MB at most

Server memory/2/Engine - Calculation Node component count 

64 GB at most

5/8 Container memory -10/7 

32766 MB at most

Server memory/8 

64 GB at most

It should scale with the container memory usage limit.

If the container memory usage limit is less than 8 GB, set the Xmx value to 2420 MB.

If the container memory usage limit is less than 16 GB, set the Xmx value to 4100 MB.

If the container memory usage limit is less than 32 GB, set the Xmx value to 9400 MB.

If the container memory usage limit is at least 32 GB, set the Xmx value to 18800 MB. 

Server memory/8

64 GB at most

Filebeat