Cloud management platform-based gateway instance configuration method, and cloud management platform

Abstract

The present application discloses a cloud management platform-based gateway instance configuration method, and a cloud management platform, capable of improving tenant experience. The method of the present application comprises: when a tenant needs to configure a gateway instance group thereof, the tenant may send an anti-affinity deployment request for the gateway instance group to a deployment interface provided by a cloud management platform. Therefore, the cloud management platform may create, on the basis of the anti-affinity deployment request, a first gateway instance and a second gateway instance comprised in the gateway instance group, wherein the first gateway instance and the second gateway instance enable the tenant to access an application of the tenant. The first gateway instance may be constructed from a plurality of first cloud instances deployed in a first fault domain, and the second gateway instance may be constructed from a plurality of second cloud instances deployed in a second fault domain. Because the first fault domain and the second fault domain are different fault domains, an anti-affinity deployment is formed between the first gateway instance and the second gateway instance.

Description

A gateway instance configuration method based on a cloud management platform and the cloud management platform

[0001] The present application claims priority to the Chinese patent application No. 202411345871.7, filed on September 25, 2024, and entitled "A gateway instance configuration method based on a cloud management platform and the cloud management platform", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of cloud technology, in particular to a gateway instance configuration method based on a cloud management platform and the cloud management platform. BACKGROUND

[0003] With the rapid development of cloud technology, more and more tenants choose to deploy their applications in the cloud to complete their business requirements through cloud services provided by cloud vendors. Based on this, the gateway instance provided by the cloud vendor serves as a communication bridge between the tenant and the application running in the cloud, and the reliability and stability of the gateway instance affect the quality of the cloud services provided by the cloud vendor for the tenant.

[0004] In the related art, when the tenant deploys its application in the cloud, the tenant usually chooses to create a gateway instance serving the tenant at the same time, and the cloud vendor can create multiple gateway instances for the tenant. Among them, these gateway instances created by the cloud vendor for the tenant are essentially logical units, each gateway instance is built based on multiple cloud instances, so each gateway instance has certain specifications and network performance, thereby enabling the tenant to access its application deployed in the cloud.

[0005] In the above process, since the cloud vendor may cause multiple gateway instances of the tenant to occupy the same part of the cloud instances, once these cloud instances fail, the multiple gateway instances will be simultaneously unavailable, causing the tenant to be unable to stably access its application, and further causing the quality of the cloud services provided by the cloud vendor for the tenant to be poor. SUMMARY

[0006] Embodiments of the present application provide a gateway instance configuration method based on a cloud management platform and the cloud management platform, which can stably ensure that the gateway instance group successfully accesses the tenant's application, thereby improving the quality of the cloud services provided by the cloud vendor for the tenant to a certain extent, and further improving the tenant's experience.

[0007] The first aspect of the embodiments of the present application provides a gateway instance configuration method based on a cloud management platform, and the cloud management platform used to implement the method can manage the infrastructure providing cloud services for the tenant. These infrastructures include a cloud instance cluster, which can include a large number of cloud instances. The method comprises:

[0008] When the tenant needs to create a gateway instance group that is exclusive to the tenant, the cloud management platform can provide a deployment interface to the tenant. Then, the tenant can input a reverse affinity deployment request for the gateway instance group set by the tenant to the deployment interface, which is used to indicate the first gateway instance and the second gateway instance included in the gateway instance group of the tenant. In this way, the cloud management platform can receive the reverse affinity deployment request sent by the tenant through the deployment interface.

[0009] After obtaining the reverse affinity deployment request, the cloud management platform can create the first gateway instance and the second gateway instance by using the cloud instances in the cloud instance cluster, and the tenant can subsequently access the application of the tenant through the first gateway instance and the second gateway instance. The first gateway instance can include a plurality of first cloud instances arranged in a first fault domain in the cloud instance cluster, the second gateway instance can include a plurality of second cloud instances arranged in a second fault domain in the cloud instance cluster, and the application of the tenant can run a third cloud instance in the cloud instance cluster. It should be noted that the first fault domain and the second fault domain can be any one of a region, an availability zone, a data center, a machine room, and a physical server group.

[0010] As can be seen from the above method, because the first fault domain and the second fault domain are different fault domains, the first gateway instance arranged in the first fault domain and the second gateway instance arranged in the second fault domain form fault isolation, that is, the first gateway instance and the second gateway instance form reverse affinity deployment. If a certain first cloud instance included in the first gateway instance fails, it will not affect the normal operation of the second gateway instance, so that the gateway instance group of the tenant can stably ensure that the tenant successfully accesses the application of the tenant, thereby improving the quality of the cloud service provided by the cloud vendor for the tenant to a certain extent, and further improving the experience of the tenant.

[0011] In one possible implementation manner, the method further includes: if there is a failed first cloud instance among the plurality of first cloud instances in the first gateway instance, the cloud management platform removes the failed first cloud instance from the first gateway instance. In the foregoing implementation manner, the cloud management platform can also perform real-time fault monitoring on the first gateway instance and the second gateway instance. If the cloud management platform finds that there is a failed first cloud instance among the plurality of first cloud instances included in the first gateway instance, the cloud management platform removes the failed first cloud instance from the first gateway instance, so that the remaining first cloud instances in the first gateway instance are all non-failed first cloud instances. As can be seen, the cloud management platform can remove the failed first cloud instance from the first gateway instance in real time, thereby ensuring the stable operation of the first gateway instance, which is equivalent to ensuring that the tenant can stably access the application, and further ensuring the stable business of the tenant.

[0012] In a possible implementation, the anti-affinity deployment request further indicates a performance requirement of the first gateway instance, and the method further includes: if the sum of the performances of the remaining first cloud instances in the first gateway instance does not meet the performance requirement of the first gateway instance, the cloud management platform selects a first cloud instance to be added from the cloud instance cluster based on a difference between the sum of the performances and the performance requirement, and adds the first cloud instance to be added to the first gateway instance, where the remaining first cloud instances and the first cloud instance to be added are both first cloud instances that do not have a fault. In the foregoing implementation, after the first cloud instance having a fault is removed from the first gateway instance, if the cloud management platform determines that the sum of the performances of the remaining first cloud instances in the first gateway instance does not meet the performance requirement of the first gateway instance, the cloud management platform selects a first cloud instance to be added from the cloud instance cluster based on a difference between the sum of the performances of the remaining first cloud instances and the performance requirement of the first gateway instance, and adds the first cloud instance to be added to the first gateway instance, so as to improve the overall performance of the first gateway instance, and enable the first gateway instance to provide stable and high-quality network services for the tenant.

[0013] In a possible implementation, the anti-affinity deployment request further indicates a specification requirement of the first gateway instance, and the sum of the specifications of the plurality of first cloud instances meets the specification requirement of the first gateway instance. In the foregoing implementation, since the anti-affinity deployment request can also be used to indicate the specification requirement of the first gateway instance and the specification requirement of the second gateway instance, the sum of the specifications of the plurality of first cloud instances selected by the cloud management platform from the cloud instance cluster can meet the specification requirement of the first gateway instance, and similarly, the sum of the specifications of the plurality of second cloud instances selected by the cloud management platform from the cloud instance cluster can meet the specification requirement of the second gateway instance.

[0014] In a possible implementation, the first gateway instance and the second gateway instance are used to enable the tenant to access the application of the tenant, including: the cloud management platform receives an access request for the application of the tenant sent by the tenant; the cloud management platform selects the first gateway instance from the first gateway instance and the second gateway instance based on the access request, and selects one of the plurality of first cloud instances in the first gateway instance; and the cloud management platform instructs the first cloud instance to send the access request to a third cloud instance running the application. In the foregoing implementation, when the tenant needs to access the application, the tenant can send an access request for the application to the cloud management platform. Then, the cloud management platform can select the first gateway instance from the first gateway instance and the second gateway instance. Since the first gateway instance includes a plurality of first cloud instances, the cloud management platform can select one of the plurality of first cloud instances, and instruct the first cloud instance to send the access request to a third cloud instance running the application, so that the application processes the access request, thereby meeting the business requirement of the tenant.

[0015] In a possible implementation, when the first cloud instances and the second cloud instances are virtual machines, containers or micro virtual machines, and the first failure domain and the second failure domain are physical server groups, the physical server group where the first failure domain is located and the physical server group where the second failure domain is located contain a same physical server. In the foregoing implementation, when the first cloud instances included in the first gateway instance and the second cloud instances included in the second gateway instance are virtual machines, containers or micro virtual machines, and the first failure domain where the first gateway instance is located and the second failure domain where the second gateway instance is located are physical server groups, the physical server group where the first failure domain is located and the physical server group where the second failure domain are located can contain a same physical server, that is, a first cloud instance of the first cloud instances and a second cloud instance of the second cloud instances can be deployed on the same physical server, and the physical server belongs to both the first failure domain and the second failure domain. The remaining first cloud instances and the remaining second cloud instances are deployed on different physical servers in the first failure domain and the second failure domain.

[0016] In a possible implementation, the first cloud instances and the second cloud instances include any one of the following: physical servers, virtual machines, containers, micro virtual machines or bare metal servers.

[0017] The second aspect of the embodiment of the application provides a cloud management platform, which is used for managing an infrastructure providing a cloud service for a tenant, and the infrastructure includes a cloud instance cluster. The cloud management platform includes: a receiving module, configured to receive, through a deployment interface, an anti-affinity deployment request for a gateway instance group sent by the tenant, the anti-affinity deployment request being used to indicate a first gateway instance and a second gateway instance included in the gateway instance group; and a creating module, configured to create the first gateway instance and the second gateway instance based on the anti-affinity deployment request, the first gateway instance and the second gateway instance being used to enable the tenant to access an application of the tenant, wherein the first gateway instance includes a plurality of first cloud instances in the cloud instance cluster, the second gateway instance includes a plurality of second cloud instances in the cloud instance cluster, and the application runs in a third cloud instance in the cloud instance cluster; the plurality of first cloud instances are arranged in a first failure domain, the plurality of second cloud instances are arranged in a second failure domain, the first failure domain and the second failure domain are different failure domains, and the first failure domain and the second failure domain are any one of the following: a region, an availability zone, a data center, a machine room or a physical server group.

[0018] In a possible implementation, the cloud management platform further includes an excluding module, configured to exclude a failed first cloud instance from the first gateway instance if the plurality of first cloud instances in the first gateway instance include the failed first cloud instance.

[0019] In a possible implementation, the anti-affinity deployment request further indicates a performance requirement of the first gateway instance, and the cloud management platform further includes an adding module configured to: if a sum of performances of the remaining first cloud instances in the first gateway instance does not meet the performance requirement of the first gateway instance, select a first cloud instance to be added from the cloud instance cluster based on a difference between the sum of performances and the performance requirement, and add the first cloud instance to be added to the first gateway instance, where the remaining first cloud instances and the first cloud instance to be added are both first cloud instances that have not failed.

[0020] In a possible implementation, the anti-affinity deployment request further indicates a specification requirement of the first gateway instance, and a sum of specifications of the plurality of first cloud instances meets the specification requirement of the first gateway instance.

[0021] In a possible implementation, the creating module is configured to: receive an access request for an application of the tenant sent by the tenant; select the first gateway instance from the first gateway instance and the second gateway instance based on the access request, and select one of the plurality of first cloud instances in the first gateway instance; and notify the first cloud instance to send the access request to a third cloud instance running the application.

[0022] In a possible implementation, when the plurality of first cloud instances and the plurality of second cloud instances are virtual machines, containers, or micro virtual machines, and the first failure domain and the second failure domain are physical server groups, the physical server group where the first failure domain is located and the physical server group where the second failure domain is located include a same physical server.

[0023] In a possible implementation, the plurality of first cloud instances and the plurality of second cloud instances include any one of the following: a physical server, a virtual machine, a container, a micro virtual machine, or a bare metal server.

[0024] A third aspect of the embodiment of the present application provides a computing device cluster, the computing device cluster including at least one computing device, each computing device including a processor and a memory: the memory is configured to store instructions; and the processor is configured to execute the method according to the instructions, so that the computing device cluster executes the method in the first aspect or any possible implementation manner of the first aspect.

[0025] A fourth aspect of the embodiment of the present application provides a computer storage medium, the computer storage medium storing one or more instructions, the instructions causing one or more computers to implement the method in the first aspect or any possible implementation manner of the first aspect when executed by the one or more computers.

[0026] The fifth aspect of the embodiments of the present application provides a computer program product, the computer program product stores instructions, when the instructions are executed by a computer, the computer implements the method in the first aspect or any possible implementation manner of the first aspect.

[0027] In the embodiments of the present application, when a tenant needs to configure a gateway instance group, the tenant can send an anti-affinity deployment request for the gateway instance group to a deployment interface provided by the cloud management platform, so that the cloud management platform can create a first gateway instance and a second gateway instance included in the gateway instance group based on the anti-affinity deployment request. The first gateway instance and the second gateway instance can be used by the tenant to access the application of the tenant. The first gateway instance can be constructed by a plurality of first cloud instances, the second gateway instance can be constructed by a plurality of second cloud instances, and the plurality of first cloud instances included in the first gateway instance are arranged in a first fault domain, and the plurality of second cloud instances included in the second gateway instance are arranged in a second fault domain. Since the first fault domain and the second fault domain are different fault domains, the first gateway instance arranged in the first fault domain and the second gateway instance arranged in the second fault domain form fault isolation, that is, the first gateway instance and the second gateway instance form anti-affinity deployment. If a certain first cloud instance included in the first gateway instance fails, it will not affect the normal operation of the second gateway instance, so that the gateway instance group of the tenant can stably ensure that the tenant successfully accesses the application of the tenant, thereby improving the quality of the cloud service provided by the cloud vendor for the tenant to a certain extent, and further improving the experience of the tenant. BRIEF DESCRIPTION OF DRAWINGS

[0028] FIG. 1 is a structural schematic diagram of a cloud service system provided by an embodiment of the present application;

[0029] FIG. 2 is another structural schematic diagram of a cloud service system provided by an embodiment of the present application;

[0030] FIG. 3 is a flow schematic diagram of a gateway instance configuration method based on a cloud management platform provided by an embodiment of the present application;

[0031] FIG. 4 is another structural diagram of a cloud service system provided by an embodiment of the present application;

[0032] FIG. 5 is another structural diagram of a cloud service system provided by an embodiment of the present application;

[0033] FIG. 6 is another structural diagram of a cloud service system provided by an embodiment of the present application;

[0034] FIG. 7 is a structural schematic diagram of a cloud management platform provided by an embodiment of the present application;

[0035] FIG. 8 is a structural schematic diagram of a computing device provided by an embodiment of the present application;

[0036] FIG. 9 is a structural schematic diagram of a computing device cluster according to an embodiment of the present application;

[0037] FIG. 10 is a schematic diagram of a network connection of computer devices in a computer cluster according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] The embodiments of the present application provide a gateway instance configuration method based on a cloud management platform and the cloud management platform, which can make a gateway instance group stably ensure a tenant to successfully access an application of the tenant, thereby improving the quality of cloud services provided by a cloud vendor for the tenant to a certain extent, and further improving the experience of the tenant.

[0039] The terms "first", "second", etc. in the description and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily have to describe a specific order or sequence. It should be understood that the terms thus used can be interchanged under appropriate circumstances, and this is merely a distinguishing way adopted in the description of the embodiments of the present application for describing the objects of the same attribute. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, so that a process, method, system, product or device containing a series of units does not have to be limited to those units, but can include other units not clearly listed or inherent to the process, method, product or device.

[0040] With the rapid development of cloud technology, more and more tenants choose to deploy their applications in the cloud to complete their business requirements through cloud services provided by cloud vendors. Based on this, the gateway instance provided by the cloud vendor serves as a communication bridge between the tenant and the application running in the cloud, and the reliability and stability of the gateway instance affect the quality of the cloud services provided by the cloud vendor for the tenant.

[0041] In the related art, when a tenant deploys its application in the cloud, the tenant usually simultaneously chooses to create a gateway instance serving the tenant, and the cloud vendor can create multiple gateway instances for the tenant. Among these gateway instances created by the cloud vendor for the tenant, each gateway instance is essentially a logical unit, and each gateway instance is built based on multiple cloud instances, so each gateway instance has certain specifications and network performance. Among the multiple gateway instances, when a gateway instance receives an access request of the tenant to the application deployed in the cloud, the gateway instance can forward the access request to the application, so that the application processes the access request, thereby meeting the business requirements of the tenant.

[0042] In the above process, since the cloud vendor can make multiple gateway instances of the tenant occupy the same part of cloud instances, once these cloud instances fail, the multiple gateway instances will be simultaneously unavailable, which will cause the tenant to be unable to stably access the application, and further cause the quality of the cloud services provided by the cloud vendor for the tenant to be poor.

[0043] To solve the above problems, the embodiment of the present application provides a gateway instance configuration method based on a cloud management platform. The method can be implemented through a cloud service system. FIG. 1 is a structural schematic diagram of a cloud service system provided by the embodiment of the present application. As shown in FIG. 1, the cloud service system includes an infrastructure that can provide cloud services and a cloud management platform that manages the infrastructure. The cloud management platform and the infrastructure are introduced respectively as follows:

[0044] The cloud management platform can comprehensively manage the infrastructure in the entire cloud service system (for example, in the infrastructure, according to the indication of a certain tenant, cloud instance clusters serving the tenant are created for the tenant, part of the cloud instances in the clusters can be used to create a gateway instance group of the tenant, and part of the cloud instances can be used to run an application of the tenant, so that the tenant can access the application through the gateway instances to meet the business requirements of the tenant, and the like). The cloud management platform can also be open to tenants outside the cloud service system and respond to their requests. For example, the cloud management platform can provide various interfaces such as a login interface and a deployment interface for the client (for example, a terminal device used by the tenant or a browser on the terminal device, and the like) of the tenant to access. Among them, the cloud management platform can authenticate the client of a certain tenant through the login interface, and allow the client of the tenant to log in to the cloud management platform after successful authentication. For another example, the cloud management platform can also allow the client of the tenant to send an anti-affinity deployment request of the tenant for a gateway instance group to the cloud management platform through the deployment interface, so that the cloud management platform can determine a plurality of gateway instances to be anti-affinity deployed in the gateway instance group of the tenant based on the anti-affinity deployment request. Then, the cloud management platform can create the plurality of gateway instances. For any one of the plurality of gateway instances, the gateway instance can include (occupy) a plurality of cloud instances, and the plurality of cloud instances included in the gateway instance are arranged in a fault domain. It is worth noting that in the plurality of gateway instances, the cloud instances occupied by different gateway instances are located in different fault domains, that is, the cloud instances occupied by different gateway instances are different cloud instances. It can be seen that the plurality of gateway instances form fault isolation between each other, and also form fault isolation within each gateway instance. Based on this, the tenant can access the application through the plurality of gateway instances, wherein the cloud instance where the application of the tenant is located and the cloud instances occupied by the plurality of gateway instances are different cloud instances.

[0045] The infrastructure includes a cluster of cloud instances providing cloud services for the tenant, and the cluster of cloud instances can include a large number of cloud instances, which can be divided into two parts. One part of the cloud instances can be used to run the application of the tenant, and can be accessed by the tenant and process the access request of the tenant to meet the business needs of the tenant. The other part of the cloud instances can be used to create a gateway instance group of the tenant. Each gateway instance in the gateway instance group can serve as a communication relay point between the tenant and the cloud instance where the application of the tenant is located. Therefore, the tenant can send the access request for the application to the gateway instances, so that the gateway instances forward the access request to the cloud instance where the application is located, and then the application processes the access request to meet the business needs of the tenant.

[0046] It is worth noting that, as shown in FIG. 2 (FIG. 2 is another structure schematic diagram of the cloud service system provided by the embodiment of the present application), the cloud management platform can include a management module for the gateway instance group of the tenant. The management module is usually remotely deployed between the gateway instance group of the tenant and the tenant (of course, the management module is closer to the gateway instance group of the tenant). When the tenant sends an access request for the application, the management module can first receive the access request, select a gateway instance from the gateway instance group of the tenant, select a cloud instance from a plurality of cloud instances occupied by the gateway instance, and then forward the access request to the cloud instance, so that the cloud instance forwards the access request to the cloud instance where the application of the tenant is located. Therefore, the application of the tenant can process the access request to meet the business needs of the tenant.

[0047] In addition, the management module can also monitor the gateway instance group of the tenant in real time. Once a cloud instance in a gateway instance fails, the management module can remove the cloud instance from the gateway instance, and add a new cloud instance to the gateway instance under certain special conditions to ensure the normal operation of the gateway instance. Here, it is not expanded.

