Construction method and device of container cluster crossing multiple cloud platforms and storage medium

By building a container cluster on the initial cloud platform and creating interoperable virtual machines on the target cloud platform, the problem that the container cluster cannot span multiple cloud platforms is solved, and the low cost, rapid migration and reduction of the Internet of Vehicles SaaS platform is achieved. machine risk.

CN119045942APending Publication Date: 2024-11-29PATEO CONNECT (WUHAN) CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202310618376.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-29
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

The container cluster cannot span multiple cloud platforms, resulting in the Internet of Vehicles SaaS platform that requires a lot of labor costs when migrating cloud platforms and poses a risk of downtime.

Method used

Build a container cluster on the initial cloud platform, and create a virtual machine on the target cloud platform through the infrastructure resource configuration library to communicate with the virtual machine intranet of the initial cloud platform, and then register the target virtual machine to the management cluster to realize the container Clusters span multiple cloud platforms.

Benefits of technology

It realizes the rapid migration of container clusters and Internet of Vehicles SaaS platforms between different cloud platforms, reducing costs and downtime risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119045942A_ABST
    Figure CN119045942A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a construction method and device of a container cluster crossing multiple cloud platforms and a storage medium. The construction method of the container cluster crossing the multiple cloud platforms can comprise the steps that the container cluster is constructed based on an initial cloud platform, the initial cloud platform comprises multiple initial virtual machines in a cloud network, the container cluster comprises a management cluster and a load cluster, and the load cluster comprises load nodes corresponding to the initial virtual machines; creating a predetermined number of target virtual machines on the at least one target cloud platform according to the infrastructure resource configuration library, and enabling the target virtual machines of the at least one target cloud platform to be in intranet intercommunication with the initial virtual machines of the initial cloud platform; and deploying an accessory component of the load node for each target virtual machine, and enabling each target virtual machine to be registered to the management cluster.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field related to cloud computing, and specifically to a method, device and storage medium for constructing a container cluster across multiple cloud platforms. Background Art

[0002] The container cluster is the basic platform for the operation of the Internet of Vehicles Software as a Service (SaaS) platform business. After the cloud computing service provider is determined, it can only be built on the cloud platform corresponding to the cloud computing service provider.

[0003] Since cloud servers on different cloud platforms have different discount prices at different stages, in order to reduce the infrastructure cost of the Internet of Vehicles SaaS platform, the Internet of Vehicles SaaS platform needs to migrate from high-priced cloud platforms to low-priced cloud platforms. However, container clusters are often built on a single cloud platform and cannot span multiple cloud platforms, which will result in a large amount of manpower costs when migrating the Internet of Vehicles SaaS platform between different cloud platforms, and there is a risk of downtime. Summary of the invention

[0004] The embodiments of the present application provide a method, device, and storage medium for constructing a container cluster across multiple cloud platforms, which can at least partially solve at least one of the above-mentioned shortcomings or other shortcomings in the prior art.

[0005] The first aspect of the present application provides a method for constructing a container cluster across multiple cloud platforms, which includes: building a container cluster based on an initial cloud platform, the initial cloud platform includes multiple initial virtual machines in a cloud network, the container cluster includes a management cluster and a load cluster, and the load cluster includes load nodes corresponding to each initial virtual machine; creating a predetermined number of target virtual machines in at least one target cloud platform according to an infrastructure resource configuration library, and making the target virtual machines of at least one target cloud platform interconnected with the initial virtual machines of the initial cloud platform through an intranet; and deploying ancillary components of the load node for each target virtual machine, and making each target virtual machine registered with the management cluster.

[0006] The second aspect of the present application provides an electronic device, which includes at least one processor and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method for building a container cluster across multiple cloud platforms of the first aspect of the present application.

[0007] The third aspect of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method for constructing a container cluster across multiple cloud platforms of the first aspect of the present application is implemented.

[0008] According to some implementation methods of the present application, a container cluster is first built on the initial cloud platform, and then a target virtual machine is created on the target cloud platform according to the infrastructure resource configuration library, and the target virtual machine is made to communicate with the initial virtual machine of the initial cloud platform through the intranet. Finally, the target virtual machines are registered one by one to the management cluster of the container cluster. This allows the container cluster to span multiple cloud platforms, making it easy to quickly migrate the container cluster and the Internet of Vehicles SaaS platform based on the container cluster between different cloud platforms, thereby reducing costs and downtime risks.

