New Project Deployment

1. To ensure the stability of the stored cluster log:

• The elasticsearch suite must be installed during the containerized deployment of a cluster, no longer an optional installation item.

• Install the filebeat component on each project node when installing elasticsearch.

2. A help folder is created in the mounting directory of the project during deployment.

1. The restrictions on project names are relaxed by supporting English uppercase and Chinese characters.

2. Support the use of external shared directories as file servers for deploying new clusters.

3) The access path in the project configuration can be empty.

1. Filling in an extranet IP address is supported in the node configuration to adapt to servers where intranet access is only supported when the intranet IP address is mapped to an extranet IP address.

2. Suspending deployment is supported to stop the deployment and remove the operations made.

3. For deployed FineBI components, the default limit of Xmx is increased to reduce the risk of out-of-memory (OOM) kill error.

• Before optimization: default value of Xmx = machine memory minus 8 GB

• After optimization: default value of Xmx  = machine memory minus 10 GB

1. The resource requirements are lowered as the node_exporter, nginx_exporter, and elasticsearch_exporter components are deleted, whose functions are merged into the ops-agent component, which can be used to collect the indicator information of the server and components.

2. The nginx component is deployed by default during standalone deployment to facilitate the subsequent SSL configuration and capacity expansion.

1. The number of application servers of FineOps-deployed projects is limited, with 5 nodes as the upper limit.

2. FineOps-deployed clusters support the deployment of clustered nginx components, as the LAN side gateway.

3. The operation area for configuring component ports is adjusted to optimize the interaction of deploying a new project, avoiding missing configuration checks.

The log service component supports the self-prepared Elasticsearch of 7.10 and above versions.

Added Environment Check to check the deployment environment and provide prompts.

FineOps deployment

Deploy FineOps.

FanRuan applications rely on FineOps for deployment, which should be deployed in advance.

1. Know various types of O&M projects.

FanRuan provides multiple products including FineBI, FineReport, and FineDataLink. Confirm the required product type.

2. Understand the role of each component of O&M projects.

The projects deployed by FineOps include projects, supporting external configuration databases, clustered components, O&M components, and so on. Understand the role of each component and determine whether to install them.

• For FineBI:

Confirm the number of FineBI nodes.

Confirm the server configuration of the FineBI project. 

Confirm the server network of the FineBI project.

Prepare the mounting directory of the FineBI project.

• For FineReport:

Confirm the number of FineReport nodes.

Confirm the server configuration of the FineReport project. 

Confirm the server network of the FineReport project. 

Prepare the mounting directory of the FineReport project.

• For FineDataLink:

Confirm the server configuration of the FineDataLink project. 

Confirm the server network of the FineDataLink project. 

Prepare the mounting directory of the FineDataLink project.

Confirm that the image repository supports the connection to the FanRuan cloud repository.

Images are required to deploy components in a new project. Ensure that it is supported to pull images from the cloud or prepare images in the image repository.

FineOps Xmx configuration

Integrating projects with FineOps may consume some FineOps server resources. 

The new project cannot be deployed if the configured FineOps resources are insufficient. It will prompt "The FineOps configuration has reached the upper limit, and no new projects are supported. Proceed as follows as soon as possible: Increase the Xmx value."

1. Choose Platform Management > O&M Component, and click the Modify Configuration button of the ops component. 

2. Configure the Xmx value as prompted to ensure the new project can be deployed.

You can customize the project name.

The project name cannot be empty.

Only Chinese characters, English letters (upper and lower cases), and numbers are supported.

The project name length cannot exceed 12 digits.

The project name cannot be duplicated with an existing project name.

FineOps V2.7.1 and earlier releases support FineReport, FineBI6.1, and FineDataLink projects.

A single FineReport/FineDataLink project can have one to five application service(s) deployed via FineOps.

For a FineBI6.1 project, a master component must be deployed. The application services include BI applications and worker components, with a mandatory 1:1 or 1:2 ratio to balance the project.

The access link of the application is domain name/IP address/path/decision.

You can customize the path to access the application, which defaults to webroot.

Note: To access the project through a short domain name or IP address, you must keep Path empty. The configuration cannot be changed once the project is successfully deployed. The access path of the root directory corresponding to the project is http://IP address:port number/root.

Basic Component

You can choose the components to install and decide whether to deploy FanRuan-prepared components and whether to access user-prepared components. The components that must be installed are not included here.

Select Main Application.

Note: The FanRuan project requires an exclusive server. You are advised not to deploy other projects or contents, including FineOps on a main application server.

Enter the host IP address (intranet IP address) of the node.

Note: You cannot add a host repetitively to the same project. 

Enter a server username with sudo permissions.

The supported verification methods include Password and Public Key.

Enter the node installation directory on the server, which is the mounting directory set in the pre-preparation phase.

The default directory is ~/data, which is the data folder in the home directory of the server being used.

Note: You can use the user account to access the server in the terminal, and enter the echo $HOME command to view the home directory.

Optional

If the server does not support intranet access unless the intranet IP address is mapped to an extranet IP address, you must fill in a connectable extranet IP address.

Select Component.

Note 1: If multiple component nodes are configured, the components are randomly deployed on these nodes.

Note: The FanRuan project requires an exclusive server. You are advised not to deploy other projects or contents, including FineOps on a component server.

Enter the host IP address (intranet IP address) of the node.

Note: You cannot add a host repetitively to the same project.

Enter a server username with sudo permissions.

The supported verification methods include Password and Public Key.

Enter the node installation directory on the server, which is the mounting directory set in the pre-preparation phase.

The default directory is ~/data, which is the data folder in the home directory of the server being used.

Note: You can use the user account to access the server in the terminal, and enter the echo $HOME command to view the home directory.

Optional

If the server does not support intranet access unless the intranet IP address is mapped to an extranet IP address, you can fill in a connectable extranet IP address.