FineOps
Version
Functional Change
When starting, stopping, or restarting components, a secondary confirmation dialog box is added to prevent accidental operation.
Non-containerized deployment project supports Component Management
operation, which is used to manage exporter component and add new
components.
Add support for exporting deployment information.
In a project, there may be multiple nodes and multiple components.
If a component of the application fails, it may result in the entire application becoming unavailable. You need to provide the admin with methods and means for rapid recovery.
FineOps provides the Component Management function, which supports the start, stop and restart of the containerized deployment project components.
1) Support to start, stop and restart all the components in the containerized deployment project.
2) Non-containerized deployment projects only support the addition of new components and the components added to the project by FineOps.
Log in to FineOps as the admin, select the corresponding project, and choose the Maintenance > Component Management button to access the Component Management page.
The Component Management page displays information of all components within the current project.
Containerized deployment project includes all components selected during the deployment process.
Non-containerized deployment project includes newly added components via FineOps.
The displayed component information includes:
Information
Whether it is started, including: started, not started and starting.
Image Information
Container Image Information
Physical Node
Container's Uptime
The operations include various actions: update, start, stop, restart, change configuration, terminate, and add components.
Prerequisite：Only project deployed via FineOps is supported.
Application Scenario
Add Component
Some components may not be installed during project deployment.
After deployment, the admin can add these components to the project in
the component management section.
For components/projects deployed on FineOps, the original deployment information may need to be consulted in the later operation and
maintenance.
You can export the JSON file and retrieve it from the server where
FineOps is located.
Container private cloud authentication is recommended for O&M
projects deployed on FineOps.
FineOps provides a frontend page for quick registration, helping users
to register rapidly.
To meet customers' new requirements and address certain deficiencies in previous versions, FanRuan's products are continuously updated and iterated upon, with FineOps supporting the updating of project
Upgrade O&M project with External
O&M Project Update with Intranet
Support the start, stop, restart and other operations of components, and quick start and stop of components.
Some components are interdependent, so restarting one component
may trigger the restart of others.
It is convenient for users to swiftly adjust and modify configurations of
project components and execute commands, such as memory
allocation, CPU, maximum thread pool, and MySQL write timeout, and
so on.
Support the configuration of SSL certificates for projects deployed on
FineOps to meet the requirements of accessing FanRuan applications HTTPS.
Enter Terminal
Although FineOps already provides many page operations, admin may still need to use terminal tools to connect and manage components.
FineOps provides terminal tools to support quick access to component
terminal.
Command Line Page is displayed on the left, where you can input
commands for query/execution. It supports a one-click clearing of the
command line page.
The specific container information of the component is displayed on the right.
Note1: Access to the terminal is only available when the component is in
the running state, otherwise, a prompt saying Entering the terminal is not
supprted in the current container state will be displayed.
Note2: Single FineOps supports the simultaneous connection of 3
component terminals at most. When exceeding 3 connections, a prompt will appear saying, Up to 3 terminals can be connected. The current limit
has been reached. Please close other terminals and try again.
Note3: If there is no command operation for 10 minutes after connecting to
the terminal, the connection will be automatically terminated, and a prompt will appear saying, Terminal connection disconnected. Please
reconnect.