CN109005071A - A kind of decision and deployment method and controlling equipment - Google Patents

Abstract

The invention discloses a decision-making deployment method and scheduling equipment, belonging to the technical field of load balancing. The method includes: the target decision-making unit of the target scheduling device acquires the target scheduling number corresponding to the target domain name system; the target decision-making unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data , and send the target deployment task to the target deployment unit of the target scheduling device; the target deployment unit executes the target deployment task and updates the target configuration information. By adopting the invention, the efficiency of decision-making and deployment can be improved.

Description

A decision-making deployment method and scheduling equipment

technical field

The invention relates to the technical field of load balancing, in particular to a decision-making deployment method and scheduling equipment.

Background technique

A CDN (Content Delivery Network, content distribution network) system may include a scheduling device and a large number of CDN servers for processing CDN service requests. The scheduling device schedules and manages the above CDN servers according to configuration information, wherein each domain name may be recorded in the configuration information The set of IP addresses of the CDN servers corresponding to the system at different division levels.

As time goes by, some CDN servers may experience scenarios such as insufficient bandwidth, performance degradation, or even failures that do not meet the requirements of carrying services. At this time, it is necessary to update the configuration information to replace these CDN servers that do not meet the scheduling requirements or delete. The scheduling device can obtain the scheduling data of each CDN server in the CDN system, such as the domain name system to which a certain CDN server belongs, disaster recovery information, and scheduling data such as the redundant bandwidth and health value of the CDN server, and based on these scheduling data, the above configuration Information is updated. When the configuration information is updated, the decision-making unit in the scheduling device generates a deployment task for updating the configuration information based on the scheduling data, and then the decision-making unit sends the deployment task to the deployment unit in the scheduling device. After receiving the deployment task, the deployment unit may execute the deployment task to update the above configuration information.

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

With the continuous expansion of the number of CDN servers, a large amount of scheduling data is generated, and the existing scheduling equipment is usually a single decision-making unit and a single deployment unit architecture, resulting in a single decision-making unit and a single deployment unit facing a high load, requiring more It takes a long time to complete the update processing of the configuration information, so the efficiency of the above-mentioned decision-making deployment processing is low.

Contents of the invention

In order to solve the problems in the prior art, an embodiment of the present invention provides a decision deployment method and a scheduling device. Described technical scheme is as follows:

In the first aspect, a decision-making and deployment method is provided, the decision-making and deployment method is applied to a scheduling device, and the scheduling device includes a plurality of decision-making units and a plurality of deployment units, and the scheduling device pre-determines each of the decision-making units and each of the The deployment unit assigns a domain name system, wherein the method includes:

The target decision-making unit of the target scheduling device acquires target scheduling data corresponding to the target domain name system;

The target decision-making unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to the target deployment unit of the target scheduling device;

The target deployment unit executes the target deployment task, and updates the target configuration information.

Further, the target dispatching device pre-allocates a domain name system for each of the decision-making units and each of the deployment units, including:

The target dispatching device configures unit identifiers for each of the decision-making units and each of the deployment units, establishes a mapping relationship between each domain name system and each of the unit identifiers, and based on the mapping relationship configures each of the decision-making units and each of the deployment units The Deployment Unit is assigned the Domain Name System.

Further, the target decision-making unit of the target scheduling device acquires target scheduling data corresponding to the target domain name system, including:

The target decision-making unit sends a scheduling data acquisition request to the target scheduling device based on the mapping relationship between the target domain name system and the unit identifier of the target decision-making unit, so that the target scheduling device will pre-acquire the target The target scheduling data corresponding to the domain name system is returned to the target decision unit.

Further, the sending the target deployment task to the target deployment unit of the target scheduling device includes:

The target decision-making unit determines the unit identifier of the target deployment unit corresponding to the target domain name system based on the mapping relationship between the target domain name system and the unit identifier of the target deployment unit;

The target decision-making unit sends the target deployment task to the target deployment unit based on the unit identifier of the target deployment unit.

Further, the method also includes:

The target scheduling device periodically detects the working status of each of the decision-making units and each of the deployment units;

If it is detected that the target decision-making unit is in a failure state, then based on a preset disaster recovery standard, determine the disaster recovery decision of the target decision-making unit in the target scheduling device or in other scheduling devices other than the target scheduling device unit;

Or, if it is detected that the target deployment unit is in a failure state, then based on a preset disaster recovery standard, determine the capacity of the target deployment unit in the target scheduling device or in other scheduling devices other than the target scheduling device. Disaster deployment unit.

Further, the determining the disaster recovery decision-making unit of the target decision-making unit in the target dispatching device or other dispatching devices other than the target dispatching device based on preset disaster recovery standards includes:

When the target scheduling device has at least one decision-making unit that meets the preset disaster recovery standard, determine the disaster recovery decision-making unit of the target decision-making unit in the at least one decision-making unit;

Or, when none of the remaining decision-making units of the target scheduling device meets the preset disaster recovery standard, and there is at least one decision-making unit that meets the preset disaster recovery standard among other scheduling devices in the cluster where the target scheduling device is located, the determining the disaster recovery decision-making unit of the target decision-making unit in the at least one decision-making unit;

Or, when the remaining decision-making units of the target scheduling device and the decision-making units in other scheduling devices in the cluster where the target scheduling device is located do not meet the preset disaster recovery standards, and other scheduling devices outside the cluster where the target scheduling device is located When there is at least one decision-making unit that meets the preset disaster recovery standard, the disaster recovery decision-making unit of the target decision-making unit is determined in the at least one decision-making unit.

Further, the determining the disaster recovery deployment unit of the target deployment unit in the target scheduling device or other scheduling devices other than the target scheduling device based on preset disaster recovery standards includes:

When the target scheduling device has at least one deployment unit that meets the preset disaster recovery standard, determine the disaster recovery deployment unit of the target deployment unit in the at least one deployment unit;

Or, when none of the remaining deployment units of the target scheduling device meets the preset disaster recovery standard, and there is at least one deployment unit that meets the preset disaster recovery standard among other scheduling devices in the cluster where the target scheduling device is located, the determining the disaster recovery deployment unit of the target deployment unit in the at least one deployment unit;

Or, when the remaining deployment units of the target scheduling device and the deployment units in other scheduling devices in the cluster where the target scheduling device is located do not meet the preset disaster recovery standards, and other scheduling devices outside the cluster where the target scheduling device is located When there is at least one deployment unit meeting the preset disaster recovery standard, determine the disaster recovery deployment unit of the target deployment unit in the at least one deployment unit.

In a second aspect, a scheduling device is provided, the scheduling device includes a plurality of decision-making units and a plurality of deployment units, and the scheduling device pre-assigns a domain name system to each of the decision-making units and each of the deployment units, wherein:

The target decision-making unit is configured to acquire target scheduling data corresponding to the target domain name system;

The target decision-making unit is further configured to generate a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and send the target deployment task to the target deployment unit;

The target deployment unit is configured to execute the target deployment task and update the target configuration information.

Further, the scheduling device also includes an allocation unit, configured to:

Configuring unit identifiers for each of the decision-making units and each of the deployment units, establishing a mapping relationship between each domain name system and each of the unit identifiers, and assigning a domain name to each of the decision-making units and each of the deployment units based on the mapping relationship system.

Further, the dispatching device also includes a disaster recovery unit, which is used for:

Periodically detect the working status of each of the decision-making units and each of the deployment units;

If it is detected that the target decision-making unit is in a failure state, then based on a preset disaster recovery standard, determine the disaster recovery decision of the target decision-making unit in the target scheduling device or in other scheduling devices other than the target scheduling device unit;

Or, if it is detected that the target deployment unit is in a failure state, then based on a preset disaster recovery standard, determine the capacity of the target deployment unit in the target scheduling device or in other scheduling devices other than the target scheduling device. Disaster deployment unit.

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

In this embodiment, the target decision-making unit of the target scheduling device acquires the target scheduling data corresponding to the target domain name system; the target decision-making unit generates and updates the target configuration information corresponding to the target domain name system based on the target scheduling data. task, and send the target deployment task to the target deployment unit of the target scheduling device; the target deployment unit executes the target deployment task and updates the target configuration information. In this way, by splitting a single decision-making unit in a scheduling device into multiple decision-making units, and splitting a single deployment unit into multiple deployment units, a scheduling device architecture with multiple decision-making units and multiple deployment units is built. All domain name systems can be assigned to each decision-making unit and deployment unit on a unit basis, so that each decision-making unit is only responsible for generating deployment tasks for updating the configuration information corresponding to the assigned domain name system, and each deployment unit is only responsible for Execute the deployment tasks corresponding to the assigned domain name system, and then make full use of the system resources of the scheduling device, improve the processing efficiency of each unit, shorten the time for updating the configuration information corresponding to each domain name system, and thus improve decision-making deployment. Processing efficiency. In addition, the scheduling device can schedule and manage the CDN server based on the latest updated configuration information as much as possible, thereby improving the scheduling quality.

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 flow chart of a decision deployment method provided by an embodiment of the present invention;

Fig. 2 is a schematic structural diagram of a scheduling device provided by an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a scheduling device provided by an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a scheduling device provided by an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of a scheduling device 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.

An embodiment of the present invention provides a method for decision-making and deployment. The execution subject of the method may be a dispatching device, and the dispatching device may be a dispatching server of a CDN system, which may be deployed in a computer room of a CDN service provider. The scheduling device can maintain the configuration information, which can record the set of IP addresses of the CDN servers corresponding to each domain name system, as well as information such as primary domain names, secondary domain names, and regions in the domain name system. When a user accesses a domain name with any terminal (such as a smart phone, a tablet computer, etc.), if the domain name system provides acceleration services for the domain name, the scheduling device can determine one or more appropriate CDN servers for the domain name based on the configuration information above. The domain name provides acceleration services, that is, the IP address of the CDN server is returned to the above-mentioned terminal through resolution, and then users can request corresponding network resources through the IP address. The above-mentioned CDN server can be an arbitrary server or a CDN service cluster composed of multiple servers. The CDN server can be used to cache network resources. If the network resource already exists in the CDN server, it can be directly returned to the terminal. Otherwise, the CDN server can pull the above-mentioned network resources from the source station, and then return them to the terminal.

It should be noted that the above scheduling device can split a single decision-making unit into multiple decision-making units, and split a single deployment unit into multiple deployment units, wherein each decision-making unit can be any A decision-making process or a decision-making thread, each deployment unit may be any deployment process or deployment thread running on the target scheduling device. The above-mentioned decision-making unit can generate a deployment task for updating the configuration information corresponding to a certain domain name system. The above-mentioned deployment unit can receive the above-mentioned deployment task generated by the above-mentioned decision-making unit, and then execute the deployment task. The IP (Internet Protocol, Internet Protocol) address of the CDN server to be scheduled corresponding to the domain name system is updated. The above scheduling device can pre-allocate the domain name system for each decision-making unit and each deployment unit.

The above-mentioned scheduling device may include a processor, a memory, and a transceiver. The processor may be used to perform scheduling processing in the following processes, and the memory may be used to store data required and generated during the following processing. The transceiver may use To receive and send data related to the processing described below.

The following will describe in detail the processing flow of a decision-making deployment method shown in Figure 1 in combination with specific implementation methods, and the content may be as follows:

Step 101: The target decision-making unit of the target scheduling device acquires target scheduling data corresponding to the target domain name system.

In implementation, a scheduling device of the CDN system (which may be referred to as a target scheduling device) can pre-configure the access domain name system in the CDN system for each website domain name system based on the CNAME technology. As an example, the target domain name system of the accelerated service platform of the above-mentioned CDN system can be www.abc.com. When a user visits www.baidu.com, the user domain name www.baidu.com can be connected to the above-mentioned accelerated service platform. Domain name system www.abc.com for acceleration services. Specifically, you can add a CNAME record to the above domain name in the domain name resolution configuration, so that the domain name www.baidu.com can point to www.abc.com (generally, the platform also supports CNAME to the second-level domain name, such as www.abc. com can CNAME to www.xyx.abc.com, this process will not be highlighted in this solution). When a user accesses the domain name www.baidu.com, the user can enter the user domain name in the browser program running on the terminal and click the access button to access the website. In this way, the terminal initiates a domain name resolution request for the above-mentioned domain name www.baidu.com to the above-mentioned acceleration service platform. Afterwards, the target dispatching device may return an IP address of a CDN server to the terminal based on the above domain name resolution request and configuration information corresponding to the target domain name system www.abc.com. Furthermore, the terminal can obtain corresponding network resources through the CDN server corresponding to the above IP address.

In this way, the target scheduling device can obtain the scheduling data (which may be referred to as target scheduling data) of each CDN server to be scheduled corresponding to the target domain name system based on the target domain name system, and the target scheduling data can include dynamic data and static data, wherein the dynamic data It can include data such as real-time bandwidth, peak bandwidth, and health value of each CDN server; static data can include modeling data of all CDN servers in the above-mentioned CDN system, such as primary domain name, secondary domain name, region, cluster, IP, etc., and Data such as the disaster recovery decision-making unit corresponding to each decision-making unit or the disaster recovery information of the disaster recovery deployment unit corresponding to each deployment unit are recorded. Static data can be stored in a database, which can be deployed in the target scheduling device or distributed Deployed in other scheduling devices, it is not limited here. Afterwards, the decision-making unit (may be referred to as a target decision-making unit) corresponding to the above-mentioned target domain name system in the target scheduling device can acquire the above-mentioned target scheduling data.

Optionally, the above-mentioned target scheduling device may pre-allocate the domain name system for each decision-making unit. Correspondingly, the specific processing may be as follows: the target scheduling device configures a unit identifier for each decision-making unit, and assigns a domain name system for each decision-making unit based on the unit identifier.

In implementation, the target scheduling device may pre-configure unit identifiers for each decision-making unit based on its own device identifier and the process number of each decision-making process. Specifically, the target dispatching device may use dispatchIP+serverID to identify each decision-making unit, where dispatchIP may be the device identifier of the target dispatching device, such as the IP address of the target dispatching device, and serverID may be a unit serial number pre-assigned by the target dispatching device, where It can be a string of characters, such as 001, 002, etc. For example, dispatchIP is the IP address 210.61.180.132. If the target dispatching device has four decision-making units, you can use 210.61.180.132: 001, 210.61.180.132: 002, 210.61 .180.132:003, 210.61.180.132:004 to identify these four decision-making units respectively. Afterwards, the target dispatching device may assign a domain name system to each decision-making unit based on the respective unit identifiers of each decision-making unit. Taking M domain name systems and N decision-making units as an example (M≥N), M domain name systems can be marked as A ₁ , A ₂ , A ₃ ... A _M , and N decision-making units can be marked as B ₁ , B ₂ , B ₃ ... B _N , the target dispatching device can randomly assign M domain name systems to N decision-making units, or assign them according to preset rules. as follows:

B ₁ : A ₁ , A _N+1 , A _2N+1 …;

B ₂ : A ₂ , A _N+2 , A _2N+2 …;

B ₃ : A ₃ , A _N+3 , A _2N+3 …;

B _N : A _N , A _2N , A _3N . . .

Optionally, the target decision-making unit of the above-mentioned target scheduling device may process the target scheduling data corresponding to the target domain name system as follows: the target decision-making unit sends a scheduling data acquisition request to the target scheduling device based on the target domain name system and the unit identifier of the target decision-making unit , so that the target scheduling device returns the pre-acquired target scheduling data corresponding to the target domain name system to the target decision-making unit.

In implementation, the target dispatching device may obtain the dispatching data corresponding to each domain name system in advance, or may obtain the dispatching data corresponding to a domain name system in real time after receiving a request for obtaining dispatching data from a certain domain name system. In this way, the target decision-making unit can send a scheduling data acquisition request to the target scheduling device based on the target domain name system and the unit identifier of the target decision-making unit. After receiving the scheduling data acquisition request, the target scheduling device may return the pre-acquired or real-time target scheduling data corresponding to the target domain name system to the target decision-making unit based on the unit identifier of the target decision-making unit. In this way, the target decision-making unit may receive target scheduling data corresponding to the target domain name system from the target scheduling device.

Step 102: The target decision-making unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to the target deployment unit of the target scheduling device.

In implementation, after the target decision-making unit obtains the target scheduling data corresponding to the target domain name system, it can perform decision-making processing based on the target scheduling data, and judge whether each CDN server to be scheduled in the current configuration information corresponding to the target domain name system meets the scheduling requirements , when there are CDN servers that do not meet the scheduling requirements, the target decision-making unit can delete or replace the CDN servers that do not meet the scheduling requirements by sending a deployment task to the target deployment unit of the target scheduling device.

Optionally, the above-mentioned target scheduling device may pre-allocate a domain name system for each deployment unit. Correspondingly, the specific processing may be as follows: the target scheduling device configures a unit ID for each deployment unit, and allocates a domain name system for each deployment unit based on the unit ID.

In an implementation, the target scheduling device may pre-configure unit identifiers for each deployment unit based on its own device identifier and the process number of each deployment process. Specifically, the target scheduling device may also identify each deployment unit in the manner of dispatchIP+serverID. Afterwards, the target scheduling device may assign a domain name system to each deployment unit based on the respective unit identifiers of each deployment unit. Taking M domain name systems and N deployment units as an example (M≥N), M domain name systems can be marked as A ₁ , A ₂ , A ₃ ... A _M , and N deployment units can be marked as C ₁ , C ₂ , C ₃ ... C _N , the target dispatching device can randomly assign M domain name systems to N deployment units, or assign them according to preset rules. as follows:

C ₁ : A ₁ , A _N+1 , A _2N+1 ...;

C ₂ : A ₂ , A _N+2 , A _2N+2 ...;

C ₃ : A ₃ , A _N+3 , A _2N+3 ...;

C _N : A _N , A _2N , A _3N . . .

Optionally, the process of sending the target deployment task to the target deployment unit by the above-mentioned target decision-making unit may be specifically as follows: the target decision-making unit determines the unit identifier of the target deployment unit corresponding to the target domain name system based on the target domain name system; The unit identifier of the deployment unit, which sends the target deployment task to the target deployment unit.

In implementation, after the target decision-making unit generates the target deployment task for updating the target configuration information corresponding to the target domain name system, it can determine the unit identifier of the target deployment unit corresponding to the target domain name system based on the target domain name system. Afterwards, the target decision-making unit may send the target deployment task to the target deployment unit based on the unit identifier of the target deployment unit.

Step 103: the target deployment unit executes the target deployment task, and updates the target configuration information.

In implementation, after receiving the target deployment task, the target deployment unit may execute the target deployment task and update the target configuration information corresponding to the target domain name system. Specifically, based on the task details of the target deployment task, the target deployment unit can obtain the change information of the current configuration information corresponding to the target domain name system, such as the IP address of the CDN server to be deleted in each area of the target domain name system or the newly added CDN The IP address of the server, and then the target deployment unit can update the target configuration information based on the change information.

Optionally, corresponding disaster recovery units can also be configured for each decision-making unit and each deployment unit. Correspondingly, the specific processing can be as follows: the target scheduling device periodically detects the working status of each decision-making unit and each deployment unit; If the decision-making unit is in a failure state, the disaster recovery decision-making unit of the target decision-making unit is determined in the target dispatching device or other dispatching devices other than the target dispatching device based on the preset disaster recovery standard; or, if it is detected that the target deployment unit is in failure The disaster recovery deployment unit of the target deployment unit is determined in the target scheduling device or other scheduling devices other than the target scheduling device based on the preset disaster recovery standard.

In implementation, the CDN system can deploy multiple dispatching devices in different computer rooms, and the decision-making unit that meets the preset disaster recovery standard in each dispatching device can be used as the disaster recovery decision-making unit of other decision-making units, wherein the preset disaster recovery standard can be Disaster recovery standards include the average processing time (x) being less than the preset processing time (x'), the queue space usage rate (y) being less than the preset threshold (y'), and so on.

For example, the disaster recovery function f(x, y) can be simply expressed by two-dimensional indicators, 0: disaster recovery, 1: normal,

Further, the target scheduling device may periodically detect the working status of each decision-making unit and each deployment unit. Specifically, the scheduling device can periodically collect health data of each decision-making unit, such as average processing time, heartbeat packets, queue capacity, IO read and write, CPU usage, and other information. The aforementioned health data of the decision-making unit are collected. In this way, the scheduling device can determine whether each decision-making unit or each deployment unit is faulty based on the health data.

In this way, when it is detected that the target decision-making unit is in a fault state, the target dispatching device can determine the disaster recovery decision-making unit of the target decision-making unit in the target dispatching device or other dispatching devices other than the target dispatching device based on the above-mentioned preset disaster recovery standard ; When detecting that the target deployment unit is in a fault state, the target scheduling device can determine the disaster recovery deployment unit of the target deployment unit in the target scheduling device or other scheduling devices other than the target scheduling device based on preset disaster recovery standards.

Optionally, the above-mentioned process of determining the disaster recovery decision-making unit of the target decision-making unit may specifically be as follows: when the target dispatching device has at least one decision-making unit that meets the preset disaster recovery standard, determine the capacity of the target decision-making unit in at least one decision-making unit. or, when the rest of the decision-making units of the target scheduling device do not meet the preset disaster recovery standards, and there is at least one decision-making unit that meets the preset disaster recovery standards in other scheduling devices in the cluster where the target scheduling device is located, at least The disaster recovery decision-making unit that determines the target decision-making unit in a decision-making unit; or, when the remaining decision-making units of the target scheduling device and the decision-making units in other scheduling devices in the cluster where the target scheduling device is located do not meet the preset disaster recovery standards, and the target scheduling When there is at least one decision-making unit that meets the preset disaster recovery standard in other scheduling devices outside the cluster where the device is located, the disaster recovery decision-making unit of the target decision-making unit is determined in the at least one decision-making unit.

In implementation, when a failure of the target decision-making unit is detected, the target scheduling device may determine the disaster recovery decision-making unit of the target decision-making unit based on the disaster recovery rules of the nearest disaster recovery. For example, when there is at least one decision-making unit in the target scheduling device that meets the preset disaster recovery standard, the target scheduling device can select a decision-making unit from among the decision-making units in the target scheduling device that meet the preset disaster recovery standard as the tolerance of the target decision-making unit. Disaster decision-making unit; when the remaining decision-making units of the target scheduling device do not meet the preset disaster recovery standards, but there is at least one decision-making unit that meets the preset disaster recovery standards in other scheduling devices in the cluster where the target scheduling device is located, the target scheduling device can Select a decision-making unit as the disaster recovery decision-making unit of the target decision-making unit among other decision-making units that meet the preset disaster recovery standards in the other scheduling units of the cluster where the target scheduling device is located; None of the decision-making units in other scheduling devices meet the preset disaster recovery standards, but when there is at least one decision-making unit that meets the preset disaster recovery standards in other scheduling devices outside the cluster where the target scheduling device is located, the target scheduling device can Select a decision-making unit from the decision-making units that meet the preset disaster recovery standards in other scheduling devices outside the cluster as the disaster recovery decision-making unit of the target decision-making unit.

