Converting a Containerized Standalone to a Cluster

Version

Application Scenario

As project usage increases, a standalone project may fail to meet the demand, requiring additional project nodes and related cluster components to ensure stable project operation.

This document describes how to expand a containerized standalone project into a single-node cluster.

Note:

If the original standalone project was not configured with an Nginx component, the project URL will change after expansion, with the IP address and port number in the URL changing to those of Nginx by default.

Note:

Read the entire document first to understand the overall steps before proceeding.

Selecting the Project

1. Log in to FineOps as the admin, and choose Maintenance Center > Structural Change > Standalone-to-Cluster Conversion.

2. Selectable projects include standalone projects that are connected to FineOps or deployed via FineOps.

Note:

1. The project type must be standalone. That is, the project is not connected to a state server or a file server.

2. The project must be deployed via FineOps. The following operations do not apply to projects not deployed via FineOps.

3. The main application type and version should be FineBI 6.0.x, FineReport 11.0.x, or FineDataLink 4.1.x. (FineBI 6.1.x is not supported because all FineOps-deployed FineBI 6.1.x projects are cluster projects.)

Preparing Cluster Ports for the Main Application Node

Description

Compared with a standalone project, the nodes in a cluster project require additional ports for inter-node communication, data synchronization, and other purposes.

Therefore, you (the admin) need to prepare cluster ports on the server where the FineBI 6 - Application Node/FineReport/FineDataLink component is located. The following table lists the default required ports.

If any of these ports are already in use, prepare other available ports. For details about port occupancy inspection, see Port Occupancy Inspection and Firewall Configuration.

Configuration

Click Configuration in Cluster Port. You can confirm port configuration or modify ports to the available ports in the Cluster Port Configuration pop-up.

Preparing Component Nodes for Deploying Cluster Components

Standalone-to-cluster conversion requires essential cluster components, including the file server, the state server, and the FanRuan internal gateway.

You must determine whether to install components and prepare servers or not by strictly following the steps sequentially.

Note:

The solution in this document only supports containerized cluster components. Scaling with self-provided cluster components is not supported.

To use self-provided cluster components, connect FineOps to them under Project Management > Maintenance > Cluster Management after the standalone-to-cluster conversion. 

Confirming Whether New Components Need to Be Deployed

If Component Node and Component Configuration do not appear after you select a project, no new components need to be installed. You can proceed to the "Starting Conversion" section.

This situation means that an admin has previously deployed all necessary cluster components via Add Component under Project Management > Maintenance > Component Management. You only need to start the structural change.

Selecting the Component Node

If Component Node and Component Configuration appear, it means some cluster components require installation.

Select the project node where you want to deploy the components from the dropdown list of Component Node.

• If a project has a component node, the main application nodes will be grayed out and unselectable. Hovering over the main application node will trigger a prompt: "Incorrect node type."

• If the CPU/memory resources on the node server fail to satisfy the default total resource requirements of the component to be installed, the node will be grayed out and unselectable. Hovering over the node will trigger a prompt: "The available memory on the current node is insufficient."

Note:

1. If no available nodes exist, you can prepare additional servers and add them to the project by clicking Add Node.

• For details about server configuration requirements, see the "Preparation" section of New Project Deployment.

• For details about the configuration during node adding, see the "Node Configuration - Adding Component Node" section of New Project Deployment.

Once a node is successfully added to the project, the system will automatically perform Docker environment integration, OPS Agent deployment, and monitoring for the new node.

Confirming Component Configuration

Confirm or adjust the ports for each component to be installed. You can modify the port, username, and password for every component.

Note that:

1. The components that can be added here include: Redis (state server), MinIO (file server), Nginx (load balancer), and Elasticsearch (log server).

• For details about the default ports of these components,  see the "Preparation" section of New Project Deployment.

• For details about port occupancy inspection, see Port Occupancy Inspection and Firewall Configuration.

2. You must modify and remember the passwords of the Redis, MinIO, and Elasticsearch components. The default passwords of these components are randomly generated.

• If you forget the username and password of relevant components, you can retrieve them by exporting deployment information. For details, see Exporting Project Deployment Information.

3. Self-provided cluster components are not supported for connection here.

• To use self-provided cluster components, connect FineOps to them under Project Management > Maintenance > Cluster Management after the standalone-to-cluster conversion.

4. The ports here refer to those on the component node server selected in the "Selecting the Component Node" section.

Starting Conversion

Click Start Change to convert the standalone project to a single-node cluster.

1. If any configuration above is found to be non-compliant, the conversion will be aborted. Review and optimize the configuration according to the prompt.

2. If the deployment of cluster components fails, or if the connection between the project and the cluster components fails, the system will automatically roll back. Check and resolve the issues based on the error message.

3. Upon successful conversion, the project will be changed to a single-node cluster. For details about transforming it to a multi-node cluster by adding project nodes, see Cluster O&M Project Scaling.