Load balancing service deployment method and apparatus

By using containers to automatically manage grid clusters in cloud service systems, and deploying load balancing services across multiple grid clusters, the problem of low resource utilization and high availability of load balancing services in public clouds is solved, and load balancing services are improved efficiency and usability.

WO2024244352A1PCT designated stage expired Publication Date: 2024-12-05HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/135613
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-26
Filing Date
2023-11-30
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

The low resource utilization rate of existing load balancing services in the public cloud, resulting in high operation and maintenance pressure and high cost, and it is difficult to meet high availability requirements.

Method used

By using containers as the minimum granular resource allocation unit in cloud service systems, we automatically manage grid clusters and deploy load balancing services across disaster recovery between multiple grid clusters, ensuring high availability and resource utilization of load balancing services. .

Benefits of technology

It improves the resource utilization rate of load balancing services, reduces operation and maintenance pressure and costs, and realizes high availability of load balancing services, which can maintain service availability in disaster recovery situations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023135613_05122024_PF_FP_ABST
    Figure CN2023135613_05122024_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a load balancing service deployment method and apparatus. The method comprises: after a first grid cluster is deployed, a load balancing service deployment apparatus determining one or more first containers from the first grid cluster to join a load balancing container set; after a second grid cluster is deployed, determining one or more second containers from the second grid cluster to join the load balancing container set; and after a deployment request for deploying a load balancing service is received, determining a resource unit from the load balancing container set to deploy the load balancing service. In this way, according to the method, after grid clusters are started, the grid clusters are automatically managed, and a load balancing service is issued by using containers as resource allocation units of the minimum granularity, so that the resource utilization rate can be improved. In addition, according to the method, corresponding containers are respectively determined from among a plurality of grid clusters to participate in the deployment of a load balancing service, so that the load balancing service has the high availability characteristic of cross-grid-cluster disaster recovery.
Need to check novelty before this filing date? Find Prior Art

Description

A load balancing service deployment method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on May 26, 2023, with application number 202310609179.X and application name “A Load Balancing Service Deployment Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of cloud computing technology, and in particular to a load balancing service deployment method and device. Background Art

[0004] Load balancing is a computer technology used to distribute load among computer clusters, network connections, CPUs, disk drives, or other resources to optimize resource usage, maximize throughput, minimize response time, and avoid overload.

[0005] Traditional load balancing services can be implemented in a variety of ways. For example, one approach is to use network hardware devices, such as F5. Another approach is to use software on physical or virtual machines, such as Linux Virtual Server (LVS), Domain Name Server (DNS) round-robin, HAProxy, or Nginx. Alternatively, load balancing services can be divided based on network layers, generally into Layer 4 load balancing and Layer 7 load balancing.

[0006] For example, taking public clouds as an example, currently mainstream public clouds all provide load balancing services in a software-based manner, such as 4-layer LVS or 7-layer Nginx, HAProxy, etc. Among them, mainstream public clouds use virtual machines (VMs) or bare metal to host load balancing resource pools, and at the same time provide multi-tenant capabilities by using VMs of different specifications and numbers. However, since load balancing services (or load balancers) are the foundational services of public clouds, almost all tenants rely on load balancing services to build their own services on public clouds. As a result, the number of VMs occupied by public cloud load balancing services continues to rise, reaching 30% or even higher. Although the specifications of these VMs are generally small, when considering the overhead of the guest operating system (Guest OS), this method of deploying load balancing services using VMs of different specifications as the minimum granularity for resource allocation still suffers from the problem of coarse resource granularity, resulting in low resource utilization.

[0007] Summary of the Invention

[0008] The embodiments of the present application provide a load balancing service deployment method and device to solve the problem of low resource utilization in the prior art and enable the load balancing service to meet high availability requirements.

[0009] In a first aspect, an embodiment of the present application provides a load balancing service deployment method, which can be applied to a cloud service system including at least one grid cluster. The method can be performed by a load balancing service deployment device or a component (such as a chip or integrated circuit) that can support the load balancing service deployment device to implement the functions required by the method. Optionally, taking the load balancing service deployment device executing the load balancing service deployment method as an example, in the method, the load balancing service deployment device can, after deploying the first grid cluster, determine one or more first containers in the first grid cluster to add to the load balancing container set, and then, after deploying the second grid cluster, determine one or more second containers in the second grid cluster to add to the load balancing container set, and then, after receiving a deployment request to deploy the load balancing service, determine a resource unit in the load balancing container set to deploy the load balancing service, wherein all first containers in the first grid cluster that have been added to the load balancing container set serve as first resource units for deploying the load balancing service, and all second containers in the second grid cluster that have been added to the load balancing container set serve as second resource units for deploying the load balancing service.

[0010] In the above design, the method automatically manages the first grid cluster or the second grid cluster after deploying the grid cluster (such as the first grid cluster or the second grid cluster), and issues load balancing services using containers as the smallest granularity of resource allocation units, thereby improving resource utilization. In addition, since the method determines the corresponding containers from multiple grid clusters to join the load balancing container set, the containers included in the load balancing container set are used to participate in the deployment of the load balancing service, so that the issued load balancing service can have high availability characteristics for disaster recovery across grid clusters, thereby ensuring that the issued load balancing service meets high availability requirements. Furthermore, the method shields the operation details of the underlying resource pool (i.e., the grid cluster) from the outside (such as users or tenants who need to apply for load balancing services), but receives load balancing service deployment requests in the form of services, and issues deployed load balancing services with availability. For example, the method can deploy and issue load balancing services according to the availability configuration policy of the load balancing service.

[0011] In one possible design, the method further includes:

[0012] Determining one or more first containers in the first grid cluster for replacing containers included in the load balancing container set and / or,

[0013] One or more second containers are determined in the second grid cluster to replace the containers included in the load balancing container set.

[0014] In the above design, the load balancing container set is updated by adopting the above-mentioned several possible implementation methods. The containers included in the updated load balancing container set are used to participate in the deployment of the load balancing service, so that the issued load balancing service has high availability characteristics of disaster recovery across multiple grid clusters (for example, across the first grid cluster and the second grid cluster), so that the issued load balancing service can meet the high availability requirements.

[0015] In one possible design, the method further includes:

[0016] A third mesh cluster is deployed, and one or more tenth containers are determined in the third mesh cluster to be added to the load-balancing container set, or one or more tenth containers are determined in the third mesh cluster to replace containers included in the load-balancing container set.

[0017] In the above design, after the third grid cluster is deployed and started, the third grid cluster is automatically managed, and corresponding containers can be selected in the third grid cluster to adjust the load balancing container set. The containers included in the adjusted load balancing container set are used to participate in the deployment of the load balancing service. In this way, the issued load balancing service can have high availability with disaster recovery across multiple grid clusters (for example, across the first grid cluster, the second grid cluster and the third grid cluster), so that the issued load balancing service can meet the high availability requirements.

[0018] In one possible design, the method further includes:

[0019] When a grid cluster to which a third container included in the load balancing container set belongs fails, a fourth container is selected from the grid clusters to which other containers included in the load balancing container set belong to replace the third container.

[0020] In the above design, when it is determined that the grid cluster to which one or several containers used to run the load balancing service belong fails, one or more containers can be automatically selected from other grid clusters to replace the affected one or more containers. In this way, the affected load balancing service can be migrated to other grid clusters, and one or more containers included in the other grid clusters can participate in running the load balancing service, thereby ensuring that the availability of the load balancing service is not affected.

[0021] In one possible design, the method further includes:

[0022] When a new container is included in the load balancing container set, the deployment form of the load balancing service is updated.

[0023] In the above design, when it is determined that a new container is used to participate in the deployment or operation of the load balancing service, the deployment form of the already issued load balancing service can be automatically updated, so that the load balancing service can meet the requirements of disaster tolerance and high availability in a self-operation and maintenance manner.

[0024] In one possible design, after deploying the first grid cluster, the method further includes:

[0025] Registering attribute information of the first grid cluster to the resource management platform;

[0026] After the second grid cluster is deployed, the method further includes:

[0027] registering attribute information of the second grid cluster to the resource management platform;

[0028] After determining resource units in the load balancing container set to deploy the load balancing service, the method further includes:

[0029] Register the attribute information of the load balancing service to the resource management platform.

[0030] In the above design, by registering the attribute information of the grid cluster and the attribute information of the load balancing service to the resource management platform, it can facilitate timely maintenance of the resource management platform, and can facilitate the requests submitted by users or tenants applying for load balancing services to accurately reach the corresponding deployment module, and can also facilitate the deployment module to understand the changes of the grid cluster in a timely manner.

[0031] In one possible design, the attribute information of the first grid cluster or the second grid cluster includes at least one of the following: a cluster identifier, an application programming interface API, or an identifier of the grid where the grid cluster is located;

[0032] The attribute information of the load balancing service includes at least one of the following: an identifier of the load balancing service, an Internet Protocol (IP) address, a blast radius, or an identifier of a grid cluster participating in the deployment or operation of the load balancing service, wherein the blast radius is used to characterize the high availability of the load balancing service, and the blast radius is determined based on the number of grid clusters participating in the deployment or operation of the load balancing service.

[0033] In a second aspect, embodiments of the present application provide a load balancing service deployment device. The beneficial effects can be found in the description of the first aspect and are not further elaborated here. The load balancing service deployment device has the function of implementing the behaviors described in the method example of the first aspect. The load balancing service deployment device is used to deploy a load balancing service on cloud computing resources, wherein the cloud computing resources include one or more servers in a database, and the cloud computing resources are used to deploy a grid cluster including multiple containers. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. In one possible design, the device includes a first bootstrapping module, a second bootstrapping module, and a deployment module. The first bootstrapping module is used to manage the first grid cluster after the first grid cluster is started, with all first containers in the first grid cluster that have been added to the load balancing container set serving as first resource units for deploying the load balancing service. The deployment module is used to determine one or more first containers in the first grid cluster to add to the load balancing container set. The second bootstrapping module is used to manage the second grid cluster after the second grid cluster is started, with all second containers in the second grid cluster that have been added to the load balancing container set serving as second resource units for deploying the load balancing service. The deployment module is further configured to determine one or more second containers in the second grid cluster to add to the load balancing container set. The deployment module is further configured to receive a deployment request for deploying a load balancing service and determine resource units in the load balancing container set to deploy the load balancing service. These modules can perform the corresponding functions in any possible design of the first aspect described above. For details, please refer to the detailed description in the example method and are not further described here.

[0034] In a third aspect, an embodiment of the present application provides a computing device, which has the function of implementing the behavior of the load balancing service deployment device in the method example of the first aspect above. The beneficial effects can be found in the description of the first aspect and will not be repeated here. The computing device includes a memory and a processor. Optionally, the computing device also includes a communication interface for communicating with other devices. The memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer program or instructions, the computing device executes the method in any possible design of the first aspect above.

[0035] In a fourth aspect, an embodiment of the present application provides a computing device cluster, which has the function of implementing the behavior of the load balancing service deployment device in the method example of the first aspect above. The beneficial effects can be found in the description of the first aspect and will not be repeated here. The computing device cluster includes at least one computing device, any computing device includes a processor and a memory, and the processor in any computing device is configured to support the load balancing service deployment device to perform part or all of the functions of the method in any possible design of the first aspect above. The memory is coupled to the processor, which stores the computer program instructions and data necessary for the load balancing service deployment device. Any computing device also includes a communication interface for communicating with other devices.

[0036] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer program instructions are stored. When the computer program instructions are executed by a computing device, the computing device executes the method in any possible design of the first aspect above.

[0037] In a sixth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computing device, enables the computing device to execute a method in any possible design of the first aspect described above.

[0038] In a seventh aspect, an embodiment of the present application further provides a computer chip, which is coupled to a memory, and is used to read a computer program stored in the memory and execute a method in any possible design of the first aspect above.

[0039] In an eighth aspect, an embodiment of the present application further provides a chip system, comprising a processor configured to support a computer device in implementing the method of any one of the possible designs of the first aspect. In one possible design, the chip system further comprises a memory configured to store programs and data necessary for the computer device. The chip system may be composed of a computer chip, or may include a computer chip and other discrete devices.

[0040] Based on the implementation methods provided in the above aspects, this application can also be further combined to provide more implementation methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] FIG1 exemplarily shows a schematic diagram of a possible application scenario provided by an embodiment of the present application;

[0042] FIG2 exemplarily shows a schematic diagram of the functional module structure of a load balancing service deployment device provided in an embodiment of the present application;

[0043] FIG3 exemplarily shows a flow chart of a load balancing service deployment method provided in an embodiment of the present application;

[0044] FIG4 a exemplarily shows a schematic diagram of related operations of a bootstrap module a after startup provided by an embodiment of the present application;

[0045] FIG4 b exemplarily shows a schematic diagram of related operations of a deployment module 1 provided in an embodiment of the present application after startup;

[0046] FIG4c is a schematic diagram showing an example of a deployment module updating or adjusting the deployment form of the load balancing service 01 when a new grid cluster b is added to a cloud service system provided by an embodiment of the present application;

[0047] FIG4 d exemplarily shows a schematic diagram of a deployment form of a deployment module 1 updated or adjusted by a bootstrapping module b when a new grid cluster b is added to a cloud service system provided by an embodiment of the present application;

[0048] FIG5 exemplarily shows a structural diagram of a possible computing device provided in an embodiment of the present application;

[0049] FIG6 exemplarily shows a schematic structural diagram of a possible computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0051] The following describes possible application scenarios to which the load balancing service deployment method provided by this application is applicable. It should be noted that these descriptions are for the purpose of facilitating understanding by those skilled in the art and do not limit the scope of protection claimed by this application.

[0052] FIG1 exemplarily shows a schematic diagram of a possible application scenario applicable to an embodiment of the present application. As shown in FIG1 , the application scenario may include a resource management platform (or may be called a registration service center) 100 and a cloud service system 110. The cloud service system 110 may include a load balancing service, a load balancing service deployment device and at least one grid (such as grid 10, grid 20, etc.). The grid is the smallest unit for fault isolation and capacity expansion. For example, a grid consists of 20 server resources in an availability zone (AZ). Each grid (Failure Domain) has a grid cluster (Grid Cluster), which is used to represent a resource pool composed of at least one cloud computing resource (such as cloud computing resources of different granularities such as virtual machines, containers, hosts or servers). When the underlying resource pool used to deploy the load balancing service is insufficient, the underlying resource pool is expanded. What is expanded are grid clusters, not individual cloud computing resources. Each grid cluster includes at least one container, and the at least one container included in each grid cluster can run on a physical host (or called a physical server, cloud server, physical computer or computing device, etc.), or can also run on multiple physical hosts (or called physical servers, cloud servers, physical computers or computing devices, etc.). For example, the first grid cluster in grid 10 includes containers 11, 12, 13 and 14, and the second grid cluster in grid 20 includes containers 21, 22, 23 and 24. For example, a grid can refer to an AZ with independent wind, fire, water and electricity. In addition, an AZ can refer to the physical area where a computer room or site is located, which has the characteristics of independent energy consumption and network. An AZ has independent water, electricity, network, etc.

[0053] Among them, the resource management platform 100 is responsible for maintaining the attribute information of the grid cluster (such as grid identification, cluster identification or API, etc.), the attribute information of the load balancing service (such as whether the load balancing service is cross-grid, which grids it is across, Internet Protocol (IP) address, explosion radius, or the identification of the load balancing service, etc.) and the corresponding attribute information of the load balancing service deployment device. Optionally, the resource management platform 100 is also used to support synchronous request calls and asynchronous message-based publishing and subscription. For example, a user who needs a load balancing service (such as a tenant who needs a load balancing service) can send a load balancing service deployment request to the resource management platform 100 through the terminal device used. The load balancing service deployment request is used to request the issuance or deployment of a load balancing service. After receiving the load balancing service deployment request, the resource management platform 100 can forward the load balancing service deployment request to the cloud service system 110, or can send the application programming interface (API) corresponding to the cloud service system 110 for issuing the load balancing service to the user's terminal device, so that the user's terminal device can send a load balancing service deployment request to the cloud service system 110 through the API. Load balancing is a service that distributes multiple cloud service requests (such as access requests) evenly to different processing devices. For example, a user may have a website with multiple servers handling access requests. To ensure that the load on each server is balanced, the user can apply for a load balancing service. This service receives all access requests to the website and evenly distributes them to the appropriate servers.

[0054] The explosion radius is used to characterize the high availability of the load balancing service. The smaller the explosion radius, the greater the high availability of the load balancing service. In other words, the explosion radius can be used to quantify the deployment form of the load balancing service. The explosion radius is determined by the number of grid clusters involved in deploying or running the load balancing service. For example, the explosion radius R satisfies the following form: R = 1 / N

[0055] Here, N is used to represent the number of grid clusters involved in deploying or running the load balancing service.

[0056] For example, when the load balancing service is carried on only one grid cluster, the explosion radius R = 1 / 1 = 1, indicating that the deployed load balancing service has the characteristics of spanning a single grid or spanning a single grid cluster. When the load balancing service is carried on two grid clusters, the explosion radius R = 1 / 2 = 0.5, indicating that the deployed load balancing service has the characteristics of spanning two grids or spanning two grid clusters. When the load balancing service is carried on three grid clusters, the explosion radius R = 1 / 3 = 0.33, indicating that the deployed load balancing service has the characteristics of spanning three grids or spanning three grid clusters.

[0057] The cloud service system 110 is used to provide external load balancing services, for example, it can deploy and issue corresponding load balancing services to users who apply for load balancing services.

[0058] For example, taking a tenant (e.g., tenant A) as an example, tenant A accesses the resource management platform 100 through the terminal device used (e.g., a smartphone, tablet, or laptop) and submits a load balancing service deployment request. The load balancing service deployment request is used to request the issuance of a load balancing service. In one possible implementation, after receiving the load balancing service deployment request, the resource management platform 100 can forward the load balancing service deployment request to a load balancing service deployment device in the cloud service system. After receiving the load balancing service deployment request, the load balancing service deployment device can deploy and issue the load balancing service to tenant A's terminal device.

[0059] In another possible implementation, after receiving the load balancing service deployment request, the resource management platform 100 may send the corresponding API of the load balancing service deployment device responsible for issuing the load balancing service to the terminal device of tenant A. After receiving the corresponding API of the load balancing service deployment device, the terminal device of tenant A may send a load balancing service deployment request to the corresponding load balancing service deployment device via the API. After receiving the load balancing service deployment request, the load balancing service deployment device may issue the load balancing service to the terminal device of tenant A.

[0060] Optionally, in one example, the load balancing service can be a single-grid load balancing service. For example, when there is only one grid (such as grid 10) in the cloud service system 110, the load balancing service deployment device can select one or more containers from the first grid cluster in grid 10 to add to the load balancing container set. After that, the load balancing service deployment device can select one or more containers in the load balancing container set to deploy the load balancing service. For example, for example, the load balancing service deployment device selects container 11, container 12, container 13, etc. from the first grid cluster to add to the load balancing container set. Container 11, container 12, container 13, etc. serve as resource units for deploying the load balancing service. When a load balancing service deployment request is received from a user terminal device, the load balancing service deployment device can select container 11 or container 12 or container 13 in the load balancing container set to deploy the load balancing service, or it can also select two containers (such as container 11 and container 12) in the load balancing container set to deploy the load balancing service, or it can also select three or more containers in the load balancing container set to deploy the load balancing service. The embodiment of the present application is not limited to this.

[0061] In another example, the load balancing service may also be a cross-grid (for example, across two grids or across more than two grids) load balancing service. For example, when there are multiple grids (for example, grid 10 and grid 20) in the cloud service system 110, the load balancing container set may be composed of one or more containers included in the first grid cluster in grid 10 and one or more containers included in the second grid cluster in grid 20. The one or more containers included in the first grid cluster serve as the first resource unit for deploying the load balancing service, and the one or more containers included in the second grid cluster serve as the second resource unit for deploying the load balancing service. Afterwards, the load balancing service deployment device may select the first resource unit or the second resource unit in the load balancing container set for deploying the load balancing application, or the load balancing service deployment device may select one or more containers in the first resource unit and one or more containers in the second resource unit in the load balancing container set for deploying the load balancing application. Exemplarily, the load balancing container set may be composed of a container (such as container 11) contained in the first grid cluster in grid 10 and a container (such as container 21) contained in the second grid cluster in grid 20, or the load balancing container set may be composed of multiple containers (such as container 11 and container 12) contained in the first grid cluster in grid 10 and multiple containers (such as container 21 and container 22) contained in the second grid cluster in grid 20, or the load balancing container set may be composed of a container (such as container 11) contained in the first grid cluster in grid 10 and multiple containers (such as container 21 and container 22) contained in the second grid cluster in grid 20, or the load balancing container set may be composed of multiple containers (such as container 11 and container 12) contained in the first grid cluster in grid 10 and a container (such as container 21) contained in the second grid cluster in grid 20. This embodiment of the present application is not limited to this.

[0062] It should be noted that Figure 1 only schematically provides a possible application scenario, and this schematic application scenario is for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the application scenario of the load balancing service deployment method provided by the present application. In addition, the form and quantity of each device in the application scenario shown in Figure 1 above are only used for example and do not constitute a limitation on the present application. Furthermore, the name of each device in the application scenario shown in Figure 1 is only an example, and the name of each device in the specific implementation may also be other names, and the present application does not make specific limitations on this. In addition, it is known to those skilled in the art that with the evolution of cloud service systems and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0063] As described in the background, existing solutions suffer from low resource utilization when deploying load balancing services. Furthermore, as the number of cloud tenants and cloud applications continues to increase, the resulting operational and maintenance pressure and costs of these solutions will also be relatively high. In light of this, the present application provides a load balancing service deployment method that effectively addresses the low resource utilization, high operational and maintenance pressure, and high costs inherent in existing technologies, while also enabling load balancing services to meet high availability requirements.

[0064] Based on the application scenario shown in FIG1 , the present application also provides a functional module structure of a load balancing service deployment device. Referring to FIG2 , according to the logical function division, the load balancing service deployment device can be divided into the following functional modules: at least one bootstrap module (such as a first bootstrap module, a second bootstrap module, etc.) and a deployment module. Among them, the first bootstrap module can be run through a container included in the first grid cluster, or it can be run through several containers included in the first grid cluster, or it can be run through any one or more of the multiple containers selected in the first grid cluster. It can be understood as setting the first bootstrap module in the first grid cluster. For example, the first bootstrap module can be run by container 11 or container 12 or container 13 or container 14 included in the first grid cluster, or it can be run jointly by two containers included in the first grid cluster (such as container 11 and container 12), or it can be run jointly by three or more containers included in the first grid cluster, or it can be run by any one (such as container 11) or any multiple (such as container 12 and container 13) of the multiple containers (such as container 11, container 12, container 13) selected in the first grid cluster. The embodiment of the present application does not limit this. The second bootstrap module is run by a container included in the second grid cluster, or it can be run by several containers included in the second grid cluster, or it can be run by any one or more of the multiple containers selected in the second grid cluster. It can be understood as setting a second bootstrap module in the second grid cluster. For example, the second bootstrap module can be run by container 21 or container 22 or container 23 or container 24 included in the second grid cluster, or it can be run jointly by two containers (such as container 21 and container 22) included in the second grid cluster, or it can be run jointly by three or more containers included in the second grid cluster, or it can be run by any one (such as container 21) or any multiple (such as container 22 and container 23) of multiple containers (such as container 21, container 22, container 23) selected in the second grid cluster. The embodiment of the present application is not limited to this.

[0065] It should be noted that the connection relationship between the various functional modules shown in Figure 2 is only an example and does not constitute a limitation of the present application. The functions of each functional module are described below.

[0066] The first bootstrap module is used to self-start when the first grid cluster starts, and automatically execute the corresponding processing flow after self-start. For example, in one example, the first bootstrap module can execute a processing flow: after self-starting, the first bootstrap module registers the attribute information of the first grid cluster (such as grid identifier, cluster identifier or API, etc.) to the resource management platform 100. In another example, the first bootstrap module can execute another processing flow: after self-starting, the first bootstrap module manages the first grid cluster, such as using the first grid cluster as the first resource pool required for deploying a load balancing service. Exemplarily, a resource pool may include multiple hosts (Host), and each host runs one or more containers. Optionally, a resource pool may be in an AZ, and a resource pool may include all containers running in an AZ.

[0067] The second bootstrap module is configured to automatically start when the second grid cluster starts and automatically execute corresponding processing flows after startup. For example, in one example, the second bootstrap module may execute a processing flow: after startup, the second bootstrap module registers attribute information (such as a grid identifier, cluster identifier, or API) of the second grid cluster with the resource management platform 100. In another example, the second bootstrap module may execute another processing flow: after startup, the second bootstrap module manages the second grid cluster, such as using the second grid cluster as a second resource pool for deploying a load balancing service.

[0068] Exemplarily, taking the first bootstrap module as an example, the first bootstrap module can also be used to execute another processing flow: when the first bootstrap module determines that there is no deployment module (Deployment Module) in the cloud service system, it is responsible for pulling up the deployment module. For example, when the first bootstrap module inquires through the resource management platform 100 that there is only one grid (such as grid 10) in the cloud service system, the first bootstrap module starts the deployment module with the selected container running after using the first grid cluster as the resource pool required for deploying the load balancing service. Optionally, the first bootstrap module can also select one or more containers in the grid cluster to participate in running the deployment module. The one or more containers can serve as a resource unit for running the deployment module, and then start the deployment module.

[0069] The deployment module is responsible for the deployment and issuance of load balancing services.

[0070] For example, continuing with tenant A as an example, in one possible implementation, after tenant A submits a load balancing service deployment request to the resource management platform 100 through the terminal device used, the resource management platform 100 can forward the load balancing service deployment request to the corresponding deployment module. After receiving the load balancing service deployment request, the deployment module can select a corresponding resource unit from the determined load balancing container set or select one or more containers from the corresponding resource unit for deploying the load balancing service, and then issue the load balancing service to tenant A's terminal device. The load balancing service deployment request is used to request the issuance of a load balancing service.

[0071] In another possible implementation, after tenant A submits a load balancing service deployment request to the resource management platform 100 through the terminal device used, the resource management platform 100 may send the API of the deployment module responsible for issuing the load balancing service to tenant A's terminal device. After receiving the deployment module API, tenant A's terminal device may use the API to send a load balancing service deployment request to the corresponding deployment module. After receiving the load balancing service deployment request, the deployment module may select a corresponding resource unit from the determined set of load balancing containers or select one or more containers from the corresponding resource unit for deploying the load balancing service, and then issue the load balancing service to tenant A's terminal device.

[0072] Optionally, in one example, when there is only a single grid (such as grid 10) in the cloud service system, after the first bootstrap module corresponding to grid 10 starts the deployment module, the deployment module can register the attribute information of the deployment module (such as the deployment module's identifier, API, or which grids are used to run the deployment module (that is, which grids the deployment module spans), etc.) to the resource management platform 100. Afterwards, the deployment module can select one or more containers from the first resource pool corresponding to grid 10 (that is, the first grid cluster) to add to the load balancing container set. The one or more containers serve as resource units for deploying the load balancing service, and can select corresponding resource units from the load balancing container set or select one or more containers from the corresponding resource units for deploying the load balancing service. At this time, the deployed load balancing service is a single-grid load balancing service.

[0073] In another example, when a new grid (such as grid 20) is added to the cloud service system, the second bootstrap module corresponding to grid 20 is automatically started when the second grid cluster in grid 20 is started, and automatically executes the corresponding processing process after self-starting. Optionally, in addition to automatically executing the processing flows described in the two relevant examples in the above-mentioned second bootstrapping module, the second bootstrapping module can also automatically execute another processing flow: when the second bootstrapping module queries in the resource management platform 100 that the deployment module 120 is only deployed in a single grid 10, the second bootstrapping module can select one or more containers in the second resource pool (i.e., the second grid cluster) corresponding to the grid 20 to add to the deployment module container set, or it can also select one or more containers in the second resource pool (i.e., the second grid cluster) corresponding to the grid 20 to replace the containers included in the deployment module container set. The one or more containers added to the deployment module container set in the second grid cluster can be used as another resource unit for running the deployment module, wherein the deployment module container set already contains one or more containers selected from the first resource pool. Afterwards, the second bootstrapping module can run the deployment module in one resource unit or several resource units, or it can select corresponding containers in different resource units to run the deployment module, thereby achieving high-availability deployment of the deployment module across grids. For example, taking the case where there are two containers (e.g., container 11 and container 12) in the first grid cluster for running the deployment module, in one possible implementation, to ensure that the container capacity required for running the deployment module remains unchanged, the second bootstrapping module may select a container (e.g., container 21) from the second resource pool to replace one of the containers 11 and 12 included in the deployment module container set. In another possible implementation, the second bootstrapping module may also select one or more containers from the second resource pool to add to the deployment module container set, and then may select one or more containers from the deployment module container set to participate in running the deployment module.

[0074] In addition, when the deployment module learns through the resource management platform 100 that a new grid 20 is added to the cloud service system, a processing flow can be automatically executed: the deployment module can select one or more containers in the second grid cluster to add to the load balancing container set, wherein the load balancing container set already has one or more containers selected from the first resource pool, and the one or more containers selected from the first resource pool serve as another resource unit for deploying the load balancing service. Afterwards, the deployment module can select a resource unit or several resource units in the load balancing container set to deploy the load balancing service, or it can select corresponding containers in different resource units to deploy the load balancing service, so as to achieve high-availability deployment of the load balancing service across grids. For example, taking the case where there are two containers (such as container 13 and container 14) in the first grid cluster for deploying the load balancing service, in one possible implementation, in order to ensure that the container capacity required for deploying the load balancing service remains unchanged, the deployment module can select a container (such as container 23) in the second grid cluster to replace one of the containers 13 and 14 included in the load balancing container set, and the unreplaced container among containers 13 and 14 serves as a resource unit for deploying the load balancing service, and container 23 serves as another resource unit for deploying the load balancing service. In another possible implementation, the deployment module can also select one or more containers in the second grid cluster to add to the load balancing container set, and the one or more containers selected in the second grid cluster serve as another resource unit for deploying the load balancing service. Afterwards, the deployment module can select a resource unit or several resource units in the load balancing container set to deploy the load balancing service, or can select corresponding containers in different resource units to deploy the load balancing service.

[0075] Optionally, the first bootstrap module, the second bootstrap module, and the deployment module illustrated in FIG2 can all be implemented via software, or can all be implemented via hardware. Exemplarily, the implementation of the deployment module will now be described using the deployment module as an example. Similarly, the implementation of the first bootstrap module and the second bootstrap module can refer to the implementation of the deployment module, and will not be further described herein.

[0076] When implemented by software, the deployment module is an example of a software functional unit, and the deployment module can be an application or code block running on a computer device. The computer device can be at least one of a physical host, a virtual machine, a container and other computing devices. Furthermore, the above-mentioned computer device can be one or more. For example, the deployment module can be an application running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the application can be distributed in the same availability zone (AZ) or in different AZs. The multiple hosts / virtual machines / containers used to run the application can be distributed in the same region or in different regions. Generally, a region can include multiple AZs.

[0077] Similarly, multiple hosts / virtual machines / containers used to run the application can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Typically, a region can include multiple VPCs, and a VPC can include multiple AZs.

[0078] When implemented through hardware, the deployment module, as an example of a hardware functional unit, may include at least one computing device, such as a server. Alternatively, the deployment module may be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0079] The multiple computing devices included in the deployment module can be distributed in the same AZ or different AZs. The multiple computing devices included in the deployment module can be distributed in the same region or different regions. Similarly, the multiple computing devices included in the deployment module can be distributed in the same VPC or across multiple VPCs. The multiple computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

[0080] It should be noted that the steps implemented by the first bootstrap module, the second bootstrap module and the deployment module can be specified as needed, and the first bootstrap module, the second bootstrap module and the deployment module respectively implement different execution steps of the load balancing service deployment method to realize all the functions of the load balancing service deployment device.

[0081] In addition, it should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods. The functional modules in the embodiments of the present application can be integrated into one module, or each module can exist physically alone, or two or more modules can be integrated into one module, for example, the first bootstrap module and the second bootstrap module are integrated into one module, or the first bootstrap module and the second bootstrap module are the same module. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0082] The following is a detailed introduction to the specific implementation of the load balancing service deployment method in the embodiment of the present application based on the application scenario shown in Figure 1 and the functional module structure of the load balancing service deployment device shown in Figure 2.

[0083] FIG3 exemplarily shows a flow chart of a load balancing service deployment method provided by an embodiment of the present application. The method is applicable to the application scenario illustrated in FIG1 . The method flow can be executed by a load balancing service deployment device or a component (such as a chip or integrated circuit) that can support the load balancing service deployment device to implement the functions required by the method. Optionally, in order to facilitate the introduction of the technical solution provided by an embodiment of the present application, the following takes the first bootstrap module, the second bootstrap module and the deployment module included in the load balancing service deployment device as an example to introduce the flow of the load balancing service deployment method executed by the first bootstrap module, the second bootstrap module and the deployment module. As shown in FIG3 , the method includes:

[0084] Step 301: After the first grid cluster is started, the first bootstrap module manages the first grid cluster.

[0085] Optionally, the first bootstrap module is deployed in a first grid cluster. The first bootstrap module may be run by one or more containers included in the first grid cluster, and the first bootstrap module is automatically started when the first grid cluster is started. The first grid cluster may be one of at least one grid cluster included in the cloud service system.

