CN111082964B - A method and device for distributing configuration information - Google Patents

Abstract

The invention discloses a method and device for distributing configuration information, belonging to the technical field of computers. The method includes: executing a target data collection task, collecting target configuration information corresponding to the target data collection task from a configuration information system; judging the target configuration information and the historical configuration collected by the last execution of the target data collection task Whether the information is the same; if not, execute the target configuration generation task corresponding to the target configuration information to generate a target configuration file; execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the target Configure the business server corresponding to the distribution task. By adopting the invention, the resource utilization rate of the service server can be improved.

Description

A method and device for distributing configuration information

technical field

The invention relates to the field of computer technology, in particular to a method and device for distributing configuration information.

Background technique

With the popularization and development of distributed technology, more and more business service providers adopt distributed technology to carry out business, such as the configuration information distribution business of CDN (Content Delivery Network, content distribution network) service providers.

The configuration information is usually generated by the configuration information system and used by the service server of the CDN system. Taking the configuration information as the billing parameters (such as billing mode, billing cycle, price, etc.) in the CDN billing package as an example, the existing configuration information distribution process is described. The service server can obtain the charging parameters from the configuration information system by calling the service interface provided by the configuration information system. When the charging parameters are changed, the service server can obtain the changed charging parameters from the configuration information system through the above acquisition method, and further, the service server can charge the CDN service used by the user based on the changed charging parameters.

In the process of realizing the present invention, the inventor finds that there are at least the following problems in the prior art:

When obtaining configuration information from the configuration information system according to the above acquisition method, each business server consumes a certain amount of machine resources. For CDN service providers who have deployed many business servers, the business servers are used to obtain configuration information as a whole More machine resources are consumed, and the overall cost is higher.

Contents of the invention

In order to solve the problems in the prior art, embodiments of the present invention provide a method and device for distributing configuration information. Described technical scheme is as follows:

In a first aspect, a method for distributing configuration information is provided, and the method includes:

Execute the target data collection task, and collect the target configuration information corresponding to the target data collection task from the configuration information system;

judging whether the target configuration information is the same as the historical configuration information collected during the last execution of the target data collection task;

If not, execute the target configuration generation task corresponding to the target configuration information to generate the target configuration file;

Execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the service server corresponding to the target configuration distribution task.

In a second aspect, an apparatus for distributing configuration information is provided, and the apparatus includes:

A collection module, configured to execute a target data collection task, and collect target configuration information corresponding to the target data collection task from the configuration information system;

A first judging module, configured to judge whether the target configuration information is the same as the historical configuration information collected during the last execution of the target data collection task;

A generation module, configured to execute a target configuration generation task corresponding to the target configuration information, and generate a target configuration file;

The distribution module is configured to execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the service server corresponding to the target configuration distribution task.

In a third aspect, a distribution device is provided, the distribution device includes a processor and a memory, at least one instruction, at least one program, code set or instruction set are stored in the memory, the at least one instruction, the at least A program, the code set or instruction set is loaded and executed by the processor to implement the method for distributing configuration information as described in the first aspect.

In a fourth aspect, a computer-readable storage medium is provided, wherein at least one instruction, at least one section of program, code set or instruction set is stored in the storage medium, and the at least one instruction, the at least one section of program, the code The set or instruction set is loaded and executed by the processor to implement the method for distributing configuration information as described in the first aspect.

The beneficial effects brought by the technical solution provided by the embodiments of the present invention are:

In this embodiment, the target data collection task is executed, and the target configuration information corresponding to the target data collection task is collected from the configuration information system; the target configuration information and the history collected by the last execution of the target data collection task are judged Whether the configuration information is the same; if not, execute the target configuration generation task corresponding to the target configuration information to generate a target configuration file; execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the The business server corresponding to the target configuration distribution task. In this way, the distribution device can directly distribute the configuration files to the business server, so that the business server does not need to obtain the configuration information from the configuration information system by calling the service interface provided by the configuration information system, which not only saves the time consumed by the business server to obtain configuration information Machine resources also reduce the access pressure of the configuration information system when facing a large number of business servers to obtain configuration information. In addition, the distribution device serves as the middleware between each business server and each configuration information system, which removes the coupling between the business server and the configuration information system. When the configuration information system is upgraded or the strategy is changed, the business server side has no perception throughout the process. Therefore, there is no need to upgrade a large number of business servers, and only the configuration information system and distribution equipment need to be upgraded, which not only reduces the upgrade cost, but also makes the upgrade more flexible. In addition, since the business server no longer integrates the configuration information, the integration capability of the business server can be released, further improving the resource utilization of the business server.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