[0009] It should be understood that the content described in this section is not intended to identify the key features or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Other features, purposes and advantages of the embodiments of the present application will become more apparent by reading the detailed description of the non-limiting embodiments made with reference to the following drawings. In the drawings:

[0011] Figure 1 A schematic system architecture of a container cluster in the prior art is provided;

[0012] Figure 2 A schematic diagram of a process for constructing a container cluster across multiple cloud platforms according to an exemplary embodiment of the present application;

[0013] Figure 3 A schematic diagram of a process for constructing a container cluster across multiple cloud platforms according to an exemplary embodiment of the present application;

[0014] Figure 4 is a schematic system architecture of a container cluster according to an exemplary embodiment of the present application;

[0015] Figure 5 A schematic system architecture of a container cluster according to an exemplary embodiment of the present application; and

[0016] Figure 6 It is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to better understand the present application, a more detailed description will be made of various aspects of the present application with reference to the accompanying drawings. It should be understood that these detailed descriptions are only descriptions of exemplary embodiments of the present application, and are not intended to limit the scope of the present application in any way. Throughout the specification, the same reference numerals refer to the same elements. The expression "and / or" includes any and all combinations of one or more of the associated listed items.

[0018] Unless otherwise defined, all terms (including technical terms and scientific terms) used in this application have the same meaning as commonly understood by ordinary technicians in the field to which this application belongs. It should also be understood that terms (such as those defined in commonly used dictionaries) should be understood to have the same meaning as their meaning in the context of the relevant technology, and should not be interpreted in an idealized or overly formal sense, unless explicitly defined in this application.

[0019] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. In addition, unless explicitly limited or contradictory to the context, the specific steps included in the method described in this application are not necessarily limited to the order described, but can be performed in any order or in parallel. The application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0020] The container cluster is the basic platform for the operation of the Internet of Vehicles Software as a Service (SaaS) platform. It can only be built on one cloud platform and cannot span multiple cloud platforms ( Figure 1 ). This kind of container cluster built on a single cloud platform often has many problems. For example, cloud servers on different cloud platforms have different discount prices at different stages. In order to reduce the infrastructure cost of the Internet of Vehicles SaaS platform, the Internet of Vehicles SaaS platform needs to be migrated from a high-priced cloud platform to a low-priced cloud platform. However, this migration process requires a lot of manpower costs and there is a risk of downtime.

[0021] In order to at least partially solve one or more of the above-mentioned problems and other potential problems, the present application proposes a method for building a container cluster across multiple cloud platforms, so as to facilitate the rapid migration of container clusters and the Internet of Vehicles SaaS platform based on the container cluster between different cloud platforms, thereby reducing costs and downtime risks.

[0022] Figure 2 and Figure 3 Schematic diagrams of the processes of a method 1000 for constructing a container cluster across multiple cloud platforms according to an exemplary embodiment of the present application are respectively shown. Figure 4 The schematic system architecture of the container cluster formed according to the above-mentioned construction method 1000 is shown. It should be understood that the construction method 1000 of the container cluster across multiple cloud platforms may also include additional steps not shown and / or may omit the steps shown, and the scope of the present application is not limited in this respect. The construction method 1000 of the container cluster across multiple cloud platforms can be applied to the Internet of Vehicles SaaS platform. It should be understood that the construction method 1000 of the container cluster across multiple cloud platforms can also be applied to other platforms of the Internet of Things or the Internet, and the present application does not limit this.

[0023] like Figure 2 As shown, the method 1000 for constructing a container cluster across multiple cloud platforms may include:

[0024] S100. Building a container cluster based on an initial cloud platform, where the initial cloud platform includes multiple initial virtual machines in a cloud network, the container cluster includes a management cluster and a load cluster, and the load cluster includes load nodes corresponding to each initial virtual machine.

[0025] S200. Create a predetermined number of target virtual machines in at least one target cloud platform according to the infrastructure resource configuration library, and enable the target virtual machines of at least one target cloud platform to communicate with the initial virtual machines of the initial cloud platform through an intranet.

[0026] S300: Deploy the auxiliary components of the load node for each target virtual machine, and register each target virtual machine with the management cluster.

