WO2021223471A1

WO2021223471A1 - Configuration file centralized management system, method and apparatus

Info

Publication number: WO2021223471A1
Application number: PCT/CN2021/073939
Authority: WO
Inventors: 陈海钊; 季统凯; 贺忠堂
Original assignee: 国云科技股份有限公司
Priority date: 2020-05-08
Filing date: 2021-01-27
Publication date: 2021-11-11
Also published as: CN111654532A; CN111654532B

Abstract

Disclosed are a configuration file centralized management system, method and apparatus. According to the technical solution provided in the embodiments of the present application, the method comprises: a proxy module scanning instance configuration files on corresponding service processing servers, and uploading a scanning result to a management module on the basis of the scanned instance configuration files; the management module receiving a first instance configuration file updating request from a user or the scanning result, and updating instance configuration files stored in a storage module and/or issuing a second instance configuration file updating request to the proxy module; and the proxy module updating the corresponding instance configuration files of the service processing servers on the basis of the received second instance configuration file updating request. By using the technical means, the unified management of instance configuration files of a server cluster can be realized, and the process of updating the configuration files is optimized, thereby reducing the operation, maintenance and management costs of application of service processing servers.

Description

System, method and device for centralized management of configuration files

Technical field

The embodiments of the application relate to the technical field, and in particular, to a system, method, and device for centralized management of configuration files.

Background technique

With the development of microservices and distributed technologies, a system is often split into multiple applications, and a single application needs to be supported by multiple instances. In addition, customizing instances or controlling the behavior of different instances often requires the use of configuration files.

When the configuration file management update is performed, the configuration center is generally used to centrally manage the update. It requires the application to actively communicate with the configuration center to complete the configuration file update. However, this method requires the application to integrate part of the logic in the code, and the process is relatively cumbersome. The application needs to be modified to apply the configuration file update, and its operation and maintenance management cost is relatively large.

Summary of the invention

The embodiments of the present application provide a system, method, and device for centralized management of configuration files, which can perform unified management of configuration files and reduce application operation, maintenance and management costs.

In the first aspect, an embodiment of the present application provides a configuration file centralized management system, including: a management module, a storage module, and an agent module running on each service processing server;

The agent module is used to scan the instance configuration file of the business processing server, and upload the scan result to the management module;

The storage module is used for the management module to store instance configuration files;

The management module is configured to update the instance configuration file stored in the storage module according to the user's first instance configuration file update request or the scan result and/or issue a second instance configuration file update request to the agent module;

The proxy module is further configured to receive the second instance configuration file update request, and update the instance configuration file corresponding to the service processing server.

In the second aspect, an embodiment of the present application provides a method for centralized management of configuration files, including:

The proxy module scans the instance configuration file on the corresponding business processing server, and uploads the scan result to the management module based on the scanned instance configuration file;

The management module receives the user’s first instance configuration file update request or the scan result, extracts the corresponding configuration file content, and retrieves the instance configuration file from the storage module for comparison, and updates the storage module based on the comparison result. The instance configuration file and/or issue a second instance configuration file update request to the agent module;

The proxy module updates the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request.

Further, the agent module scans the instance configuration file on the corresponding business processing server, and uploads the scanning result to the management module based on the scanned instance configuration file, including:

The proxy module scans the instance on the corresponding service processing server, and obtains the application configuration file setting information of the management module. The application configuration file setting information is set in the management module in advance and is used to instruct the instance configuration file in the corresponding service processing The storage path on the server;

Scanning and acquiring an instance configuration file corresponding to the instance based on the application configuration file setting information;

The corresponding MD5 code is calculated according to the scanned instance configuration file, and the scanned instance configuration file and the MD5 code are reported to the management module as the scanning result.

Further, the application configuration file setting information includes the name of the instance configuration file, the storage path of the instance configuration file, the application to which the instance configuration file belongs, and the updated automatic restart setting information;

The instance configuration file includes the content of the configuration file, the corresponding MD5 code, the instance to which the instance configuration file belongs, and the latest update time of the instance configuration file.

Further, the management module receives the user’s first instance configuration file update request or the scan result, extracts the corresponding configuration file content, retrieves the instance configuration file from the storage module for comparison, and updates the storage based on the comparison result. The instance configuration file stored by the module and/or the second instance configuration file update request issued to the agent module includes:

In response to the user’s first instance configuration file update request, the management module retrieves the storage module based on the configuration file content included in the first instance configuration file update request;

If the storage module does not have a corresponding instance configuration file, the current process is ended;

If there is a corresponding instance configuration file in the storage module, compare the MD5 code corresponding to the configuration file content with the corresponding instance configuration file, if they are the same, end the current process, if they are different, update the content based on the configuration file content and the corresponding MD5 code Store the corresponding instance configuration file stored by the module, and issue a second instance configuration file update request to the agent module.

Further, the management module receives the user’s first instance configuration file update request or the scan result, extracts the corresponding configuration file content, retrieves the instance configuration file from the storage module for comparison, and updates the storage based on the comparison result. The instance configuration file stored by the module and/or issuing the second instance configuration file update request to the agent module also includes:

The management module receives the scan result, and retrieves the storage module based on the scan result;

If the corresponding instance configuration file does not exist in the storage module, update the corresponding instance configuration file stored in the storage module based on the scan result;

If there is a corresponding instance configuration file in the storage module, compare the MD5 code in the scan result with the corresponding instance configuration file, if they are the same, end the current process, if they are different, issue the first instance configuration file based on the retrieved corresponding instance configuration file. 2. The instance configuration file update request is sent to the proxy module.

Further, the agent module updating the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request includes:

Scan the instance configuration file of the corresponding instance of the business processing server, obtain the content of the corresponding configuration file, and calculate the corresponding MD5 code;

Comparing the calculated MD5 code with the MD5 code included in the second instance configuration file update request;

If the MD5 codes are the same, the current process ends, and if the MD5 codes are different, the content of the configuration file included in the second instance configuration file update request is overwritten to the instance configuration file of the corresponding instance.

Further, after the proxy module updates the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request, the method further includes:

The management module receives the storage path update request of the corresponding instance configuration file;

The management module sends a delete request to the storage module based on the storage path update request to delete the corresponding instance configuration file, and notifies the agent module to reacquire application configuration file setting information;

The proxy module rescans the instance configuration file of the corresponding business processing server, and reports the scanning result to the management module.

In the third aspect, an embodiment of the present application provides an apparatus for centralized management of configuration files, including:

The scanning module is used to scan the instance configuration file on the corresponding business processing server through the proxy module, and upload the scanning result to the management module based on the scanned instance configuration file;

The comparison module is used to receive the user’s first instance configuration file update request or the scan result through the management module, extract the corresponding configuration file content, and retrieve the instance configuration file from the storage module for comparison, based on the comparison result Update the instance configuration file stored in the storage module and/or issue a second instance configuration file update request to the agent module;

The update module is configured to update the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request through the proxy module.

In a fourth aspect, embodiments of the present application provide a storage medium containing computer-executable instructions, which are used to execute the method for centralized management of configuration files as described in the first aspect when the computer-executable instructions are executed by a computer processor .

In this embodiment of the application, the proxy module scans the instance configuration file on the corresponding business processing server, uploads the scan result to the management module based on the scanned instance configuration file, and the management module receives the user’s first instance configuration file update request or scan result, and updates The instance configuration file stored by the storage module and/or the second instance configuration file update request is issued to the agent module, and the agent module updates the instance configuration file corresponding to the business processing server based on the received second instance configuration file update request. Using the above technical means, it is possible to realize unified management of the instance configuration files of the server cluster, optimize the configuration file update process, and reduce the operation and maintenance and management costs of the application of each business processing server.

Description of the drawings

FIG. 1 is a schematic structural diagram of a configuration file centralized management system provided by Embodiment 1 of the present application;

2 is a flowchart of a method for centralized management of configuration files provided by Embodiment 1 of the present application;

Fig. 3 is a scanning flowchart of the proxy module in the first embodiment of the present application;

Fig. 4 is a search and comparison flowchart of the management module based on the update request in the first embodiment of the present application;

Fig. 5 is a search and comparison flowchart of the management module based on the scan result in the first embodiment of the present application;

FIG. 6 is an example configuration file update flowchart of the proxy module in the first embodiment of the present application;

FIG. 7 is a flowchart of configuration file update in Embodiment 1 of the present application;

FIG. 8 is a flowchart of updating the storage path of the example configuration file in the first embodiment of the present application;