[0086] After the first bootstrap module is self-started, it can use the first grid cluster as the resource pool (or underlying resource pool) required for deploying the load balancing service. In this way, the first grid cluster can be transformed into the underlying resource pool required for deploying the load balancing service through the bootstrap module with a small amount of resource consumption, thereby enabling the first bootstrap module to automatically manage the first grid cluster without the need for manual human intervention, thereby solving the problem of high startup cost and high operation and maintenance pressure caused by the use of VM as the minimum resource granularity for load balancing services in the prior art. In addition, the self-starting method of the first bootstrap module can effectively reduce the consumption of startup resources, thereby reducing the startup cost, thereby enabling the load balancing service deployment method provided in the embodiment of the present application to be adapted to a variety of application scenarios (such as resource-constrained scenarios such as private clouds).

[0087] Optionally, after self-starting, the first bootstrap module may also register the attribute information of the first grid cluster with the resource management platform so that the resource management platform can maintain and manage the attribute information of the first grid cluster. Optionally, illustratively, the first bootstrap module registers the attribute information of the first grid cluster with the resource management platform, which can also facilitate the subsequent deployment module to be informed of changes in the grid cluster included in the cloud service system through the resource management platform, thereby enabling the deployment module to automatically adjust the set of load balancing containers required for deploying the load balancing service based on changes in the grid cluster included in the cloud service system. The attribute information of the first grid cluster may include at least one of the following: an identifier of the grid where the first grid cluster is located, a cluster identifier of the first grid cluster, or an API of the first grid cluster, etc.

[0088] For example, in one example, the first grid cluster is taken as the initial grid cluster in the cloud service system. In this case, the first grid cluster is a grid cluster of a single grid (such as grid a) in the cloud service system. As shown in FIG4a , the bootstrap module a can be run by one or more containers included in the grid cluster a in grid a. Optionally, the bootstrap module a is run by one or more containers in the bootstrap module container set. For example, if the bootstrap module container set includes two containers selected from the grid cluster a (such as container a1 and container a2), the bootstrap module a can be run by either container a1 or container a2, or can be run by both container a1 and container a2. For example, taking the bootstrap module container set as an example, in which the bootstrap module container set includes two containers selected from the grid cluster (such as container a1 and container a2), when the grid cluster a is started, the bootstrap module a is automatically started along with the startup of the grid cluster a, and after the startup, the cluster identifier a, grid identifier a, and API1 of the grid cluster a are registered with the resource management platform. In addition, after the bootstrapping module a is self-started, the grid cluster a can be turned into the first underlying resource pool required for deploying the load balancing service.

[0089] Step 302: The deployment module determines one or more first containers in the first grid cluster to add to the load balancing container set.

[0090] Optionally, when the first grid cluster is the first grid cluster required for deploying a load balancing service, in one example, the deployment module can determine one or more first containers in the first grid cluster to add to the load balancing container set. All first containers in the first grid cluster that have been added to the load balancing container set can serve as the first resource unit for deploying the load balancing service, and the containers included in the first resource unit are used to participate in deploying the load balancing service. Afterwards, the deployment module can provide the load balancing service to the outside world (that is, the deployment module can issue a load balancing service with single grid or single grid cluster characteristics to users who apply for the load balancing service). Then, when the deployment module receives a load balancing service deployment request from a user terminal device, it can determine the first resource unit in the load balancing container set to deploy the load balancing service, or it can select one or more containers in the first resource unit to deploy the load balancing service, and can issue the deployed load balancing service with single grid or single grid cluster characteristics to the user terminal device. Among them, the load balancing service deployment request is used to request the issuance of a load balancing service, and the first resource unit includes one or more containers.

[0091] In another example, the deployment module can pre-determine the first resource unit in the load balancing container set to deploy the load balancing service, and after receiving the load balancing service deployment request from the user terminal device, it can distribute the deployed load balancing service with single grid or single grid cluster characteristics to the user terminal device.

[0092] In addition, when a new grid cluster (i.e., a new resource pool, for example, the new resource pool is the second underlying resource pool required for deploying the load balancing service) is added to the cloud service system after the first grid cluster (in this case, the first grid cluster is the first grid cluster required for deploying the load balancing service), the deployment module can select one or more containers in the new grid cluster to add to the load balancing container set, where the load balancing container set already contains one or more containers selected from the first grid cluster, or the deployment module can also select one or more containers in the new grid cluster to replace the containers included in the load balancing container set. Afterwards, the deployment module can update the deployment form of the issued load balancing service, so that the deployment form of the issued load balancing service changes from having the characteristics of spanning a single grid or spanning a single grid cluster to having the characteristics of spanning multiple grids or spanning multiple grid clusters.

[0093] When the first grid cluster is a newly added grid cluster located after the initial grid cluster, the deployment module can select one or more first containers in the first grid cluster to add to the load balancing container set, and the load balancing container set already contains one or more containers selected from other grid clusters, or the deployment module can also select one or more first containers in the first grid cluster to replace the containers included in the load balancing container set. After that, the deployment module can provide load balancing services to the outside world based on the load balancing container set (that is, the deployment module can issue load balancing services with cross-grid or cross-grid cluster characteristics to users who apply for load balancing services). In one example, the deployment module can pre-determine a resource unit or several resource units in the load balancing container set to deploy the load balancing service, or can pre-select one or more containers in a resource unit to deploy the load balancing service, or can pre-select corresponding containers in different resource units to deploy the load balancing service. When the deployment module receives a load balancing service deployment request from a user terminal device, it can issue the already deployed load balancing service with cross-grid or cross-grid cluster characteristics to the user terminal device. Wherein, the load balancing service deployment request is used to request the issuance of a load balancing service.

[0094] In another example, after receiving a load balancing service deployment request from a user terminal device, the deployment module can determine a resource unit or several resource units in the load balancing container set to deploy the load balancing service, or it can select one or more containers in a resource unit to deploy the load balancing service, or it can select corresponding containers in different resource units to deploy the load balancing service, and can distribute the deployed load balancing service with cross-grid or cross-grid cluster characteristics to the user terminal device.

[0095] Illustratively, the following describes the implementation process of the deployment module selecting one or more first containers in the first grid cluster to participate in deploying the load balancing service through the following possible implementation methods.

[0096] Implementation method 1: When the first grid cluster is an initial grid cluster in the cloud service system, the deployment module may select one or more first containers in the first grid cluster for deploying the load balancing service.

[0097] Furthermore, when the first grid cluster is the initial grid cluster in the cloud service system, in one example, after converting the first grid cluster into the first underlying resource pool required for deploying the load balancing service, the first bootstrapping module may start a deployment module (e.g., deployment module 1) running in one or more containers selected in the first resource pool. In another example, the first bootstrapping module may also select one or more containers in the first grid cluster for running a deployment module (e.g., deployment module 1) and start the deployment module.

[0098] For example, the deployment module 1 shown in FIG4b is composed of two containers (such as container a3 and container a4) contained in a first grid cluster (such as grid cluster a). When the bootstrap module a uses grid cluster a as the underlying resource pool required for deploying the load balancing service, after startup, the deployment module 1 can register the attribute information of the deployment module 1 (such as deployment module identifier 1, API 2, and grid identifier a) to the resource management platform. At this time, grid cluster a becomes an underlying resource pool required for deploying the load balancing service. Based on this, the deployment module 1 can select one or more containers in grid cluster a to add to the load balancing container set. After that, the deployment module 1 can deploy the load balancing service based on the load balancing container set.

[0099] In one possible implementation, the deployment module 1 may deploy a load balancing service (e.g., load balancing service 01 or load balancing service 02) in advance. For example, the deployment module 1 may select two containers (e.g., container a5 and container a6) in the grid cluster a and add them to the load balancing container set. The deployment module 1 may then select either container a5 or container a6 from the load balancing container set to deploy the load balancing service 01, or may select both container a5 and container a6 from the load balancing container set to deploy the load balancing service 01. Alternatively, the deployment module 1 may select two containers (e.g., container a7 and container a8) in the grid cluster a and add them to the load balancing container set. The deployment module 1 may then select either container a7 or container a8 from the load balancing container set to deploy the load balancing service 02, or may select both container a7 and container a8 from the load balancing container set to deploy the load balancing service 02. Then, upon receiving a load balancing service deployment request from tenant A via a terminal device, the deployment module 1 may provide the load balancing service externally, for example, by issuing the deployed load balancing service 01 or load balancing service 02 to tenant A. At this time, the deployment module 1 may also register the attribute information of the load balancing service 01 (such as the load balancing service identifier 01, IP address, blast radius 1, and grid identifier a) to the resource management platform.

[0100] For example, taking a tenant (such as tenant A) applying for load balancing service 01 from the deployment module as an example, tenant A can send a load balancing service deployment request to the resource management platform through the terminal device used. The load balancing service deployment request is used to request the issuance of the load balancing service. Afterwards, the resource management platform can send the API1 of the deployment module responsible for issuing the load balancing service to tenant A's terminal device after receiving the load balancing service deployment request. Then, tenant A's terminal device can send a load balancing service deployment request to the corresponding deployment module through the API1. Finally, after receiving the load balancing service deployment request, the deployment module issues the load balancing service 01 to tenant A's terminal device.

[0101] In another possible implementation, after receiving a load balancing service deployment request from tenant A via a terminal device, deployment module 1 may select one or more containers from the load balancing container set for deploying the load balancing service and may then distribute the deployed load balancing service to tenant A. For example, assuming that the load balancing container set includes containers a5 and a6, deployment module 1 may select containers a5 and a6 from the load balancing container set to run load balancing service 01 together, or may select either container a5 or container a6 from the load balancing container set to deploy load balancing service 01. Deployment module 1 may then distribute load balancing service 01 to tenant A's terminal device. When a new grid cluster is added to the cloud service system, the bootstrap module set in the new grid cluster uses the new grid cluster as the underlying resource pool required for deploying the load balancing service. The deployment module 1 can automatically select one or more containers in the new underlying resource pool to update or adjust the deployment form of the issued load balancing service 01, that is, to change the deployment form of the issued load balancing service 01 from having the characteristics of spanning a single grid or spanning a single grid cluster to having the characteristics of spanning multiple grids or spanning multiple grid clusters.

[0102] In another possible implementation, after receiving a load balancing service deployment request from tenant B via a terminal device, deployment module 1 may select one or more containers from the load balancing container set for deploying the load balancing service, and may then provision the deployed load balancing service to tenant B. For example, taking the load balancing container set as an example, where container a7 and container a8 exist in the load balancing container set, deployment module 1 may select container a7 and container a8 from the load balancing container set to run load balancing service 02 together, or may select either container a7 or container a8 from the load balancing container set to deploy load balancing service 02. Optionally, after receiving a load balancing service deployment request from tenant B via a terminal device, deployment module 1 may select multiple containers (e.g., container a7 and container a8) from grid cluster a to add to the load balancing container set. Thereafter, deployment module 1 may select container a7 and container a8 from the load balancing container set to run load balancing service 02 together, or may select either container a7 or container a8 from the load balancing container set to deploy load balancing service 02. Deployment module 1 may then provision load balancing service 02 to tenant B's terminal device. When a new grid cluster is added to the cloud service system, the bootstrap module set in the new grid cluster uses the new grid cluster as the underlying resource pool required for deploying the load balancing service. The deployment module 1 can automatically select one or more containers in the new underlying resource pool to update or adjust the deployment form of the issued load balancing service 02, that is, to change the deployment form of the issued load balancing service 02 from having the characteristics of spanning a single grid or spanning a single grid cluster to having the characteristics of spanning multiple grids or spanning multiple grid clusters.