[0048] Further, for the plurality of cloud instances in the cloud instance cluster serving the tenant, the cloud instances can be presented in various forms, for example, the cloud instances can be physical servers (containing certain specifications of computing resources, storage resources, network resources, etc.) selected by the cloud management platform in the infrastructure, for another example, the cloud instances can also be bare metal servers (containing certain specifications of computing resources, storage resources, network resources, etc.) selected by the cloud management platform in the infrastructure. For another example, the cloud instances can also be virtual machines (VM) created by the cloud management platform in the physical servers or bare metal servers through virtualization technology, for another example, the cloud instances can also be containers (docker) created by the cloud management platform in the physical servers or bare metal servers through virtualization technology, for another example, the cloud instances can also be micro virtual machines (microVM) created by the cloud management platform in the physical servers or bare metal servers through virtualization technology, and the like.

[0049] Further, for the gateway instance group of the tenant, the cloud instances occupied by different gateway instances in the gateway instance group are usually deployed in different failure domains (a logical concept), which can be presented in various forms, for example, the cloud instances occupied by different gateway instances can be arranged in different regions of the infrastructure, for another example, the cloud instances occupied by different gateway instances can be arranged in different availability zones of the infrastructure, for another example, the cloud instances occupied by different gateway instances can be arranged in different data centers (DC) of the infrastructure, for another example, the cloud instances occupied by different gateway instances can be arranged in different rooms of the infrastructure, for another example, the cloud instances occupied by different gateway instances can be arranged in different groups of physical servers (also referred to as racks) of the infrastructure, and the like.

[0050] Based on the cloud service system, when a tenant needs to configure a gateway instance group, the tenant can send an anti-affinity deployment request for the gateway instance group to a deployment interface provided by the cloud management platform, so that the cloud management platform can create multiple gateway instances included in the gateway instance group based on the anti-affinity deployment request, and the multiple gateway instances can be used by the tenant to access the application of the tenant. For any one of the multiple gateway instances, the gateway instance can include multiple cloud instances, and the multiple cloud instances included in the gateway instance are arranged in one fault domain. Since the cloud instances occupied by different gateway instances are located in different fault domains, that is, the cloud instances occupied by different gateway instances are different cloud instances, it can be seen that the multiple gateway instances form fault isolation, that is, the multiple gateway instances form anti-affinity deployment. If a cloud instance in a gateway instance fails, it will not affect the normal operation of the remaining gateway instances, so the gateway instance group can stably ensure that the tenant successfully accesses the application of the tenant, thereby improving the quality of the cloud service provided by the cloud vendor for the tenant to a certain extent, and further improving the experience of the tenant. In order to further understand the working process of the foregoing cloud management platform, the working process is further introduced in combination with FIG. 3. FIG. 3 is a flowchart of a gateway instance configuration method based on a cloud management platform provided by an embodiment of the present application. As shown in FIG. 3, the method can be implemented by the cloud service system shown in FIG. 1. The cloud service system includes infrastructure for providing cloud services for tenants and a cloud management platform for managing the infrastructure. The infrastructure can include a cloud instance cluster, and the cloud instance cluster includes a large number of cloud instances. The method includes the following steps.

[0051] 301. The cloud management platform receives, through the deployment interface, an anti-affinity deployment request for a gateway instance group sent by a tenant, and the anti-affinity deployment request is used to indicate a first gateway instance and a second gateway instance included in the gateway instance group.

[0052] In this embodiment, when a tenant needs to create a gateway instance group that is exclusively used by the tenant, the cloud management platform can provide a deployment interface (for example, a gateway instance deployment column of a tenant interface, etc.) to a client of the tenant. Then, the tenant can input an anti-affinity deployment request set by the tenant for the gateway instance group of the tenant to the deployment interface through the client used by the tenant. The anti-affinity deployment request is used to indicate a first gateway instance and a second gateway instance included in the gateway instance group of the tenant. In this way, the cloud management platform can receive the anti-affinity deployment request sent by the client of the tenant through the deployment interface.

[0053] Specifically, the anti-affinity deployment request can contain the following information: the identity of the gateway instance group, the affinity policy for the gateway instance group, the identity document (ID) of the first gateway instance, the type of the first gateway instance, the specification requirement of the first gateway instance, the performance requirement of the first gateway instance, the ID of the second gateway instance, the type of the second gateway instance, the specification requirement of the second gateway instance, and the performance requirement of the second gateway instance, and the like. It should be noted that since the affinity policy for the gateway instance group is used to indicate that the gateway instances in the gateway instance group need to be deployed in an anti-affinity manner, the gateway instance group can also be referred to as an anti-affinity group.

[0054] For example, when tenant 1 needs to create a gateway instance group 1, tenant 1 can log in to the cloud management platform, and the cloud management platform provides a tenant interface to tenant 1, the tenant interface contains a gateway instance deployment column, and tenant 1 can input an anti-affinity deployment request for the gateway instance group 1 in the gateway instance deployment column, the request contains the following parameters:

[0055] Table 1

[0056] Table 2

[0057] Table 1 is the main parameters in the anti-affinity deployment request, including the ID of the gateway instance group of tenant 1 (the ID is 1), the gateway instance list of gateway instance group 1 of tenant 1 (the content of the list is table 2), the affinity policy for gateway instance group 1 of tenant 1 (the policy is used to indicate that all gateway instances in gateway instance group 1 need to be deployed in anti-affinity). Table 2 is the parameters of each gateway instance in gateway instance group 1 of tenant 1, wherein the gateway instance group contains two gateway instances, and their IDs are 1 and 2 respectively. Moreover, in gateway instance group 1, the type of gateway instance 1 and the type of gateway instance 2 are both Load Balancer (of course, it can also be NAT gateway or VPC EP, etc.), and the gateway instance 1 and the gateway instance 2 in the gateway instance group 1 can be called Load Balancer 1 and Load Balancer 2 in the future. Of course, table 2 does not show all the parameters of Load Balancer 1 and Load Balancer 2, for example, table 2 can also contain the specification requirements of Load Balancer 1 (i.e. the size of the computing resources, storage resources and network resources required by Load Balancer 1) and the specification requirements of Load Balancer 2 (i.e. the size of the computing resources, storage resources and network resources required by Load Balancer 2), table 2 can also contain the performance requirements of Load Balancer 1 (i.e. the total bandwidth required by Load Balancer 1, etc.) and the performance requirements of Load Balancer 2 (i.e. the total bandwidth required by Load Balancer 2, etc.) and so on.

[0058] It should be understood that the above example only illustrates that gateway instance group 1 of tenant 1 contains two gateway instances, in actual application, gateway instance group 1 of tenant 1 can contain more gateway instances, for example, gateway instance group 1 can contain 3 gateway instances, 4 gateway instances or 5 gateway instances, etc., which is not limited here.

[0059] 302、The cloud management platform creates a first gateway instance and a second gateway instance based on the anti-affinity deployment request, the first gateway instance and the second gateway instance are used for the tenant to access the application of the tenant, wherein the first gateway instance contains a plurality of first cloud instances in a cloud instance cluster, the second gateway instance contains a plurality of second cloud instances in the cloud instance cluster, the application runs in a third cloud instance in the cloud instance cluster, the plurality of first cloud instances are arranged in a first fault domain, the plurality of second cloud instances are arranged in a second fault domain, the first fault domain and the second fault domain are different fault domains, and the first fault domain and the second fault domain are any one of the following: region, availability zone, data center, machine room or physical server group.

