Overview
Version
| FineBI Version |
|---|
| 6.1 |
Function Description
Server deployment always requires cumbersome O&M operations.
FineBI 6.1 uses a containerized deployment solution to reduce high costs caused by deployment.
This document briefly and clearly describes how to deploy FineOps and FanRuan apps and how to perform O&M operations using FineOps.
The general deployment process is to deploy FineOps through the FineKey tool, and deploy/connect O&M projects through FineOps.
Deployment Guide
After FineBI 6.1 is released, the brand-new FineBI 6.0 deployment solution will no longer be provided.
FineBI 6.1 supports only containerized deployment, reducing project performance and downtime risks caused by improper deployment.
| Type | Description |
|---|---|
Personal trial of FineBI 6.1 | Two trial methods are available. (1) Online trial Access the online FineBI entry using your FanRuan passport. (2) Local deployment Download FineBI 6.1 Personal Trial by referring to the following document and trial FineBI 6.1 on your local computer. FineBI 6.1 Personal Trial can be installed only in a full-English path. For details, see Guide to Deploy FineBI Personal Trial. |
Brand-new deployment of FineBI 6.1 | FineBI 6.1 Enterprise can be deployed only through FineOps. (1) Sufficient server resource If server resources are sufficient, FineBI 6.1 can be deployed on a full-volume brand-new server. For details, see Quick Start. (2) Limited server resource If server resources are limited, situations such as port occupation may occur. For details, see FineBI 6.1 Deployment. |
Upgrade from FineBI 6.0 to FineBI 6.1 | Contact technical support to help you upgrade FineBI Enterprise from 6.0 to 6.1. You can contact technical support by referring to Technical Support Channel Introduction. |
Project registration | This is the most suitable registration method for containerized projects. |
Deployment Process
Deploy FineOps through the FineKey tool, and the FineBI 6.1 project through FineOps.
FineBI 6.1 Architecture Description
FineBI 6.1 adopts a storage-computing separation architecture.
Node description:
| Node | Description |
|---|---|
BI | BI business node |
Master | Engine metadata node |
Worker | Engine computing node |
MinIO | Data storage node |
Advantage description:
| Advantage | |
|---|---|
Higher stability | The BI node and engine node are separated and do not affect each other if downtime occurs. With FineOps, the system automatically recovers from downtime. |
Higher scalability | Storage-computing separation achieves flexible scalability. Nodes can be added upon computing power insufficiency, and disks can be added upon storage insufficiency. The query performance is improved linearly after one-click capacity expansion. |
Higher performance | Read-write separation keeps the query performance unaffected by updates. Shared data storage is introduced, requiring no inter-node file synchronization. |
Product architecture:
