Overview
Version
| FineOps Version | Functional Change |
|---|---|
| V1.5.5 | / |
Function Description
FineOps provides the Business Group Management function to help you manage project resources.
To use this function, Nginx with a prefix identical to that of the O&M project must exist in the O&M project.
This document introduces how to quickly start and access NGINX in an O&M project.
Procedure
Checking Whether Available NGINX Exists
Log in to FineOps as the admin, select the required project, and choose Business Tool > Resource Isolation.
Hover the mouse over the Business Group Management button, the prompt "No available NGINX. No business group can be added." is displayed.
Starting NGINX
After you enable Business Group Management, the prompt box "You need to start NGINX to use this function. Do you want to start it?" will pop up.
Click Start to start a new NGINX container at the node where FineOps is located. The new container will automatically connect to each cluster node of the current project, as shown in the following figure.
The app access address of the new NGINX will be returned after the new NGINX is successfully started.
The prompt box "Nginx is enabled. Forward the load balancing of the original project cluster to the following address: IP address:Port number" will pop up.
Obtaining the New NGINX Configuration Information
After the new NGINX is started, you can click NGINX Configuration to obtain the NGINX configuration path of the original project cluster and the app access address of the new NGINX.
Modifying the nginx.conf File of the Original Cluster
According to NGINX Configuration Path, locate and modify the nginx.conf file in the NGINX configuration path of the original project cluster.
1. Comment out the original random request forwarding.
2. Comment out the original health check.
3. Add Nginx App Access Address obtained in the previous section as a random forwarding node.
4. Restart the NGINX component of the original project cluster.
Restarting NGINX
After the nginx.conf file is modified, you need to restart the NGINX component of the original project cluster for the configuration to take effect.
After successful restart, the original load balancer in the O&M project cluster will be connected to the new NGINX container.