FIG. 9 is a schematic structural diagram of an apparatus for centralized management of configuration files provided by Embodiment 2 of the present application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, specific embodiments of the present application will be described in further detail below with reference to the accompanying drawings. It can be understood that the specific embodiments described here are only used to explain the application, but not to limit the application. In addition, it should be noted that, for ease of description, the drawings only show part of the content related to the present application, but not all of the content. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowchart describes various operations (or steps) as sequential processing, many of the operations can be implemented in parallel, concurrently, or simultaneously. In addition, the order of operations can be rearranged. The processing may be terminated when its operation is completed, but may also have additional steps not included in the drawings. The processing may correspond to methods, functions, procedures, subroutines, subroutines, and so on.

The configuration file centralized management system and method provided in this application aim to reduce the operation, maintenance and management costs of various business processing server applications by uniformly managing and updating the instance configuration files of the server cluster. Compared with the traditional configuration file management method, when the configuration file is updated, the corresponding application code on the business processing server needs to integrate corresponding logic to realize the configuration file update. This method requires that every business processing server integrates the logic code of configuration file management. For some legacy applications or open source applications, it needs to be modified to be applicable. For the consideration of operation and maintenance management costs, the way to modify the application is obviously not It is too realistic, and its transformation process is complicated, which is not convenient for the configuration file update management of this business processing server cluster. Based on this, a configuration file centralized management system and method according to the embodiments of the present application are provided to solve the technical problems of complicated processes and high investment costs when the existing server clusters perform configuration file management.

Example one:

Figure 1 shows a schematic structural diagram of a configuration file centralized management system provided in the first embodiment of the present application. The configuration file centralized management system includes: a management module, a storage module, and an agent module running on each service processing server; The proxy module is used to scan the instance configuration file of the business processing server and upload the scanning result to the management module; the storage module is used to store the instance configuration file in the management module; the management module is used to store the instance configuration file according to the user The first instance configuration file update request or the scan results update the instance configuration file stored in the storage module and/or issue the second instance configuration file update request to the proxy module; the proxy module is also used to receive all The second instance configuration file update request is described, and the instance configuration file corresponding to the business processing server is updated. It can be understood that, corresponding to each server on the business processing server cluster, an agent module (ProfileAgent) is set correspondingly, and each agent module runs on the corresponding business processing server to manage the instance configuration file of the application on the corresponding business processing server . The management module (ProfileServer) and storage module are used as the centralized processing and storage modules of the system. Through the management module, each agent module is docked to centrally manage the configuration files of each business processing server instance. In addition, the configuration file centralized management system of the embodiment of the present application further includes a database. The database is used to store the application configuration file setting information generated by the management module for setting the application configuration file, and call it through the management module and send it to the agent module when needed. .

Further, FIG. 2 provides a flow chart of a method for centralized management of configuration files according to an embodiment of the present application. The method for centralized management of configuration files provided in this embodiment can be executed by the above-mentioned centralized management system for configuration files. It can be implemented by software and/or hardware. The following description takes the configuration file centralized management system as the main body that executes the configuration file centralized management method as an example. Referring to Figure 2, the method for centralized management of configuration files specifically includes:

S110. The agent module scans the instance configuration file on the corresponding business processing server, and uploads the scanning result to the management module based on the scanned instance configuration file.

Specifically, in practical applications, there are generally two types of instance configuration file update triggered by the system. One is to periodically scan the instance configuration file on its corresponding node (ie, business processing server) through the proxy module, and further upload the scanning result To the management module, the management module compares and judges whether the instance configuration file needs to be updated based on the scanning result. One is that the management module receives the user's instance configuration file update request, and compares and judges whether the instance configuration file needs to be updated based on the content contained in the instance configuration file update request. It should be noted that the update of the instance configuration file here may be the update of the instance configuration file stored in the storage module, or the update of the instance configuration file of the corresponding business processing server. The management module updates the instance configuration files in different forms according to the actual search and comparison results.

Further, referring to Fig. 3, a scanning flowchart of the agent module is provided, wherein the routine scanning process of the agent module includes:

S1101. The proxy module scans the instance on the corresponding service processing server, and obtains the application configuration file setting information of the management module. The application configuration file setting information is set in the management module in advance to indicate that the instance configuration file is in the corresponding The storage path on the business processing server;

S1102, scan and obtain an instance configuration file corresponding to the instance based on the application configuration file setting information;

S1103: Calculate the corresponding MD5 code according to the scanned instance configuration file, and report the scanned instance configuration file and the MD5 code to the management module as a scanning result.

Periodically scan the instances on the node (that is, the business processing server) through each agent module to obtain sample configuration files. Among them, the timing scan is performed according to the preset time period. The proxy module can be configured with a timer. The timer is used to time the scan period. The scan period of the timer is set according to the set time period, and the corresponding timing scan operation is performed in each scan period. Specifically, the agent module first obtains the application configuration file setting information from the management module according to the scanned instance to determine the storage path of the corresponding instance configuration file on the current business processing server. Since the application configuration file setting information stores the storage path of the instance configuration file on the corresponding business processing server, the agent module can scan the instance configuration file corresponding to the instance according to this information. And calculate the corresponding MD 5 code according to the configuration content in the example configuration file. In addition, based on the above scanning result, it will be sent to the management module in real time, so that the management module can compare and determine whether the instance configuration file needs to be updated.

Specifically, the application configuration file setting information includes the name of the instance configuration file, the storage path of the instance configuration file, the application to which the instance configuration file belongs, and the updated automatic restart setting information; the instance configuration file includes the content of the configuration file and the corresponding MD5 code , The instance to which the instance configuration file belongs and the latest update time of the instance configuration file. Among them, the storage path of the instance configuration file supports wildcards to support the configuration of a single node with multiple instances. The automatic restart setting information sets whether the instance configuration file needs to be restarted automatically after the update, which can be set according to actual operation and maintenance needs. For instance configuration files, the latest update time information contained therein should be updated according to each instance configuration file update record to ensure the real-time record of the update time.

S120. The management module receives the user's first instance configuration file update request or the scan result, extracts the corresponding configuration file content, retrieves the instance configuration file from the storage module for comparison, and updates the storage module based on the comparison result The stored instance configuration file and/or issue a second instance configuration file update request to the agent module.

Further, for the management module, the update of the instance configuration file can be triggered by comparison according to the scanning results of the above-mentioned proxy module, or the instance configuration can be triggered according to the user's instance configuration file update request (defined as the first instance configuration file update request) File update. It should be noted that the management module needs to retrieve the instance configuration file of the storage module for comparison when the instance configuration file update is triggered. Therefore, the scan result or the first instance configuration file update request received by the management module needs to include the corresponding configuration file content and the corresponding MD5 code. In order to compare the content of the configuration file and the corresponding MD5 code with the content of the configuration file and the MD5 code of the instance configuration file stored in the storage module, to determine whether the instance configuration file needs to be updated.

The following describes the retrieval and comparison of the trigger instance configuration file update corresponding to the scan result and the first instance configuration file update request respectively. Among them, referring to Figure 4, the retrieval and comparison process of the management module based on the update request includes:

S1201. In response to the user’s first instance configuration file update request, the management module retrieves the storage module based on the configuration file content included in the first instance configuration file update request;

S1202, if there is no corresponding instance configuration file in the storage module, end the current process;

S1203. If the storage module has a corresponding instance configuration file, compare the MD5 code corresponding to the content of the configuration file with the corresponding instance configuration file, if they are the same, end the current process, if they are different, update based on the content of the configuration file and the corresponding MD5 code The storage module stores the corresponding instance configuration file, and issues a second instance configuration file update request to the agent module.

In actual applications, according to the actual needs of the user, when the instance configuration file needs to be updated, the user end sends the first instance configuration file update request to the management module. Among them, the first instance configuration file update request needs to include the content of the configuration file that needs to be updated and the corresponding MD5 code, so as to facilitate subsequent comparison with the corresponding instance configuration file of the storage module. Further, according to the received user's first instance configuration file update request, the management module extracts the configuration file content and MD5 code, and further searches the storage module to determine whether there is a corresponding instance configuration file on the storage module. According to the retrieval result, if the instance configuration file does not exist in the storage module, there is no need to update the instance configuration file, and the management module ends the current process. If the corresponding instance configuration file is retrieved, the MD5 codes of the two need to be further compared to determine whether the configuration content is the same. The management module first calculates the MD5 code based on the configuration file content of the instance configuration file retrieved by the storage module, and compares it with the MD5 code contained in the first instance configuration file update request. If the same, it means the first instance configuration file update request The content of the configuration file is the same as the configuration file content of the corresponding instance configuration file on the storage module, and there is no need to update, and the management module ends the current process. If the MD5 code comparison is inconsistent, it means that the configuration file content of the first instance configuration file update request is different from the configuration file content of the corresponding instance configuration file on the storage module. At this time, the management module updates the corresponding instance configuration file on the storage module. Specifically, when updating, the current time is used as the instance configuration file update time, and the configuration file content, MD5 code, and configuration file update time are overwritten in the corresponding instance configuration file of the storage module to complete the instance configuration file update of the storage module. And, further, after completing the instance configuration file update of the storage module, it is necessary to update the instance configuration file of the corresponding instance on each service processing server to realize the application update. The management module defines the notification as a second instance configuration file update request by sending a notification to the agent module. One end of the proxy module updates the instance configuration file of the instance corresponding to the node based on the received second instance configuration file update request.