Optionally, the above-mentioned process of determining the disaster recovery deployment unit of the target deployment unit may specifically be as follows: when the target scheduling device has at least one deployment unit that meets the preset disaster recovery standard, determine the capacity of the target deployment unit in at least one deployment unit. disaster recovery deployment unit; or, when the remaining deployment units of the target scheduling device do not meet the preset disaster recovery standards, and there is at least one deployment unit that meets the preset disaster recovery standards in other scheduling devices in the cluster where the target scheduling device is located, at least The disaster recovery deployment unit that determines the target deployment unit in a deployment unit; or, when the remaining deployment units of the target scheduling device and the deployment units in other scheduling devices in the cluster where the target scheduling device is located do not meet the preset disaster recovery standards, and the target scheduling device When there is at least one deployment unit that meets the preset disaster recovery standard in other scheduling devices outside the cluster where the device is located, the disaster recovery deployment unit of the target deployment unit is determined in the at least one deployment unit.

In an implementation, when a failure of the target deployment unit is detected, the target scheduling device may determine the disaster recovery deployment unit of the target deployment unit based on the disaster recovery rules of the nearest disaster recovery. For example, when there is at least one deployment unit that meets the preset disaster recovery standard in the target scheduling device, the target scheduling device may select a deployment unit in the target scheduling device that meets the preset disaster recovery standard as the capacity of the target deployment unit. Disaster recovery deployment unit; when the remaining deployment units of the target scheduling device do not meet the preset disaster recovery standards, but there is at least one deployment unit that meets the preset disaster recovery standards among other scheduling devices in the cluster where the target scheduling device is located, the target scheduling device can Select a deployment unit among the deployment units that meet the preset disaster recovery standards in the other scheduling devices of the cluster where the target scheduling device is located as the disaster recovery deployment unit of the target deployment unit; None of the deployment units in other scheduling devices meet the preset disaster recovery standards, but there is at least one deployment unit that meets the preset disaster recovery standards in other scheduling devices outside the cluster where the target scheduling device is located. Select a deployment unit from the deployment units that meet the preset disaster recovery standards of other scheduling devices outside the cluster as the disaster recovery deployment unit of the target deployment unit.

In this embodiment, the target decision-making unit of the target scheduling device obtains the target scheduling data corresponding to the target domain name system; the target decision-making unit generates a target deployment task for updating the target configuration information corresponding to the target domain name system based on the target scheduling data, and deploys the target The task is sent to the target deployment unit of the target scheduling device; the target deployment unit executes the target deployment task and updates the target configuration information. In this way, by splitting a single decision-making unit in a scheduling device into multiple decision-making units, and splitting a single deployment unit into multiple deployment units, a scheduling device architecture with multiple decision-making units and multiple deployment units is built. All domain name systems can be assigned to each decision-making unit and deployment unit on a unit basis, so that each decision-making unit is only responsible for generating deployment tasks for updating the configuration information corresponding to the assigned domain name system, and each deployment unit is only responsible for Execute the deployment tasks corresponding to the assigned domain name system, and then make full use of the system resources of the scheduling device, improve the processing efficiency of each unit, shorten the time for updating the configuration information corresponding to each domain name system, and thus improve decision-making deployment. Processing efficiency. In addition, the scheduling device can schedule and manage the CDN server based on the latest updated configuration information as much as possible, thereby improving the scheduling quality.

Based on the same technical concept, the embodiment of the present invention also provides a scheduling device. As shown in FIG. and each of said deployment units is assigned a Domain Name System, wherein:

The target decision-making unit 201 is configured to acquire target scheduling data corresponding to the target domain name system;

The target decision unit 201 is further configured to generate a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and send the target deployment task to the target deployment unit 202;

The target deployment unit 202 is configured to execute the target deployment task and update the target configuration information.

As shown in FIG. 3, optionally, the scheduling device further includes an allocation unit 203, configured to:

Configuring unit identifiers for each of the decision-making units and each of the deployment units, establishing a mapping relationship between each domain name system and each of the unit identifiers, and assigning a domain name to each of the decision-making units and each of the deployment units based on the mapping relationship system.

Optionally, the target decision unit 201 is also configured to:

Based on the target domain name system and the unit identifier of the target decision-making unit 201, send a scheduling data acquisition request to the target scheduling device, so that the target scheduling device will pre-acquire the target scheduling data corresponding to the target domain name system Return to the target decision unit 201.

Optionally, the target decision unit 201 is also configured to:

Based on the target domain name system, determine the unit identifier of the target deployment unit 202 corresponding to the target domain name system;

The target deployment task is sent to the target deployment unit 202 based on the unit identifier of the target deployment unit 202 .

As shown in FIG. 4, optionally, the scheduling device further includes a disaster recovery unit 204, configured to:

Periodically detect the working status of each of the decision-making units and each of the deployment units;