[0103] Implementation method 2: When the first grid cluster is not the initial grid cluster in the cloud service system, and one or more containers in other grid clusters have been selected to be added to the load balancing container set or to replace the containers included in the load balancing container set, the deployment module can select one or more containers in the first grid cluster to be added to the load balancing container set. Afterwards, the deployment module can select one or more containers in the load balancing container set for deploying the load balancing service.

[0104] Implementation method three: When the first grid cluster corresponding to the first resource pool is not the initial grid cluster in the cloud service system, and one or more containers in other grid clusters have been selected to be added to the load balancing container set or to replace containers included in the load balancing container set, the deployment module can select a first container in the first grid cluster to replace any container selected in the other grid cluster that already exists in the load balancing container set, or the deployment module can also select multiple first containers in the first grid cluster to replace any multiple containers selected in the other grid cluster that already exist in the load balancing container set.

[0105] For example, the solutions provided by the above-mentioned implementation methods 2 and 3 are described using the example of an initial grid cluster (e.g., grid cluster a) existing before the first grid cluster in the cloud service system. As shown in FIG4c , when a first grid cluster (e.g., grid cluster b) is added to the cloud service system, the bootstrap module b of grid cluster b automatically starts when grid cluster b starts. After self-starting, the cluster identifier b, grid identifier b, and API 3 of grid cluster b are registered with the resource management platform. At this point, grid cluster b becomes another underlying resource pool required for deploying load balancing services. Optionally, the bootstrap module b can be run by one or more containers included in grid cluster b in grid b. The bootstrap module b is run by one or more containers in the bootstrap module container set. For example, if the bootstrap module container set includes two containers selected from grid cluster b (e.g., container b1 and container b2), the bootstrap module b can be run by either container b1 or container b2, or by both container b1 and container b2. Based on this, when deployment module 1 detects a new grid cluster b in the cloud service system through the resource management platform, it can select one or more containers in grid cluster b and add them to the load balancing container set, where one or more containers selected from grid cluster a already exist in the load balancing container set. Optionally, deployment module 1 can also select one or more containers in grid cluster b to replace containers included in the load balancing container set. For example, deployment module 1 can select a container in grid cluster b to replace any container selected in grid cluster a that already exists in the load balancing container set, or it can select multiple containers in grid cluster b to replace any multiple containers selected in grid cluster a that already exist in the load balancing container set. Then, deployment module 1 can deploy a load balancing service based on the load balancing container set. For example, if the load balancing container set includes container a6 in grid cluster a and container b5 in grid cluster b, deployment module 1 can select one or more containers in the load balancing container set (such as either container a6 or container b5, or a combination of container a6 and container b5) to deploy load balancing service 01. Optionally, the deployment module 1 may also register the attribute information of the load balancing service 01 (such as the load balancing service identifier 01, IP address, blast radius 2, and grid identifier a) to the resource management platform.

[0106] Illustratively, the following examples describe the implementation process of the deployment module 1 selecting a container in the grid cluster b to be added to the load balancing container set or to replace a container included in the load balancing container set.

[0107] Example 1: Taking the example of deployment module 1 selecting a container in grid cluster b to replace one of multiple containers (such as container a5 and container a6) selected in grid cluster a and already existing in the load balancing container set, deployment module 1 can select container b5 in grid cluster b to add to the running container of load balancing service 01, and at the same time release any one of container a5 and container a6 included in the load balancing container set, such as releasing container a5. At this time, the multiple containers included in the load balancing container set are container b5 included in grid cluster b in grid b and container a6 included in grid cluster a in grid a. Deployment module 1 can select one or more containers in the load balancing container set to deploy the load balancing service (such as load balancing service 01), realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of load balancing service 01. In this way, it can be ensured that load balancing service 01 has high availability characteristics across grid clusters or across grids, and the container capacity of the running load balancing container set can be ensured to remain unchanged.

[0108] Example 2: Taking the example where the deployment module 1 selects a container in grid cluster b and adds it to the load balancing container set, and the load balancing container set already contains multiple containers (such as container a5 and container a6) selected from grid cluster a, the deployment module 1 can select container b5 in grid cluster b and add it to the load balancing container set. At this time, the multiple containers included in the load balancing container set are container b5 included in grid cluster b in grid b and container a5 and container a6 included in grid cluster a in grid a. The deployment module 1 can select one or more containers in the load balancing container set for deploying a load balancing service (such as load balancing service 01), thereby realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of the load balancing service 01, thereby ensuring that the load balancing service 01 has high availability characteristics across grid clusters or across grids.

[0109] Example 3: Taking the example of deployment module 1 selecting multiple containers in grid cluster b and adding them to the load balancing container set, where multiple containers (such as container a5 and container a6) selected from grid cluster a already exist in the load balancing container set, deployment module 1 can select container b6 and container b5 in grid cluster b and add them to the load balancing container set. At this time, the multiple containers included in the load balancing container set are container b6 and container b5 included in grid cluster b in grid b and container a5 and container a6 included in grid cluster a in grid a. Deployment module 1 can select one or more containers in the load balancing container set for deploying a load balancing service (such as load balancing service 01), thereby realizing cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of load balancing service 01, thereby ensuring that load balancing service 01 has high availability characteristics across grid clusters or across grids.

[0110] Example 4: Taking the example where the deployment module 1 selects a container in grid cluster b and adds it to the load balancing container set, and a container (such as container a5) selected from grid cluster a already exists in the load balancing container set, the deployment module 1 can select container b5 in grid cluster b and add it to the load balancing container set. At this time, the multiple containers included in the load balancing container set are container b5 included in grid cluster b in grid b and container a5 included in grid cluster a in grid a. The deployment module 1 can select one or more containers in the load balancing container set for deploying a load balancing service (such as load balancing service 01), thereby realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of the load balancing service 01, thereby ensuring that the load balancing service 01 has high availability characteristics across grid clusters or across grids.

[0111] Example 5: Taking the example of deployment module 1 selecting multiple containers in grid cluster b and adding them to the load balancing container set, where a container (such as container a5) selected from grid cluster a already exists in the load balancing container set, deployment module 1 can select containers b6 and b5 in grid cluster b and add them to the load balancing container set. At this time, the multiple containers included in the load balancing container set are container b6 and container b5 included in grid cluster b in grid b and container a5 included in grid cluster a in grid a. Deployment module 1 can select one or more containers in the load balancing container set to deploy a load balancing service (such as load balancing service 01), thereby realizing cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of load balancing service 01, thereby ensuring that load balancing service 01 has high availability characteristics across grid clusters or across grids.

[0112] In addition, when the first grid cluster is not the initial grid cluster in the cloud service system, and one or more containers in other grid clusters have been selected to be added to the load balancing container set or to replace the containers included in the load balancing container set, before the deployment module adjusts or updates the deployment form of the load balancing service, the first bootstrap module will also update or adjust the deployment form of the deployment module, that is, the first bootstrap module adjusts or updates the deployment module container set required for running the deployment module. For example, the first bootstrap module can determine one or more fifth containers in the first grid cluster to add to the deployment module container set, or it can also determine one or more fifth containers in the first grid cluster to replace the containers included in the deployment module container set. Afterwards, the first bootstrap module can determine one or more sixth containers in the deployment module container set to participate in running the deployment module.

[0113] Exemplarily, the following describes the implementation process of the first bootstrap module adjusting or updating the deployment module container set required for running the deployment module through the following possible implementation methods.

[0114] Method 1: When the first bootstrap module queries through the resource management platform that the deployment module container set only includes one container selected from other grid clusters, the first bootstrap module can select one or more containers in the first grid cluster to add to the deployment module container set, or can also select a container in the first grid cluster to replace the container included in the deployment module container set.

[0115] Method 2: When the first bootstrapping module queries the resource management platform and finds that the deployment module container set includes multiple containers selected from other grid clusters, the first bootstrapping module can select one or more containers in the first grid cluster to add to the deployment module container set.

[0116] Method three: When the first bootstrap module queries through the resource management platform that the deployment module container set includes multiple containers selected from other grid clusters, the first bootstrap module can select a container in the first grid cluster to replace any one of the multiple containers included in the deployment module container set, or the first bootstrap module can select multiple containers in the first grid cluster to replace any multiple of the multiple containers included in the deployment module container set.

[0117] For example, let's continue to explain the solutions provided by Methods 1, 2, and 3 above, assuming that an initial mesh cluster (e.g., mesh cluster a) exists before the first mesh cluster in the cloud service system. As shown in Figure 4d, when a new mesh cluster (e.g., mesh cluster b) is added to the cloud service system, the bootstrapping module b of mesh cluster b automatically starts when mesh cluster b starts. After startup, it registers the cluster identifier b, mesh identifier b, and API 3 of mesh cluster b with the resource management platform. At this point, mesh cluster b becomes another underlying resource pool required for deploying the load balancing service.

[0118] In one possible implementation, after the bootstrap module b registers the cluster identifier b, grid identifier b, and API 3 of grid cluster b with the resource management platform, when the bootstrap module b queries the resource management platform and finds that the deployment module has been deployed and that the deployment module is only deployed in grid a, the bootstrap module b can select one or more containers in grid cluster b to add to the deployment module container set, where one or more containers selected from grid cluster a already exist in the deployment module container set, or the bootstrap module b can also select one or more containers in grid cluster b to replace containers included in the deployment module container set. For example, the bootstrap module b can also select a container in grid cluster b to replace any container in the deployment module container set, or the bootstrap module b can also select multiple containers in grid cluster b to replace any multiple containers in the deployment module container set. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to run the deployment module (for example, deployment module 1).

[0119] Illustratively, the following examples introduce an implementation process of the bootstrapping module b selecting one or more containers in the grid cluster b to be added to the deployment module container set or to replace containers included in the deployment module container set.

[0120] Example 1: Taking the example of the bootstrap module b selecting a container in grid cluster b to replace one of the multiple containers (such as container a3 and container a4) selected in grid cluster a and already existing in the deployment module container set, the bootstrap module b can select container b4 in grid cluster b to add to the deployment module container set, and at the same time release any one of the containers a3 and a4 included in the deployment module container set required for running the deployment module, such as releasing container a4. At this time, the multiple containers included in the deployment module container set are container b4 included in grid cluster b in grid b and container a3 included in grid cluster a in grid a. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in running the deployment module (such as deployment module 1), thereby realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of deployment module 1. This can ensure that deployment module 1 has high availability characteristics across grid clusters or across grids, and can ensure that the container capacity of the deployment module container set remains unchanged.

[0121] Example 2: Taking the example of the bootstrap module b selecting a container in grid cluster b to add to the deployment module container set that already has multiple containers selected from grid cluster a (such as container a3 and container a4), the bootstrap module b can select container b4 in grid cluster b to add to the deployment module container set. At this time, the multiple containers included in the deployment module container set required to run the deployment module are container b4 included in grid cluster b in grid b and container a3 and container a4 included in grid cluster a in grid a. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) deployment or cross-grid (i.e., across grid a and grid b) deployment of deployment module 1, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids.

[0122] Example 3: Taking the example of the bootstrap module b selecting multiple containers in grid cluster b to add to the deployment module container set that already has multiple containers selected from grid cluster a (such as container a3 and container a4), the bootstrap module b can select container b3 and container b4 in grid cluster b to add to the deployment module container set. At this time, the multiple containers included in the deployment module container set required to run the deployment module are container b3 and container b4 included in grid cluster b in grid b and container a3 and container a4 included in grid cluster a in grid a. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of deployment module 1, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids.