On the other hand, referring to FIG. 5, the retrieval and comparison process based on the scan result of the management module of the embodiment of the present application includes:

S1204. The management module receives the scan result, and retrieves the storage module based on the scan result.

S1205: If the corresponding instance configuration file does not exist in the storage module, update the corresponding instance configuration file stored in the storage module based on the scanning result;

S1206. If the storage module has a corresponding instance configuration file, compare the MD5 code in the scan result with the corresponding instance configuration file, if they are the same, end the current process, if they are different, download the corresponding instance configuration file based on the retrieved Send a second instance configuration file update request to the proxy module.

Wherein, refer to the manner in which the management module performs retrieval and comparison based on the configuration file content of the configuration file update request of the first example and the corresponding MD5. When the corresponding instance configuration file of the comparison storage module is retrieved based on the scan result, the comparison is performed by extracting the instance configuration file in the scan result and the corresponding MD5 code. The management module first retrieves the corresponding instance configuration file on the storage module. If the instance configuration file does not exist on the storage module, it needs to use the instance configuration file provided by the scan result to set the instance configuration file on the storage module. Use the current time as the instance configuration file update time, and save the configuration file content, MD5 code, and instance configuration file update time to the storage module. If there is a corresponding instance configuration file on the storage module, it is necessary to further compare the MD5 codes of the two to determine whether the configuration content is the same. The management module first calculates the MD5 code based on the configuration file content of the instance configuration file retrieved by the storage module, and compares it with the MD5 code contained in the scan result. If they are the same, it means that the configuration file content of the first instance configuration file update request is the same as The configuration file content of the corresponding instance configuration file on the storage module is the same, and there is no need to update, and the management module ends the current process. If the MD5 code comparison is inconsistent, it means that the configuration file content of the configuration file update request of the first instance is different from the configuration file content of the corresponding instance configuration file on the storage module. At this time, the instance configuration file stored in the storage module shall prevail for business processing. The instance configuration file on the server is updated. The management module sends a notification to the corresponding agent module to notify it to update the instance configuration file. Define this notification as a second instance configuration file update request. One end of the proxy module updates the instance configuration file of the instance corresponding to the node based on the received second instance configuration file update request.

S130. The proxy module updates the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request.

Further, based on the second instance configuration file update request issued after the above-mentioned management module search and comparison, the proxy module correspondingly updates the instance configuration file. Among them, referring to Figure 6, the example configuration file update process of the proxy module includes:

S1301: Scan the instance configuration file of the corresponding instance of the business processing server, obtain the content of the corresponding configuration file, and calculate the corresponding MD5 code;

S1302. Compare the calculated MD5 code with the MD5 code included in the second instance configuration file update request.

S1303. If the MD5 codes are the same, end the current process; if the MD5 codes are different, overwrite the configuration file content included in the second instance configuration file update request to the instance configuration file of the corresponding instance.

Specifically, when the agent module updates the instance configuration file, it first scans the instance configuration file of the corresponding instance by acquiring the application configuration file setting information of the management module. For the scanning of the example configuration file, refer to the above step S110, which will not be repeated here. Further, based on the scanned example configuration file, extract the configuration file content, and calculate the MD5 code of the configuration file content. Based on the calculated MD5 code, compare it with the MD5 code contained in the second instance configuration file update request. If the two are the same, it will identify that the instance configuration file of the current node is the same as the instance configuration file on the storage module, and no update is required. , The agent module ends the current process. If the two are different, the content of the configuration file in the second instance configuration file update request is overwritten to the instance configuration file corresponding to the current instance to complete the instance configuration file update of the instance corresponding to this node. In addition, when the instance configuration file is updated, if it is set in the application configuration file setting information previously obtained that the corresponding instance is automatically restarted after the sample configuration file is updated, the automatic restart operation is performed on the instance.