If it is detected that the target decision-making unit 201 is in a failure state, the capacity of the target decision-making unit 201 is determined in the target dispatching device or in other dispatching devices other than the target dispatching device based on a preset disaster tolerance standard. Disaster decision-making unit;

Or, if it is detected that the target deployment unit 202 is in a failure state, then determine the target deployment unit 202 in the target scheduling device or in other scheduling devices other than the target scheduling device based on a preset disaster recovery standard disaster recovery deployment unit.

Optionally, the disaster recovery unit 204 is also used for:

When the target scheduling device has at least one decision-making unit that meets the preset disaster recovery standard, determine the disaster recovery decision-making unit of the target decision-making unit 201 in the at least one decision-making unit;

Or, when none of the remaining decision-making units of the target scheduling device meets the preset disaster recovery standard, and there is at least one decision-making unit that meets the preset disaster recovery standard among other scheduling devices in the cluster where the target scheduling device is located, the determining the disaster recovery decision-making unit of the target decision-making unit 201 in the at least one decision-making unit;

Or, when the remaining decision-making units of the target scheduling device and the decision-making units in other scheduling devices in the cluster where the target scheduling device is located do not meet the preset disaster recovery standards, and other scheduling devices outside the cluster where the target scheduling device is located When there is at least one decision-making unit meeting the preset disaster recovery standard, the disaster recovery decision-making unit of the target decision-making unit 201 is determined in the at least one decision-making unit.

Optionally, the disaster recovery unit 204 is also used for:

When the target scheduling device has at least one deployment unit that meets the preset disaster recovery standard, determine the disaster recovery deployment unit of the target deployment unit 202 in the at least one deployment unit;

Or, when none of the remaining deployment units of the target scheduling device meets the preset disaster recovery standard, and there is at least one deployment unit that meets the preset disaster recovery standard among other scheduling devices in the cluster where the target scheduling device is located, the Determine the disaster recovery deployment unit of the target deployment unit 202 in the at least one deployment unit;

Or, when the remaining deployment units of the target scheduling device and the deployment units in other scheduling devices in the cluster where the target scheduling device is located do not meet the preset disaster recovery standards, and other scheduling devices outside the cluster where the target scheduling device is located When there is at least one deployment unit meeting the preset disaster recovery standard, the disaster recovery deployment unit of the target deployment unit 202 is determined in the at least one deployment unit.

It should be noted that when scheduling the scheduling device provided by the above embodiments, the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to needs, that is, the device. The internal structure is divided into different functional modules to complete all or part of the functions described above. In addition, the scheduling device and the decision-making and deployment method embodiments provided by the above embodiments belong to the same concept, and the specific implementation process thereof is detailed in the method embodiments, and will not be repeated here.

Fig. 5 is a schematic structural diagram of a scheduling device provided by an embodiment of the present invention. The scheduling device 500 may have relatively large differences due to different configurations or performances, and may include one or more central processing units 522 (for example, one or more processors) and memory 532, one or more storage application programs 542 or Storage medium 530 for data 544 (eg, one or more mass storage devices). Wherein, the memory 532 and the storage medium 530 may be temporary storage or persistent storage. The program stored in the storage medium 530 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the scheduling device. Furthermore, the central processing unit 522 may be configured to communicate with the storage medium 530 , and execute a series of instruction operations in the storage medium 530 on the scheduling device 500 .

The scheduling device 500 may also include one or more power supplies 526, one or more wired or wireless network interfaces 550, one or more input and output interfaces 558, and/or, one or more operating systems 531, such as Windows Server™, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

The scheduling device 500 may include a memory, and one or more programs, wherein the one or more programs are stored in the memory, and are configured to be executed by one or more processors, including for performing The above dispatched directives.

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 (10)

1. a kind of decision and deployment method, which is characterized in that the decision and deployment method is applied to controlling equipment, the controlling equipment Including multiple decision packages and multiple deployment units, the controlling equipment is each decision package and each portion in advance It affixes one's name to unit and distributes domain name system, wherein the described method includes:

The objective decision unit of target dispatch equipment obtains the corresponding target dispatch data of target domain name system；

The objective decision unit is based on the target dispatch data, generates the corresponding target of the update target domain name system and matches The target deployment task of confidence breath, and the target deployment task is sent to the target deployment list of the target dispatch equipment Member；

The target deployment unit executes the target deployment task, updates the target configuration information.

2. the method according to claim 1, wherein the target dispatch equipment is each decision list in advance First and each deployment unit distributes domain name system, comprising:

The target dispatch equipment is each decision package and each deployment unit configuration unit mark, and is based on institute Stating unit marks is that each decision package and each deployment unit distribute domain name system.

3. according to the method described in claim 2, it is characterized in that, the objective decision unit of the target dispatch equipment obtains mesh Mark the corresponding target dispatch data of domain name system, comprising:

Unit marks of the objective decision unit based on the target domain name system and the objective decision unit, to the mesh It marks controlling equipment and sends scheduling data acquisition request, so that the target domain name system that the target dispatch equipment will obtain in advance Corresponding target dispatch data of uniting are back to the objective decision unit.

4. according to the method described in claim 2, it is characterized in that, described be sent to the target for the target deployment task The target deployment unit of controlling equipment, comprising:

The objective decision unit is based on the target domain name system, determines the corresponding target deployment list of the target domain name system The unit marks of member；

The target deployment task is sent to institute by unit marks of the objective decision unit based on the target deployment unit State target deployment unit.

5. the method according to claim 1, wherein the method also includes:

The target dispatch device periodically detects the working condition of each decision package and each deployment unit；

If detecting that the objective decision unit is in malfunction, set based on default disaster tolerance standard in the target dispatch In other controlling equipments in standby or except the target dispatch equipment, the disaster tolerance decision list of the objective decision unit is determined Member；

Alternatively, if detecting that the target deployment unit is in malfunction, based on default disaster tolerance standard in the target In other controlling equipments in controlling equipment or except the target dispatch equipment, the disaster tolerance of the target deployment unit is determined Deployment unit.

6. according to the method described in claim 5, it is characterized in that, described set based on default disaster tolerance standard in the target dispatch In other controlling equipments in standby or except the target dispatch equipment, the disaster tolerance decision list of the objective decision unit is determined Member, comprising:

When the target dispatch equipment exist meet default disaster tolerance standard at least one decision package when, it is described at least one The disaster tolerance decision package of the objective decision unit is determined in decision package；

Alternatively, remaining decision package when the target dispatch equipment does not meet default disaster tolerance standard, and the target tune When there is at least one decision package for meeting default disaster tolerance standard in other controlling equipments of cluster where degree equipment, described The disaster tolerance decision package of the objective decision unit is determined at least one decision package；

Alternatively, when other scheduling of remaining decision package of the target dispatch equipment and target dispatch equipment place cluster Decision package in equipment does not meet default disaster tolerance standard, and other scheduling where the target dispatch equipment outside cluster When there is at least one decision package for meeting default disaster tolerance standard in equipment, institute is determined at least one described decision package State the disaster tolerance decision package of objective decision unit.

7. according to the method described in claim 5, it is characterized in that, described set based on default disaster tolerance standard in the target dispatch In other controlling equipments in standby or except the target dispatch equipment, determine that the disaster tolerance deployment of the target deployment unit is single Member, comprising:

When the target dispatch equipment exist meet default disaster tolerance standard at least one deployment unit when, it is described at least one The disaster tolerance deployment unit of the target deployment unit is determined in deployment unit；

Alternatively, remaining deployment unit when the target dispatch equipment does not meet default disaster tolerance standard, and the target tune When there is at least one deployment unit for meeting default disaster tolerance standard in other controlling equipments of cluster where degree equipment, described The disaster tolerance deployment unit of the target deployment unit is determined at least one deployment unit；

Alternatively, when other scheduling of remaining deployment unit of the target dispatch equipment and target dispatch equipment place cluster Deployment unit in equipment does not meet default disaster tolerance standard, and other scheduling where the target dispatch equipment outside cluster When there is at least one deployment unit for meeting default disaster tolerance standard in equipment, institute is determined at least one described deployment unit State the disaster tolerance deployment unit of target deployment unit.

8. a kind of controlling equipment, which is characterized in that the controlling equipment includes multiple decision packages and multiple deployment units, described Controlling equipment is each decision package and each deployment unit distribution domain name system in advance, in which:

The objective decision unit, for obtaining the corresponding target dispatch data of target domain name system；

The objective decision unit is also used to that it is corresponding to generate the update target domain name system based on the target dispatch data Target configuration information target deployment task, and the target deployment task is sent to the target deployment unit；

The target deployment unit updates the target configuration information for executing the target deployment task.

9. controlling equipment according to claim 8, which is characterized in that the controlling equipment further includes allocation unit, is used for:

It is identified for each decision package and each deployment unit configuration unit, and is each based on the unit marks The decision package and each deployment unit distribute domain name system.

10. controlling equipment according to claim 8, which is characterized in that the controlling equipment further includes disaster tolerance unit, is used In:

It is periodically detected the working condition of each decision package and each deployment unit；

If detecting that the objective decision unit is in malfunction, set based on default disaster tolerance standard in the target dispatch In other controlling equipments in standby or except the target dispatch equipment, the disaster tolerance decision list of the objective decision unit is determined Member；

Alternatively, if detecting that the target deployment unit is in malfunction, based on default disaster tolerance standard in the target In other controlling equipments in controlling equipment or except the target dispatch equipment, the disaster tolerance of the target deployment unit is determined Deployment unit.