[0027] According to some implementation methods of the present application, a container cluster is first built on the initial cloud platform, and then a target virtual machine is created on the target cloud platform according to the infrastructure resource configuration library, and the target virtual machine is made to communicate with the initial virtual machine of the initial cloud platform through the intranet. Finally, the target virtual machines are registered one by one to the management cluster of the container cluster. This allows the container cluster to span multiple cloud platforms, making it easy to quickly migrate the container cluster and the Internet of Vehicles SaaS platform based on the container cluster between different cloud platforms, thereby reducing costs and downtime risks.

[0028] The following is an exemplary description of steps S100 to S300 of an exemplary embodiment of the present application.

[0029] S100, build a container cluster based on the initial cloud platform, the initial cloud platform includes multiple Initial virtual machine, container cluster includes management cluster and load cluster, and load cluster includes each initial virtual machine The corresponding load node .

[0030] The initial cloud platform may include one of the cloud computing service platforms such as Huawei Cloud Platform, Alibaba Cloud Platform, Baidu Cloud Platform, Tencent Cloud Platform, Google Cloud Platform, Microsoft Cloud Platform, Amazon Cloud Platform, etc., which has multiple initial virtual machines, and all initial virtual machines in the initial cloud platform are in the initial cloud network. Use the kubernetes container orchestration tool to build a container cluster on the initial cloud platform. The container cluster may include a management cluster and a load cluster, wherein the management cluster creates a load cluster in a declarative manner and manages the load cluster; the load cluster includes load nodes corresponding to each initial virtual machine, each initial virtual machine corresponds to a load node, and each load node is used to run the Internet of Vehicles business microservices.

[0031] The auxiliary components of the load node may include at least one of the kube-proxy component and the kubelet component. The kube-proxy component may serve as a network proxy component of the load node, which is used to maintain the network rules of the load node and load balance the traffic sent to the application interface service to the correct backend pod. In other words, the kube-proxy component monitors the changes of resource objects in the application interface service and configures load balancing for the application interface service by operating the proxy backend pod based on the monitored resource changes. The kubelet component may serve as a proxy component of the load node, which receives new or modified backend pod specifications from the application interface service and ensures that the pod and its containers run under the expected specifications. At the same time, the kubelet component may also serve as a monitoring component of the load node to report the operating status of the virtual machine to the application interface service.

[0032] S200: Create a predetermined number of target virtual machines on at least one target cloud platform according to the infrastructure resource configuration library. and enables at least one target virtual machine of the target cloud platform to communicate with the initial virtual machine of the initial cloud platform through the intranet.

[0033] The infrastructure resource configuration library is configured with definition resources of various cloud computing service platforms, and the definition resources of different cloud computing service platforms are different. When the infrastructure resource configuration library monitors a certain definition resource, the infrastructure resource configuration library will call the application program interface of the cloud computing service platform corresponding to the definition resource in a declarative manner and create a virtual machine on the cloud computing service platform corresponding to the definition resource.

[0034] First, the user initiates a first instruction to create a target virtual machine in at least one target cloud platform to the infrastructure resource configuration library based on the client, wherein the first instruction carries information that the number of target virtual machines is a predetermined number. The type of the target cloud platform is different from the type of the initial cloud platform, and the target cloud platform may include one or more cloud computing service platforms such as Huawei Cloud Platform, Alibaba Cloud Platform, Baidu Cloud Platform, Tencent Cloud Platform, Google Cloud Platform, Microsoft Cloud Platform, and Amazon Cloud Platform.

[0035] After receiving the first instruction, the infrastructure resource configuration library monitors the definition resources and, when monitoring the definition resources of at least one target cloud platform for the first time, calls the application program interface corresponding to the target cloud platform and initiates a request to create a predetermined number of target virtual machines to the target cloud platform. In response to receiving the above request, a predetermined number of target virtual machines are created on the target cloud platform. It should be noted that the number of target cloud platforms can be one or more, and this application does not impose specific restrictions on this.

[0036] Then, the target virtual machine of at least one target cloud platform is interconnected with the initial virtual machine of the initial cloud platform through the intranet of the communication tunnel. The communication tunnel may be, for example, a Generic Routing Encapsulation (GRE) tunnel. GRE tunnel technology is to encapsulate certain network layer protocol data packets, and enable these encapsulated data packets to be transmitted in another network layer protocol, thereby realizing point-to-point connection on the network. All target virtual machines of the same target cloud platform are in the same target cloud network. The data packets of the target cloud network layer protocol can be encapsulated through the GRE tunnel technology, and these encapsulated packets can be transmitted in the initial cloud network layer protocol to realize the point-to-point connection between the target cloud network and the initial cloud network, thereby realizing the intranet interconnection between the target virtual machine of the target cloud platform and the initial virtual machine of the initial cloud platform.

[0037] S300, deploy the auxiliary components of the load node for each target virtual machine, and make each target virtual machine register to the management cluster.

[0038] After the target virtual machine and the initial virtual machine are interconnected in the intranet, the auxiliary components of the load node are deployed for each target virtual machine, and the load nodes corresponding to each target virtual machine can be formed. Accordingly, the entire load cluster can cover the load nodes corresponding to each initial virtual machine and the target virtual machine. The auxiliary components of the load node of the target virtual machine are the same as the auxiliary components of the load node of the initial virtual machine, that is, the auxiliary components of the load node of the target virtual machine may include at least one of the kube-proxy component and the kubelet component.

[0039] After forming the load nodes corresponding to each target virtual machine, each target virtual machine is registered to the management cluster, so that the management cluster can manage each initial virtual machine and each target virtual machine, thereby forming a container cluster spanning the initial cloud platform and at least one target cloud platform ( Figure 4 ). The kubernetes container orchestration tool can deploy the Internet of Vehicles business microservices to the load nodes corresponding to each target virtual machine.

[0040] like Figure 3 As shown, after each target virtual machine is registered with the management cluster, the method 1000 for constructing a container cluster across multiple cloud platforms may further include:

[0041] S400: In response to each target virtual machine being registered with the management cluster, dynamically adjust the number of initial virtual machines of the initial cloud platform and / or target virtual machines of at least one target cloud platform according to configuration rules of the infrastructure resource configuration library.

[0042] The user initiates a second instruction to the infrastructure resource configuration library based on the client, wherein the second instruction carries the preset configuration rules of the infrastructure resource configuration library. After receiving the second instruction, the infrastructure resource configuration library determines whether the preset configuration rules carried by the second instruction are the same as the original configuration rules of the infrastructure resource configuration library. If the preset configuration rules are the same as the original configuration rules, it means that the configuration rules of the infrastructure resource configuration library have not changed. If the preset configuration rules are different from the original configuration rules, it means that the configuration rules of the infrastructure resource configuration library have changed. In response to the change in the configuration rules of the infrastructure resource configuration library, the number of initial virtual machines of the initial cloud platform and / or target virtual machines of at least one target cloud platform is dynamically adjusted according to the preset configuration rules carried by the second instruction.

[0043] As an example, the preset configuration rules carried by the second instruction depend on the current prices of the initial virtual machine and the target virtual machine. When the current price of a virtual machine increases compared to the previous price, the number of the virtual machines in the preset configuration rules decreases. Conversely, the number of the virtual machines in the preset configuration rules increases.

[0044] As an example, in response to a change in the configuration rules of the infrastructure resource configuration library, the infrastructure resource configuration library declaratively calls the application program interface of the initial cloud platform and / or at least one target cloud platform, and adjusts the number of initial virtual machines of the initial cloud platform and / or target virtual machines of at least one target cloud platform according to the preset configuration rules carried by the second instruction.

[0045] As an example, in response to a change in the configuration rules of the infrastructure resource configuration library, the infrastructure resource configuration library calls the application program interfaces of the initial cloud platform and at least one target cloud platform in a declarative manner to reduce the number of initial virtual machines of the initial cloud platform and increase the number of target virtual machines of at least one target cloud platform; or, increase the number of initial virtual machines of the initial cloud platform and reduce the number of target virtual machines of at least one target cloud platform. It should be noted that when there are multiple target cloud platforms, the number of target virtual machines of some target cloud platforms can be increased or decreased at the same time, and the number of target virtual machines of all target cloud platforms can also be increased or decreased at the same time.

[0046] As an example, in response to a change in the configuration rules of the infrastructure resource configuration library, the infrastructure resource configuration library calls the application program interface of the initial cloud platform in a declarative manner and deletes a preset number of initial virtual machines, calls the application program interface of at least one target cloud platform and copies a preset number of target virtual machines; or, the infrastructure resource configuration library calls the application program interface of the initial cloud platform in a declarative manner and copies a preset number of initial virtual machines, calls the application program interface of at least one target cloud platform and deletes a preset number of target virtual machines. It should be noted that when there are multiple target cloud platforms, a preset number of target virtual machines of some target cloud platforms can be copied or deleted at the same time, or a preset number of target virtual machines of all target cloud platforms can be copied or deleted at the same time.