Referring to FIG. 7, a configuration file update flowchart of an embodiment of the present application is provided. The management module of the embodiment of the present application triggers the retrieval and comparison process through user request or the scan result of the instance configuration file reported by the agent module, and retrieves and compares the instance of the storage module. Configuration file, and then determine to update the instance configuration file stored in the storage module and/or issue a second instance configuration file update request to the agent module, and the agent module updates the instance configuration file of the corresponding instance of the node by receiving the second instance configuration file update request . For example, there are two applications AppA and AppB. Among them, an instance of AppA, AppA, and an instance of AppB, AppB-0 and AppB-1, are deployed on the business processing server. Then the application configuration files corresponding to the two applications are set as follows:

AppA:

(1) The application to which the configuration file belongs: AppA;

(2) Configuration file name: xx.conf;

(3) Configuration file path: /etc/AppA/{instanceName}/xx.conf;

(4) Automatic restart: true.

AppB:

(1) The application to which the configuration file belongs: AppB;

(2) Configuration file name: application.yml;

(3) Configuration file path: /opt/AppB/{instanceName}/application.yml;

(4) Automatic restart: true.

Further, when the agent module on the business processing server scans the instance configuration file regularly, it scans the instances on the node through the agent module to obtain the instance AppA of the application AppA, and the instances AppB-0 and AppB-1 of the application AppB. The agent module further obtains the application configuration file setting information from the management module, and scans the instance configuration file of the corresponding instance based on the application configuration file setting information. The content of the configuration file is obtained by scanning, and the MD5 code of the content of the configuration file is calculated. Among them, when scanning the instance configuration file, scan the configuration file /etc/AppA/AppA/xx.conf of the instance AppA, the configuration file /opt/AppB/AppB-0/application.ym of the instance AppB-0, and the instance AppB- 1 configuration file /opt/AppB/AppB-1/application.yml. Further, based on the scanned instance configuration file and the corresponding MD5 code, the scan result is reported to the management module. The management module retrieves the storage module based on the scan result. If there is no instance configuration file of the instance AppA in the storage module at this time, the management module saves the relevant information of the instance configuration file of the instance AppA to the storage module. If the instance configuration file of the instance AppB exists in the storage module at this time, the management module compares the MD5 codes of the instance AppB-0 and AppB-1, where the MD5 codes of AppB-1 are not the same, the management module informs the agent on the corresponding service processing server The module updates the configuration file of the instance AppB-1.

Further, after receiving the instance configuration file update request for updating the instance AppB-1, the proxy module scans the instance configuration file /opt/AppB/AppB-1/application.yml corresponding to the instance AppB-1, obtains the content of the configuration file, and Calculate the MD5 code of the configuration file content. Compare the calculated MD5 code with the MD5 code in the received second instance configuration file update request, and if the result is not the same, overwrite the configuration file content in the second instance configuration file update request to the instance AppB-1 The corresponding instance configuration file. In addition, since the application AppB is set to automatically restart after the instance configuration file is updated, the automatic restart operation is performed on the instance AppB-1 at this time.

In addition, referring to FIG. 8, a flowchart for updating the storage path of the instance configuration file is provided. When the embodiment of the present application performs management and updating of the instance configuration file, it further provides an update of the storage path of the instance configuration file. The update process includes:

S1401. The management module receives a storage path update request of the corresponding instance configuration file;

S1402. The management module sends a deletion request to the storage module based on the storage path update request to delete the corresponding instance configuration file, and notifies the agent module to reacquire application configuration file setting information;

S1403. The agent module rescans the instance configuration file of the corresponding business processing server, and reports the scanning result to the management module.

It is understandable that, in actual applications, when the storage path of the instance configuration file needs to be updated, the management module sends a delete request to the storage module based on this update request, and deletes all instances under the application corresponding to the application configuration Example configuration file for file settings. In addition, in order to ensure that the storage module and the instance on the agent module are synchronized, the management module notifies the agent module to re-acquire the application configuration file setting information, and rescans the instance configuration file through the agent module, and reports the scan results to the management module. Realize the storage path update of the storage module and the proxy module instance configuration file.