[0123] Example 4: Taking the example of the bootstrap module b selecting a container in grid cluster b to add to an existing container (such as container a3) selected from grid cluster a, the bootstrap module b can select container b4 in grid cluster b to add to the deployment module container set. At this time, the multiple containers included in the deployment module container set required to run the deployment module are container b4 included in grid cluster b in grid b and container a3 included in grid cluster a in grid a. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of deployment module 1, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids.

[0124] Example 5: Taking the example of the bootstrap module b selecting multiple containers in grid cluster b to add to an existing container (such as container a3) selected from grid cluster a, the bootstrap module b can select container b3 and container b4 in grid cluster b to add to the deployment module container set. At this time, the multiple containers included in the deployment module container set required to run the deployment module are container b3 and container b4 included in grid cluster b in grid b and container a3 included in grid cluster a in grid a. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), realizing the cross-grid cluster (i.e., across grid cluster a and grid cluster b) or cross-grid (i.e., across grid a and grid b) deployment of deployment module 1, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids.

[0125] In another possible implementation, after the bootstrap module b registers the cluster identifier b, grid identifier b, and API3 of the grid cluster b to the resource management platform, when the bootstrap module b queries the resource management platform that the deployment module has been deployed and the deployment module is deployed in multiple grids (each of the multiple grids has a grid cluster), the bootstrap module b can select one or more containers in the grid cluster b from the deployment module container set required to run the deployment module (such as deployment module 1), or the bootstrap module b can also select a container in the grid cluster b to replace any container in the deployment module container set, and the deployment module container set includes one or more containers selected from multiple grid clusters, or the bootstrap module b can also select multiple containers in the grid cluster b to replace any multiple containers in the deployment module container set.

[0126] Illustratively, another implementation process of the bootstrapping module b selecting one or more containers in the grid cluster b to be added to the deployment module container set or to replace containers included in the deployment module container set is described below through the following examples.

[0127] Example 1: Take the example of bootstrapping module b selecting a container in grid cluster b to replace one of the multiple containers selected from multiple grid clusters that already exist in the deployment module container set (such as container a3 included in grid cluster a in grid a, container c3 and container c4 included in grid cluster c in grid c). Bootstrapping module b can select container b4 in grid cluster b to add to the deployment module container set, and at the same time release any one of containers a3, c3 and c4 included in the deployment module container set required for running the deployment module, such as releasing container a3. At this time, the deployment module container set The multiple containers included in the container set are container b4 included in grid cluster b in grid b and container c3 and container c4 included in grid cluster c in grid c. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), thereby realizing the cross-grid cluster (i.e., across grid cluster b and grid cluster c) or cross-grid (i.e., across grid b and grid c) deployment of the deployment module 1. This ensures that the deployment module 1 has high availability characteristics across grid clusters or across grids, and ensures that the container capacity of the deployment module container set remains unchanged.

[0128] Example 2: Taking the example of the bootstrap module b selecting multiple containers in grid cluster b to replace any multiple containers selected in multiple grid clusters and already existing in the deployment module container set (such as container a3 included in grid cluster a in grid a, container c3 and container c4 included in grid cluster c in grid c) as an example, the bootstrap module b can select container b3 and container b4 in grid cluster b to add to the deployment module container set, and at the same time release any two of containers a3, container c3 and container c4 included in the deployment module container set required to run the deployment module. In one example, the bootstrap module b releases container a3 and container c3. At this time, the multiple containers included in the deployment module container set are container b3 and container b4 included in grid cluster b in grid b and container c4 included in grid cluster c in grid c. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), realizing the cross-grid cluster (i.e., across grid cluster b and grid cluster c) or cross-grid (i.e., across grid b and grid c) deployment of the deployment module 1. This can ensure that the deployment module 1 has high availability characteristics across grid clusters or across grids, and can ensure that the container capacity of the deployment module container set remains unchanged. In another example, the bootstrap module b releases container c3 and container c4. At this time, the multiple containers included in the deployment module container set are container b3 and container b4 included in grid cluster b in grid b and container a3 included in grid cluster a in grid a. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), realizing the cross-grid cluster (i.e., across grid cluster b and grid cluster a) or cross-grid (i.e., across grid b and grid a) deployment of the deployment module 1. This can ensure that the deployment module 1 has high availability characteristics across grid clusters or across grids, and can ensure that the container capacity of the deployment module container set remains unchanged.

[0129] Example 3: Taking the example of the bootstrap module b selecting a container in grid cluster b to add to the deployment module container set that already has multiple containers selected from multiple grid clusters (such as container a3 included in grid cluster a in grid a, container c3 and container c4 included in grid cluster c in grid c), the bootstrap module b can select container b4 in grid cluster b to add to the deployment module container set. At this time, the multiple containers included in the deployment module container set are container b4 included in grid cluster b in grid b, container a3 included in grid cluster a in grid a, and container c3 and container c4 included in grid cluster c in grid c. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), thereby realizing the cross-grid cluster (i.e., across grid cluster b, grid cluster a and grid cluster c) or cross-grid (i.e., across grid b, grid a and grid c) deployment of deployment module 1, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids.

[0130] Example 4: Taking the example of the bootstrap module b selecting multiple containers in grid cluster b to add to the deployment module container set that already has multiple containers selected from multiple grid clusters (such as container a3 included in grid cluster a in grid a, and container c3 and container c4 included in grid cluster c in grid c), the bootstrap module b can select container b3 and container b4 in grid cluster b to add to the deployment module container set. At this time, the multiple containers included in the deployment module container set are container b3 and container b4 included in grid cluster b in grid b, container a3 included in grid cluster a in grid a, and container c3 and container c4 included in grid cluster c in grid c. Afterwards, the bootstrap module b can select one or more containers in the deployment module container set to participate in the operation of the deployment module (such as deployment module 1), thereby realizing the cross-grid cluster (i.e., across grid cluster b, grid cluster a, and grid cluster c) deployment or cross-grid (i.e., across grid b, grid a, and grid c) deployment of deployment module 1, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids.

[0131] Step 303: After the second grid cluster is started, the second bootstrapping module manages the second grid cluster.

[0132] Optionally, the second bootstrap module is deployed in a second mesh cluster. The second bootstrap module may be run by one or more containers included in the second mesh cluster, and the second bootstrap module is automatically started when the second mesh cluster is started. The second mesh cluster may be one of at least one mesh cluster included in the cloud service system, excluding the first mesh cluster.

[0133] After the second bootstrap module is self-started, it can use the second grid cluster as the underlying resource pool required for deploying the load balancing service. In this way, the second grid cluster can be transformed into the underlying resource pool required for deploying the load balancing service through the bootstrap module with a small amount of resource consumption, so that the second bootstrap module can automatically manage the second grid cluster without manual intervention. This can solve the problem of high starting cost and high operation and maintenance pressure caused by the use of VM as the minimum load-bearing resource granularity of the load balancing service in the prior art, and can realize the automatic expansion of the underlying resource pool at the granularity of the grid cluster before the existing underlying resource pool is exhausted. Since each grid cluster is in a grid, it can be achieved while taking into account the high availability requirements of the load balancing service. In addition, the self-starting method of the second bootstrap module can effectively reduce the consumption of starting resources, thereby reducing the starting cost, and thus making the load balancing service deployment method provided in the embodiment of the present application adaptable to a variety of application scenarios (such as resource-constrained scenarios such as private clouds).

[0134] Optionally, after self-starting, the second bootstrap module may also register the attribute information of the second grid cluster with the resource management platform so that the resource management platform can maintain and manage the attribute information of the second grid cluster. Optionally, the second bootstrap module registers the attribute information of the second grid cluster with the resource management platform, which can also facilitate the subsequent deployment module to be able to obtain changes in the grid cluster included in the cloud service system through the resource management platform, so that the deployment module can automatically adjust or update the set of load balancing containers required for deploying the load balancing service according to the changes in the grid cluster included in the cloud service system, which helps to achieve the load balancing service meeting the requirements of disaster recovery and high availability in a self-operation and maintenance manner. The attribute information of the second grid cluster may include at least one of the following: the identifier of the grid where the second grid cluster is located, the cluster identifier of the second grid cluster, or the API of the second grid cluster, etc.

[0135] In addition, after the second bootstrap module is self-started, it queries the resource management platform for relevant information of the deployment module, and updates or adjusts the deployment module container set required for running the deployment module based on the queried relevant information of the deployment module. For example, the second bootstrap module can determine one or more seventh containers in the second grid cluster to add to the deployment module container set, or it can also determine one or more seventh containers in the second grid cluster to replace the containers included in the deployment module container set. After that, the second bootstrap module can determine one or more eighth containers in the deployment module container set to participate in running the deployment module. Optionally, the updated or adjusted deployment module can also be used to automatically update or adjust the deployment form of the load balancing service according to changes in the grid cluster included in the cloud service system.

[0136] In one possible implementation, when it is queried through the resource management platform that the deployment module container set only includes one container selected from the first grid cluster, the second bootstrap module can select one or more containers in the second grid cluster to add to the deployment module container set. At this time, the deployment module container set includes one or more containers selected from the second grid cluster and one container selected from the first grid cluster. In this way, the deployment module can be deployed across grid clusters or across grids, thereby ensuring that the deployment module has high availability characteristics across grid clusters or across grids.

[0137] In another possible implementation, when a query through the resource management platform finds that the deployment module container set includes multiple containers selected from the first grid cluster, the second bootstrap module can select one or more containers in the second grid cluster to add to the deployment module container set. At this time, the deployment module container set includes one or more containers selected from the second grid cluster and multiple containers selected from the first grid cluster. In this way, the deployment module can be deployed across grid clusters or across grids, thereby ensuring that the deployment module has high availability characteristics across grid clusters or across grids.

[0138] In another possible implementation, when a query through the resource management platform finds that the deployment module container set includes multiple containers selected from the first grid cluster, the second bootstrap module can select a container in the second grid cluster to replace any one of the multiple containers included in the deployment module container set. In this way, the deployment module can be deployed across grid clusters or across grids, thereby ensuring that the deployment module has high availability characteristics across grid clusters or across grids, and ensuring that the container capacity required to run the deployment module remains unchanged.

[0139] In another possible implementation, when a query through the resource management platform finds that the deployment module container set includes multiple containers selected from the first grid cluster, the second bootstrap module can select multiple containers in the second grid cluster to replace any multiple of the multiple containers included in the deployment module container set. In this way, the deployment module can be deployed across grid clusters or across grids, thereby ensuring that the deployment module has high availability characteristics across grid clusters or across grids, and ensuring that the container capacity required to run the deployment module remains unchanged.

[0140] Optionally, when a third mesh cluster is added to the cloud service system, a third bootstrap module deployed in the third mesh cluster can be automatically started when the third mesh cluster is started. The third bootstrap module can be run by one or more containers included in the third mesh cluster, which can be one of the at least one mesh cluster included in the cloud service system, excluding the first and second mesh clusters.

