CN114327507B - Automatic arranging method and device for CDN nodes - Google Patents
Automatic arranging method and device for CDN nodes Download PDFInfo
- Publication number
- CN114327507B CN114327507B CN202111564129.1A CN202111564129A CN114327507B CN 114327507 B CN114327507 B CN 114327507B CN 202111564129 A CN202111564129 A CN 202111564129A CN 114327507 B CN114327507 B CN 114327507B
- Authority
- CN
- China
- Prior art keywords
- node
- cdn
- mirror image
- cdn node
- container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000004806 packaging method and process Methods 0.000 claims abstract description 13
- 238000009434 installation Methods 0.000 claims abstract description 7
- 238000010586 diagram Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000011156 evaluation Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000005096 rolling process Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides an automatic arranging method of CDN nodes, which comprises the following steps: deploying a K8S cluster in a central server; packaging application services of CDN nodes into a container mirror image, comprising: a central node mirror image, a regional node mirror image and an edge node mirror image; writing a K8S deployment file according to the container image, including: the central deployment file, the area deployment file and the edge deployment file correspond to the central node mirror image, the area node mirror image and the edge node mirror image; deploying the container mirror image to a CDN node according to the deployment file through the K8S cluster. The CDN nodes are managed and deployed in a unified mode through the K8S, manual installation and deployment of the CDN nodes are not needed to be carried out on the spot, time and labor cost are saved, and deployment is easier. The application also provides an automatic arranging device of the CDN node.
Description
Technical Field
The present application relates to a CDN node deployment technology, and in particular, to an automatic arranging method for CDN nodes. The application also relates to an automatic arranging device of the CDN node.
Background
The basic idea of the CDN (content delivery network) is to avoid bottlenecks and links on the internet that may affect the data transmission speed and stability as much as possible, so that content transmission is faster and more stable.
The CDN is a one-layer intelligent virtual network based on the existing internet, which is formed by placing node servers at various places in the network, and the CDN system can redirect a user's request to a service node closest to the user in real time according to network traffic, connection of each node, load conditions, distance to the user, response time, and other comprehensive information. The method aims to enable the user to obtain the required content nearby, solve the problem of congestion of the Internet network and improve the response speed of the user in accessing the website. CDN nodes are distributed and deployed in various regions all over the country, and service association and communication are possible among the nodes.
In the prior art, for the deployment of the CDN nodes, manual work is required to be performed on site, the deployment difficulty is high, and the labor cost, the time cost and the capital cost are huge.
Disclosure of Invention
In order to solve the problem of difficulty in deploying CDN nodes, the application provides an automatic arranging method for CDN nodes. The application also relates to an automatic arranging device of the CDN node.
The application provides an automatic arranging method of CDN nodes, which comprises the following steps:
deploying a K8S cluster in a central server;
packaging application services of CDN nodes into a container mirror image, comprising: the method comprises the following steps of (1) carrying out central node mirroring, area node mirroring and edge node mirroring, and storing container mirroring in a memory;
writing a K8S deployment file according to the container image, including: the central deployment file, the area deployment file and the edge deployment file respectively correspond to the central node mirror image, the area node mirror image and the edge node mirror image and are stored in the memory;
deploying the container mirror image to a CDN node through the K8S cluster according to the deployment file, backing up data in the storage to a preset CDN node, and when the CDN node fails, extracting backup data from the preset CDN node through the K8S cluster according to a preset rule to reset the failed CDN node.
Optionally, when a new CDN node is expanded, the K8S cluster calls the container mirror 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.
Optionally, when an error occurs in the CDN node, the K8S cluster calls the container mirror image according to the type of the CDN node to redeploy the CDN node; the categories include central CDN nodes, regional CDN nodes, or edge CDN nodes.
Optionally, the container mirror image comprises: docker mirrors.
Optionally, the application service includes: a web application server.
The present application further provides an automatic arrangement device for CDN nodes, including:
the installation module is used for deploying the K8S cluster in the central server;
the packaging module is used for packaging the application service of the CDN node into a container mirror image, and comprises: the method comprises the following steps of (1) carrying out central node mirroring, area node mirroring and edge node mirroring, and storing container mirroring in a memory;
the compiling module is used for compiling the K8S deployment file according to the container mirror image, and comprises: the central deployment file, the area deployment file and the edge deployment file respectively correspond to the central node mirror image, the area node mirror image and the edge node mirror image and are stored in the memory;
and the deployment module is used for deploying the container mirror image to the CDN node through the K8S cluster according to the deployment file, backing up data in the storage to a preset CDN node, and when the CDN node fails, extracting backup data from the preset CDN node according to a preset rule through the K8S cluster to reset the failed CDN node.
Optionally, when a new CDN node is expanded, the K8S cluster calls the container mirror 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.
Optionally, when the CDN node has an error, the K8S cluster calls the container mirror image according to the type of the CDN node to redeploy the CDN node; the categories include central CDN nodes, regional CDN nodes, or edge CDN nodes.
Optionally, the container mirror image comprises: docker mirrors.
Optionally, the application service includes: a web application server.
The application has the advantages relative to the prior art:
the application provides an automatic arranging method for CDN nodes, which comprises the following steps: deploying a K8S cluster in a central server; packaging application services of CDN nodes into a container mirror image, comprising: a central node mirror image, a regional node mirror image and an edge node mirror image; writing a K8S deployment file according to the container image, including: the central deployment file, the area deployment file and the edge deployment file correspond to the central node mirror image, the area node mirror image and the edge node mirror image; and deploying the container mirror image to a CDN node according to the deployment file through the K8S cluster. The CDN nodes are managed and deployed in a unified mode through the K8S, manual installation and deployment of the CDN nodes are not needed to be carried out on the spot, time and labor cost are saved, and deployment is easier.
Drawings
Fig. 1 is a flow chart of automatic orchestration of CDN nodes in the present application.
Fig. 2 is a schematic diagram of the K8S framework in the present application.
Fig. 3 is a schematic diagram of an automatic scheduling device for CDN nodes in the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit and scope of this application, and thus this application is not limited to the specific implementations disclosed below.
The application provides an automatic arranging method for CDN nodes, which comprises the following steps: deploying a K8S cluster in a central server; packaging application services of CDN nodes into a container mirror image, comprising: a central node mirror image, a region node mirror image and an edge node mirror image; writing a K8S deployment file according to the container image, including: the central deployment file, the area deployment file and the edge deployment file correspond to the central node mirror image, the area node mirror image and the edge node mirror image; and deploying the container mirror image to a CDN node according to the deployment file through the K8S cluster. The CDN nodes are managed and deployed in a unified mode through the K8S, manual installation and deployment of the CDN nodes are not needed to be carried out on the spot, time and labor cost are saved, and deployment is easier.
Fig. 1 is a flow chart of automatic orchestration of CDN nodes in the present application.
Referring to fig. 1, S101 deploys a K8S cluster in a central server.
In the present application, the central server is a device for providing computing services, and the central server includes a processor, a hard disk, a memory, a system bus, and the like, and is similar to a general computer architecture. The central server shown in this application includes: file servers, database servers, application servers, WEB servers, and the like.
Deploying a K8S (kubernets) cluster in the central server, wherein the K8S cluster is an orchestration management tool of a portable container generated for container service.
Fig. 2 is a schematic diagram of the K8S framework in the present application.
Referring to fig. 2, the K8S cluster includes: a command input 201 of a user, the command input 201 being connected to a cluster control terminal 202, said cluster control terminal 202 being connected to a plurality of node terminals 203.
Specifically, the load control and management of the cluster control end 202 on the whole K8S cluster includes: fault detection, automatic expansion, rolling update and the like are command execution ends of users; the node 203 is responsible for creating a container and starting and stopping the container, and in the present application, the node 203 is deployed in a CDN node.
Referring to fig. 1, step S102 of packaging application services of CDN nodes into a container mirror includes: and the container mirror image is stored in a memory.
In the application, the CDN node has multiple types, and comprises a central server, a first-level CDN node connected with the central server, and a second-level CDN node connected with the first-level CDN node, wherein the second-level CDN node is connected with a client.
The central server is a main computing and storage device, is linked to the client through a primary CDN node and a secondary CDN node, and provides computing and storage services according to a client request. In another embodiment, the primary CDN node and the secondary CDN node may also provide limited computation and storage services, which is beneficial to improving timeliness of a client acquiring data.
In the application, all or part of application services in CDN nodes are packaged into container mirrors through a container configuration process provided by K8S, where the container mirrors are a center node mirror, a region node mirror, and an edge node mirror, respectively, according to different types of CDN nodes. The central node mirror image is deployed in a central server, and the area node mirror image and the edge node mirror image are respectively used for being deployed to a primary CDN node and a secondary CDN node.
Specifically, the container image is stored in an image memory, and the container image is called from the image memory in the deployment process, and is stored in a backup memory at the same time.
Referring to fig. 1, S103 writes a K8S deployment file according to the container image, including: and the central deployment file, the area deployment file and the edge deployment file respectively correspond to the central node mirror image, the area node mirror image and the edge node mirror image and are stored in the backup memory.
After the container mirror image is created, a deployment file of K8S may be written, where the deployment file mainly includes: 1) creating a user and importing a database; 2) deploying container images on nodes, comprising: the container mirror image file is copied to a CDN node, decoded and stored under a preset directory, and in the application, the configuration parameters of the container mirror image are configured in advance.
And after the deployment file is finished, storing the deployment file into a backup memory.
Referring to fig. 1, in S104, deploying the container mirror image to CDN nodes according to the deployment file through the K8S cluster, and backing up data in the backup storage to preset CDN nodes at the same time, and when a failure occurs in the CDN node, extracting backup data from the preset CDN nodes through the K8S cluster according to a preset rule to perform CDN node reset in which the failure occurs.
The deployment files in the application also select corresponding central deployment files, regional deployment files and edge deployment files according to the type of each CDN node to deploy the files to the central server, the primary CDN node server and the secondary CDN node server.
And after the deployment of each CDN node is finished, starting and operating the container mirror image, and sending a result message to a central server according to the operating result. The result message includes whether the application service of the CDN node server is running, a running speed, a resource occupation ratio, and the like.
The result message is displayed on a display interface of K8S, whether the container mirror image is installed successfully can be judged according to whether the application service runs, whether the CDN node is old and aged and whether maintenance is needed can be judged according to the running speed, and whether the CDN node hardware equipment needs to be maintained can be judged according to the resource occupation.
In a preferred embodiment, an evaluation score of the CDN node may be calculated by weighted summation of the CDN node operation, the operation speed, and the resource occupancy ratio, and the number of connections of users that the CDN node can carry is determined according to the evaluation score. And carrying out user connection distribution again according to a preset proportion by the number of user connections of a plurality of adjacent CDN nodes. The preset proportion is determined by a predetermined evaluation score and user connection number corresponding table.
Preferably, when a new CDN node is expanded, the K8S cluster calls the container mirror 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.
Preferably, when the CDN node has an error, the K8S cluster calls the container mirror image according to the type of the CDN node to redeploy the CDN node; the categories include central CDN nodes, regional CDN nodes, or edge CDN nodes.
And in the process of deploying the container mirror image, the data or files in the backup memory are sent to a preset CDN node together for storage. In a preferred embodiment, the preset CDN node is set according to a CDN node density and a location area of the CDN node. For example:
and step one, judging the region, namely judging whether a preset CDN node needs to be set or not according to the distance between the regional position of the CDN node and a central server. Specifically, a preset distance length can be preset, and if a distance between one region and the central server exceeds the preset distance length, setting of a preset CDN node can be performed.
And secondly, judging the density of the CDN nodes, namely calculating the quantity of the CDN nodes in an area, and taking the density centroid of the CDN nodes as the preset CDN nodes. The density centroid refers to the distance and the shortest distance from the preset CDN node to other CDN nodes in an area.
When the CDN node fails, extracting backup data from the preset CDN node through the K8S cluster according to a preset rule to reset the failed CDN node.
Corresponding to the above method, the present application further provides an automatic arrangement device for CDN nodes, including:
an installation module 301, configured to deploy a K8S cluster in a central server;
a packaging module 302, configured to package an application service of a CDN node into a container mirror, where the packaging module includes: a central node mirror image, a regional node mirror image and an edge node mirror image;
the authoring module 303 is configured to author a K8S deployment file according to the container image, and includes: the central deployment file, the area deployment file and the edge deployment file correspond to the central node mirror image, the area node mirror image and the edge node mirror image;
a deployment module 304, configured to deploy, by the K8S cluster, the container image to a CDN node according to the deployment file.
Fig. 3 is a schematic diagram of an automatic scheduling device for CDN nodes in the present application.
Referring to fig. 3, an installation module 301 is used for deploying a K8S cluster in a central server.
In the present application, the central server is a device for providing computing services, and the central server includes a processor, a hard disk, a memory, a system bus, and the like, and is similar to a general computer architecture. The central server shown in this application comprises: file servers, database servers, application servers, WEB servers, and the like.
Deploying a K8S (kubernets) cluster in the central server, wherein the K8S cluster is an orchestration management tool of a portable container generated for container service.
Referring to fig. 2, the K8S cluster includes: a command input 201 of a user, the command input 201 being connected to a cluster control terminal 202, said cluster control terminal 202 being connected to a plurality of node terminals 203.
Specifically, the load control and management of the whole K8S cluster by the cluster control end 202 includes: fault detection, automatic expansion, rolling update and the like are command execution ends of users; the node 203 is responsible for creating a container and starting and stopping the container, and in the present application, the node 203 is deployed in a CDN node.
Referring to fig. 3, a packaging module 302 is configured to package an application service of a CDN node into a container mirror, and includes: and the container mirror image is stored in a memory.
In the application, the CDN node has multiple types, and comprises a central server, a first-level CDN node connected with the central server, and a second-level CDN node connected with the first-level CDN node, wherein the second-level CDN node is connected with a client.
The central server is a main computing and storage device, is linked to the client through a primary CDN node and a secondary CDN node, and provides computing and storage services according to a client request. In another embodiment, the primary CDN node and the secondary CDN node may also provide limited computation and storage services, which is beneficial to improving timeliness of a client acquiring data.
In the present application, all or part of application services in CDN nodes are packaged into container mirrors through a container configuration process provided by K8S, where the container mirrors are a center node mirror, a region node mirror, and an edge node mirror, respectively, according to different CDN node types. The central node mirror image is deployed in a central server, and the area node mirror image and the edge node mirror image are respectively used for being deployed to a primary CDN node and a secondary CDN node.
Specifically, the container image is stored in an image memory, and the container image is called from the image memory in the deployment process, and is stored in a backup memory at the same time.
Referring to fig. 3, the writing module 303 is configured to write a K8S deployment file according to the container image, and includes: and the central deployment file, the area deployment file and the edge deployment file which correspond to the central node mirror image, the area node mirror image and the edge node mirror image are stored in the backup memory.
After the container mirror image is created, a deployment file of K8S may be written, where the deployment file mainly includes: 1) creating a user and importing a database; 2) deploying container images on nodes, comprising: the container mirror image file is copied to a CDN node, decoded and stored under a preset directory, and in the application, the configuration parameters of the container mirror image are configured in advance.
And after the deployment file is finished, storing the deployment file into a backup memory.
Referring to fig. 1, the deployment module 304 is configured to deploy, by the K8S cluster, the container mirror image to a CDN node according to the deployment file, and simultaneously backup data in the backup storage to a preset CDN node, and when the CDN node fails, extract backup data from the preset CDN node by the K8S cluster according to a preset rule to perform resetting of the failed CDN node.
The deployment file in the application also selects a corresponding central deployment file, a corresponding regional deployment file and a corresponding edge deployment file according to the type of each CDN node and deploys the files to the central server, the primary CDN node server and the secondary CDN node server.
The automatic arranging device of the CDN nodes can also execute the method, when a new CDN node is expanded, the K8S cluster calls the container mirror 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.
The automatic arranging device of the CDN nodes can also execute the method, when the CDN nodes have errors, the K8S cluster calls the container mirror images according to the types of the CDN nodes to relocate the CDN nodes; the categories include central CDN nodes, regional CDN nodes, or edge CDN nodes.
And in the process of deploying the container mirror image, the data or files in the backup memory are sent to a preset CDN node together for storage. In a preferred embodiment, the preset CDN node is set according to CDN node density and a location area of the CDN node. For example:
and step one, judging the region, namely judging whether a preset CDN node needs to be set or not according to the distance between the regional position of the CDN node and a central server. Specifically, a preset distance length can be preset, and if a distance between one region and the central server exceeds the preset distance length, setting of a preset CDN node can be performed.
And secondly, judging the density of the CDN nodes, namely calculating the quantity of the CDN nodes in an area, and taking the density centroid of the CDN nodes as the preset CDN nodes. The density centroid refers to the distance and the shortest distance from the preset CDN node to other CDN nodes in an area.
When the CDN node fails, extracting backup data from the preset CDN node through the K8S cluster according to a preset rule to reset the failed CDN node.
Claims (8)
1. An automatic arranging method for CDN nodes is characterized by comprising the following steps:
deploying a K8S cluster in a central server, wherein the cluster is used for unified management and deployment of CDN nodes;
packaging application services of CDN nodes into a container mirror image, comprising: the method comprises the steps that a central node mirror image, an area node mirror image and an edge node mirror image are obtained, and the container mirror image is stored in a backup memory;
writing a K8S deployment file according to the container image, including: the central deployment file, the area deployment file and the edge deployment file respectively correspond to the central node mirror image, the area node mirror image and the edge node mirror image and are stored in the backup memory;
deploying the container mirror image to a CDN node through the K8S cluster according to the deployment file, backing up data in the backup storage to a preset CDN node, extracting backup data from the preset CDN node through the K8S cluster according to a preset rule to reset the failed CDN node when the CDN node fails, setting the preset CDN node according to CDN node density and the regional position of the CDN node, and judging whether the preset CDN node needs to be set according to the distance between the regional position of the CDN node and a central server; after deployment of each CDN node is completed, starting and operating the container mirror image, and sending a result message to a central server according to an operation result;
when a new CDN node is expanded, the K8S cluster calls the container mirror image to deploy the new CDN node according to the type of the new CDN node; the types include central CDN nodes, regional CDN nodes, and edge CDN nodes.
2. The method of claim 1, wherein when an error occurs in the CDN node, the K8S cluster invokes the container mirror to redeploy the CDN node according to the type of the CDN node.
3. The method of automated orchestration of CDN nodes according to claim 1, wherein the container mirroring comprises: docker mirrors.
4. The method of claim 1, wherein the application services comprise: a web application server.
5. An automatic arranging device for CDN nodes is characterized by comprising:
the installation module is used for deploying a K8S cluster in the central server and uniformly managing and deploying CDN nodes;
the packaging module is used for packaging the application service of the CDN node into a container mirror image, and comprises: the method comprises the following steps of carrying out central node mirroring, area node mirroring and edge node mirroring, and storing container mirroring into a backup memory;
the compiling module is used for compiling the K8S deployment file according to the container mirror image, and comprises the following steps: the central deployment file, the area deployment file and the edge deployment file respectively correspond to the central node mirror image, the area node mirror image and the edge node mirror image and are stored in the backup memory;
the deployment module is used for deploying the container mirror image to a CDN node through the K8S cluster according to the deployment file, backing up data in the backup storage to a preset CDN node, extracting backup data from the preset CDN node through the K8S cluster according to a preset rule to reset the failed CDN node when the CDN node fails, setting the preset CDN node according to CDN node density and regional positions of the CDN node, and judging whether the preset CDN node needs to be set according to the distance between the regional position of the CDN node and a central server; after deployment of each CDN node is completed, starting and operating the container mirror image, and sending a result message to a central server according to an operating result;
when a new CDN node is expanded, the K8S cluster calls the container mirror image to deploy the new CDN node according to the type of the new CDN node; the types include a central CDN node, a regional CDN node, and an edge CDN node.
6. The automatic programming device for CDN nodes of claim 5, wherein when an error occurs in the CDN node, the K8S cluster invokes the container mirror to redeploy the CDN node according to a type of the CDN node.
7. The automated orchestration mechanism of CDN nodes of claim 5, wherein the container mirroring comprises: docker mirrors.
8. The automatic orchestration device according to claim 5, wherein the application services comprise: a web application server.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111564129.1A CN114327507B (en) | 2021-12-20 | 2021-12-20 | Automatic arranging method and device for CDN nodes |
| PCT/CN2021/141410 WO2023115591A1 (en) | 2021-12-20 | 2021-12-25 | Automatic arrangement method and apparatus for cdn nodes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111564129.1A CN114327507B (en) | 2021-12-20 | 2021-12-20 | Automatic arranging method and device for CDN nodes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114327507A CN114327507A (en) | 2022-04-12 |
| CN114327507B true CN114327507B (en) | 2022-07-15 |
Family
ID=81052616
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111564129.1A Active CN114327507B (en) | 2021-12-20 | 2021-12-20 | Automatic arranging method and device for CDN nodes |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114327507B (en) |
| WO (1) | WO2023115591A1 (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017039579A1 (en) * | 2015-08-28 | 2017-03-09 | Hewlett Packard Enterprise Development Lp | Recovering from an origination node failure during an asynchronous replication |
| CN109067890A (en) * | 2018-08-20 | 2018-12-21 | 广东电网有限责任公司 | A kind of CDN node edge calculations system based on docker container |
| CN109246224A (en) * | 2018-09-25 | 2019-01-18 | 麒麟合盛网络技术股份有限公司 | The containerization dispositions method and device of CDN system |
| CN110460628A (en) * | 2019-06-11 | 2019-11-15 | 国网浙江省电力有限公司宁波供电公司 | Distributed mist calculates mirror image processing storage method |
| CN111682973A (en) * | 2020-08-17 | 2020-09-18 | 烽火通信科技股份有限公司 | Method and system for arranging edge cloud |
| CN111984366A (en) * | 2020-07-24 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method and system for deploying disaster recovery mechanism in containerization manner |
| CN112994937A (en) * | 2021-02-10 | 2021-06-18 | 北京交通大学 | Deployment and migration system of virtual CDN in intelligent fusion identification network |
| CN113259447A (en) * | 2021-05-26 | 2021-08-13 | 中国电子信息产业集团有限公司第六研究所 | Cloud platform deployment method and device, electronic equipment and storage medium |
| CN113296882A (en) * | 2021-02-10 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Container arranging method, device, system and storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104023375B (en) * | 2013-02-28 | 2017-06-23 | 株式会社理光 | Network node finds method and apparatus |
| CN109800055A (en) * | 2018-12-27 | 2019-05-24 | 北京航天智造科技发展有限公司 | Container dispatches method of combination and system |
| CN112087312B (en) * | 2019-06-15 | 2023-02-03 | 华为云计算技术有限公司 | Method, device and equipment for providing edge service |
| US20210014113A1 (en) * | 2020-09-25 | 2021-01-14 | Intel Corporation | Orchestration of meshes |
| CN112698992B (en) * | 2021-03-23 | 2021-06-25 | 腾讯科技（深圳）有限公司 | Disaster recovery management method and related device for cloud cluster |
| CN113377519B (en) * | 2021-07-07 | 2022-03-22 | 江苏云工场信息技术有限公司 | CDN-based content scheduling method |
-
2021
- 2021-12-20 CN CN202111564129.1A patent/CN114327507B/en active Active
- 2021-12-25 WO PCT/CN2021/141410 patent/WO2023115591A1/en unknown
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017039579A1 (en) * | 2015-08-28 | 2017-03-09 | Hewlett Packard Enterprise Development Lp | Recovering from an origination node failure during an asynchronous replication |
| CN109067890A (en) * | 2018-08-20 | 2018-12-21 | 广东电网有限责任公司 | A kind of CDN node edge calculations system based on docker container |
| CN109246224A (en) * | 2018-09-25 | 2019-01-18 | 麒麟合盛网络技术股份有限公司 | The containerization dispositions method and device of CDN system |
| CN110460628A (en) * | 2019-06-11 | 2019-11-15 | 国网浙江省电力有限公司宁波供电公司 | Distributed mist calculates mirror image processing storage method |
| CN111984366A (en) * | 2020-07-24 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method and system for deploying disaster recovery mechanism in containerization manner |
| CN111682973A (en) * | 2020-08-17 | 2020-09-18 | 烽火通信科技股份有限公司 | Method and system for arranging edge cloud |
| CN112994937A (en) * | 2021-02-10 | 2021-06-18 | 北京交通大学 | Deployment and migration system of virtual CDN in intelligent fusion identification network |
| CN113296882A (en) * | 2021-02-10 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Container arranging method, device, system and storage medium |
| CN113259447A (en) * | 2021-05-26 | 2021-08-13 | 中国电子信息产业集团有限公司第六研究所 | Cloud platform deployment method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023115591A1 (en) | 2023-06-29 |
| CN114327507A (en) | 2022-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101916847B1 (en) | Cross-cloud management and troubleshooting | |
| US7000141B1 (en) | Data placement for fault tolerance | |
| CN110209492B (en) | Data processing method and device | |
| CN109582335B (en) | Method, device and equipment for on-line upgrading of non-interrupt storage cluster nodes | |
| US7519785B1 (en) | Storage layout and data replication | |
| CN109769040A (en) | Content delivery network service switching method, device, equipment and storage medium | |
| KR20010072379A (en) | Fault tolerant computer system | |
| JP7122332B2 (en) | Information processing system and method | |
| AU2012259086A1 (en) | Cross-cloud management and troubleshooting | |
| EP1654664A1 (en) | A contents synchronization system in network environment and a method therefor | |
| CN111736872A (en) | Gray scale release upgrading method and device, computer system and readable storage medium | |
| CN104378423A (en) | Metadata cluster distribution storage system and storage data reading and writing method | |
| CN110149366B (en) | Method and device for improving availability of cluster system and computer equipment | |
| CN106452836B (en) | main node setting method and device | |
| CN115698954A (en) | Managing failover area availability to implement failover services | |
| CN113315754A (en) | Intelligent linkage method, device, equipment and medium for firewall of container visit | |
| CN114327507B (en) | Automatic arranging method and device for CDN nodes | |
| CN113596087A (en) | Application upgrading method and device and computer readable storage medium | |
| US6675259B2 (en) | Method and apparatus for validating and ranking disk units for switching | |
| JP4571090B2 (en) | Scheduler program, server system, scheduler device | |
| CN115550164A (en) | Method and system for one-key installation and management of single-node big data assembly | |
| CN114385498A (en) | Performance test method, system, computer equipment and readable storage medium | |
| JP5464675B2 (en) | Mirroring system, node, mirroring method, and program | |
| CN103384258B (en) | Generate the method and system of new host | |
| CN115858246B (en) | Disaster recovery exercise method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: An Automatic Arrangement Method and Device of CDN Nodes Effective date of registration: 20220929 Granted publication date: 20220715 Pledgee: WUXI BRANCH, INDUSTRIAL BANK CO.,LTD. Pledgor: JIANGSU YUNGONGCHANG INFORMATION TECHNOLOGY CO.,LTD. Registration number: Y2022320010559 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right | ||
| PC01 | Cancellation of the registration of the contract for pledge of patent right |
Date of cancellation: 20230922 Granted publication date: 20220715 Pledgee: WUXI BRANCH, INDUSTRIAL BANK CO.,LTD. Pledgor: JIANGSU YUNGONGCHANG INFORMATION TECHNOLOGY CO.,LTD. Registration number: Y2022320010559 |
|
| PC01 | Cancellation of the registration of the contract for pledge of patent right | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: An automatic arrangement method and device for CDN nodes Effective date of registration: 20231215 Granted publication date: 20220715 Pledgee: WUXI BRANCH, INDUSTRIAL BANK CO.,LTD. Pledgor: JIANGSU YUNGONGCHANG INFORMATION TECHNOLOGY CO.,LTD. Registration number: Y2023980071397 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |