WO2023115591A1

WO2023115591A1 - Automatic arrangement method and apparatus for cdn nodes

Info

Publication number: WO2023115591A1
Application number: PCT/CN2021/141410
Authority: WO
Inventors: 孙涛
Original assignee: 江苏云工场信息技术有限公司
Priority date: 2021-12-20
Filing date: 2021-12-25
Publication date: 2023-06-29
Also published as: CN114327507B; CN114327507A

Abstract

The present application provides an automatic arrangement method for CDN nodes, comprising: deploying a K8S cluster in a central server; packaging application services of CDN nodes into container images, comprising a central node image, a regional node image, and an edge node image; compiling, according to the container images, K8S deployment files, comprising a central deployment file, a regional deployment file, and an edge deployment file corresponding to the central node image, the regional node image, and the edge node image; and deploying the container images to the CDN nodes by means of the K8S cluster according to the deployment files. CDN nodes are collectively managed and deployed by means of K8S, the CDN nodes do not need to be manually installed and deployed on site, the time and labor costs are saved, and it is easier to deploy. The present application further provides an automatic arrangement apparatus for CDN nodes.

Description

A method and device for automatically orchestrating CDN nodes

technical field

The present application relates to a CDN node deployment technology, in particular to a method for automatically orchestrating CDN nodes. The present application also relates to an automatic arrangement device for CDN nodes.

Background technique

The basic idea of CDN (Content Distribution Network) is to avoid bottlenecks and links on the Internet that may affect the speed and stability of data transmission as much as possible, so as to make content transmission faster and more stable.

CDN is a layer of intelligent virtual network based on the existing Internet by placing node servers all over the network. Comprehensive information such as response time redirects the user's request to the service node closest to the user. Its purpose is to enable users to obtain the required content nearby, solve the congestion situation of the Internet network, and improve the response speed of users' access to websites. CDN nodes are distributed and deployed in various regions of the country, and there may be service association and communication between nodes.

In the prior art, the deployment of CDN nodes needs to be carried out manually on the spot, which is difficult to deploy, and the cost of manpower, time and capital is huge.

Contents of the invention

In order to solve the problem of difficulty in deploying CDN nodes, the present application provides an automatic orchestration method for CDN nodes. The present application also relates to an automatic arrangement device for CDN nodes.

This application provides an automatic orchestration method for CDN nodes, including:

Deploy the K8S cluster in the central server;

The application services of the CDN nodes are packaged into container images, including: central node images, regional node images and edge node images, and the container images are stored in storage;

Write the K8S deployment file according to the container image, including: the central deployment file, the regional deployment file and the edge deployment file corresponding to the central node image, the regional node image and the edge node image respectively, and store them in the memory;

Deploy the container image to the CDN node through the K8S cluster according to the deployment file, and at the same time back up the data in the storage to the preset CDN node, when the CDN node fails, through the K8S cluster according to The preset rule extracts the backup data from the preset CDN node to reset the faulty CDN node.

Optionally, when expanding a new CDN node, the K8S cluster calls the container image to deploy the new CDN node according to the type of the new CDN node; the category includes a central CDN node, a regional CDN node or an edge CDN nodes.

Optionally, when an error occurs in the CDN node, the K8S cluster invokes the container image to redeploy the CDN node according to the type of the CDN node; the category includes a central CDN node, a regional CDN node or an edge CDN node .

Optionally, the container image includes: a Docker image.

Optionally, the application service includes: a web application server.

The present application also provides an automatic arrangement device for CDN nodes, including:

Install modules for deploying K8S clusters in the central server;

The packaging module is used to package the application service of the CDN node into a container image, including: a central node image, an area node image and an edge node image, and store the container image in a memory;

Compose module, be used for writing K8S deployment file according to described container mirror image, comprise: the central deployment file corresponding to central node mirror image, area node mirror image and edge node mirror image respectively, regional deployment file and edge deployment file, and be stored in described memory middle;

A deployment module, configured to deploy the container image to a CDN node through the K8S cluster according to the deployment file, and at the same time back up the data in the storage to a preset CDN node, when the CDN node fails, through The K8S cluster extracts backup data from the preset CDN node according to preset rules to reset the faulty CDN node.

Optionally, the container image includes: a Docker image.

Optionally, the application service includes: a web application server.

Advantages of the present application relative to the prior art:

This application provides an automatic orchestration method for CDN nodes, including: deploying K8S clusters in the central server; packaging the application services of CDN nodes into container images, including: central node images, regional node images, and edge node images; Write the K8S deployment file according to the container image, including: the central deployment file, the regional deployment file and the edge deployment file corresponding to the central node image, the regional node image and the edge node image; deploy the K8S cluster according to the deployment file through the K8S cluster The above container image is uploaded to the CDN node. Through K8S unified management and deployment of CDN nodes, there is no need to manually install and deploy CDN nodes on the spot, saving time and labor costs, and making deployment easier.

Description of drawings

Fig. 1 is a flow chart of automatic arrangement of CDN nodes in this application.

Figure 2 is a schematic diagram of the K8S framework in this application.

FIG. 3 is a schematic diagram of an automatic orchestration device for CDN nodes in this application.

Detailed ways

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the application. However, the present application can be implemented in many other ways different from those described here, and those skilled in the art can make similar promotions without violating the connotation of the present application. Therefore, the present application is not limited by the specific implementation disclosed below.

Please refer to Figure 1, S101 deploys a K8S cluster in the central server.

In this application, the central server shown is a device that provides computing services, and the composition of the central server includes a processor, hard disk, memory, system bus, etc., and is similar to a general-purpose computer architecture. The central server shown in this application includes: file server, database server, application program server, WEB server and so on.

A K8S (kubernetes) cluster is deployed in the central server, and the K8S cluster is a portable container orchestration management tool for container services.

Figure 2 is a schematic diagram of the K8S framework in this application.

Referring to FIG. 2 , the K8S cluster includes: a user's command input terminal 201 , the command input terminal 201 is connected to a cluster control terminal 202 , and the cluster control terminal 202 is connected to a plurality of node terminals 203 .

Specifically, the cluster control terminal 202 load controls and manages the entire K8S cluster, including: fault detection, automatic expansion, rolling update, etc., and is the user's command execution terminal; the node terminal 203 is responsible for the creation, start and stop of the container, in The node end 203 described in this application is deployed in a CDN node.

Referring to FIG. 1, S102 packages the application services of the CDN nodes into container images, including: central node images, regional node images, and edge node images, and stores the container images in storage.

In this application, the CDN node has multiple types, including a central server, a first-level CDN node connected to the central server, and a second-level CDN node connected to the first-level CDN node, and the second-level CDN node That is, connect the client.

The central server is the main computing and storage device, which is connected to the client through the first-level CDN node and the second-level CDN node, and provides computing and storage services according to the client's request. In another implementation manner, the first-level CDN node and the second-level CDN node may also provide limited computing and storage services, which is beneficial to improve the timeliness of data acquisition by the client.

In this application, all or part of the application services in the CDN nodes are packaged into container images through the container configuration process provided by K8S. The container images are respectively center node images, regional node images, and edge node images according to different types of CDN nodes. . The central node image is deployed to the central server, and the regional node image and the edge node image are used to deploy to the first-level CDN node and the second-level CDN node respectively.

Specifically, the container image will be stored in an image storage, and the container image will be called from the image storage during deployment, and the container image will be stored in a backup storage at the same time.

Please refer to Fig. 1, S103 writes the K8S deployment file according to the container image, including: the central deployment file, the regional deployment file and the edge deployment file respectively corresponding to the central node image, the regional node image and the edge node image, and store them in in the backup memory.

After the container image is created, the K8S deployment file can be written. The deployment file mainly includes: 1) creating a user and importing the database; 2) deploying the container image on the node, including: copying the container image file to the CDN node, It is decoded and stored under the preset directory. In this application, the configuration parameters of the container image have been pre-configured.

After the deployment file is completed, the deployment file is stored in a backup memory.

Please refer to Figure 1, S104 deploys the container image to the CDN node through the K8S cluster according to the deployment file, and at the same time backs up the data in the backup storage to the preset CDN node. In case of a failure, the K8S cluster extracts backup data from the preset CDN node according to preset rules to reset the failed CDN node.

The deployment file described in this application also selects the corresponding central deployment file, regional deployment file and edge deployment file according to the type of each CDN node and deploys it to the central server, first-level CDN node server and second-level CDN node server.

After completing the deployment, each CDN node starts and runs the container image, and sends a result message to the central server according to the result of the operation. The result message includes whether the application service of the CDN node server is running, running speed, resource occupation ratio, etc.

The result message is displayed on the display interface of K8S. According to whether the application service is running, it can be judged whether the container image is installed successfully. According to the running speed, it can be judged whether the CDN node is old and needs maintenance. According to the occupancy of the resource, it can be judged whether the hardware device of the CDN node needs to be maintained.

In a preferred embodiment, the evaluation score of the CDN node can be calculated according to whether the CDN node is running, the running speed, and the weighted sum of resource occupation ratios, and the number of user connections that the CDN node can carry is determined according to the evaluation score. According to the number of user connections of multiple adjacent CDN nodes, the user connection allocation is re-allocated according to the preset ratio. The preset ratio is determined by a predetermined correspondence table between the evaluation score and the number of user connections.

Preferably, when expanding a new CDN node, the K8S cluster calls the container image to deploy the new CDN node according to the type of the new CDN node; the category includes a central CDN node, a regional CDN node or an edge CDN node.

Preferably, when an error occurs in the CDN node, the K8S cluster invokes the container image to redeploy the CDN node according to the type of the CDN node; the category includes a central CDN node, a regional CDN node or an edge CDN node.

During the process of deploying the container image, the data or files in the backup storage will be sent together to a preset CDN node for storage. A preferred implementation manner is that the preset CDN nodes are set according to the CDN node density and the location area of the CDN nodes. For example:

The first step is regional judgment, judging whether a preset CDN node needs to be set according to the regional location of the CDN node and the distance from the central server. Specifically, a preset distance length can be set in advance, and if an area is more than the preset distance length from the central server, the preset CDN node can be set.

The second step is to judge the density of CDN nodes, which is to calculate the number of CDN nodes in an area, and use the density centroid of the CDN nodes as the preset CDN nodes. The density centroid refers to the shortest sum of distances from the preset CDN node to all other CDN nodes in an area.

When the CDN node fails, the K8S cluster extracts backup data from the preset CDN node according to preset rules to reset the failed CDN node.

Corresponding to the above method, the present application also provides an automatic arrangement device for CDN nodes, including:

The installation module 301 is used to deploy the K8S cluster in the central server;

The packaging module 302 is used to package the application services of CDN nodes into container images, including: central node images, regional node images and edge node images;

The writing module 303 is used to write the K8S deployment file according to the container image, including: a central deployment file, a regional deployment file and an edge deployment file corresponding to the central node image, the regional node image and the edge node image;

A deployment module 304, configured to deploy the container image to a CDN node through the K8S cluster according to the deployment file.

Please refer to FIG. 3 , the installation module 301 is used to deploy the K8S cluster in the central server.

Please refer to FIG. 3 , the packaging module 302 is configured to package the application services of the CDN nodes into container images, including: central node images, regional node images and edge node images, and store the container images in memory.

Please refer to shown in Figure 3, write module 303, be used for writing K8S deployment file according to described container mirror image, include: center deployment file, regional deployment file and edge deployment file corresponding to central node image, regional node image and edge node image , and stored in the backup memory.