[0141] After the third bootstrap module is self-started, it can use the third grid cluster as the underlying resource pool required for deploying the load balancing service. In this way, the third grid cluster can be transformed into the underlying resource pool required for deploying the load balancing service through the bootstrap module with a small amount of resource consumption, so that the third bootstrap module can automatically manage the third grid cluster without manual intervention. This can solve the problem of high starting cost and high operation and maintenance pressure caused by the use of VM as the minimum load-bearing resource granularity of the load balancing service in the prior art, and can realize the automatic expansion of the underlying resource pool at the granularity of the grid cluster before the existing underlying resource pool is exhausted. Since each grid cluster is in a grid, it can be achieved while expanding the resource pool while taking into account the high availability requirements of the load balancing service. In addition, the self-starting method of the third bootstrap module can effectively reduce the consumption of starting resources, thereby reducing the starting cost, and thus making the load balancing service deployment method provided in the embodiment of the present application adaptable to a variety of application scenarios (such as resource-constrained scenarios such as private clouds).

[0142] After self-starting, the third bootstrap module can also register the attribute information of the third grid cluster with the resource management platform so that the resource management platform can maintain and manage the attribute information of the third grid cluster. Optionally, the third bootstrap module registers the attribute information of the third grid cluster with the resource management platform, which can also facilitate the subsequent deployment module to be able to obtain changes in the grid cluster included in the cloud service system through the resource management platform, so that the deployment module can automatically adjust or update the set of load balancing containers required for running the load balancing service according to the changes in the grid cluster included in the cloud service system, which helps to achieve the load balancing service meeting the requirements of disaster recovery and high availability in a self-operation and maintenance manner. The attribute information of the third grid cluster can include at least one of the following: the identifier of the grid where the third grid cluster is located, the cluster identifier of the third grid cluster, or the API of the third grid cluster, etc.

[0143] In addition, after self-starting, the third bootstrap module queries the resource management platform for relevant information of the deployment module, and updates or adjusts one or more containers used to run the deployment module based on the queried relevant information of the deployment module. Optionally, the updated or adjusted deployment module is used to automatically update or adjust the deployment form of the load balancing service based on changes in the grid cluster included in the cloud service system. Among them, the implementation method of the third bootstrap module updating or adjusting one or more containers used to run the deployment module can refer to the implementation method of the second bootstrap module updating or adjusting one or more containers used to run the deployment module, which will not be repeated here. Furthermore, the implementation method of the updated or adjusted deployment module selecting one or more containers in the third grid cluster to add to the load balancing container set or selecting one or more containers in the third grid cluster to replace the containers included in the load balancing container set can refer to the implementation methods described in the following implementation methods four and five, which will not be repeated here.

[0144] Step 304: The deployment module determines one or more second containers in the second grid cluster to add to the load balancing container set.

[0145] Optionally, when a second grid cluster is added to the cloud service system after the first grid cluster (in this case, the first grid cluster serves as the first underlying resource pool required for deploying the load balancing service) (i.e., a second resource pool is added, which serves as the second underlying resource pool required for deploying the load balancing service after the first resource pool), in one example, the deployment module selects one or more second containers in the second grid cluster to be added to the load balancing container set, and all second containers in the second grid cluster that have been added to the load balancing container set serve as second resource units for deploying the load balancing service, and the containers included in the second resource units are used to participate in the deployment of the load balancing service. Afterwards, the deployment module can provide the load balancing service externally (i.e., it can issue a load balancing service with cross-grid or cross-grid cluster characteristics to users who apply for the load balancing service). Then, when the deployment module receives a load balancing service deployment request from a user terminal device, it can determine a resource unit or several resource units in the load balancing container set to deploy the load balancing service, or it can select one or more containers in a resource unit to deploy the load balancing service, or it can select corresponding containers in different resource units to deploy the load balancing service, and can issue the deployed load balancing service to the user terminal device. The load balancing service deployment request is used to request the issuance of a load balancing service, and the second resource unit includes one or more containers.

[0146] In another example, the deployment module can pre-determine resource units in the load balancing container set for deploying the load balancing service, and after receiving a load balancing service deployment request from a user terminal device, distribute the deployed load balancing service with cross-grid or cross-grid cluster characteristics to the user terminal device.

[0147] When a second grid cluster is added to the cloud service system after the first grid cluster (the first grid cluster is a newly added resource pool located after the first underlying resource pool) (i.e., a second resource pool is added, and the second resource pool is another underlying resource pool required for deploying the load balancing service after the first resource pool), the deployment module selects one or more second containers in the second grid cluster to add to the load balancing container set, and the load balancing container set already contains one or more containers selected from other grid clusters, or the deployment module can also select one or more containers in the second grid cluster to replace the containers included in the load balancing container set. Afterwards, the deployment module can provide load balancing services to the outside (i.e., the deployment module can issue load balancing services with cross-grid or cross-grid cluster characteristics to users who apply for load balancing services). In one example, when the deployment module receives a load balancing service deployment request from a user terminal device, it can determine a resource unit or several resource units in the load balancing container set to deploy the load balancing service, or it can select one or more containers in a resource unit to deploy the load balancing service, or it can select corresponding containers in different resource units to deploy the load balancing service, and can issue the deployed load balancing service with cross-grid or cross-grid cluster characteristics to the user terminal device. The load balancing service deployment request is used to request the issuance of a load balancing service.

[0148] In another example, the deployment module may pre-determine a resource unit or several resource units in the load balancing container set to deploy the load balancing service, or may pre-select one or more containers in a resource unit to deploy the load balancing service, or may pre-select corresponding containers in different resource units to deploy the load balancing service, and after receiving a load balancing service deployment request from a user terminal device, the deployed load balancing service with cross-grid or cross-grid cluster characteristics is distributed to the user terminal device.

[0149] Illustratively, the following describes the implementation process of the deployment module selecting one or more second containers in the second grid cluster to participate in deploying the load balancing service through the following possible implementation methods.

[0150] Implementation Method 1: When a second grid cluster is used as the second underlying resource pool for deploying a load balancing service after a first grid cluster (in which case the first grid cluster serves as the first underlying resource pool for deploying a load balancing service), if the deployment module queries the resource management platform and finds that the set of load balancing containers required for participating in the deployment of the load balancing service only includes a first container selected from the first grid cluster, the deployment module may select one or more second containers from the second grid cluster to add to the set of load balancing containers. Alternatively, the deployment module may select a second container from the second grid cluster to replace a container included in the set of load balancing containers. In this case, the set of load balancing containers includes containers from both grid clusters. This allows the load balancing service provided by the deployment module to have high availability across grid clusters or grids. For example, when a grid cluster to which a container for running a load balancing service belongs fails, the deployment module may replace the container with any container in another grid cluster in the set of load balancing containers that is in normal operation to run the load balancing service. This means that the deployment module switches or migrates the load balancing service to another normal container for operation.

[0151] Implementation method 2: When the second grid cluster is used as the second underlying resource pool required for deploying the load balancing service after the first grid cluster (in this case, the first grid cluster is used as the first underlying resource pool required for deploying the load balancing service), if the deployment module queries through the resource management platform that the load balancing container set required for participating in the deployment of the load balancing service includes multiple first containers selected from the first grid cluster, then the deployment module can select one or more second containers in the second grid cluster to add to the load balancing container set, or the deployment module can also select a second container in the second grid cluster to replace the container included in the load balancing container set. At this time, the load balancing container set includes containers from two grid clusters. In this way, the load balancing service issued by the deployment module can have high availability characteristics across grid clusters or across grids.

[0152] Implementation method three: When the second grid cluster is used as the second underlying resource pool required for deploying the load balancing service after the first grid cluster (in this case, the first grid cluster is used as the first underlying resource pool required for deploying the load balancing service), if the deployment module queries through the resource management platform that the load balancing container set required for participating in the deployment of the load balancing service includes multiple first containers selected from the first grid cluster, then the deployment module can select a second container in the second grid cluster to replace any container in the load balancing container set, or the deployment module can also select multiple second containers in the second grid cluster to replace any multiple containers in the load balancing container set.

[0153] Implementation method four: When the second grid cluster is used as another underlying resource pool (such as the third resource pool or the fourth resource pool, etc.) required for deploying the load balancing service after the first grid cluster (in this case, the first grid cluster is a newly added resource pool located after the first underlying resource pool), if the deployment module queries through the resource management platform that the load balancing container set required for participating in the deployment of the load balancing service includes multiple containers selected from other multiple grid clusters, then the deployment module can select one or more second containers in the second grid cluster to add to the load balancing container set. At this time, the load balancing container set includes containers from multiple grid clusters. In this way, the load balancing service issued by the deployment module can have high availability characteristics across multiple grid clusters or across multiple grids.

[0154] Implementation method five: When the second grid cluster serves as another underlying resource pool (such as the third resource pool, the fourth resource pool, or the fifth resource pool, etc.) required for deploying the load balancing service after the first grid cluster (in this case, the first grid cluster serves as a newly added resource pool located after the first underlying resource pool), if the deployment module queries through the resource management platform that the load balancing container set required for participating in the deployment of the load balancing service includes multiple containers selected from multiple other grid clusters, then the deployment module can select a second container in the second grid cluster to replace any container in the load balancing container set, or the deployment module can also select multiple second containers in the second grid cluster to replace any multiple containers in the load balancing container set.

[0155] In addition, when a grid cluster to which a third container included in the set of load-balancing containers required for deploying a load-balancing service belongs fails, the deployment module can select a fourth container from the grid clusters to which other containers included in the set of load-balancing containers belong to replace the third container. In this way, when one or more grid clusters fail, the deployment module can automatically migrate the affected load-balancing service to other grid clusters, and the load-balancing service is run by one or more containers included in the other grid clusters, thereby ensuring that the availability of the load-balancing service is not affected. In addition, it should be noted that even if a large-scale resource pool suffers severe damage from wind, fire, water, electricity, etc., and only the underlying resource pool corresponding to one grid cluster is operating normally, the complete load-balancing service can be gradually restored and rebuilt through the bootstrapping module of the grid cluster.

[0156] Step 305: The deployment module receives a deployment request for deploying a load balancing service, and determines a resource unit in the load balancing container set to deploy the load balancing service.

[0157] Optionally, in one example, when the deployment module receives a deployment request for deploying a load balancing service from a user terminal device or other user device, it determines a certain resource unit (such as a first resource unit) or several resource units (such as a first resource unit and a second resource unit) in the load balancing container set to deploy the load balancing service, or it can also select one or more containers in a certain resource unit to deploy the load balancing service, or it can also select corresponding containers in different resource units to deploy the load balancing service, and the deployed load balancing service can be issued to the user terminal device or other user device. In another example, the deployment module can pre-determine a certain resource unit or several resource units in the load balancing container set to deploy the load balancing service, or it can pre-select one or more containers in a certain resource unit to deploy the load balancing service, or it can pre-select corresponding containers in different resource units to deploy the load balancing service, and when it receives a deployment request for deploying a load balancing service from a user terminal device or other user device, it can issue the deployed load balancing service to the user terminal device or other user device. In this way, the solution provided by the embodiment of the present application shields the operation details of the underlying resource pool from the outside (such as users or tenants who need to apply for load balancing services), but instead receives load balancing service deployment requests in the form of services and issues deployed and available load balancing services.

[0158] It should be noted that in the description of this application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, the ordinal numbers such as "first", "second", and "third" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects. In addition, the terms "including", "comprising", "having" and their variations appearing in this application all mean "including but not limited to" unless otherwise specifically emphasized.

[0159] In addition, it should be noted that each step involved in the above embodiments can be performed by a corresponding device, or by a component such as a chip, processor, or chip system within the device, and the embodiments of the present application do not limit this. The above embodiments are described only as examples of execution by corresponding devices.

[0160] It should be noted that in each of the above embodiments, some steps may be selected for implementation, and the order of the steps in the diagrams may be adjusted for implementation, and this application does not limit this. It should be understood that executing some of the steps in the diagrams, adjusting the order of the steps, or combining them for specific implementation all fall within the scope of protection of this application.

[0161] It is understandable that in order to implement the functions in the above embodiments, the various devices involved in the above embodiments include hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of the various examples described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0162] It should be noted that the "steps" in the embodiments of this application are merely illustrative and serve as a method of expression for a better understanding of the embodiments. They do not constitute a substantial limitation on the execution of the solutions of this application. For example, the "steps" can also be understood as "features." Furthermore, the steps do not constitute any limitation on the execution order of the solutions of this application. Any changes to the order of steps, or any operations such as step merging or splitting that do not affect the implementation of the overall solution, resulting in new technical solutions, are also within the scope of this application.

[0163] Based on the same concept, the embodiment of the present application also provides a possible computing device for executing the load balancing service deployment method illustrated in the above method embodiment. The relevant features can be found in the above method embodiment and will not be repeated here. As shown in Figure 5, the computing device 500 includes: a bus 501, a processor 502, a communication interface 503 and a memory 504. The processor 502, the communication interface 503 and the memory 504 communicate with each other via the bus 501. The computing device 500 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 500.

[0164] Bus 501 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG5 shows only one bus line, but this does not imply a single bus or type of bus. Bus 501 may include a path for transmitting information between various components of computing device 500 (e.g., memory 504, processor 502, and communication interface 503).

[0165] The processor 502 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0166] The memory 504 may include volatile memory, such as random access memory (RAM). The processor 502 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0167] The memory 504 stores executable program code, and the processor 502 executes the executable program code to implement the functions of the aforementioned load balancing service deployment device (e.g., the first bootstrapping module, the second bootstrapping module, and the deployment module), thereby implementing the load balancing service deployment method provided in the embodiments of the present application. In other words, the memory 504 stores computer program instructions for executing the load balancing service deployment method.

[0168] Alternatively, the memory 504 stores executable code, and the processor 502 executes the executable code to implement the functions of the aforementioned load balancing service deployment device (e.g., the first bootstrapping module, the second bootstrapping module, and the deployment module), thereby implementing the load balancing service deployment method provided in the embodiments of the present application. That is, the memory 504 stores computer program instructions for the load balancing service deployment device to execute the load balancing service deployment method provided in the embodiments of the present application.

[0169] The communication interface 503 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 500 and other devices or a communication network.

[0170] Based on the same concept, the embodiment of the present application also provides a possible computing device cluster for executing the method shown in the above method embodiment. The relevant features can be found in the above method embodiment and will not be repeated here. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0171] As shown in Figure 6, the computing device cluster includes at least one computing device 500. The memory 504 in one or more computing devices 500 in the computing device cluster may store the same instructions for executing the load balancing service deployment method provided in the embodiment of the present application.

[0172] In some possible implementations, the memory 504 of one or more computing devices 500 in the computing device cluster may also store partial instructions for executing the load balancing service deployment method. In other words, the combination of one or more computing devices 500 can jointly execute the instructions for executing the load balancing service deployment method.

[0173] It should be noted that the memory 504 in different computing devices 500 in the computing device cluster can store different instructions, each for executing a portion of the functions of the load balancing service deployment apparatus. In other words, the instructions stored in the memory 504 in different computing devices 500 can implement the functions of one or more of the first bootstrapping module, the second bootstrapping module, and the deployment module.

[0174] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network, which may be a wide area network or a local area network.

[0175] Based on the same concept, embodiments of the present application also provide a computer program product containing instructions. The computer program product can be software or a program product containing instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to execute the load balancing service deployment method provided in embodiments of the present application.

[0176] Based on the same concept, an embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the load balancing service deployment method provided in the embodiment of the present application.

[0177] Based on the same concept, an embodiment of the present application also provides a computer chip, which is coupled to a memory and is used to read a computer program stored in the memory and execute the load balancing service deployment method provided in the embodiment of the present application.

[0178] Based on the same concept, an embodiment of the present application also provides a chip system, which includes a processor for supporting a computer device to implement the load balancing service deployment method provided in an embodiment of the present application. In one possible design, the chip system also includes a memory for storing the necessary programs and data for the computer device. The chip system can be composed of a computer chip, or it can include a computer chip and other discrete devices.

[0179] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A load balancing service deployment method, characterized in that: The method is used to deploy a load balancing service on a cloud computing resource, wherein the cloud computing resource includes one or more servers in a data center, and the cloud computing resource is used to deploy a grid cluster including multiple containers; the method includes: Deploy a first grid cluster, determine one or more first containers in the first grid cluster to add to the load balancing container set, and use all first containers in the first grid cluster that have been added to the load balancing container set as first resource units for deploying the load balancing service; Deploy a second grid cluster, determine one or more second containers in the second grid cluster to add to the load balancing container set, and use all second containers in the second grid cluster that have been added to the load balancing container set as second resource units for deploying the load balancing service; Receive a deployment request for deploying a load balancing service; A resource unit is determined in the load balancing container set to deploy a load balancing service.

2. The method according to claim 1, characterized in that The method further comprises: Determining in the first grid cluster that the one or more first containers are used to replace containers included in the load balancing container set; and / or The one or more second containers are determined in the second grid cluster to replace containers included in the load balancing container set.

3. The method according to claim 1 or 2, characterized in that The method further comprises: When a grid cluster to which a third container included in the load balancing container set belongs fails, a fourth container is selected from grid clusters to which other containers included in the load balancing container set belong to replace the third container.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: When there is a new container included in the load balancing container set, the deployment form of the load balancing service is updated.

5. The method according to any one of claims 1 to 4, characterized in that: After the first grid cluster is deployed, the method further includes: Registering the attribute information of the first grid cluster to a resource management platform; After the second grid cluster is deployed, the method further includes: registering the attribute information of the second grid cluster to the resource management platform; After determining resource units in the load balancing container set to deploy the load balancing service, the method further includes: Registering the attribute information of the load balancing service to the resource management platform.

6. The method according to claim 5, characterized in that The attribute information of the first grid cluster or the second grid cluster includes at least one of the following: a cluster identifier, an application programming interface API, or an identifier of a grid where the grid cluster is located; The attribute information of the load balancing service includes at least one of the following: an identifier of the load balancing service, an Internet Protocol IP address, a blast radius, or an identifier of a grid cluster participating in the deployment or operation of the load balancing service, wherein the blast radius is used to characterize the high availability of the load balancing service, and the blast radius is determined based on the number of grid clusters participating in the deployment or operation of the load balancing service.

7. A load balancing service deployment device, characterized in that: The apparatus is used to deploy a load balancing service on a cloud computing resource, the cloud computing resource comprising one or more servers in a data center, and the cloud computing resource is used to deploy a grid cluster comprising a plurality of containers; The device comprises: A first bootstrap module is used to manage the first grid cluster after the first grid cluster is started; all first containers in the first grid cluster that have been added to the load balancing container set are used as first resource units for deploying the load balancing service; A deployment module, configured to determine one or more first containers in the first grid cluster to add to the load balancing container set; A second bootstrap module is used to manage the second grid cluster after the second grid cluster is started, and all second containers in the second grid cluster that have been added to the load balancing container set are used as second resource units for deploying the load balancing service; The deployment module is further used to determine one or more second containers in the second grid cluster to add to the load balancing container set; The deployment module is further configured to receive a deployment request for deploying a load balancing service, and to determine a resource unit in the load balancing container set to deploy the load balancing service.

8. The device according to claim 7, characterized in that The deployment module is further used to determine in the first grid cluster that the first container is used to replace the container included in the load balancing container set; and / or The deployment module is further configured to determine in the second grid cluster that the second container is used to replace a container included in the load balancing container set.

9. The device according to claim 7 or 8, characterized in that The deployment module is also used to: When a grid cluster to which a third container included in the load balancing container set belongs fails, a fourth container is selected from grid clusters to which other containers included in the load balancing container set belong to replace the third container.

10. The device according to any one of claims 7 to 9, characterized in that: The deployment module is also used to: When there is a new container included in the load balancing container set, the deployment form of the load balancing service is updated.

11. The device according to any one of claims 7 to 10, characterized in that: When the first grid cluster is started, the first bootstrap module is further used for: Registering the attribute information of the first grid cluster to a resource management platform; When the second grid cluster is started, the second bootstrap module is further used for: Registering the attribute information of the load balancing service to the resource management platform; After the deployment module determines the resource units in the load balancing container set to deploy the load balancing service, it is further used to: Registering the attribute information of the load balancing service to the resource management platform.

12. The device according to claim 11, characterized in that The attribute information of the first grid cluster or the second grid cluster includes at least one of the following: a cluster identifier, an application programming interface API, or an identifier of a grid where the grid cluster is located; The attribute information of the load balancing service includes at least one of the following: an identifier of the load balancing service, an Internet Protocol IP address, a blast radius, or an identifier of a grid cluster participating in the deployment or operation of the load balancing service, wherein the blast radius is used to characterize the high availability of the load balancing service, and the blast radius is determined based on the number of grid clusters participating in the deployment or operation of the load balancing service.

13. The device according to claim 12, characterized in that The resource management platform is also used to maintain the attribute information of the deployment module.

14. The device according to any one of claims 11 to 13, characterized in that: The deployment module is also used to monitor changes in the grid cluster included in the cloud service system through the resource management platform, and update the deployment form of the load balancing service according to the changes in the grid cluster included in the cloud service system.

15. The device according to any one of claims 11 to 14, characterized in that: After the first grid cluster is started, the first bootstrap module is further used for: Determining one or more fifth containers in the first grid cluster to add to the deployment module container set; Determine one or more sixth containers in the deployment module container set for participating in running the deployment module; After the second grid cluster is started, the second bootstrap module is further used for: Determining one or more seventh containers in the second grid cluster to add to the deployment module container set; One or more eighth containers are determined in the deployment module container set to participate in running the deployment module.

16. The device according to any one of claims 11 to 14, characterized in that After the first grid cluster is started, the first bootstrap module is further used for: Determining, in the first grid cluster, one or more fifth containers for replacing containers included in the deployment module container set; Determine one or more sixth containers in the deployment module container set for running the deployment module; After the second grid cluster is started, the second bootstrap module is further used for: Determining, in the second grid cluster, one or more seventh containers for replacing containers included in the deployment module container set; One or more eighth containers are determined in the deployment module container set for running the deployment module.

17. A computing device, characterized in that The computing device includes a processor and a memory; The memory is used to store computer program instructions; The processor calls the computer program instructions stored in the memory to execute the method according to any one of claims 1 to 6.

18. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device includes a processor and a memory; the memory in the at least one computing device is used to store computer program instructions; The processor in the at least one computing device calls the computer program instructions stored in the memory to execute the method according to any one of claims 1 to 6.

19. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device, the computing device performs the method according to any one of claims 1 to 6.

20. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device, the computing device is caused to perform the method as claimed in any one of claims 1 to 6.

Citation Information

Patent Citations

  • Multi-cluster management method and system, server and storage medium

    CN111405055A

  • Load balancing method, system and device

    CN113783922A

  • Cloud computing resource scheduling method and device, equipment and medium

    CN115065685A

  • Management for a load balancer cluster

    US20210281637A1