[0047] As an example, at least one created target virtual machine is used as a template and a preset number of target virtual machines are copied. The copied target virtual machines automatically install the attached components of the load node, that is, form load nodes corresponding to each copied target virtual machine; after forming the load nodes corresponding to each copied target virtual machine, each copied target virtual machine can be automatically registered to the management cluster. The kubernetes container orchestration tool deploys the Internet of Vehicles business microservices to the load nodes corresponding to each copied target virtual machine.

[0048] As an example, an initial virtual machine is used as a template and a preset number of initial virtual machines are copied. The copied initial virtual machines automatically install and deploy the auxiliary components of the load nodes, that is, form load nodes corresponding to each copied initial virtual machine; after forming the load nodes corresponding to each copied initial virtual machine, each copied initial virtual machine can be automatically registered to the management cluster. The kubernetes container orchestration tool deploys the Internet of Vehicles business microservices to the load nodes corresponding to each copied initial virtual machine.

[0049] Figure 5 A schematic system architecture of a container cluster spanning cloud platform A, cloud platform C, and cloud platform C is shown. The following takes the initial cloud platform as cloud platform A and the target cloud platform as cloud platform B and cloud platform C as an example to illustrate the construction method 1000 of a container cluster spanning multiple cloud platforms.

[0050] Use the kubernetes container orchestration tool to build a container cluster on cloud platform A. Cloud platform A includes 100 cloud servers A, and these 100 cloud servers A are all in the first cloud network. The container cluster may include a management cluster and a load cluster, wherein the management cluster creates the load cluster in a declarative manner and manages the load cluster; the load cluster includes 100 load nodes, and the load nodes correspond to cloud servers A one-to-one, and each load node is used to run the Internet of Vehicles business microservice. The attached components of the load node may include at least one of the kube-proxy component and the kubelet component.

[0051] The user initiates a first instruction to the infrastructure resource configuration library based on the client to create cloud server B on cloud platform B and cloud server C on cloud platform C, wherein the first instruction carries information that the number of cloud servers B and cloud servers C is 20. After receiving the first instruction, the infrastructure resource configuration library monitors the definition resources and, when monitoring the definition resources of cloud platform B and cloud server C for the first time, calls the application program interfaces of cloud platform B and cloud platform C respectively, and initiates a request to create 20 cloud servers B to cloud platform B and 20 cloud servers C to cloud platform C. In response to receiving the above request, 20 cloud servers B are created on cloud platform B and 20 cloud servers C are created on cloud platform C.

[0052] The communication tunnel is used to enable the cloud server B of cloud platform B, the cloud server C of cloud platform C and the cloud server A of cloud platform A to communicate with each other in the intranet, and the communication tunnel may be, for example, a GRE tunnel. The communication tunnel may include a first GRE tunnel and a second GRE tunnel, wherein the first GRE tunnel is used to achieve the intranet communication between the cloud server B of cloud platform B and the cloud server A of cloud platform A, and the second GRE tunnel is used to achieve the intranet communication between the cloud server C of cloud platform C and the cloud server B of cloud platform B, or the second GRE tunnel is used to achieve the intranet communication between the cloud server C of cloud platform C and the cloud server A of cloud platform A.

[0053] After cloud servers B, C and A are interconnected in the intranet, the auxiliary components of the load nodes are deployed for each cloud server B and each cloud server C, so that load nodes corresponding to each cloud server B and each cloud server C can be formed. Accordingly, the entire load cluster can cover the load nodes corresponding to each cloud server A, cloud server B and cloud server C. The auxiliary components of the load nodes of cloud servers B and C are the same as those of the load nodes of cloud server A, and are at least one of the kube-proxy components and the kubelet components.

[0054] After forming the load nodes corresponding to each cloud server B and cloud server C, each cloud server B and cloud server C are registered to the management cluster, so that the management cluster can manage each cloud server A, cloud server B and cloud server C, thereby forming a container cluster across cloud platforms A, cloud platform B and cloud platform C ( Figure 5 ). The kubernetes container orchestration tool deploys the Internet of Vehicles business microservices to the load nodes corresponding to each cloud server B and cloud server C.

[0055] After the above container cluster is formed, the number of cloud servers A, cloud servers B and cloud servers C can be dynamically adjusted according to the configuration rules of the infrastructure resource configuration library.

