FineOps Version
Functional Change
After an Nginx component was added, forwarding was automatically configured, so you no longer needed to manually modify nginx.conf.
After a project is deployed, you may want to add or scale project components. Select a solution based on your scenario.
Application scenario:
You need to convert a FineBI 6.0, FineReport 11.0, or FineDataLink 4.1 project from a single-node application to a multi-node cluster.
Solution overview:
1. First, switch the standalone application to a single-node cluster. For details, see Converting a Containerized Standalone to a Cluster.
Install cluster components such as Nginx, MinIO, and Redis.
2. Then scale the single-node cluster to a multi-node cluster based on this document.
Install business components such as FineBI - Application Node, FineReport, and FineDataLink.
Some components may not have been deployed during the initial project deployment, and you later need to use them. For example:
If you did not select Nginx during standalone deployment, you must add Nginx to configure SSL.
If you did not select Elasticsearch during standalone deployment, you must add Elasticsearch to replace Swift (LogDB) for log storage.
Refer to this document.
Only Nginx is automatically connected to the project after it is added. You need to manually connect other components after they have been deployed.
The Add Component function is usually used when you convert a standalone application to a cluster. See the first scenario.
As business usage grows, the existing cluster configuration may no longer support service needs. You need to add business nodes or compute workers, such as scaling a two-node cluster to a three-node cluster.
For security reasons, you may need to scale an existing single-node internal gateway to two nodes to ensure high availability.
Use the Scale function to scale the number of containers of a component from 1 to X. For details, see Scaling Components for Cluster Projects.
Add main application nodes to increase the number of business component instances, such as bi-web, bi6, fr, and fdl.
Increase the number of bi-engine-worker instances. They can be deployed on existing main application nodes.
Scale the Nginx component from one node to a multi-node cluster. It can be deployed on existing main application nodes or component nodes.
This document describes the "Add a component" scenario.
The image repository must contain the image of the target component. If the image is missing, the component cannot be deployed.
For details, see Ensuring Access to FanRuan Cloud Repository.
The AI service, FVS Task Schedule, and Fine Canvas are supported only for specified products and versions, as follows:
AI: FineOps V2.20.0 or later and FineBI 6.1.6 or later.
FVS Task Schedule: FineOps V2.23.0 or later, and FineReport or FineBI projects.
Fine Canvas: FineOps V2.26.0 or later and FineBI 7.0 projects.
1. Log in to FineOps as an admin, select the target project, choose Maintenance > Component Management, and click Add Component.
If Add Component is not displayed, the project deployment method does not meet the requirement or no components need to be added.
2. Select the component to add.
Before selecting a component, confirm its purpose. For details, see Understanding Roles of O&M Project Components.
After Nginx is added, FineOps automatically configures forwarding. After other components are deployed, manually connect them to the project.
3. Select the node on which you want to deploy the component.
The system validates nodes based on the following rules. Nodes that do not meet the requirements are grayed out, and the reason is displayed.
The node passes validation when its available resources reach 7/8 of the estimated required resources of the component.
For example, if the component is estimated to require 8 GB of memory, deployment is allowed when the node has 7 GB of available memory.
If no available node exists, click Add Node and add a server.
For server configuration requirements, see the "Preparation" section in New Project Deployment.
For node-adding configurations, see the "Node Configuration-Adding Component Node" section in New Project Deployment.
After the node is connected, FineOps automatically sets up the Docker environment, deploys OPS Agent, and sets up monitoring. You can then select this node to deploy the component.
4. Adjust component configurations.
You can modify host ports, passwords, and other information as needed.
Before deployment, modify and properly save the passwords of bi-minio, mysql, redis, minio, elasticsearch, nacos, and nacos_mysql.
The default passwords of these components are randomly generated and are uneditable after deployment succeeds.
5. After confirming the component, node, and configurations, click Start Deployment.
6. View the deployment progress.
After deployment starts, progress is displayed on the page. You can click Run in Background and perform other operations. After deployment is complete, the message "The component was deployed successfully." is displayed.
Return to Component Management. The newly deployed component is displayed and starts by default. Wait until the container status changes to running, which means the component has been added successfully.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy