Load balancing service deployment method and device
By using grid cluster and container technology in cloud service systems, efficient deployment and high availability of load balancing services are achieved, the problems of low resource utilization and high operation and maintenance pressure in the existing technology are solved, and the load balancing services are improved Performance and reliability.
Patent Information
- Application Number
- CN202310609179.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-26
- Publication Date
- 2024-11-26
AI Technical Summary
The low resource utilization rate of load balancing services in existing cloud computing leads to high operation and maintenance pressure and high cost, and is difficult to meet high availability requirements.
By using grid clusters in cloud service systems to deploy load balancing services, using containers as the minimum granular resource allocation unit, automatically managing grid clusters, and deploying load balancing services across disaster recovery between multiple grid clusters, Achieve high availability.
It improves resource utilization, reduces operation and maintenance pressure and costs, and ensures high availability of load balancing services and cross-grid cluster disaster recovery capabilities.
Smart Images

Figure CN119025254A_ABST
Abstract
Description
Technical Field
[0001] 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
[0002] 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.
[0003] Traditional load balancing services have multiple implementations. For example, one implementation is based on network hardware devices, such as F5. Another implementation is based on physical machines and virtual machines through software, such as Linux Virtual Server (LVS), Domain Name Server (DNS) polling, HAProxy or Nginx. Optionally, load balancing services can be divided based on network layers, generally divided into 4-layer load balancing and 7-layer load balancing.
[0004] For example, taking the public cloud as an example, the current mainstream public clouds all provide load balancing services based on software, such as 4-layer LVS or 7-layer Nginx, HAProxy, etc. Among them, the mainstream public clouds use virtual machines (VM) or bare metal to carry the load balancing resource pool, and provide multi-tenant capabilities to the outside world through VMs of different specifications and different numbers. However, since the load balancing service (or load balancer) is the basic service of the public cloud, almost all tenants rely on the load balancing service to build their own services on the public cloud, so the number of VMs occupied by the load balancing service of the public cloud continues to rise, and the number of VMs occupied reaches 30% or even higher. Although the specifications of these VMs are generally small, when considering the overhead of the guest operating system (Guest Operating System, Guest OS), this method of deploying load balancing services with VMs of different specifications as the minimum granularity resource allocation unit will still have the problem of coarse resource granularity, which will lead to low resource utilization. Summary of the invention
[0005] 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.
[0006] 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, and 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 determine one or more first containers in the first grid cluster to add to the load balancing container set after deploying the first grid cluster, 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 for deploying 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 are used 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 are used as second resource units for deploying the load balancing service.
[0007] 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 with containers as the smallest granularity of resource allocation units, so that resource utilization can be improved. In addition, since the method determines the corresponding containers from multiple grid clusters to join the load balancing container set, and the containers included in the load balancing container set are used to participate in the deployment of load balancing services, the issued load balancing services can have high availability characteristics for cross-grid cluster disaster recovery, thereby ensuring that the issued load balancing services meet 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.
[0008] In one possible design, the method further includes:
[0009] Determining one or more first containers in the first grid cluster for replacing containers included in the load balancing container set and / or,
[0010] One or more second containers are determined in the second grid cluster to replace the containers included in the load balancing container set.
[0011] 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.
[0012] In one possible design, the method further includes:
[0013] A third grid cluster is deployed, and one or more tenth containers are determined in the third grid cluster to be added to the load balancing container set, or one or more tenth containers are determined in the third grid cluster to replace containers included in the load balancing container set.
[0014] In the above design, after the deployment of the third grid cluster, the third grid cluster is automatically managed, and the corresponding container 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.
[0015] In one possible design, the method further includes:
[0016] 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.
[0017] 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 other grid clusters can participate in running the load balancing service, thereby ensuring that the availability of the load balancing service is not affected.
[0018] In one possible design, the method further includes:
[0019] When a new container is included in the load balancing container set, the deployment state of the load balancing service is updated.
[0020] 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 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.
[0021] In one possible design, after the first grid cluster is deployed, the method further includes:
[0022] Registering the attribute information of the first grid cluster to the resource management platform;
[0023] After the second grid cluster is deployed, the method further includes:
[0024] registering the attribute information of the second grid cluster to the resource management platform;
[0025] After determining resource units in the load balancing container set to deploy the load balancing service, the method further includes:
[0026] Register the attribute information of the load balancing service to the resource management platform.
[0027] 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 is convenient for the resource management platform to be maintained in a timely manner, and it is convenient for the requests submitted by users or tenants applying for load balancing services to accurately reach the corresponding deployment module, and it is convenient for the deployment module to understand the changes of the grid cluster in a timely manner.
[0028] 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 a grid where the grid cluster is located;
[0029] 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 involved in deploying or running 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 involved in deploying or running the load balancing service.
[0030] In a second aspect, an embodiment of the present application provides a load balancing service deployment device, and the beneficial effects can be found in the description of the first aspect, which will not be repeated here. The load balancing service deployment device has the function of implementing the behavior in the method example of the first aspect. The load balancing service deployment device is used to deploy a load balancing service in a cloud computing resource, and the cloud computing resource includes one or more servers in the data, and the cloud computing resource is used to deploy a grid cluster including multiple containers. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the device includes a first bootstrap module, a second bootstrap module and a deployment module. The first bootstrap module is used for the first bootstrap module to manage the first grid cluster after the first grid cluster is started, and all the first containers in the first grid cluster that have been added to the load balancing container set are used as the first resource unit for deploying the load balancing service. The deployment module is used to determine one or more first containers in the first grid cluster to join the load balancing container set. The second bootstrap module is used for managing the second grid cluster after the second grid cluster is started, and all the second containers in the second grid cluster that have been added to the load balancing container set are used as the second resource unit 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 used to receive a deployment request for deploying a load balancing service, and determine a resource unit 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 above, and refer to the detailed description in the method example for details, which will not be repeated here.
[0031] 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.
[0032] 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 necessary computer program instructions and data for the load balancing service deployment device. Any computing device also includes a communication interface for communicating with other devices.
[0033] 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 a method in any possible design of the first aspect above.
[0034] 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.
[0035] 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 to execute a method in any possible design of the first aspect above.
[0036] In an eighth aspect, an embodiment of the present application further provides a chip system, which includes a processor for supporting a computer device to implement the method in any possible design of the first aspect. In one possible design, the chip system also includes a memory, which is used to store the necessary programs and data of the computer device. The chip system can be composed of a computer chip, or it can include a computer chip and other discrete devices.
[0037] Based on the implementations provided in the above aspects, this application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] Figure 1 A schematic diagram of a possible application scenario provided by an embodiment of the present application is exemplified;
[0039] Figure 2 A schematic diagram showing the functional module structure of a load balancing service deployment device provided in an embodiment of the present application is exemplified;
[0040] Figure 3 A schematic diagram showing an exemplary process of a load balancing service deployment method provided in an embodiment of the present application;
[0041] Figure 4a A schematic diagram showing the related operations of a bootstrap module a after startup provided by an embodiment of the present application is exemplified;
[0042] Figure 4b A schematic diagram of related operations of a deployment module 1 after startup provided by an embodiment of the present application is exemplified;
[0043] Figure 4c A schematic diagram showing, by way of example, that a deployment module updates or adjusts the deployment form of a load balancing service 01 when a new grid cluster b is added to a cloud service system provided in an embodiment of the present application;
[0044] Figure 4d A schematic diagram exemplarily shows that when a grid cluster b is added to a cloud service system provided by an embodiment of the present application, a bootstrap module b updates or adjusts the deployment form of a deployment module 1;
[0045] Figure 5 A schematic diagram showing a possible structure of a computing device provided by an embodiment of the present application is exemplified;
[0046] Figure 6 A schematic diagram of the structure of a possible computing device cluster provided in an embodiment of the present application is exemplified. DETAILED DESCRIPTION
[0047] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.
[0048] The following introduces possible application scenarios to which the load balancing service deployment method provided by the present application is applicable. It should be noted that these introductions are for the convenience of understanding by those skilled in the art and do not constitute a limitation on the scope of protection claimed by the present application.
[0049] Figure 1 The following is a schematic diagram of a possible application scenario to which the present application embodiment is applicable. Figure 1As shown, 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 (FailureDomain) 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 is the grid clusters, not the cloud computing resources. Each grid cluster includes at least one container, and the at least one container included in each grid cluster can be run on a physical host (or called a physical server, a cloud server, a physical computer or a computing device, etc.), or can also be 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. Exemplarily, a grid can refer to an AZ with independent wind, fire, water and electricity. In addition, 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.
[0050] 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 are specifically 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, users who need load balancing services (such as tenants who need load balancing services) 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 (Application Program Interface, API) corresponding to the cloud service system 110 for issuing load balancing services 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. The load balancing service is used to evenly distribute multiple cloud service requests (such as access requests) to different processing devices for processing. For example, a website owned by a certain user has multiple servers corresponding to processing access requests to the website. In order to balance the pressure of processing access requests on each server, the user can apply for a load balancing service, which is used to uniformly receive access requests to the website and evenly distribute the received access requests to the corresponding servers.
[0051] 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 according to the number of grid clusters involved in deploying or running the load balancing service. Exemplarily, the explosion radius R satisfies the following form:
[0052] R=1 / N
[0053] Where N is used to represent the number of grid clusters involved in deploying or running the load balancing service.
[0054] 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.
[0055] 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.
[0056] Exemplarily, taking a tenant (such as tenant A) as an example, tenant A accesses the resource management platform 100 through the terminal device used (such as a smart phone, tablet computer or laptop computer, etc.) and submits a load balancing service deployment request, which is used to request the issuance of a load balancing service. In a 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 the terminal device of tenant A.
[0057] 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 the load balancing service deployment request to the corresponding load balancing service deployment device through 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.
[0058] Optionally, in one example, the load balancing service may 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 may select one or more containers from the first grid cluster in grid 10 to join the load balancing container set, and then the load balancing service deployment device may select one or more containers from the load balancing container set to deploy the load balancing service. Exemplarily, for example, the load balancing service deployment device selects container 11, container 12, container 13, etc. from the first grid cluster to join the load balancing container set, and container 11, container 12, container 13, etc. are used 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 may select container 11 or container 12 or container 13 from the load balancing container set to deploy the load balancing service, or may select two containers (such as container 11 and container 12) from the load balancing container set to deploy the load balancing service, or may select three or more containers from the load balancing container set to deploy the load balancing service, and the embodiments of the present application are not limited to this.
[0059] 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 select one or more containers in the second resource unit in the load balancing container set together 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, and the embodiments of the present application are not limited to this.
[0060] It should be noted that Figure 1 Only one possible application scenario is provided schematically, which is intended to more clearly illustrate the technical solution of the embodiment of the present application, and does not limit the application scenario of the load balancing service deployment method provided by the present application. Figure 1 The form and quantity of each device in the application scenario shown are only for example and do not constitute a limitation of the present application. Figure 1 The names of the various devices in the application scenario shown are only examples, and the names of the various devices in the specific implementation may also be other names, which are not specifically limited in this application. 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 solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0061] As described in the background technology, the existing solutions have the problem of low resource utilization in the process of deploying load balancing services. In addition, as the number of cloud tenants and cloud applications continues to increase, the operation and maintenance pressure and cost of the existing solutions will also be relatively large. In view of this, the present application provides a load balancing service deployment method to effectively solve the problems of low resource utilization, high operation and maintenance pressure and cost in the existing technology, and can realize the load balancing service to meet the high availability characteristics.
[0062] based on Figure 1 In the application scenario shown in the figure, the present application also provides a functional module structure of a load balancing service deployment device. Figure 2 , divided according to logical functions, the load balancing service deployment device can be divided into the following functional modules: at least one bootstrap module (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 by a container included in the first grid cluster, or it can also be run by several containers included in the first grid cluster, or it can also be run by any one or more of the multiple containers selected in the first grid cluster, which 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 also be run by two containers (such as container 11 and container 12) included in the first grid cluster, or it can also be run by three or more containers included in the first grid cluster, or it can also 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 is not limited to 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, which can be understood as setting the second bootstrap module in the second grid cluster. For example, the second bootstrap module can be run by container 21, container 22, container 23, or container 24 included in the second grid cluster, or it can be run by two containers (such as container 21 and container 22) included in the second grid cluster, or it can be run 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 the multiple containers (such as container 21, container 22, container 23) selected in the second grid cluster, and the embodiment of the present application is not limited to this.
[0063] It should be noted that Figure 2 The connection relationship between the various functional modules shown is only an example and does not constitute a limitation of the present application. The functions of each functional module are described below.
[0064] The first bootstrap module is used to self-start when the first grid cluster is started, 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 the first bootstrap module is self-started, the attribute information of the first grid cluster (such as grid identification, cluster identification or API, etc.) is registered to the resource management platform 100. In another example, the first bootstrap module can execute another processing flow: after the first bootstrap module is self-started, it manages the first grid cluster, such as using the first grid cluster as the first resource pool required for deploying load balancing services. Exemplarily, a resource pool may include multiple hosts (Host), and one or more containers are running on each host. Optionally, a resource pool may be in an AZ, and a resource pool may include all containers running in an AZ.
[0065] The second bootstrap module is used to start up when the second grid cluster starts up, and automatically execute the corresponding processing flow after starting up. For example, in one example, the second bootstrap module can execute a processing flow: after starting up, the second bootstrap module registers the attribute information (such as grid identifier, cluster identifier or API, etc.) of the second grid cluster to the resource management platform 100. In another example, the second bootstrap module can execute another processing flow: after starting up, the second bootstrap module manages the second grid cluster, such as using the second grid cluster as a second resource pool required for deploying a load balancing service.
[0066] 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 be used as a resource unit for running the deployment module, and then start the deployment module.
[0067] The deployment module is responsible for the deployment and issuance of load balancing services.
[0068] Exemplarily, continuing to take tenant A as an example, in a possible implementation, when 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 issue the load balancing service to the terminal device of tenant A. Among them, the load balancing service deployment request is used to request the issuance of a load balancing service.
[0069] In another possible implementation, when 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 send the API of the deployment module responsible for issuing the load balancing service to the terminal device of tenant A. After receiving the API of the deployment module, the terminal device of tenant A can send a load balancing service deployment request to the corresponding deployment module through the API. 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 issue the load balancing service to the terminal device of tenant A.
[0070] 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 may register the attribute information of the deployment module (such as the deployment module's identifier, API, or the number of grids used to run the deployment module (that is, which grids the deployment module spans), etc.) to the resource management platform 100. Thereafter, the deployment module may select one or more containers from the first resource pool (i.e., the first grid cluster) corresponding to grid 10 to add to the load balancing container set. The one or more containers serve as resource units for deploying the load balancing service, and may 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.
[0071] 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 the self-startup. Optionally, in addition to automatically executing the processing flow described in the two related examples in the second bootstrap module mentioned above, the second bootstrap module can also automatically execute another processing flow: when the second bootstrap module queries in the resource management platform 100 that the deployment module 120 is only deployed in a single grid 10, the second bootstrap 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 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, and one or more containers in the second grid cluster that have been added to the deployment module container set can be used as another resource unit for running the deployment module, wherein the deployment module container set already has one or more containers selected from the first resource pool. Afterwards, the second bootstrap module can run the deployment module in one resource unit or several resource units, or can also select corresponding containers in different resource units to run the deployment module, thereby achieving high-availability deployment of the deployment module across grids. Exemplarily, taking the case where there are two containers (such as container 11 and container 12) for running the deployment module in the first grid cluster, in one possible implementation, in order to ensure that the container capacity required for running the deployment module remains unchanged, the second bootstrap module may select a container (such as container 21) in 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 bootstrap module may also select one or more containers in the second resource pool to add to the deployment module container set, and then may select one or more containers in the deployment module container set to participate in running the deployment module.
[0072] 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 one 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, thereby achieving high-availability deployment of the load balancing service across grids. Exemplarily, taking the case where there are two containers (such as container 13 and container 14) for deploying a load balancing service in the first grid cluster, in one possible implementation, in order to ensure that the container capacity required for deploying the load balancing service remains unchanged, the deployment module may 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 in 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 may 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 may select one or several resource units in the load balancing container set to deploy the load balancing service, or may select corresponding containers in different resource units to deploy the load balancing service.
[0073] Optional, above Figure 2 The first bootstrap module, the second bootstrap module and the deployment module shown in the figure can all be implemented by software, or can all be implemented by hardware. Exemplarily, the implementation of the deployment module is introduced below by taking 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, which will not be repeated here.
[0074] When implemented by software, the deployment module is used as an example of a software functional unit, and the deployment module can be an application or code block running on a computer device. Among them, 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 (region) or in different regions. Among them, usually a region can include multiple AZs.
[0075] Similarly, multiple hosts / virtual machines / containers for running 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.
[0076] When implemented by hardware, the deployment module is used as an example of a hardware functional unit, and the deployment module may include at least one computing device, such as a server, etc. Alternatively, the deployment module may also be a device implemented by 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.
[0077] The multiple computing devices included in the deployment module can be distributed in the same AZ or in different AZs. The multiple computing devices included in the deployment module can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the deployment module can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.
[0078] It should be noted that the steps that the first bootstrap module, the second bootstrap module and the deployment module are responsible for implementing can be specified as needed. 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 the full functions of the load balancing service deployment device.
[0079] In addition, it should be noted that the division of modules in the embodiments of the present application is schematic, which is only a logical function division, and there may be other division methods in actual implementation. Each functional module in the embodiments of the present application can be integrated into one module, or each module can exist physically separately, 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.
[0080] The following is based on Figure 1 The application scenarios and Figure 2 The functional module structure of the load balancing service deployment device shown in the figure provides a detailed introduction to the specific implementation of the load balancing service deployment method in the embodiment of the present application.
[0081] Figure 3 A schematic diagram showing a flow chart of a load balancing service deployment method provided in an embodiment of the present application is shown as an example. The method is applicable to Figure 1 The application scenario shown. The method process 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 the embodiment of the present application, the first bootstrap module, the second bootstrap module and the deployment module included in the load balancing service deployment device are taken as an example to introduce the process of executing the load balancing service deployment method by the first bootstrap module, the second bootstrap module and the deployment module. Figure 3 As shown, the method includes:
[0082] Step 301: After the first grid cluster is started, the first bootstrap module manages the first grid cluster.
[0083] Optionally, the first bootstrap module is deployed in the 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.
[0084] After the first bootstrap module is self-started, the first grid cluster can be used 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 with a small amount of resource consumption through the bootstrap module, so that the first bootstrap module can automatically manage the first grid cluster without manual intervention, thereby solving the problem of high starting cost and high operation and maintenance pressure caused by using VM as the minimum bearing resource granularity of the load balancing service in the prior art. In addition, the self-starting method of the first 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).
[0085] Optionally, after the first bootstrap module is self-started, it can also register the attribute information of the first grid cluster to the resource management platform so that the resource management platform can maintain and manage the attribute information of the first grid cluster. Optionally, exemplarily, the first bootstrap module registers the attribute information of the first grid cluster to the resource management platform, which can also facilitate the subsequent deployment module to be able to learn about the changes in the grid cluster included in the cloud service system through the resource management platform, so that the deployment module can automatically adjust 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. The attribute information of the first grid cluster may include at least one of the following: the identifier of the grid where the first grid cluster is located, the cluster identifier of the first grid cluster, or the API of the first grid cluster, etc.
[0086] For example, in one example, the first grid cluster is an 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. Figure 4a As shown, the bootstrap module a can be run by one or more containers included in the grid cluster a in the 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), then the bootstrap module a can be run by any one of container a1 and container a2, or can be run by container a1 and container a2 together. For example, taking the bootstrap module container set including two containers selected from the grid cluster (such as container a1 and container a2) as an example, when the grid cluster a is started, the bootstrap module a is self-started along with the start of the grid cluster a, and after self-starting, the cluster identifier a of the grid cluster a, the grid identifier a and the API1 of the grid cluster a are registered to the resource management platform. In addition, after self-starting, the bootstrap module a can turn the grid cluster a into the first underlying resource pool required to deploy the load balancing service.
[0087] Step 302: The deployment module determines one or more first containers in the first grid cluster to add to the load balancing container set.
[0088] Optionally, when the first grid cluster is the first grid cluster required for deploying the load balancing service, in one example, the deployment module can determine one or more first containers in the first grid cluster to join the load balancing container set, and all first containers added to the load balancing container set in the first grid cluster can be used as the first resource unit for deploying the load balancing service, and the container included in the first resource unit is used to participate in the deployment of the load balancing service. Afterwards, the deployment module can provide load balancing services to the outside (that is, the deployment module can issue a load balancing service with single grid or single grid cluster characteristics to users who apply for load balancing services). 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 also 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.
[0089] 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, distribute the deployed load balancing service with single grid or single grid cluster characteristics to the user terminal device.
[0090] In addition, when a new grid cluster (i.e., a new resource pool, such as the second underlying resource pool required for deploying the load balancing service) is added to the cloud service system after the first grid cluster (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, in which one or more containers selected from the first grid cluster already exist, 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.
[0091] When the first grid cluster is a newly added grid cluster 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 has 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 according to 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 an 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, the already deployed load balancing service with cross-grid or cross-grid cluster characteristics can be issued to the user terminal device. Among them, the load balancing service deployment request is used to request the issuance of a load balancing service.
[0092] 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 can select one or more containers in a resource unit to deploy the load balancing service, or 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.
[0093] Exemplarily, the following describes the implementation process of the deployment module selecting one or more first containers in the first grid cluster to participate in the deployment of the load balancing service through the following possible implementation methods.
[0094] 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.
[0095] In addition, when the first grid cluster is the initial grid cluster in the cloud service system, in one example, the first bootstrap module can start the deployment module (such as deployment module 1) that has been selected to run one or more containers in the first resource pool after changing the first grid cluster to the first underlying resource pool required for deploying the load balancing service. In another example, the first bootstrap module can also select one or more containers in the first grid cluster for running the deployment module (such as deployment module 1) and start the deployment module.
[0096] For example, Figure 4b The deployment module 1 shown is taken as an example of two containers (such as container a3 and container a4) contained in the first grid cluster (such as grid cluster a). When the bootstrap module a uses the grid cluster a as the underlying resource pool required for deploying the load balancing service, after the deployment module 1 is started, the attribute information of the deployment module 1 (such as the deployment module identifier 1, API2 and grid identifier a) can be registered to the resource management platform. At this time, the 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 the grid cluster a to add to the load balancing container set. After that, the deployment module 1 can deploy the load balancing service according to the load balancing container set.
[0097] In a possible implementation, the deployment module 1 may deploy a load balancing service (such as load balancing service 01 or load balancing service 02) in advance. For example, the deployment module 1 may select two containers (such as container a5 and container a6) in the grid cluster a and add them to the load balancing container set. Then, the deployment module 1 may select any one of container a5 and container a6 in the load balancing container set to deploy the load balancing service 01, or may select container a5 and container a6 together in the load balancing container set to deploy the load balancing service 01, or the deployment module 1 may select two containers (such as container a7 and container a8) in the grid cluster a and add them to the load balancing container set. Then, the deployment module 1 may select any one of container a7 and container a8 in the load balancing container set to deploy the load balancing service 02, or may select container a7 and container a8 together in the load balancing container set to deploy the load balancing service 02. Then, after receiving a load balancing service deployment request sent by tenant A through a terminal device, the deployment module 1 may provide a load balancing service to the outside, such as issuing the deployed load balancing service 01 or load balancing service 02 to tenant A. At this time, the deployment module 1 can also register the attribute information of the load balancing service 01 (such as the load balancing service identifier 01, IP address, explosion radius 1 and grid identifier a) to the resource management platform.
[0098] 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, and the load balancing service deployment request is used to request the issuance of the load balancing service. After that, the resource management platform can send the API1 of the deployment module responsible for issuing the load balancing service to the terminal device of tenant A after receiving the load balancing service deployment request. Then, the terminal device of tenant A can send the 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 the terminal device of tenant A.
[0099] In another possible implementation, after receiving a load balancing service deployment request sent from tenant A through a terminal device, deployment module 1 may select one or more containers in the load balancing container set for deploying the load balancing service, and may issue the deployed load balancing service to tenant A. For example, taking the existence of container a5 and container a6 in the load balancing container set as an example, deployment module 1 may select container a5 and container a6 in the load balancing container set to run load balancing service 01 together, or may select any one of container a5 and container a6 in the load balancing container set to deploy load balancing service 01. Afterwards, deployment module 1 may issue load balancing service 01 to tenant A's terminal device. When a new grid cluster is added to the cloud service system, after 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.
[0100] In another possible implementation, after receiving the load balancing service deployment request sent from tenant B through the terminal device, the deployment module 1 can select one or more containers in the load balancing container set for deploying the load balancing service, and can issue the deployed load balancing service to tenant B. For example, taking the existence of container a7 and container a8 in the load balancing container set as an example, the deployment module 1 can select container a7 and container a8 in the load balancing container set to run the load balancing service 02 together, or can also select any one of container a7 and container a8 in the load balancing container set to deploy the load balancing service 02. Optionally, after receiving the load balancing service deployment request sent from tenant B through the terminal device, the deployment module 1 can also select multiple containers (such as container a7 and container a8) in the grid cluster a to add to the load balancing container set, and then the deployment module 1 can select container a7 and container a8 in the load balancing container set to run the load balancing service 02 together, or can also select any one of container a7 and container a8 in the load balancing container set to deploy the load balancing service 02. Then, the deployment module 1 can issue the load balancing service 02 to the terminal device of tenant B. When a new grid cluster is added to the cloud service system, after 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.
[0101] 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, and then the deployment module can select one or more containers in the load balancing container set for deploying the load balancing service.
[0102] 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 the 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 other grid clusters 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 other grid clusters that already exist in the load balancing container set.
[0103] For example, the solution provided by the above implementation method 2 and implementation method 3 is introduced by taking the initial grid cluster (such as grid cluster a) existing before the first grid cluster in the cloud service system as an example. Figure 4c As shown, when a first grid cluster (such as grid cluster b) is added to the cloud service system, the bootstrap module b of grid cluster b is self-started when grid cluster b is started, and after self-starting, the cluster identifier b, grid identifier b and API3 of grid cluster b are registered to the resource management platform. At this time, 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, the bootstrap module container set includes two containers selected from grid cluster b (such as container b1 and container b2), then the bootstrap module b can be run by any one of container b1 and container b2, or it can also be run by container b1 and container b2 together. Based on this, when the deployment module 1 detects the addition of a grid cluster b in the cloud service system through the resource management platform, one or more containers can be selected in grid cluster b to be added to the load balancing container set, and one or more containers selected from grid cluster a already exist in the load balancing container set. Optionally, the deployment module 1 may also select one or more containers in the grid cluster b to replace the containers included in the load balancing container set, such as the deployment module 1 selects a container in the grid cluster b to replace any container selected in the grid cluster a and already existing in the load balancing container set, or may also select multiple containers in the grid cluster b to replace any multiple containers selected in the grid cluster a and already existing in the load balancing container set. Then, the deployment module 1 may deploy the load balancing service according to the load balancing container set, such as the load balancing container set includes container a6 in the grid cluster a and container b5 in the grid cluster b, and the deployment module 1 may select one or more containers in the load balancing container set (such as any one of container a6 and container b5, or a combination of container a6 and container b5) for deploying the 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, explosion radius 2 and grid identifier a) to the resource management platform.
[0104] Exemplarily, the following examples introduce 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.
[0105] Example 1: Taking the example that the deployment module 1 selects a container in grid cluster b to replace one of the multiple containers (such as container a5 and container a6) selected in grid cluster a and existing in the load balancing container set, the deployment module 1 can select container b5 in grid cluster b to add to the running container of the load balancing service 01, and at the same time release any one of the containers a5 and 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. The 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), thereby realizing the cross-grid cluster (i.e., cross-grid cluster a and grid cluster b) deployment or cross-grid (i.e., cross-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, and ensuring that the container capacity of the running load balancing container set remains unchanged.
[0106] Example 2: Taking the example that 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 selected from grid cluster a (such as container a5 and container a6), 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 to deploy 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) deployment 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.
[0107] Example 3: Taking the example that the deployment module 1 selects multiple containers in grid cluster b and adds them to the load balancing container set, and the load balancing container set already contains multiple containers selected from grid cluster a (such as container a5 and container a6), the 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. The 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 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 the load balancing service 01, thereby ensuring that the load balancing service 01 has high availability characteristics across grid clusters or across grids.
[0108] Example 4: Taking the example that 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 to deploy 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 5: Taking the example that the deployment module 1 selects multiple containers in grid cluster b and adds them 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 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. The 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 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.
[0110] 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, and then the first bootstrap module can determine one or more sixth containers in the deployment module container set to participate in running the deployment module.
[0111] 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.
[0112] 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.
[0113] Mode 2: 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 one or more containers in the first grid cluster to add to the deployment module container set.
[0114] 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.
[0115] For example, the solution provided by the above-mentioned method 1, method 2 and method 3 is introduced by continuing to take the case where there is an initial grid cluster (such as grid cluster a) before the first grid cluster in the cloud service system as an example. Figure 4dAs shown, when a first grid cluster (for example, grid cluster b) is added to the cloud service system, the bootstrap module b of grid cluster b starts automatically when grid cluster b starts, and after self-starting, the cluster identifier b, grid identifier b and API 3 of grid cluster b are registered to the resource management platform. At this time, grid cluster b becomes another underlying resource pool required for deploying load balancing services.
[0116] In a possible implementation, after the bootstrap module b registers the cluster identifier b, the grid identifier b and the API 3 of the grid cluster b to the resource management platform, when the bootstrap module b inquires in the resource management platform that the deployment module has been deployed and the deployment module is only deployed in the grid a, the bootstrap module b can select one or more containers in the grid cluster b to add to the deployment module container set, and the deployment module container set already has one or more containers selected from the grid cluster a, or the bootstrap module b can also select one or more containers in the grid cluster b to replace the containers included in the deployment module container set, for example, the bootstrap module b can also select a container in the grid cluster b to replace any one of the containers in the deployment module container set, 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. 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).
[0117] Exemplarily, the following examples introduce an implementation process of the bootstrap module b selecting one or more containers in the grid cluster b to add to the deployment module container set or to replace the containers included in the deployment module container set.
[0118] Example 1: Taking the example of 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, 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 container a3 and container 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, 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) 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, and ensuring that the container capacity of the deployment module container set remains unchanged.
[0119] Example 2: Taking the example of 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), 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, bootstrap module b can select one or more containers in the deployment module container set to participate in the running of the deployment module (such as deployment module 1), thereby 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.
[0120] Example 3: Taking the example of bootstrap module b selecting multiple containers in grid cluster b to add to the deployment module container set that already has multiple containers (such as container a3 and container a4) selected from grid cluster a, 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, bootstrap module b can select one or more containers in the deployment module container set to participate in the running of the deployment module (such as deployment module 1), thereby 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.
[0121] Example 4: Taking the example of 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, 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, bootstrap module b can select one or more containers in the deployment module container set to participate in the running of 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, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids.
[0122] Example 5: Taking the example of 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, 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, bootstrap module b can select one or more containers in the deployment module container set to participate in the running of the deployment module (such as deployment module 1), thereby 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.
[0123] 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.
[0124] Exemplarily, 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 the containers included in the deployment module container set is introduced below through the following examples.
[0125] Example 1: Taking the example that the bootstrap module b selects a container in the grid cluster b to replace one of the multiple containers selected from the multiple grid clusters that already exist in the deployment module container set (such as the container a3 included in the grid cluster a in the grid a, and the container c3 and the container c4 included in the grid cluster c in the grid c), the bootstrap module b can select the container b4 in the grid cluster b to add to the deployment module container set, and at the same time release any one of the containers a3, c3 and c4 included in the deployment module container set required for running the deployment module, such as releasing the 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, 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 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 deployment module 1, thereby ensuring that deployment module 1 has high availability characteristics across grid clusters or across grids, and ensuring that the container capacity of the deployment module container set remains unchanged.
[0126] Example 2: Taking the example of 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), 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), 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 deployment module 1. This ensures that 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. 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), thereby 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 deployment module 1. This ensures that 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.
[0127] Example 3: Taking the example of bootstrap module b selecting a container in grid cluster b to add to a 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), 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, 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.
[0128] Example 4: Taking the example of bootstrap module b selecting multiple containers in grid cluster b to add to a 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), 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, 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.
[0129] Step 303: After the second grid cluster is started, the second bootstrap module manages the second grid cluster.
[0130] Optionally, the second bootstrap module is deployed in the second grid cluster, the second bootstrap module may be run by one or more containers included in the second grid cluster, and the second bootstrap module is automatically started when the second grid cluster is started. The second grid cluster may be one of the at least one grid cluster included in the cloud service system except the first grid cluster.
[0131] After the second bootstrap module is self-started, the second grid cluster can be used 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, thereby solving the problems of high starting cost and high operation and maintenance pressure caused by using VM as the minimum 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 that the high availability requirements of the load balancing service can be taken into account while expanding the resource pool. In addition, the self-starting mode 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).
[0132] Optionally, after the second bootstrap module is self-started, it can also register the attribute information of the second grid cluster to 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 to the resource management platform, which can also facilitate the subsequent deployment module to learn about the 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 in a self-operated and maintained manner to meet the requirements of disaster tolerance and high availability. The attribute information of the second grid cluster can 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.
[0133] In addition, after the second bootstrap module is self-started, it queries the relevant information of the deployment module in the resource management platform, and updates or adjusts the deployment module container set required for running the deployment module based on the relevant information of the deployment module that has been queried. 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, and then 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.
[0134] 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, cross-grid cluster deployment or cross-grid deployment of the deployment module can be achieved, thereby ensuring that the deployment module has high availability characteristics across grid clusters or across grids.
[0135] In another possible implementation, when it is queried through the resource management platform 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, cross-grid cluster deployment or cross-grid deployment of the deployment module can be achieved, thereby ensuring that the deployment module has high availability characteristics across grid clusters or across grids.
[0136] In another possible implementation, when it is queried through the resource management platform 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, cross-grid cluster deployment or cross-grid deployment of the deployment module can be achieved, 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.
[0137] In another possible implementation, when it is queried through the resource management platform 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.
[0138] Optionally, when a third grid cluster is added to the cloud service system, a third bootstrap module deployed in the third grid cluster may be automatically started when the third grid cluster is started. The third bootstrap module may be run by one or more containers included in the third grid cluster, and the third grid cluster may be one of at least one grid cluster included in the cloud service system except the first grid cluster and the second grid cluster.
[0139] After the third bootstrap module is self-started, the third grid cluster can be used 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, thereby solving the problem of high starting cost and high operation and maintenance pressure caused by using VM as the minimum bearing resource granularity of the load balancing service in the prior art, and realizing 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 is possible to achieve the high availability requirements of the load balancing service while expanding the resource pool. In addition, the self-starting mode 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).
[0140] After the third bootstrap module is self-started, it can also register the attribute information of the third grid cluster to 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 to the resource management platform, which can also facilitate the subsequent deployment module to learn about the 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 load balancing container set 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 in a self-operated and maintained manner to meet the requirements of disaster tolerance and high availability. 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.
[0141] In addition, after the third bootstrap module is self-started, it queries the relevant information of the deployment module in the resource management platform, and updates or adjusts one or more containers used to run the deployment module according to the relevant information of the deployment module queried. Optionally, the updated or adjusted deployment module is used to automatically update or adjust the deployment form of the load balancing service according to the 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.
[0142] Step 304: The deployment module determines one or more second containers in the second grid cluster to add to the load balancing container set.
[0143] Optionally, when a second grid cluster is added to the cloud service system after the first grid cluster (the first grid cluster is used as the first underlying resource pool required for deploying the load balancing service), in one example, the deployment module selects one or more second containers in the second grid cluster to join the load balancing container set, and all second containers added to the load balancing container set in the second grid cluster are used as the 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. After that, the deployment module can provide load balancing services to the outside (that is, it can issue load balancing services with cross-grid or cross-grid cluster characteristics to users who apply for load balancing services). Then, when the deployment module receives a load balancing service deployment request from a user terminal device, it can determine a certain resource unit or several resource units 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. 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.
[0144] In another example, the deployment module may 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.
[0145] 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 after the first underlying resource pool), the deployment module selects one or more second containers in the second grid cluster to join the load balancing container set, and the load balancing container set already has 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. After that, the deployment module can provide load balancing services to the outside (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 an example, when the deployment module receives a load balancing service deployment request from a user terminal device, it can determine a certain resource unit or several resource units 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 with cross-grid or cross-grid cluster characteristics can be issued to the user terminal device. The load balancing service deployment request is used to request the issuance of a load balancing service.
[0146] 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.
[0147] Exemplarily, the following describes the implementation process of the deployment module selecting one or more second containers in the second grid cluster to participate in the deployment of the load balancing service through the following possible implementation methods.
[0148] Implementation method 1: 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 (at this time, 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 only includes a first container 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 of 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. For example, when the grid cluster to which the container used to run a certain load balancing service belongs fails, the deployment module can replace the container with any container in other grid clusters that are in normal operation in the load balancing container set to run the load balancing service. It can be understood that the deployment module switches or migrates the load balancing service to other containers that are running normally for operation.
[0149] 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 (at this time, 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 of two grid clusters, so that the load balancing service issued by the deployment module can have high availability characteristics across grid clusters or across grids.
[0150] 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 (at this time, 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.
[0151] 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 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 of multiple grid clusters, so that the load balancing service issued by the deployment module can have high availability characteristics across multiple grid clusters or across multiple grids.
[0152] Implementation method five: When the second grid cluster is used 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 is a resource pool newly added 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, 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] In addition, when the grid cluster to which the third container included in the load balancing container set required for deploying the load balancing service belongs fails, the deployment module can select a fourth container in the grid cluster to which other containers included in the load balancing container set 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 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 is severely damaged by wind, fire, water, electricity, etc., and only the underlying resource pool corresponding to one grid cluster is left to operate normally, the complete load balancing service can be gradually restored and rebuilt through the bootstrap module of the grid cluster.
[0154] 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.
[0155] 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, 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) is determined in the load balancing container set to deploy the load balancing service, or one or more containers may be selected in a certain resource unit to deploy the load balancing service, or corresponding containers may be selected in different resource units to deploy the load balancing service, and the deployed load balancing service may be issued to the user terminal device or other user device. In another example, the deployment module may pre-determine a certain resource unit or several resource units in the load balancing container set to deploy the load balancing service, or one or more containers may be selected in a certain resource unit to deploy the load balancing service, or corresponding containers may be selected in different resource units to deploy the load balancing service, and when a deployment request for deploying a load balancing service is received from a user terminal device or other user device, the already deployed load balancing service may be issued 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.
[0156] It should be noted that in the description of the present application, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there may be three relationships, for example, A and / or B, which can represent: the situation where A exists alone, A and B exist at the same time, and B exists alone, wherein A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are an "or" relationship. "At least one of the following (individuals)" or its similar expression refers to any combination of these items, including any combination of single items (individuals) or plural items (individuals). 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 the present 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 the present application all mean "including but not limited to", unless otherwise specifically emphasized in other ways.
[0157] In addition, it should be noted that each step involved in the above embodiments can be performed by a corresponding device, or by a chip, processor, or chip system in the device, and the embodiments of the present application do not limit them. The above embodiments are only described by taking the corresponding device as an example.
[0158] It should be noted that in the above embodiments, some steps can be selected for implementation, and the order of the steps in the diagram can be adjusted for implementation, and this application does not limit this. It should be understood that executing some steps in the diagram, adjusting the order of the steps, or combining them for specific implementation all fall within the scope of protection of this application.
[0159] 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 the various functions. It should be easily appreciated by 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.
[0160] It should be noted that the "steps" in the embodiments of the present application are only for illustration, and are a method of expression used to better understand the embodiments, and do not constitute a substantial limitation on the execution of the scheme of the present application. For example, the "steps" can also be understood as "features". In addition, the steps do not constitute any limitation on the execution order of the scheme of the present application. Any changes in the order of steps, step merging, or step splitting made on this basis that do not affect the implementation of the overall scheme, and the resulting new technical solutions are also within the scope of the disclosure of the present application.
[0161] Based on the same concept, the present application embodiment also provides a possible computing device for executing the load balancing service deployment method shown in the above method embodiment. The relevant features can be found in the above method embodiment and will not be repeated here. Figure 5 As shown, computing device 500 includes: bus 501, processor 502, communication interface 503 and memory 504. Processor 502, communication interface 503 and memory 504 communicate with each other through bus 501. 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 computing device 500.
[0162] The bus 501 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The bus 501 is represented by only one line, but it does not mean that there is only one bus or one type of bus. The bus 501 may include a path for transmitting information between various components of the computing device 500 (for example, the memory 504, the processor 502, and the communication interface 503).
[0163] The processor 502 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).
[0164] The memory 504 may include a volatile memory, such as a random access memory (RAM). The processor 502 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).
[0165] The memory 504 stores executable program codes, and the processor 502 executes the executable program codes to respectively implement the functions of the aforementioned load balancing service deployment device (such as the first bootstrap module, the second bootstrap module, and the deployment module), thereby implementing the load balancing service deployment method provided in the embodiment of the present application. That is, the memory 504 stores computer program instructions for executing the load balancing service deployment method.
[0166] 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 (such as the first bootstrap module, the second bootstrap module, and the deployment module), thereby implementing the load balancing service deployment method provided in the embodiment 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 embodiment of the present application.
[0167] 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.
[0168] 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, which 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, a laptop, or a smart phone.
[0169] like Figure 6 As shown, 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.
[0170] 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 may jointly execute instructions for executing the load balancing service deployment method.
[0171] It should be noted that the memory 504 in different computing devices 500 in the computing device cluster can store different instructions, which are respectively used to execute part of the functions of the load balancing service deployment device. That is, the instructions stored in the memory 504 in different computing devices 500 can implement the functions of one or more modules among the first bootstrap module, the second bootstrap module, and the deployment module.
[0172] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network.
[0173] Based on the same concept, an embodiment of the present application also provides a computer program product including instructions. The computer program product may be a software or program product including 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, the at least one computing device executes the load balancing service deployment method provided in the embodiment of the present application.
[0174] 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 containing 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 hard disk). 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.
[0175] 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 to execute the load balancing service deployment method provided in an embodiment of the present application.
[0176] 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, which is used to store the necessary programs and data of the computer device. The chip system can be composed of a computer chip, or it can include a computer chip and other discrete devices.
[0177] 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 it. 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 cause the essence of the corresponding technical solutions to deviate 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, 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.