[0060] After obtaining the anti-affinity deployment request for the gateway instance group of the tenant, the cloud management platform can parse the anti-affinity deployment request, so as to determine that the gateway instance group to be created by the tenant includes the first gateway instance and the second gateway instance, and the first gateway instance and the second gateway instance need to be deployed in an anti-affinity manner. Then, the cloud management platform can use the cloud instances in the cloud instance cluster to create the first gateway instance and the second gateway instance. Then, the tenant can subsequently access the application of the tenant through the first gateway instance and the second gateway instance.

[0061] It should be noted that the first gateway instance can include a plurality of first cloud instances in the cloud instance cluster arranged in the first failure domain, the second gateway instance can include a plurality of second cloud instances in the cloud instance cluster arranged in the second failure domain, and the application of the tenant can run a third cloud instance in the cloud instance cluster. Since the first failure domain and the second failure domain are two different failure domains, the plurality of first cloud instances arranged in the first failure domain and the plurality of second cloud instances arranged in the second failure domain are two parts of cloud instances that are different from each other, that is, the plurality of first cloud instances (the first gateway instance) and the plurality of second cloud instances (the second gateway instance) are fault-isolated, that is, the first gateway instance and the second gateway instance are deployed in an anti-affinity manner.

[0062] In addition, the first failure domain and the second failure domain can be any one of a region, an availability zone, a data center, a computer room, and a physical server group.

[0063] Still as the above example, as shown in FIG. 4 (FIG. 4 is another structural diagram of the cloud service system provided by the embodiment of the present application), it is assumed that the virtual machine cluster created in advance by the cloud management platform includes virtual machine 1 to virtual machine 10. After receiving the anti-affinity deployment request for the gateway instance group 1 by the tenant 1, the cloud management platform can create the gateway instance group 1 based on the request, and the gateway instance group 1 includes Load Balancer 1 and Load Balancer 2, Load Balancer 1 occupies virtual machine 1 and virtual machine 2, and Load Balancer 2 occupies virtual machine 5 to virtual machine 7. Among them, virtual machine 1 and virtual machine 2 are located in AZ1, and virtual machine 5 and virtual machine 7 are located in AZ2. As can be seen, Load Balancer 1 and Load Balancer 2 are deployed in different AZs, and there is a certain fault isolation.

[0064] In particular, since the anti-affinity deployment request can also be used to indicate the specification requirement of the first gateway instance and the specification requirement of the second gateway instance, the sum of the specifications of the multiple first cloud instances selected by the cloud management platform from the cloud instance cluster can satisfy the specification requirement of the first gateway instance (e.g., the sum of the computing resources of the multiple first cloud instances is greater than or equal to the required computing resources of the first gateway instance, the sum of the storage resources of the multiple first cloud instances is greater than or equal to the required storage resources of the first gateway instance, the sum of the network resources of the multiple first cloud instances is greater than or equal to the required network resources of the first gateway instance, etc.), and likewise, the sum of the specifications of the multiple second cloud instances selected by the cloud management platform from the cloud instance cluster can satisfy the specification requirement of the second gateway instance (e.g., the sum of the computing resources of the multiple second cloud instances is greater than or equal to the required computing resources of the second gateway instance, the sum of the storage resources of the multiple second cloud instances is greater than or equal to the required storage resources of the second gateway instance, the sum of the network resources of the multiple second cloud instances is greater than or equal to the required network resources of the second gateway instance, etc.).

[0065] Still as in the above example, since the anti-affinity deployment request for the gateway instance group 1 contains the specification requirement of Load Balancer 1 and the specification requirement of Load Balancer 2, the sum of the specification of virtual machine 1 and the specification of virtual machine 2 selected by the cloud management platform satisfies the specification requirement of Load Balancer 1, and the sum of the specification of virtual machine 5, the specification of virtual machine 6, and the specification of virtual machine 7 satisfies the specification requirement of Load Balancer 2.

[0066] More particularly, since the anti-affinity deployment request can also be used to indicate the performance requirement of the first gateway instance and the performance requirement of the second gateway instance, the sum of the performances of the multiple first cloud instances selected by the cloud management platform from the cloud instance cluster can satisfy the performance requirement of the first gateway instance (e.g., the sum of the bandwidths of the multiple first cloud instances is greater than or equal to the total bandwidth required by the first gateway instance, etc.), and likewise, the sum of the performances of the multiple second cloud instances selected by the cloud management platform from the cloud instance cluster can satisfy the performance requirement of the second gateway instance (e.g., the sum of the bandwidths of the multiple second cloud instances is greater than or equal to the total bandwidth required by the second gateway instance, etc.).

[0067] Still as the above example, since the anti-affinity deployment request for the gateway instance group 1 contains the performance requirement of Load Balancer 1 and the performance requirement of Load Balancer 2, the sum of the performance of the selected virtual machine 1 and the performance of the selected virtual machine 2 satisfies the performance requirement of Load Balancer 1, and the sum of the performance of the selected virtual machine 5, the performance of the selected virtual machine 6 and the performance of the selected virtual machine 7 satisfies the performance requirement of Load Balancer 2.

[0068] More specifically, when the multiple first cloud instances contained in the first gateway instance and the multiple second cloud instances contained in the second gateway instance are virtual instances (containing any one of virtual machines, containers and micro virtual machines), and the first fault domain where the first gateway instance is located and the second fault domain where the second gateway instance is located are physical server groups, the physical server group where the first fault domain is located and the physical server group where the second fault domain is located can contain the same physical server, which is the overlapping part between the first fault domain and the second fault domain, that is, some (or some) of the multiple first cloud instances and some (or some) of the multiple second cloud instances can be deployed on the same physical server, which belongs to both the first fault domain and the second fault domain. The remaining first cloud instances and the remaining second cloud instances are deployed on different physical servers in the first fault domain and the second fault domain.

[0069] When the multiple first cloud instances contained in the first gateway instance and the multiple second cloud instances contained in the second gateway instance are virtual instances or physical instances (containing physical servers or bare metal servers), and the first fault domain where the first gateway instance is located and the second fault domain where the second gateway instance is located are any one of regions, availability zones, data centers and machine rooms, the physical server group where the first fault domain is located and the physical server group where the second fault domain is located must be different physical server groups, that is, the multiple first cloud instances and the multiple second cloud instances are respectively deployed on different physical servers in the first fault domain and the second fault domain.