Please refer to FIG. 1 , the deployment module 304 is configured to deploy the container image to a CDN node through the K8S cluster according to the deployment file, and at the same time back up the data in the backup storage to a preset CDN node. When the CDN node fails, the K8S cluster extracts backup data from the preset CDN node according to preset rules to reset the failed CDN node.

The automatic orchestration device of the CDN node described in this application can also be executed. When expanding a new CDN node, the K8S cluster invokes the container image to deploy the new CDN node according to the type of the new CDN node; Categories include central CDN nodes, regional CDN nodes, or edge CDN nodes.

The automatic orchestration device of the CDN node described in this application can also be executed. When an error occurs in the CDN node, the K8S cluster calls the container image to redeploy the CDN node according to the type of the CDN node; the categories include Central CDN node, regional CDN node or edge CDN node.

Claims

A method for automatically orchestrating CDN nodes, comprising:

Deploy the K8S cluster in the central server;

Packaging the application service of the CDN node into a container image, including: a central node image, an area node image and an edge node image, and storing the container image in a backup storage;

Write the K8S deployment file according to the container image, including: the central deployment file, the regional deployment file and the edge deployment file corresponding to the central node image, the regional node image and the edge node image respectively, and store them in the backup memory;

Deploy the container image to the CDN node through the K8S cluster according to the deployment file, and at the same time back up the data in the backup storage to the preset CDN node, when the CDN node fails, through the K8S cluster The backup data is extracted from the preset CDN node according to preset rules to reset the faulty CDN node.
According to the automatic orchestration method of the CDN node described in claim 1, it is characterized in that, when expanding a new CDN node, the K8S cluster invokes the container image to deploy the new CDN node according to the type of the new CDN node; The categories include central CDN nodes, regional CDN nodes or edge CDN nodes.
According to the automatic orchestration method of the CDN node described in claim 1, it is characterized in that, when an error occurs in the CDN node, the K8S cluster invokes the container image to redeploy the CDN node according to the type of the CDN node; Categories include central CDN nodes, regional CDN nodes, or edge CDN nodes.
The method for automatically orchestrating CDN nodes according to claim 1, wherein the container image comprises: a Docker image.
The method for automatically orchestrating CDN nodes according to claim 1, wherein the application service comprises: a web application server.
An automatic orchestration device for a CDN node, characterized in that it includes:

Install modules for deploying K8S clusters in the central server;

The packaging module is used to package the application service of the CDN node into a container image, including: a central node image, a regional node image and an edge node image, and store the container image in a backup memory;

Compose module, be used for writing K8S deployment file according to described container mirror image, comprise: the central deployment file corresponding to center node mirror image, area node mirror image and edge node mirror image respectively, regional deployment file and edge deployment file, and store in described backup in memory;

A deployment module, configured to deploy the container image to a CDN node through the K8S cluster according to the deployment file, and at the same time back up the data in the backup storage to a preset CDN node, when the CDN node fails, The K8S cluster extracts the backup data from the preset CDN node according to preset rules to reset the faulty CDN node.
According to the automatic orchestration device of the CDN node described in claim 6, it is characterized in that, when expanding a new CDN node, the K8S cluster invokes the container image to deploy the new CDN node according to the type of the new CDN node; The categories include central CDN nodes, regional CDN nodes or edge CDN nodes.
According to the automatic orchestration device of the CDN node according to claim 6, it is characterized in that, when an error occurs in the CDN node, the K8S cluster invokes the container image to redeploy the CDN node according to the type of the CDN node; Categories include central CDN nodes, regional CDN nodes, or edge CDN nodes.
The device for automatically orchestrating CDN nodes according to claim 6, wherein the container image comprises: a Docker image.
The device for automatically orchestrating CDN nodes according to claim 6, wherein the application service comprises: a web application server.