FIG. 1 is a flowchart of a method for distributing configuration information provided by an embodiment of the present invention;

FIG. 2 is an architecture diagram of a distribution device provided by an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of an apparatus for distributing configuration information provided by an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an apparatus for distributing configuration information provided by an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of an apparatus for distributing configuration information provided by an embodiment of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the implementation manner of the present invention will be further described in detail below in conjunction with the accompanying drawings.

The embodiment of the present invention provides a method for distributing configuration information. The execution subject of the method may be a distribution device in a CDN system. The distribution device may be a single server or may consist of multiple servers. The server may be pre-installed with a Environment, such as JDK (Java SE Development Kit, Java Development Kit), mysql database, redis, zookeeper, etc. The above distribution device can obtain configuration information from various configuration information systems, integrate the configuration information, and then distribute the integrated configuration information to corresponding service servers. The distribution device above may include a processor, a memory, and a transceiver. The processor may be used for distributing configuration information in the following processes. The memory may be used to store data required and generated during the processing. The transceiver may use Relevant data in the process of receiving and sending.

The processing flow of a method for distributing configuration information shown in FIG. 1 will be described in detail below in conjunction with specific implementation methods, and the content may be as follows:

Step 101, execute the target data collection task, and collect the target configuration information corresponding to the target data collection task from the configuration information system.

In implementation, the distribution device can distribute and process configuration information through task queues. Task queues can include task queues such as data collection task queues, configuration generation task queues, and configuration distribution task queues. Each task queue can contain several tasks. The operation and maintenance personnel of the CDN system can pre-configure the above task queue and the tasks in the queue in the distribution device, as well as the task execution conditions of each task. The distribution device can sequentially take out tasks from the above task queue according to the order in which the tasks are arranged in the task queue. If the task execution conditions are met, the distribution device can execute the task; if the task execution conditions are not met, the distribution device can execute the task. Put it back in the task queue. Specifically, the distribution device can adopt a multi-thread processing mode. When a thread takes out a task from the task queue, the thread can lock the task, such as using a distributed lock, to prevent other threads from processing the same task; When the task is completed or does not meet the task execution conditions, the above-mentioned thread can unlock the task, and then put the task back into the task queue.

Taking a certain data collection task (which can be called a target data collection task) as an example, when the distribution device takes out the target data collection task from the data collection task queue and meets the execution conditions, the distribution device can execute the target data collection task. The information system collects configuration information corresponding to the target data collection task (may be referred to as target configuration information).

Optionally, the execution condition of the data collection task can be executed periodically. Correspondingly, the processing of the above-mentioned execution target data collection task can be as follows: obtain the difference between the current time and the execution time of the last time the target data collection task is executed; If the value is greater than or equal to the preset execution period, the target data collection task will be executed.

In implementation, after the distribution device takes out the target data collection task from the data collection task queue, it can judge whether the target data collection task meets the task execution conditions, so as to determine whether to execute the target data collection task. Specifically, the distribution device may perform difference processing on the current time and the last execution time of the target data collection task, and obtain the difference between the current time and the last execution time of the target data collection task. Afterwards, the distribution device may compare the relationship between the above difference and the preset execution period. If the difference is greater than or equal to the preset execution cycle, it indicates that the target data collection task has not been executed in the current cycle, so it is judged that the task execution condition is met, and the distribution device can execute the target data collection task; if the difference is less than the preset execution cycle, then Indicates that the target data collection task has been executed in the current period, and thus it is judged that the task execution condition is not met, and the distribution device can put the target data collection task back into the data collection task queue.

Step 102, judging whether the target configuration information is the same as the historical configuration information collected in the last execution of the target data collection task.

In an implementation, the distribution device may process its class of tasks in parallel. When the distribution device takes out the configuration generation task corresponding to the target configuration information (which may be called the target configuration generation task) from the data collection task queue, the distribution device can judge whether the target configuration generation task meets the task execution conditions to determine whether to execute the target Configure build tasks. It is easy to understand that the processed configuration information will not be repeatedly processed, so the configuration generation task corresponding to the processed configuration information will not be executed again. Specifically, the distribution device can determine whether the target configuration generation task meets the task execution conditions by comparing whether the target configuration information is the same as the historical configuration information collected during the last execution of the target data collection task.

Optionally, it can be judged whether the target configuration information is the same as the historical configuration information collected by the last execution of the target data collection task according to the MD5 (Message Digest 5, message digest algorithm fifth edition) value, and the corresponding processing can be as follows: obtain the target The MD5 value of the configuration information; if the MD5 value of the target configuration information is the same as the MD5 value of the historical configuration information, it is determined that the target configuration information is the same as the historical configuration information, otherwise it is determined that the target configuration information is different from the historical configuration information.

In implementation, after the distribution device completes the data collection task, it can archive the collected configuration information. In this way, the distribution device can separately obtain the MD5 value of the target configuration information and the MD5 value of the historical configuration information collected by the distribution device last time it executed the target data collection task. Afterwards, the distribution device can judge whether the target configuration information is the same as the historical configuration information through the MD5 value. Specifically, if the MD5 value of the target configuration information is the same as the MD5 value of the historical configuration information, the distribution device can determine that the target configuration information is the same as the historical configuration information; if the MD5 value of the target configuration information is different from the MD5 value of the historical configuration information, then The distribution device may determine that the target configuration information is different from the historical configuration information.

Step 103, if not, execute the target configuration generation task corresponding to the target configuration information to generate the target configuration file.

In implementation, if the target configuration information is different from the historical configuration information, the distribution device can determine that the target configuration generation task meets the task execution conditions, so that the distribution device can execute the target configuration generation task corresponding to the target configuration information to generate the target configuration file. Further, in order to judge whether the subsequent configuration generation task is executed, the distribution device may update the recorded historical configuration information to the target configuration information, and record the MD5 value and collection time of the target configuration information as a basis for judgment.

Optionally, the execution of the target configuration generation task corresponding to the target configuration information in the above step 103, and the processing of generating the target configuration file can be specifically as follows: if the target configuration generation task is accompanied by a data integration rule, the target configuration is configured according to the data integration rule. Information is integrated, and the integrated target configuration information is packaged to generate a target configuration file; otherwise, the target configuration information is packaged to generate a target configuration file.

In an implementation, generally, the configuration information may include the first type of configuration information collected by the distribution device from the configuration information system, and the second type of configuration information uploaded manually. Operation and maintenance personnel can separately configure the configuration generation tasks corresponding to the above two types of configuration information. For the first type of configuration information, the corresponding configuration generation tasks can be accompanied by data integration rules, such as script files such as perl, shell, and python; The second type of configuration information has been manually integrated, so the corresponding configuration generation tasks do not need to be accompanied by data integration rules. In this way, the distribution device can execute the target configuration generation task according to whether the target configuration generation task is accompanied by a data integration rule. Specifically, if the target configuration generation task is accompanied by data integration rules, the distribution device can integrate the target configuration information according to the attached data integration rules. After the integration is completed, the distribution device can package the integrated target configuration information. to generate the target configuration file. If there is no data integration rule attached to the target configuration generation task, the distribution device may directly package the target configuration information to generate the target configuration file.

Optionally, after the distribution device generates the target configuration file, it may perform the following processing: determine whether the target configuration file is the same as the historical configuration file generated by executing the target configuration generation task last time.

In implementation, after the target configuration file is generated, or after the verification process exists and the target configuration file is successfully verified, the distribution device can check whether the target configuration file is consistent with the historical configuration file generated by the last execution of the target configuration generation task. The same judgment is made to determine whether to distribute the target configuration file generated this time. It is easy to understand that, for repeatedly generated configuration files, the distribution device will no longer distribute them. Specifically, the distribution device may use the above method of comparing MD5 values to determine whether the target configuration file is the same as the historical configuration file generated by executing the target configuration generation task last time. If the target configuration file is different from the historical configuration file generated by the last execution of the target configuration generation task, the distribution device can execute the target configuration distribution task corresponding to the target configuration file. At the same time, it can record the version information of the target configuration file, which is convenient for operation and maintenance personnel View the version history of each configuration file, track historical configurations, and troubleshoot problems. If the target configuration file is the same as the historical configuration file generated by executing the target configuration generation task last time, the distribution device will no longer distribute the target configuration file.

Optionally, the distribution device can verify the generated target configuration file, and the corresponding processing can be as follows: verify the target configuration file; Whether the historical configuration files are the same; if the verification fails, the target configuration file will be intercepted and an alarm message will be issued.

In implementation, in order to ensure the integrity of the configuration file, the distribution device may verify the target configuration file after generating the target configuration file. Specifically, the distribution device may verify the content of the target configuration file according to the verification rule, such as verifying the script file. If the verification is successful, the distribution device can proceed to the next step of processing, that is, to judge whether the target configuration file is the same as the historical configuration file generated by executing the target configuration generation task last time. If the verification fails, the distribution device can intercept the target configuration file, and at the same time send out an alarm message, such as an email addressed to the operation and maintenance personnel.

Step 104, execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the service server corresponding to the target configuration distribution task.

In implementation, after the distribution device determines that the target configuration file is different from the historical configuration file generated by executing the target configuration generation task last time, it can execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the target configuration distribution The business server corresponding to the task can realize the distribution and processing of configuration information. Further, in order to judge whether the subsequent configuration distribution task is executed, the distribution device may update the recorded historical configuration file to the target configuration file, and record the MD5 value of the target configuration file as a basis for judgment. In this way, the distribution device can be used as the middleware between each business server and each configuration information system, which removes the coupling between the business server and the configuration information system, and then when the configuration information system is upgraded or the policy is changed, the business server side can Perception, so that there is no need to upgrade a large number of business servers, only the configuration information system and distribution equipment need to be upgraded, which not only reduces the upgrade cost, but also makes the upgrade more flexible. In addition, the business server can obtain configuration information from the configuration information system without calling the service interface provided by the configuration information system. Access pressure when the business server obtains configuration information. Further, since the service server no longer integrates the configuration information, this part of the integration capability can be released, effectively improving the resource utilization of the service server.

Optionally, the execution of the target configuration distribution task corresponding to the target configuration file in the above step 104, and the processing of distributing the target configuration file to the service server corresponding to the target configuration distribution task can be specifically as follows: obtain all pending Distribute the group's respective server lists; distribute the target configuration files to all business servers recorded in the server list.

In the implementation, the operation and maintenance personnel can divide the business servers into groups in advance, for example, according to the business category, so that the distribution device can uniformly push the configuration files to the business servers corresponding to a certain type of business within the same period of time to ensure These service servers can process services in a timely manner according to the latest configuration files to ensure uniform and accurate service processing. Specifically, the distribution device can maintain a server list of each group, and the communication identification of the corresponding service server can be recorded in the list, such as IP (Internet Protocol, network interconnection protocol) address, MAC (Media Access Control, media access control) address wait. In this way, when the distribution device executes the target configuration distribution task corresponding to the target configuration file, it can distribute the target configuration file to the services recorded in all the server lists according to the obtained server lists of all groups to be distributed corresponding to the target configuration distribution task. server. Further, if there is a group that fails to distribute, such as a service server that fails to distribute or a newly added service server in the group, the distribution device can periodically redistribute the target configuration file to the group that fails to distribute, that is, the target configuration file Distribute to the business server that fails to distribute or the newly added business server until the target configuration file is successfully distributed to all groups.

An architecture diagram of a distribution device is given below. As shown in Figure 2, the distribution device may include a management platform, a task scheduling module, a data collection module, a configuration integration module, a configuration distribution module, and operating environments such as task information channels and databases.

The management platform can be a web application. Operation and maintenance personnel can log in to the management platform and perform online management configurations, such as group configuration, collection policy management, grayscale testing, and configuration integration strategies, etc., providing a one-stop management site. It is worth mentioning that since the distribution device adopts the method of distributing configuration files, operation and maintenance personnel can conduct online grayscale testing more conveniently.