[0070] Still as the above example, as shown in FIG. 5 (FIG. 5 is another structure diagram of the cloud service system provided by the embodiment of the present application, and FIG. 5 is drawn on the basis of FIG. 4), suppose that the virtual machine 1 is deployed on the physical server 1 in the physical server group 1, the virtual machine 2 is deployed on the physical server 2 in the physical server group 1, the virtual machine 5 is deployed on the physical server 2 in the physical server group 2, the virtual machine 6 is deployed on the physical server 3 in the physical server group 2, and the virtual machine 7 is deployed on the physical server 4 in the physical server group 2. As can be seen, the physical server group 1 and the physical server group 2 are two fault domains, and there is an overlapping part between the two, that is, the physical server 2, so the virtual machine 2 in the Load Balancer 1 and the virtual machine 5 in the Load Balancer 2 are both deployed on the physical server 2, while the rest of the virtual machines in the Load Balancer 1 and the rest of the virtual machines in the Load Balancer 2 are respectively deployed on different physical servers. As can be seen, the virtual machines occupied by the two gateway instances are partially shared (resources) and partially independent.

[0071] Still as the above example, as shown in FIG. 6 (FIG. 6 is another structure diagram of the cloud service system provided by the embodiment of the present application, and FIG. 6 is drawn on the basis of FIG. 4), suppose that the virtual machine 1 is deployed on the physical server 1 in AZ1, the virtual machine 2 is deployed on the physical server 2 in AZ1, the virtual machine 5 is deployed on the physical server 3 in AZ2, the virtual machine 6 is deployed on the physical server 4 in AZ2, and the virtual machine 7 is deployed on the physical server 5 in AZ2. As can be seen, AZ1 and AZ2 are two fault domains, and there is no overlapping part between the two, that is, all the virtual machines in the Load Balancer 1 and all the virtual machines in the Load Balancer 2 are respectively deployed on different physical servers. As can be seen, the virtual machines occupied by the two gateway instances are all independent of each other.

[0072] More specifically, the first gateway instance and the second gateway instance can realize the communication between the tenant and the application of the tenant in the following way:

[0073] When the tenant needs to access the application, the tenant can send an access request for the application to the cloud management platform. Then, the cloud management platform can determine that the tenant needs to access the application based on the access request, so the cloud management platform can select the first gateway instance (of course, the second gateway instance can also be selected) from the first gateway instance and the second gateway instance included in the gateway instance group of the tenant. Since the first gateway instance includes a plurality of first cloud instances, the cloud management platform can select one of the plurality of first cloud instances and notify the first cloud instance to send the access request to the third cloud instance running the application, so that the application processes the access request, thereby meeting the business needs of the tenant.

[0074] Still as the above example, when the tenant 1 needs to access the application 1, the management module of the cloud management platform can receive the access request sent by the tenant 1 for the application 1, the management module can select the Load Balancer 1 from the Load Balancer 1 and the Load Balancer 2, and select the virtual machine 1 from the virtual machine 1 and the virtual machine 2 contained by the Load Balancer 1. Then, the management module can send the access request to the virtual machine 1, so that the virtual machine 1 sends the access request to the application 1 for processing, thereby meeting the service requirement of the tenant 1.

[0075] More specifically, the cloud management platform can further perform the following operations:

[0076] The cloud management platform can also perform real-time fault monitoring on the first gateway instance and the second gateway instance. If the cloud management platform finds that there is a (one or more) first cloud instance that has failed in the plurality of first cloud instances contained by the first gateway instance, the cloud management platform removes the failed first cloud instance from the first gateway instance, so that the remaining first cloud instances in the first gateway instance are all non-failed first cloud instances. Therefore, if the cloud management platform receives an access request of the tenant for the application thereof, and the cloud management platform selects the first gateway instance for forwarding, the cloud management platform can send the access request to the remaining first cloud instances in the first gateway instance, so that the remaining first cloud instances send the access request to the third cloud instance where the application of the tenant is located. The same applies to the second gateway instance, which will not be described here.

[0077] Still as the above example, the management module of the cloud management platform can monitor the Load Balancer 1 and the Load Balancer 2 in real time. If the management module finds that the virtual machine 1 has failed, the management module can remove the virtual machine 1 from the Load Balancer 1, so that only the virtual machine 2 is available in the Load Balancer 1. Then, when the tenant 1 needs to access the application 1 subsequently, if the management module selects the Load Balancer 1, the access request will be forwarded by the virtual machine 2, because the virtual machine 1 has been removed.

[0078] More specifically, the cloud management platform can further perform the following operations:

[0079] After the failed first cloud instance is removed from the first gateway instance, the cloud management platform can determine whether the sum of the performances of the remaining first cloud instances in the first gateway instance meets the performance requirement of the first gateway instance. If not, the cloud management platform can select a first cloud instance to be added from the cloud instance cluster based on the difference between the sum of the performances of the remaining first cloud instances and the performance requirement of the first gateway instance (the performance of the first cloud instance can make up for the difference), and add the first cloud instance to be added to the first gateway instance to improve the overall performance of the first gateway instance. It should be noted that the remaining first cloud instances in the first gateway instance and the first cloud instance to be added are all first cloud instances that have not failed.

[0080] Still as in the above example, after the cloud management platform removes virtual machine 1 from Load Balancer 1, the management module of the cloud management platform can detect whether the performance of virtual machine 2 meets the performance requirement of Load Balancer 1. If not, the management module can select virtual machine 3 to be added from the virtual machine cluster based on the gap between the performance of virtual machine 2 and the performance requirement of Load Balancer 1, and add virtual machine 3 to Load Balancer 1 to improve the overall performance of Load Balancer 1.

[0081] In the embodiments of the present application, when a tenant needs to configure a gateway instance group thereof, the tenant can send an anti-affinity deployment request for the gateway instance group to a deployment interface provided by the cloud management platform, so that the cloud management platform can create a first gateway instance and a second gateway instance included in the gateway instance group based on the anti-affinity deployment request. The first gateway instance and the second gateway instance can be used by the tenant to access the application of the tenant. The first gateway instance can be constructed by a plurality of first cloud instances, and the second gateway instance can be constructed by a plurality of second cloud instances. The plurality of first cloud instances included in the first gateway instance are arranged in a first fault domain, and the plurality of second cloud instances included in the second gateway instance are arranged in a second fault domain. Since the first fault domain and the second fault domain are different fault domains, the first gateway instance arranged in the first fault domain and the second gateway instance arranged in the second fault domain form fault isolation, that is, the first gateway instance and the second gateway instance form anti-affinity deployment. If a certain first cloud instance included in the first gateway instance fails, it will not affect the normal operation of the second gateway instance, so that the gateway instance group of the tenant can stably ensure that the tenant can successfully access the application of the tenant, thereby improving the quality of the cloud service provided by the cloud vendor for the tenant to a certain extent, and further improving the experience of the tenant.

[0082] Further, since the anti-affinity deployment of the gateway instance group of the tenant can be specified by the tenant, the tenant can achieve fault isolation management of the gateway instance group thereof to ensure that the tenant can stably access the application thereof, thereby improving the stability of the business.

[0083] The above is a detailed description of the gateway instance configuration method based on the cloud management platform provided by the embodiments of the present application. The cloud management platform provided by the embodiments of the present application will be introduced below. FIG. 7 is a structural schematic diagram of a cloud management platform provided by an embodiment of the present application. The cloud management platform is used to manage an infrastructure that provides cloud services for tenants. The infrastructure includes a cloud instance cluster. The cloud management platform includes:

[0084] The receiving module 701 is configured to receive, through a deployment interface, an anti-affinity deployment request for a gateway instance group sent by a tenant. The anti-affinity deployment request is used to indicate a first gateway instance and a second gateway instance included in the gateway instance group. For example, the receiving module 701 is configured to implement step 301 in the embodiment shown in FIG. 3.

[0085] The creating module 702 is configured to create the first gateway instance and the second gateway instance based on the anti-affinity deployment request. The first gateway instance and the second gateway instance are used to access an application of the tenant by the tenant. The first gateway instance includes a plurality of first cloud instances in the cloud instance cluster. The second gateway instance includes a plurality of second cloud instances in the cloud instance cluster. The application runs in a third cloud instance in the cloud instance cluster. The plurality of first cloud instances are arranged in a first fault domain. The plurality of second cloud instances are arranged in a second fault domain. The first fault domain and the second fault domain are different fault domains. The first fault domain and the second fault domain are any of the following: a region, an availability zone, a data center, a machine room, or a physical server group. For example, the receiving module 702 is configured to implement step 302 in the embodiment shown in FIG. 3.

[0086] In a possible implementation manner, the cloud management platform further includes an excluding module configured to exclude a failed first cloud instance from the first gateway instance if the failed first cloud instance exists in the plurality of first cloud instances in the first gateway instance.

[0087] In a possible implementation manner, the anti-affinity deployment request is further used to indicate a performance requirement of the first gateway instance. The cloud management platform further includes an adding module configured to select a first cloud instance to be added from the cloud instance cluster based on a difference between a sum of performances of remaining first cloud instances in the first gateway instance and the performance requirement of the first gateway instance, and add the first cloud instance to be added to the first gateway instance if the sum of performances of the remaining first cloud instances does not meet the performance requirement of the first gateway instance, where the remaining first cloud instances and the first cloud instance to be added are both non-failed first cloud instances.

[0088] In a possible implementation manner, the anti-affinity deployment request is further used to indicate a specification requirement of the first gateway instance. A sum of specifications of the plurality of first cloud instances meets the specification requirement of the first gateway instance.

[0089] In a possible implementation, the creating module 702 is configured to: receive an access request for an application of a tenant sent by the tenant; select a first gateway instance from the first gateway instance and the second gateway instance based on the access request, and select one of the first cloud instances from the first gateway instance; and notify the first cloud instance to send the access request to a third cloud instance running the application.

[0090] In a possible implementation, when the first cloud instances and the second cloud instances are virtual machines, containers or micro virtual machines, and the first failure domain and the second failure domain are physical server groups, the physical server group where the first failure domain is located and the physical server group where the second failure domain is located contain a same physical server.

[0091] In a possible implementation, the first cloud instances and the second cloud instances include any one of the following: a physical server, a virtual machine, a container, a micro virtual machine or a bare metal server.

[0092] It should be noted that the information interaction and implementation process between the modules / units of the apparatus described above are based on the same concept as the method embodiments of the present application, and the technical effects brought by the same are the same as those of the method embodiments of the present application. For details, refer to the foregoing description of the method embodiments.

[0093] Please refer to FIG. 8, which is a structural schematic diagram of a computing device provided by an embodiment of the present application. As shown in FIG. 8, the computing device 800 (which can be used to present the cloud management platform described above) includes a processor 801, a memory 802, a communication interface 803 and a bus 804. The processor 801, the memory 802 and the communication interface 803 are coupled through a bus (not shown in the figure). The memory 802 stores instructions, and when the instructions stored in the memory 802 are executed, the computing device 800 performs the method performed by the cloud management platform in the method embodiments described above.

[0094] The computing device 800 can be one or more integrated circuits (ICs) configured to implement one or more of the above methods, e.g., one or more application specific integrated circuits (ASICs), or, one or more digital signal processors (DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when units of the apparatus can be implemented by way of a processing element scheduler, the processing element can be a general purpose processor, e.g., a central processing unit (CPU) or other processor that can invoke a program. As another example, these units can be integrated together in a system-on-a-chip (SOC) form.

[0095] The processor 801 can be a central processing unit (CPU), and can also be other general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general purpose processor can be a microprocessor or any conventional processor.

[0096] The memory 802 can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example, and not limitation, many forms of RAM can be used, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0097] The executable program code stored in the memory 802 is executed by the processor 801 to realize the functions of the aforementioned receiving module, creating module and other modules, thereby realizing the cloud management platform-based gateway instance configuration method described above. That is, the memory 802 has instructions for executing the cloud management platform-based gateway instance configuration method described above.

[0098] The communication interface 803 uses a transceiving module such as, but not limited to, a network interface card, a transceiver, to realize the communication between the computing device 800 and other devices or communication networks.

[0099] The bus 804 can include, in addition to a data bus, a power bus, a control bus, and a state signal bus, etc. The bus can be a peripheral component interconnect express (PCIe) bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0100] Referring to FIG. 9, FIG. 9 is a structural schematic diagram of a computing device cluster provided by an embodiment of the present application. As shown in FIG. 9, the computing device cluster 900 includes at least one computing device 800.

[0101] As shown in FIG. 9, the computing device cluster 900 includes at least one computing device 800. The memory 802 in one or more computing devices 800 in the computing device cluster 900 can store the same instructions for performing the cloud management platform-based gateway instance configuration method described above.

[0102] In some possible implementation manners, the memory 802 of one or more computing devices 800 in the computing device cluster 900 can also respectively store partial instructions for performing the cloud management platform-based gateway instance configuration method described above. In other words, the combination of one or more computing devices 800 can collectively perform the cloud management platform-based gateway instance configuration method described above.

[0103] It should be noted that the memory 802 in different computing devices 800 in the computing device cluster 900 can store different instructions, respectively, for performing part of the functions of the cloud management platform described above. That is, the instructions stored in the memory 802 in different computing devices 800 can implement the functions of one or more of the receiving module, the creating module, and the like.

[0104] In some possible implementation manners, one or more computing devices 800 in the computing device cluster 900 can be connected through a network. The network can be a wide area network or a local area network, etc.

[0105] Please refer to Fig. 10, which is a schematic diagram of the connection of the computer devices in the computer cluster provided by the embodiment of the present application. As shown in Fig. 10, the two computer devices 800A and 800B are connected through the network. Specifically, the communication interface in each computer device is connected to the network.

[0106] In a possible implementation, the memory in the computer device 800A stores instructions for performing the functions of the receiving module and other modules. Meanwhile, the memory in the computer device 800B stores instructions for performing the functions of the creating module and other modules.

[0107] It should be understood that the functions of the computer device 800A shown in Fig. 10 can also be completed by multiple computer devices. Similarly, the functions of the computer device 800B can also be completed by multiple computer devices.

[0108] The embodiment of the present application also relates to a computer storage medium, which stores a program for signal processing, and when the program runs on a computer, the computer executes the steps performed by the cloud management platform in the embodiment shown in Fig. 3.

[0109] The embodiment of the present application also relates to a computer program product, which stores instructions, and when the instructions are executed by a computer, the computer executes the steps performed by the cloud management platform in the embodiment shown in Fig. 3.

[0110] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described herein.

[0111] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the above-described device embodiments are merely schematic, for example, the division of the units is merely a logical function division, and actual implementation can have another division manner, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0112] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, can be located in one place, or can be distributed on multiple network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment scheme.

[0113] In addition, each function unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software function unit.

[0114] When the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, essentially or in other words, the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, read-only memory), a random access memory (RAM, random access memory), a magnetic disk or an optical disk, and various media that can store program codes.

Claims

1. A gateway instance configuration method based on a cloud management platform, characterized in that, The cloud management platform is configured to manage an infrastructure providing cloud services for a tenant, the infrastructure comprising a cluster of cloud instances, and the method comprises: The cloud management platform receives, through a deployment interface, an anti-affinity deployment request for a gateway instance group sent by the tenant, the anti-affinity deployment request being configured to indicate a first gateway instance and a second gateway instance included in the gateway instance group; The cloud management platform creates the first gateway instance and the second gateway instance based on the anti-affinity deployment request, the first gateway instance and the second gateway instance being configured to be accessed by the tenant for an application of the tenant, wherein the first gateway instance comprises a plurality of first cloud instances in the cluster of cloud instances, the second gateway instance comprises a plurality of second cloud instances in the cluster of cloud instances, the application is running in a third cloud instance in the cluster of cloud instances, the plurality of first cloud instances are arranged in a first fault domain, the plurality of second cloud instances are arranged in a second fault domain, the first fault domain and the second fault domain are different fault domains, and the first fault domain and the second fault domain are any one of the following: a region, an availability zone, a data center, a machine room, or a physical server group.

2. The method of claim 1, wherein, The method further comprises: If there is a failed first cloud instance in the plurality of first cloud instances in the first gateway instance, the cloud management platform removes the failed first cloud instance from the first gateway instance.

3. The method of claim 2, wherein, The anti-affinity deployment request is further configured to indicate a performance requirement of the first gateway instance, and the method further comprises: If the sum of the performances of the remaining first cloud instances in the first gateway instance does not meet the performance requirement of the first gateway instance, the cloud management platform selects a first cloud instance to be added from the cluster of cloud instances based on the difference between the sum of the performances and the performance requirement, and adds the first cloud instance to be added to the first gateway instance, wherein the remaining first cloud instances and the first cloud instance to be added are both non-failed first cloud instances.

4. The method of claim 3, wherein, The anti-affinity deployment request is further configured to indicate a size requirement of the first gateway instance, and the sum of the sizes of the plurality of first cloud instances meets the size requirement of the first gateway instance.

5. The method according to any one of claims 1 to 3, characterized in that, The first gateway instance and the second gateway instance being configured to be accessed by the tenant for the application of the tenant comprises: The cloud management platform receives an access request for the application of the tenant sent by the tenant; The cloud management platform selects a first gateway instance from the first gateway instance and the second gateway instance based on the access request, and selects one of the plurality of first cloud instances in the first gateway instance; The cloud management platform notifies the first cloud instance to send the access request to a third cloud instance running the application.

6. The method according to any one of claims 1 to 5, characterized in that, When the plurality of first cloud instances and the plurality of second cloud instances are virtual machines, containers, or micro virtual machines, and the first fault domain and the second fault domain are physical server groups, the physical server group where the first fault domain is located and the physical server group where the second fault domain are located comprise the same physical server.

7. The method according to any one of claims 1 to 6, characterized in that, The first cloud instances and the second cloud instances include any of the following: physical servers, virtual machines, containers, micro virtual machines, or bare metal servers.

8. A cloud management platform, characterized by, The cloud management platform is configured to manage infrastructure for providing cloud services for tenants, the infrastructure including a cluster of cloud instances, and the cloud management platform includes: a receiving module configured to receive, through a deployment interface, an anti-affinity deployment request for a gateway instance group sent by a tenant, the anti-affinity deployment request being configured to indicate a first gateway instance and a second gateway instance included in the gateway instance group; a creating module configured to create, based on the anti-affinity deployment request, the first gateway instance and the second gateway instance, the first gateway instance and the second gateway instance being configured to be accessed by the tenant for an application of the tenant, wherein the first gateway instance includes a plurality of first cloud instances in the cluster of cloud instances, the second gateway instance includes a plurality of second cloud instances in the cluster of cloud instances, the application is running in a third cloud instance in the cluster of cloud instances, the plurality of first cloud instances are arranged in a first fault domain, the plurality of second cloud instances are arranged in a second fault domain, the first fault domain and the second fault domain are different fault domains, and the first fault domain and the second fault domain are any of the following: a region, an availability zone, a data center, a machine room, or a physical server group.

9. The cloud management platform of claim 8, wherein, The cloud management platform further includes: an excluding module configured to exclude, from the first gateway instance, a failed first cloud instance if the failed first cloud instance exists in the plurality of first cloud instances in the first gateway instance.

10. The cloud management platform of claim 9, wherein, The anti-affinity deployment request is further configured to indicate a performance requirement of the first gateway instance, and the cloud management platform further includes: an adding module configured to, if a sum of performances of remaining first cloud instances in the first gateway instance does not meet the performance requirement of the first gateway instance, select a first cloud instance to be added from the cluster of cloud instances based on a difference between the sum of performances and the performance requirement, and add the first cloud instance to be added to the first gateway instance, wherein the remaining first cloud instances and the first cloud instance to be added are both non-failed first cloud instances.

11. The cloud management platform of claim 10, wherein, The anti-affinity deployment request is further configured to indicate a size requirement of the first gateway instance, and a sum of sizes of the plurality of first cloud instances meets the size requirement of the first gateway instance.

12. The cloud management platform of any of claims 8 to 10, wherein, The creating module is configured to: receive an access request for the application of the tenant sent by the tenant; select, based on the access request, a first gateway instance from the first gateway instance and the second gateway instance, and select one of the plurality of first cloud instances in the first gateway instance; notify the first cloud instance to send the access request to a third cloud instance running the application.

13. The cloud management platform of any of claims 8 to 12, wherein, When the first and second cloud instances are virtual machines, containers, or micro virtual machines, and the first and second failure domains are groups of physical servers, the group of physical servers in which the first failure domain is located and the group of physical servers in which the second failure domain is located include a same physical server.

14. The cloud management platform of any of claims 8 to 13, wherein, The first and second cloud instances include any of the following: physical servers, virtual machines, containers, micro virtual machines, or bare metal servers.

15. A cluster of computing devices, characterized in that, The cluster of computing devices includes at least one computing device, each computing device including a processor and a memory: The memory is configured to store instructions; The processor is configured to cause the cluster of computing devices to perform the method of any one of claims 1-7 according to the instructions.

16. A computer storage medium, comprising, The computer storage medium stores one or more instructions that when executed by one or more computers cause the one or more computers to perform the method of any one of claims 1-7.

17. A computer program product, characterised in that, The computer program product stores instructions that when executed by a computer cause the computer to perform the method of any one of claims 1-7.

Images