[0056] For example, a user initiates a second instruction to the infrastructure resource configuration library based on the client, wherein the second instruction carries the preset configuration rules of the infrastructure resource configuration library. After receiving the second instruction, the infrastructure resource configuration library determines that the preset configuration rules carried by the second instruction are different from the original configuration rules of the infrastructure resource configuration library, that is, the configuration rules of the infrastructure resource configuration library have changed, and then calls the application program interfaces of cloud platform A, cloud platform B, and cloud platform C respectively in a declarative manner and dynamically adjusts the number of cloud servers A, cloud server B, and cloud server C according to the preset configuration rules carried by the second instruction.

[0057] As an example, the infrastructure resource configuration library reduces the number of cloud servers A and increases the number of cloud servers B and cloud servers C according to the preset configuration rules carried by the second instruction; or, increases the number of cloud servers A and reduces the number of cloud servers B and cloud servers C; or, reduces the number of cloud servers A and cloud servers C and increases the number of cloud servers B.

[0058] As an example, the preset configuration rule carried by the second instruction depends on the current prices of cloud servers A, B, and C. When the current price of a cloud server increases compared to the previous price, the number of cloud servers in the preset configuration rule decreases, and vice versa, the number of cloud servers in the preset configuration rule increases. When the current price of cloud server A increases compared to the previous price, and the current prices of cloud servers B and C decrease compared to the previous prices, the number of cloud servers A in the preset configuration rule decreases and the number of cloud servers B and C increases. For example, the infrastructure resource configuration library calls the application program interface of cloud platform A in a declarative manner and deletes 20 cloud servers A, calls the application program interface of cloud platform B and copies 10 cloud servers B using the created cloud server B as a template, and calls the application program interface of cloud platform C and copies 10 cloud servers C using the created cloud server C as a template. The copied cloud servers B and C automatically install the attached components of the deployment load node and automatically register with the management cluster. The kubernetes container orchestration tool deploys the Internet of Vehicles business microservices to the load nodes corresponding to each copied cloud server B and cloud server C.

[0059] The container cluster formed by the construction method 1000 provided in the present application can span multiple cloud platforms, ensuring that the Internet of Vehicles SaaS platform based on the container cluster is not deeply bound to any cloud platform and is not subject to any cloud computing service provider. When the Internet of Vehicles SaaS platform needs to be optimized according to infrastructure costs, it is only necessary to dynamically adjust the number of virtual machines on different cloud platforms, thereby enabling the Internet of Vehicles SaaS platform to be migrated between different cloud platforms at low cost and quickly.

[0060] The step division of the above methods is only for the purpose of clear description. When implemented, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent; adding insignificant modifications to the algorithm or process or introducing insignificant designs without changing the core design of the algorithm and process are all within the scope of protection of this patent.

[0061] An exemplary embodiment of the present application also provides an electronic device, which includes at least one processor and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute one or more steps of the above-mentioned method 1000 for building a container cluster across multiple cloud platforms.

[0062] The exemplary embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements one or more steps of the above-mentioned method 1000 for building a container cluster across multiple cloud platforms when the computer program is executed by a processor.

[0063] Figure 6 Schematically shows a block diagram of an electronic device 600 suitable for implementing the exemplary embodiments of the present application. Figure 6 As shown, the electronic device 600 includes a processor 601, which can perform various appropriate steps and processes according to computer program instructions stored in a read-only memory (ROM) 602 or computer program instructions loaded from a memory 608 to a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 600 can also be stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0064] Multiple components in the electronic device 600 are connected to the I / O interface 605, including: an input unit 606; an output unit 607; a memory 608, such as a disk, an optical disk, etc.; and a communication unit 609, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 609 allows the electronic device 600 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0065] The processor 601 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 601 may execute the various methods and processes described above, such as executing one or more steps of the method 1000 for building a container cluster across multiple cloud platforms. For example, in some embodiments, one or more steps of the method 1000 for building a container cluster across multiple cloud platforms may be implemented as a computer software program, which is stored in a machine-readable medium, such as a memory 608. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 600 via the ROM 602 and / or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the processor 601, one or more steps of the method 1000 for building a container cluster across multiple cloud platforms described above may be executed. Alternatively, in other embodiments, the processor 601 may be configured to execute one or more steps of the above-mentioned method 1000 for building a container cluster across multiple cloud platforms in any other appropriate manner (for example, by means of firmware).