As mentioned above, the proxy module scans the instance configuration file on the corresponding business processing server, uploads the scan result to the management module based on the scanned instance configuration file, and the management module receives the user’s first instance configuration file update request or scan result, and updates the storage module The stored instance configuration file and/or issue a second instance configuration file update request to the agent module, and the agent module updates the instance configuration file corresponding to the business processing server based on the received second instance configuration file update request. Using the above technical means, it is possible to realize unified management of the instance configuration files of the server cluster, optimize the configuration file update process, and reduce the operation and maintenance and management costs of the application of each business processing server.

Embodiment two:

On the basis of the foregoing embodiment, FIG. 9 is a schematic structural diagram of an apparatus for centralized management of configuration files provided in Embodiment 2 of this application. Referring to FIG. 9, the device for centralized management of configuration files provided by this embodiment specifically includes: a scanning module 21, a comparison module 22, and an update module 23.

Wherein, the scanning module 21 is configured to scan the instance configuration file on the corresponding business processing server through the proxy module, and upload the scanning result to the management module based on the scanned instance configuration file;

The comparison module 22 is configured to receive the user’s first instance configuration file update request or the scan result through the management module, extract the corresponding configuration file content, and retrieve the instance configuration file from the storage module for comparison, based on the comparison result Update the instance configuration file stored in the storage module and/or issue a second instance configuration file update request to the agent module;

The update module 23 is configured to update the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request through the proxy module.

The device for centralized management of configuration files provided in the second embodiment of the present application can be used to execute the method for centralized management of configuration files provided in the first embodiment above, and has corresponding functions and beneficial effects.

Example three:

The embodiment of the present application also provides a storage medium containing computer-executable instructions, when the computer-executable instructions are executed by a computer processor, are used to execute a configuration file centralized management method, the configuration file centralized management method includes: an agent The module scans the instance configuration file on the corresponding business processing server, and uploads the scan result to the management module based on the scanned instance configuration file. The scan result includes the instance configuration file and the corresponding MD5 code; the management module receives the user's first instance For the configuration file update request or the scan result, extract the corresponding configuration file content, retrieve the instance configuration file from the storage module for comparison, update the instance configuration file stored in the storage module based on the comparison result and/or issue the second An instance configuration file update request is sent to an agent module; the agent module updates the instance configuration file corresponding to the business processing server based on the received second instance configuration file update request.

Storage medium-any of various types of storage devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc. ; Non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements. The storage medium may further include other types of memory or a combination thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system connected to the first computer system through a network (such as the Internet). The second computer system can provide the program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (for example, in different computer systems connected through a network). The storage medium may store program instructions (for example, embodied as a computer program) executable by one or more processors.

Of course, the storage medium containing computer-executable instructions provided by the embodiments of the present application is not limited to the above-mentioned centralized management method for configuration files, and can also execute the configuration files provided in any embodiment of the present application. Related operations in the centralized management method.

The configuration file centralized management apparatus, storage medium, and electronic equipment provided in the above embodiments can execute the configuration file centralized management method provided in any embodiment of this application. For technical details not described in detail in the above embodiments, please refer to any of this application. The method for centralized management of configuration files provided by the embodiment.

The above are only the preferred embodiments of this application and the technical principles used. The application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not depart from the protection scope of the application. Therefore, although the application has been described in more detail through the above embodiments, the application is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the application. The scope of is determined by the scope of the claims.

Claims

A centralized management system for configuration files, which is characterized by comprising: a management module, a storage module, and an agent module running on each service processing server;

The agent module is used to scan the instance configuration file of the business processing server, and upload the scan result to the management module;

The storage module is used for the management module to store instance configuration files;

The management module is configured to update the instance configuration file stored in the storage module according to the user's first instance configuration file update request or the scan result and/or issue a second instance configuration file update request to the agent module;

The proxy module is further configured to receive the second instance configuration file update request, and update the instance configuration file corresponding to the service processing server.
A method for centralized management of configuration files, applied to the system for centralized management of configuration files according to claim 1, characterized in that it comprises:

The proxy module scans the instance configuration file on the corresponding business processing server, and uploads the scan result to the management module based on the scanned instance configuration file;

The management module receives the user’s first instance configuration file update request or the scan result, extracts the corresponding configuration file content, and retrieves the instance configuration file from the storage module for comparison, and updates the storage module based on the comparison result. The instance configuration file and/or issue a second instance configuration file update request to the agent module;

The proxy module updates the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request.
The method for centralized management of configuration files according to claim 2, wherein the proxy module scans the instance configuration file on the corresponding service processing server, and uploads the scanning result to the management module based on the scanned instance configuration file, comprising:

The proxy module scans the instance on the corresponding service processing server, and obtains the application configuration file setting information of the management module. The application configuration file setting information is set in the management module in advance and is used to instruct the instance configuration file in the corresponding service processing The storage path on the server;

Scanning and acquiring an instance configuration file corresponding to the instance based on the application configuration file setting information;

The corresponding MD5 code is calculated according to the scanned instance configuration file, and the scanned instance configuration file and the MD5 code are reported to the management module as the scanning result.
The method for centralized management of configuration files according to claim 3, wherein the application configuration file setting information includes the name of the instance configuration file, the storage path of the instance configuration file, the application to which the instance configuration file belongs, and the updated automatic restart settings information;

The instance configuration file includes the content of the configuration file, the corresponding MD5 code, the instance to which the instance configuration file belongs, and the latest update time of the instance configuration file.
The method for centralized management of configuration files according to claim 2, wherein the management module receives the user’s first instance configuration file update request or the scan result, extracts the corresponding configuration file content, and sends it to the storage module Retrieving the instance configuration file for comparison, updating the instance configuration file stored in the storage module based on the comparison result and/or issuing a second instance configuration file update request to the agent module includes:

In response to the user’s first instance configuration file update request, the management module retrieves the storage module based on the configuration file content included in the first instance configuration file update request;

If the storage module does not have a corresponding instance configuration file, the current process is ended;

If there is a corresponding instance configuration file in the storage module, compare the MD5 code corresponding to the configuration file content with the corresponding instance configuration file, if they are the same, end the current process, if they are different, update the content based on the configuration file content and the corresponding MD5 code Store the corresponding instance configuration file stored by the module, and issue a second instance configuration file update request to the agent module.
The method for centralized management of configuration files according to claim 2, wherein the management module receives the user’s first instance configuration file update request or the scan result, extracts the corresponding configuration file content, and sends it to the storage module Retrieving the instance configuration file for comparison, updating the instance configuration file stored in the storage module based on the comparison result and/or issuing a second instance configuration file update request to the agent module, further includes:

The management module receives the scan result, and retrieves the storage module based on the scan result;

If the corresponding instance configuration file does not exist in the storage module, update the corresponding instance configuration file stored in the storage module based on the scan result;

If there is a corresponding instance configuration file in the storage module, compare the MD5 code in the scan result with the corresponding instance configuration file, if they are the same, end the current process, if they are different, issue the first instance configuration file based on the retrieved corresponding instance configuration file. 2. The instance configuration file update request is sent to the proxy module.
The method for centralized management of configuration files according to claim 2, wherein the proxy module updates the configuration file of the corresponding instance of the service processing server based on the received second instance configuration file update request, comprising: :

Scan the instance configuration file of the corresponding instance of the business processing server, obtain the content of the corresponding configuration file, and calculate the corresponding MD5 code;

Comparing the calculated MD5 code with the MD5 code included in the second instance configuration file update request;

If the MD5 codes are the same, the current process ends, and if the MD5 codes are different, the content of the configuration file included in the second instance configuration file update request is overwritten to the instance configuration file of the corresponding instance.
A method for centralized management of configuration files according to any one of claims 2-7, wherein the proxy module performs configuration of the corresponding instance of the service processing server based on the received second instance configuration file update request After the file is updated, it also includes:

The management module receives the storage path update request of the corresponding instance configuration file;

The management module sends a delete request to the storage module based on the storage path update request to delete the corresponding instance configuration file, and notifies the agent module to reacquire application configuration file setting information;

The proxy module rescans the instance configuration file of the corresponding business processing server, and reports the scanning result to the management module.
A device for centralized management of configuration files is characterized in that it comprises:

The scanning module is used to scan the instance configuration file on the corresponding business processing server through the proxy module, and upload the scanning result to the management module based on the scanned instance configuration file;

The comparison module is used to receive the user’s first instance configuration file update request or the scan result through the management module, extract the corresponding configuration file content, and retrieve the instance configuration file from the storage module for comparison, based on the comparison result Update the instance configuration file stored in the storage module and/or issue a second instance configuration file update request to the agent module;

The update module is configured to update the instance configuration file corresponding to the service processing server based on the received second instance configuration file update request through the proxy module.
A storage medium containing computer-executable instructions, wherein the computer-executable instructions are used to execute the method for centralized management of configuration files according to any one of claims 1-7 when the computer-executable instructions are executed by a computer processor.