The task scheduling module can schedule and maintain various tasks.

The data collection module can collect configuration data through distributed operations according to preset collection parameters and store them in the server disk.

The configuration integration module can generate configuration files according to the configuration parameters that have taken effect on the management platform through distributed operations, and store them in the server disk.

The configuration distribution module can distribute the generated configuration files to the corresponding business servers in accordance with the distribution strategy maintained on the management platform through distributed operations.

The task information channel can be built based on redis and zookeeper, and is used to transmit various data required for task execution, such as configuration information and configuration files. It is worth mentioning that the above-mentioned task scheduling module, data collection module, configuration integration module and configuration distribution module can run in parallel, and their running order is not in particular order, and each module can independently interact with the task information channel for data.

In this embodiment, the target data collection task is executed, and the target configuration information corresponding to the target data collection task is collected from the configuration information system; the target configuration information and the history collected by the last execution of the target data collection task are judged Whether the configuration information is the same; if not, execute the target configuration generation task corresponding to the target configuration information to generate a target configuration file; execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the The business server corresponding to the target configuration distribution task. In this way, the distribution device can directly distribute the configuration files to the business server, so that the business server does not need to obtain the configuration information from the configuration information system by calling the service interface provided by the configuration information system, which not only saves the time consumed by the business server to obtain configuration information Machine resources also reduce the access pressure of the configuration information system when facing a large number of business servers to obtain configuration information. In addition, the distribution device serves as the middleware between each business server and each configuration information system, which removes the coupling between the business server and the configuration information system. When the configuration information system is upgraded or the policy is changed, the business server side has no perception, thus There is no need to upgrade a large number of business servers, only the configuration information system and distribution equipment need to be upgraded, which not only reduces the upgrade cost, but also makes the upgrade more flexible. In addition, since the business server no longer integrates the configuration information, the integration capability of the business server can be released, further improving the resource utilization of the business server.

Based on the same technical concept, an embodiment of the present invention also provides a device for distributing configuration information, as shown in Figure 3, the device includes:

The collection module 301 is configured to execute the target data collection task, and collect the target configuration information corresponding to the target data collection task from the configuration information system;

A first judging module 302, configured to judge whether the target configuration information is the same as the historical configuration information collected during the last execution of the target data collection task;

A generation module 303, configured to execute a target configuration generation task corresponding to the target configuration information, and generate a target configuration file;

The distribution module 304 is configured to execute the target configuration distribution task corresponding to the target configuration file, and distribute the target configuration file to the service server corresponding to the target configuration distribution task.

Optionally, the collection module 301 is also used for:

Acquiring the difference between the current moment and the last execution moment of the target data collection task;

If the difference is greater than or equal to a preset execution period, the target data collection task is executed.

Optionally, the first judging module 302 is also configured to:

Obtain the MD5 value of the target configuration information;

If the MD5 value of the target configuration information is the same as the MD5 value of the historical configuration information, it is judged that the target configuration information is the same as the historical configuration information, otherwise it is judged that the target configuration information is different from the historical configuration information .

Optionally, the generating module 303 is also used for:

If the target configuration generation task is accompanied by data integration rules, the target configuration information is integrated according to the data integration rules, and the integrated target configuration information is packaged to generate the target configuration file; otherwise, all Package the above target configuration information to generate a target configuration file.

Optionally, as shown in FIG. 4, the device further includes a second judging module 305, configured to:

After the target configuration file is generated, it is judged whether the target configuration file is the same as the historical configuration file generated by executing the target configuration generating task last time.

Optionally, as shown in FIG. 5, the device further includes a verification module 306, configured to:

After generating the target configuration file, verifying the target configuration file;

If the verification is successful, the second judging module 305 judges whether the target configuration file is the same as the historical configuration file generated by executing the target configuration generation task last time;

If the verification fails, the target configuration file is intercepted and an alarm message is issued.

Optionally, the distribution module 304 is further configured to:

Obtain the respective server lists of all groups to be distributed corresponding to the target configuration distribution task;

Distributing the target configuration file to all service servers recorded in the server list.

It should be noted that: when the configuration information distribution device provided by the above-mentioned embodiment performs distribution processing of configuration information, it only uses the division of the above-mentioned functional modules as an example for illustration. In practical applications, the above-mentioned functions can be allocated by different The functional modules are completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device for distributing configuration information provided by the above embodiment and the embodiment of the method for distributing configuration information belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.

Based on the same technical concept, an embodiment of the present invention also provides a distribution device, which may have large differences due to different configurations or performances, including one or more memory and processors, where the memory may be Temporary storage or permanent storage. The memory may store at least one instruction, at least one section of program, code set or instruction set, the at least one instruction, the at least one section of program, the code set or instruction set are loaded and executed by the processor to implement the above step 101 - Distribution process of configuration information in step 104 .

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware, and can also be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk, and the like.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection of the present invention. within range.

Claims (9)

1. A method for distributing configuration information, wherein the method is applied to a distribution device, and the method comprises the following steps:

executing a target data acquisition task, and acquiring target configuration information corresponding to the target data acquisition task from a configuration information system;

judging whether the target configuration information is the same as historical configuration information acquired by executing the target data acquisition task last time;

if not, executing a target configuration generation task corresponding to the target configuration information, and generating a target configuration file, wherein the target configuration generation task comprises the following steps: if the target configuration generation task is accompanied by a data integration rule, integrating the target configuration information according to the data integration rule, packaging the integrated target configuration information to generate a target configuration file, and otherwise, packaging the target configuration information to generate a target configuration file;

and executing a target configuration distribution task corresponding to the target configuration file, and distributing the target configuration file to a service server corresponding to the target configuration distribution task.

2. The method of claim 1, wherein performing a target data collection task comprises:

acquiring a difference value between the current moment and the execution moment of executing the target data acquisition task last time;

and if the difference value is larger than or equal to a preset execution period, executing the target data acquisition task.

3. The method according to claim 1, wherein after the executing the target configuration generation task corresponding to the target configuration information and generating the target configuration file, the method further comprises:

and judging whether the target configuration file is the same as a historical configuration file generated by executing the target configuration generation task last time.

4. The method according to claim 1, wherein after the executing the target configuration generation task corresponding to the target configuration information generates the target configuration file, the method further comprises:

verifying the target configuration file;

if the verification is successful, judging whether the target configuration file is the same as a historical configuration file generated by executing the target configuration generation task last time;

and if the verification fails, intercepting the target configuration file and sending out alarm information.

5. The method according to claim 1, wherein the executing a target configuration distribution task corresponding to the target configuration file and distributing the target configuration file to a service server corresponding to the target configuration distribution task includes:

acquiring respective server lists of all groups to be distributed corresponding to the target configuration distribution task;

and distributing the target configuration file to all the service servers recorded in the server list.

6. An apparatus for distributing configuration information, the apparatus being applied to a distribution device, the apparatus comprising:

the acquisition module is used for executing a target data acquisition task and acquiring target configuration information corresponding to the target data acquisition task from a configuration information system;

the first judgment module is used for judging whether the target configuration information is the same as the historical configuration information acquired by executing the target data acquisition task last time;

a generating module, configured to execute a target configuration generating task corresponding to the target configuration information, and generate a target configuration file, where the generating module includes: if the target configuration generation task is accompanied by a data integration rule, integrating the target configuration information according to the data integration rule, packaging the integrated target configuration information to generate a target configuration file, otherwise, packaging the target configuration information to generate the target configuration file;

and the distribution module is used for executing a target configuration distribution task corresponding to the target configuration file and distributing the target configuration file to a service server corresponding to the target configuration distribution task.

7. The apparatus of claim 6, wherein the acquisition module is further configured to:

acquiring a difference value between the current moment and the execution moment of executing the target data acquisition task last time;

and if the difference value is larger than or equal to a preset execution period, executing the target data acquisition task.

8. A distribution device, characterized in that the distribution device comprises a processor and a memory, in which at least one instruction, at least one program, set of codes or set of instructions is stored, which is loaded and executed by the processor to implement the distribution method of configuration information according to any one of claims 1 to 5.

9. A computer-readable storage medium, having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the method of distributing configuration information according to any one of claims 1 to 5.

Images