[0066] Various aspects of the present application are described herein with reference to the flow chart and / or step diagram of the method, device (system), and computer program product according to the exemplary embodiments of the present application. It should be understood that each step of the flow chart and / or step diagram and the combination of each step in the flow chart and / or step diagram can be implemented by computer-readable program instructions.

[0067] These computer-readable program instructions can be provided to a processor in a voice interaction device, a general-purpose computer, a special-purpose computer, or a processing unit of other programmable data processing devices, thereby producing a machine, so that when these instructions are executed by a processing unit of a computer or other programmable data processing device, a device that implements the functions / steps specified in one or more steps in a flowchart and / or a step diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions enable a computer, a programmable data processing device, and / or other devices to work in a specific manner, so that a computer-readable medium storing instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / steps specified in one or more steps in a flowchart and / or a step diagram.

[0068] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / steps specified in one or more steps in the flowchart and / or step diagram.

[0069] The flow chart and step diagram in the accompanying drawings show the possible architecture, function and operation of the equipment, method and computer program product according to multiple embodiments of the present application. In this regard, each step in the flow chart or step diagram can represent a part of a module, program segment or instruction, and a part of the module, program segment or instruction includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the steps can also occur in a sequence different from that marked in the accompanying drawings. For example, two consecutive steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each step in the step diagram and / or flow chart, and the combination of the steps in the step diagram and / or flow chart, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0070] The above description is only an exemplary implementation of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of protection involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the technical concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method for constructing a container cluster across multiple cloud platforms, characterized in that: include: Building a container cluster based on an initial cloud platform, the initial cloud platform including a plurality of initial virtual machines in a cloud network, the container cluster including a management cluster and a load cluster, and the load cluster including load nodes corresponding to each of the initial virtual machines; Creating a predetermined number of target virtual machines on at least one target cloud platform according to the infrastructure resource configuration library, and making the target virtual machines of the at least one target cloud platform interconnected with the initial virtual machines of the initial cloud platform through an intranet; as well as The auxiliary components of the load node are deployed for each of the target virtual machines, and each of the target virtual machines is registered with the management cluster.

2. The method according to claim 1, wherein: Creating a predetermined number of target virtual machines on at least one target cloud platform according to the infrastructure resource configuration library includes: In response to the infrastructure resource configuration library monitoring the defined resources of at least one target cloud platform and initiating a request to create a predetermined number of the target virtual machines to the at least one target cloud platform, a predetermined number of the target virtual machines are created on the at least one target cloud platform.

3. The method according to claim 1, wherein: The target virtual machine of the at least one target cloud platform and the initial virtual machine of the initial cloud platform are interconnected through an intranet, including: The target virtual machine of the at least one target cloud platform communicates with the initial virtual machine of the initial cloud platform through an intranet of a communication tunnel.

4. The method according to claim 1, wherein: The auxiliary components include at least one of a kube-proxy component and a kubelet component.

5. The method according to any one of claims 1 to 4, wherein: The method further comprises: In response to each of the target virtual machines being registered with the management cluster, the number of initial virtual machines of the initial cloud platform and / or target virtual machines of the at least one target cloud platform is dynamically adjusted according to configuration rules of the infrastructure resource configuration library.

6. The method according to claim 5, wherein: Dynamically adjusting the number of initial virtual machines of the initial cloud platform and / or target virtual machines of the at least one target cloud platform according to the configuration rules of the infrastructure resource configuration library includes: In response to a change in a configuration rule of the infrastructure resource configuration library, the number of the initial virtual machines of the initial cloud platform is reduced and the number of the target virtual machines of the at least one target cloud platform is increased.

7. The method according to claim 5, wherein: Dynamically adjusting the number of initial virtual machines of the initial cloud platform and / or target virtual machines of the at least one target cloud platform according to the configuration rules of the infrastructure resource configuration library includes: In response to a change in the configuration rules of the infrastructure resource configuration library, the application program interface of the initial cloud platform is called and a preset number of the initial virtual machines are deleted; and the application program interface of the at least one target cloud platform is called and a preset number of the target virtual machines are copied.

8. The method according to claim 7, wherein: Copying a preset number of target virtual machines includes: At least one of the created target virtual machines is used as a template and a preset number of the target virtual machines are copied, and the copied target virtual machines automatically install and deploy the auxiliary components and automatically register with the management cluster.

9. An electronic device, characterized in that: include: at least one processor; as well as A memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor so that the at least one processor can execute the method of any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Citation Information

Cited By

  • Data processing

    WO2026118793A1