Micro-service management method based on cloud management platform and cloud management platform
By providing microservice configuration interfaces and SLA constraints in the cloud management platform, the cloud management platform can select appropriate deployment sites from multiple sites according to the needs of tenants, solving the problem of inaccurate deployment in the existing technology and achieving more Efficient resource utilization and user needs satisfaction.
Patent Information
- Application Number
- CN202311287719.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-06
- Filing Date
- 2023-09-28
- Publication Date
- 2024-12-06
AI Technical Summary
When deploying microservices across regions, existing cloud management platforms only consider the call relationship and performance factors between microservices, and cannot accurately meet users' cross-region deployment needs.
By providing a microservice configuration interface, allowing tenants to enter microservice configuration information, including region groups and service level agreement (SLA) constraints, the cloud management platform selects a site that meets SLA parameters from multiple sites based on this information and creates a site at that site Virtual instance deployment microservices.
Ensure the correct deployment of microservices, meet users' cross-regional deployment needs for applications, and improve resource utilization efficiency and user experience.
Smart Images

Figure CN119094595A_ABST
Abstract
Description
[0001] This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on June 6, 2023, with application number 202310664774.3 and invention name “A microservice deployment method based on cloud management platform and cloud management platform”, all contents of which are incorporated by reference in this application. Technical Field
[0002] The embodiments of the present application relate to the field of cloud technology, and in particular to a microservice management method based on a cloud management platform and a cloud management platform. Background Art
[0003] Cloud-native applications refer to scalable applications that can be built and run in the dynamic environment of cloud service systems (for example, public clouds, private clouds, and hybrid clouds, etc.). Considering various factors such as globalization, data security, and resource utilization, tenants (enterprises, individuals, etc.) increasingly hope that the cloud service systems provided by cloud vendors have the ability to deploy cloud-native applications across regions.
[0004] In the related art, the cloud service system includes a cloud management platform and multiple sites located in different geographical locations. After receiving a deployment request from a tenant for an application, the cloud management platform can determine all microservices included in the application based on the request. Then, the cloud management platform can deploy these microservices in different sites based on the calling relationship between these microservices and the performance of these microservices. In this way, the cloud management platform completes the cross-regional deployment of the application.
[0005] In the above process, since the cloud management platform deploys these multiple microservices only based on the calling relationship between these microservices and the performance of these microservices, the factors considered are relatively one-sided, and these microservices cannot be deployed in the correct site, and thus cannot accurately meet the user's cross-regional deployment requirements for applications. Summary of the invention
[0006] The embodiments of the present application provide a microservice management method and a cloud management platform based on a cloud management platform. The cloud management platform can correctly deploy multiple microservices in corresponding sites according to the instructions of the tenants, thereby accurately meeting the user's cross-regional deployment requirements for applications.
[0007] A first aspect of an embodiment of the present application provides a microservice management method based on a cloud management platform, where the cloud management platform is used to manage an infrastructure for providing cloud services, where the infrastructure includes multiple sites located in different geographical locations, and the method includes:
[0008] When a tenant needs to deploy an application, the cloud management platform can provide the tenant with a microservice configuration interface, so the tenant can input microservice configuration information into the microservice configuration interface. The microservice configuration information is used to indicate the regional group and the service level agreement (SLA) constraints for the regional group. The regional group includes multiple first microservices of the application (also referred to as multiple specific microservices of the application, such as business logic components and intermediate components of the application, etc.), and the SLA constraints include first SLA parameters that need to be met by multiple first microservices.
[0009] After receiving the microservice configuration information through the microservice configuration interface, the cloud management platform can obtain the regional group and SLA constraints based on the microservice configuration information. Based on the multiple first microservices included in the regional group, the cloud management platform can determine that the multiple first microservices need to be deployed in the same site, and use the first SLA parameters that the multiple first microservices included in the SLA constraints need to meet as the site selection criteria. Therefore, the cloud management platform can select a site that meets the first SLA parameters from multiple sites as the first site, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0010] It can be seen from the above method that when a tenant needs to deploy microservices of an application, the tenant can input microservice configuration information into the microservice configuration interface provided by the cloud management platform, wherein the microservice configuration information is used to indicate the regional group and the SLA constraints for the regional group, the regional group includes multiple first microservices, and the SLA constraints include the first SLA parameters that the multiple first microservices need to meet. After receiving the microservice configuration information, the cloud management platform can select a first site that meets the first SLA parameters from multiple sites based on the microservice configuration information, then create multiple first virtual instances in the first site, and then deploy multiple first microservices in the multiple first virtual instances. In the above process, since the regional group indicates that the tenant needs to deploy multiple first microservices in the same site, and the SLA constraints indicate the tenant's resource requirements for the sites where the multiple first microservices are located, it can be seen that the cloud management platform strictly follows the tenant's instructions to select the first site for deploying multiple first microservices, so the cloud management platform can correctly deploy multiple first microservices in the first site, thereby accurately meeting the user's cross-regional deployment requirements for applications.
[0011] In a possible implementation, the configuration information is also used to indicate a microservice topology structure, the microservice topology structure includes multiple first microservices and second microservices, the SLA constraint also includes a second SLA parameter that the multiple first microservices and the second microservices need to satisfy together, and the method also includes: if the site combination formed by the first site and the second site satisfies the second SLA parameter, then a second virtual instance is created in the second site, and the second microservice is deployed in the second virtual instance, and the multiple sites include the second site; if only the first site satisfies the second SLA parameter, then a second virtual instance is created in the first site, and the second microservice is deployed in the second virtual instance. In the aforementioned implementation, the microservice configuration information is not only used to indicate the regional group and the SLA constraint for the regional group, but also used to indicate the microservice topology structure, the microservice topology structure includes multiple first microservices and the second microservice (that is, the general microservice of the application), and the microservice topology structure indicates that the tenant indicates that the second microservice can be deployed in the first site with the multiple first microservices. Accordingly, the SLA constraint includes not only the first SLA parameter that the multiple first microservices need to satisfy, but also the second SLA parameter that the multiple first microservices and the second microservice need to satisfy together. Then, after the cloud management platform deploys multiple first microservices at the first site, considering the effective use of site resources, the cloud management platform can first detect whether there is a site combination that meets the second SLA parameters. If so, it means that the site combination composed of the first site and the second site meets the second SLA parameters. The cloud management platform creates a second virtual instance in the second site and deploys the second microservice in the second virtual instance. If not, only the first site can meet the second SLA parameters. The cloud management platform creates a second virtual instance in the first site and deploys the second microservice in the second virtual instance.
[0012] In one possible implementation, the configuration information is also used to indicate the site range specified by the tenant, the site range includes at least one site among the multiple sites, and based on the microservice configuration information, selecting the first site that meets the first SLA parameter from the multiple sites includes: based on the microservice configuration information, selecting the first site that meets the first SLA parameter from at least one site. In the aforementioned implementation, the microservice configuration information is not only used to indicate the regional group and the SLA constraints for the regional group, but also to indicate the site range, the site range includes at least one site among the multiple sites, and this at least one site is the site specified by the tenant. Then, the cloud management platform can obtain the regional group, the SLA constraints for the regional group, and the site range based on the microservice configuration information. Based on the multiple first microservices included in the regional group, the cloud management platform can determine that the multiple first microservices need to be deployed in the same site, use the first SLA parameters that the multiple first microservices included in the SLA constraints need to meet as the site selection criteria, and select the site to deploy the multiple first microservices from the site range. Therefore, the cloud management platform can select a site that meets the first SLA parameters from at least one site included in the site range as the first site, create multiple first virtual instances on the physical server of the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0013] In one possible implementation, the regional group also includes a third microservice, the multiple first microservices are microservices defined by the tenant, the third microservice is a microservice provided to the tenant by the cloud management platform, and based on the microservice configuration information, selecting a first site that meets the first SLA parameter from multiple sites includes: based on the microservice configuration information, determining a site that can provide the third microservice from multiple sites, and selecting a site that meets the first SLA parameter from the sites that can provide the third microservice as the first site. In the aforementioned implementation, the regional group indicated by the microservice configuration information includes not only multiple first microservices, but also a third microservice (that is, a cloud microservice). Then, the cloud management platform can obtain the regional group and the SLA constraints for the regional group based on the microservice configuration information. Based on the multiple first microservices and the third microservices included in the regional group, the cloud management platform can determine that the multiple first microservices and the third microservice need to be deployed in the same site, and use the first SLA parameters that the multiple first microservices included in the SLA constraints need to meet as the site selection criteria. Since the third microservice is a microservice provided by the cloud management platform to tenants, the cloud management platform can select a site that can provide the third microservice from multiple sites, and select a site that meets the first SLA parameters from the sites that can provide the third microservice as the first site, create multiple first virtual instances on the physical server of the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0014] In a possible implementation, multiple first microservices are microservices defined by tenants, and based on microservice configuration information, selecting a first site that meets the first SLA parameter from multiple sites includes: based on the microservice configuration information, determining a third microservice associated with the multiple first microservices from a preset microservice relationship template from the tenant, the third microservice being a microservice provided to the tenant by the cloud management platform; determining a site that can provide the third microservice from multiple sites, and selecting a site that meets the first SLA parameter from the site that can provide the third microservice as the first site. In the aforementioned implementation, the tenant can preset the microservice relationship template of the application at the cloud management platform in advance. Then, based on the microservice configuration information, the cloud management platform can obtain the regional group and the SLA constraints for the regional group, and determine the third microservice associated with the multiple first microservices in the regional group from the microservice relationship template, so the cloud management platform can determine that the multiple first microservices and the third microservice need to be deployed in the same site, and use the first SLA parameter that the multiple first microservices included in the SLA constraint need to meet as the site selection criterion. Since the third microservice is a microservice provided by the cloud management platform to tenants, the cloud management platform can select a site that can provide the third microservice from multiple sites, and select a site that meets the first SLA parameters from the sites that can provide the third microservice as the first site, create multiple first virtual instances on the physical server of the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0015] In one possible implementation, the method further includes: creating a third virtual instance in the first site, and deploying a third microservice in the third virtual instance. In the aforementioned implementation, after the cloud management platform deploys multiple first microservices in the first site, it can also deploy the third microservice in the first site.
[0016] In a possible implementation, the first virtual instance includes at least one of the following: a virtual machine or a container.
[0017] In one possible implementation, the multiple sites are multiple availability zones, multiple regions, or at least one edge site and at least one central site.
[0018] In a possible implementation manner, the first SLA parameter includes at least one of the following: communication delay, throughput, and processing time.
[0019] A second aspect of an embodiment of the present application provides a cloud management platform, which is used to manage an infrastructure for providing cloud services, wherein the infrastructure includes multiple sites located in different geographical locations, and the cloud management platform includes: an acquisition module, which is used to obtain microservice configuration information input by a tenant from a microservice configuration interface, wherein the microservice configuration information is used to indicate a regional group and a service level agreement (SLA) constraint for the regional group, wherein the regional group includes multiple first microservices, and the SLA constraint includes first SLA parameters that need to be satisfied by multiple first microservices; a first deployment module, which is used to select a first site that satisfies the first SLA parameters from multiple sites based on the microservice configuration information, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0020] It can be seen from the above cloud management platform that when a tenant needs to deploy microservices of an application, the tenant can input microservice configuration information into the microservice configuration interface provided by the cloud management platform, wherein the microservice configuration information is used to indicate the regional group and the SLA constraints for the regional group, the regional group includes multiple first microservices, and the SLA constraints include the first SLA parameters that the multiple first microservices need to meet. After receiving the microservice configuration information, the cloud management platform can select a first site that meets the first SLA parameters from multiple sites based on the microservice configuration information, then create multiple first virtual instances in the first site, and then deploy multiple first microservices in the multiple first virtual instances. In the above process, since the regional group indicates that the tenant needs to deploy multiple first microservices in the same site, and the SLA constraints indicate the tenant's resource requirements for the sites where the multiple first microservices are located, it can be seen that the cloud management platform strictly follows the tenant's instructions to select the first site for deploying multiple first microservices, so the cloud management platform can correctly deploy multiple first microservices in the first site, thereby accurately meeting the user's cross-regional deployment requirements for applications.
[0021] In one possible implementation, the configuration information is also used to indicate a microservice topology structure, the microservice topology structure includes multiple first microservices and second microservices, the SLA constraints also include second SLA parameters that need to be satisfied by the multiple first microservices and the second microservices, and the cloud management platform also includes: a second deployment module, used to: if the site combination formed by the first site and the second site satisfies the second SLA parameters, then create a second virtual instance in the second site and deploy the second microservice in the second virtual instance, and the multiple sites include the second site; if only the first site satisfies the second SLA parameters, then create a second virtual instance in the first site and deploy the second microservice in the second virtual instance.
[0022] In one possible implementation, the configuration information is also used to indicate a site range specified by the tenant, where the site range includes at least one site among multiple sites, and a first deployment module is used to select a first site that meets a first SLA parameter from at least one site based on the microservice configuration information.
[0023] In one possible implementation, the regional group further includes a third microservice, multiple first microservices are microservices defined by tenants, the third microservice is a microservice provided to tenants by the cloud management platform, and a first deployment module is used to determine a site that can provide the third microservice from multiple sites based on the microservice configuration information, and select a site that meets the first SLA parameters from the sites that can provide the third microservice as the first site.
[0024] In one possible implementation, multiple first microservices are microservices defined by tenants, and the first deployment module is used to: determine a third microservice associated with the multiple first microservices from a preset microservice relationship template derived from the tenant based on microservice configuration information, where the third microservice is a microservice provided to the tenant by the cloud management platform; determine a site that can provide the third microservice from multiple sites, and select a site that meets the first SLA parameters from the sites that can provide the third microservice as the first site.
[0025] In one possible implementation, the cloud management platform further includes: a third deployment module, configured to create a third virtual instance in the first site and deploy a third microservice in the third virtual instance.
[0026] In a possible implementation, the first virtual instance includes at least one of the following: a virtual machine or a container.
[0027] In one possible implementation, the multiple sites are multiple availability zones, multiple regions, or at least one edge site and at least one central site.
[0028] In a possible implementation manner, the first SLA parameter includes at least one of the following: communication delay, throughput, and processing time.
[0029] A third aspect of an embodiment of the present application provides a computing device cluster, the computing device cluster includes at least one computing device, each computing device includes a processor and a memory: the memory is used to store instructions; the processor is used to enable the computing device cluster to execute the method described in the first aspect or any possible implementation method of the first aspect according to the instructions.
[0030] A fourth aspect of an embodiment of the present application provides a computer storage medium, which stores one or more instructions. When the instructions are executed by one or more computers, the one or more computers implement the method described in the first aspect or any possible implementation method of the first aspect.
[0031] A fifth aspect of the embodiments of the present application provides a computer program product, which stores instructions. When the instructions are executed by a computer, the computer implements the method described in the first aspect or any possible implementation method of the first aspect.
[0032] In an embodiment of the present application, when a tenant needs to deploy an application's microservices, the tenant can input microservice configuration information into the microservice configuration interface provided by the cloud management platform, wherein the microservice configuration information is used to indicate a regional group and an SLA constraint for the regional group, the regional group includes multiple first microservices, and the SLA constraint includes the first SLA parameter that the multiple first microservices need to meet. After receiving the microservice configuration information, the cloud management platform can select a first site that meets the first SLA parameter from multiple sites based on the microservice configuration information, then create multiple first virtual instances in the first site, and then deploy multiple first microservices in the multiple first virtual instances. In the aforementioned process, since the regional group indicates that the tenant needs to deploy multiple first microservices in the same site, and the SLA constraint indicates the tenant's resource requirements for the sites where the multiple first microservices are located, it can be seen that the cloud management platform strictly follows the tenant's instructions to select the first site for deploying multiple first microservices, so the cloud management platform can correctly deploy multiple first microservices in the first site, thereby accurately meeting the user's cross-regional deployment requirements for applications. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] Figure 1 A schematic diagram of the structure of a cloud service system provided in an embodiment of the present application;
[0034] Figure 2 A flowchart of a microservice management method based on a cloud management platform provided in an embodiment of the present application;
[0035] Figure 3 A schematic diagram of a microservice relationship template provided for an embodiment of the present application;
[0036] Figure 4 A schematic diagram of microservice configuration information provided in an embodiment of the present application;
[0037] Figure 5 Another schematic diagram of a microservice management method based on a cloud management platform provided in an embodiment of the present application;
[0038] Figure 6 Another schematic diagram of microservice configuration information provided in an embodiment of the present application;
[0039] Figure 7 Another schematic diagram of a microservice management method based on a cloud management platform provided in an embodiment of the present application;
[0040] Figure 8 Another schematic diagram of microservice configuration information provided in an embodiment of the present application;
[0041] Fig. 9 Another schematic diagram of a microservice management method based on a cloud management platform provided in an embodiment of the present application;
[0042] Fig.10 Another schematic diagram of a microservice relationship template provided in an embodiment of the present application;
[0043] Fig.11 Another schematic diagram of microservice configuration information provided in an embodiment of the present application;
[0044] Fig.12 Another schematic diagram of a microservice management method based on a cloud management platform provided in an embodiment of the present application;
[0045] Fig.13 Another schematic diagram of microservice configuration information provided in an embodiment of the present application;
[0046] Fig.14 A schematic diagram of the structure of the cloud management platform provided in the embodiment of the present application;
[0047] Fig.15 A schematic diagram of a computing device provided in an embodiment of the present application;
[0048] Fig.16 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;
[0049] Fig.17 A schematic diagram of computer devices in a computer cluster provided in an embodiment of the present application being connected via a network. DETAILED DESCRIPTION
[0050] The embodiments of the present application provide a microservice management method and a cloud management platform based on a cloud management platform. The cloud management platform can correctly deploy multiple microservices in corresponding sites according to the instructions of the tenants, thereby accurately meeting the user's cross-regional deployment requirements for applications.
[0051] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.
[0052] Cloud-native applications refer to scalable applications that can be built and run in the dynamic environment of cloud service systems (for example, public clouds, private clouds, and hybrid clouds, etc.). Considering various factors such as globalization, data security, and resource utilization, tenants (enterprises, individuals, etc.) increasingly hope that the cloud service systems provided by cloud vendors have the ability to deploy cloud-native applications across regions.
[0053] In the related art, the cloud service system includes a cloud management platform and multiple sites located in different geographical locations. After receiving a deployment request from a tenant for an application, the cloud management platform can determine all the microservices contained in the application based on the request. Then, the cloud management platform can deploy these microservices in different sites based on the calling relationship between these microservices and the performance of these microservices. In this way, the cloud management platform completes the cross-regional deployment of the application. For example, suppose the tenant's application includes microservice A, microservice B, microservice C, microservice D, and microservice E. Based on the calling relationship and performance between these five microservices (for example, microservice A and microservice B often communicate, microservice C and microservice D often communicate, and microservice B and microservice C communicate less), the cloud management platform can deploy microservice A and microservice B at site 1, and deploy microservice C and microservice D at site B.
[0054] In the above process, since the cloud management platform deploys these multiple microservices only based on the calling relationship between these microservices and the performance of these microservices, the factors considered are relatively one-sided, and these microservices cannot be deployed in the correct site, and thus cannot accurately meet the user's cross-regional deployment requirements for applications.
[0055] In order to solve the above problems, an embodiment of the present application provides a microservice management method based on a cloud management platform, which can be implemented through a cloud management platform in a cloud service system. Figure 1 A schematic diagram of the structure of the cloud service system provided in the embodiment of the present application is as follows: Figure 1As shown in the figure, the cloud service system includes the infrastructure that can provide cloud services and the cloud management platform that manages these infrastructures. The cloud management platform and infrastructure are introduced separately below:
[0056] The cloud management platform can coordinate the management of virtual instances of multiple sites in the entire cloud service system (for example, selecting a physical server in the site, creating a virtual instance on the physical server, and deploying microservices in the virtual instance), and can also be open to tenants outside the system and respond to their requests. For example, the cloud management platform can provide various interfaces such as a login interface and a microservice configuration interface for access by the tenant's client (for example, the terminal device used by the tenant or the browser on the terminal device, etc.). Among them, the cloud management platform can authenticate the tenant's client through the login interface, and after successful authentication, the tenant's client can be allowed to log in to the cloud management platform. The cloud management platform can also allow the tenant's client to send microservice configuration information to the cloud management platform through the microservice configuration interface. Based on this configuration information, the cloud management platform can select a site for multiple microservices of a certain application specified by the tenant, and create multiple virtual instances for deploying these multiple microservices on the physical server in the site. Then, these virtual instances can run corresponding microservices to process the user's business, thereby meeting the user's business processing needs.
[0057] The infrastructure includes multiple sites located in different geographical locations that can be selected by the cloud management platform. Each site includes a certain number of physical servers and various devices such as network, storage, and power supply. Under the instruction of the tenant's client, the cloud management platform can select a site for the tenant from multiple sites and select at least one physical server in the site, so as to create multiple virtual instances (also called cloud instances) exclusively for the tenant on these physical servers, and deploy the microservices specified by the tenant on these multiple virtual instances. Among them, the multiple sites in the infrastructure can be presented in various forms. For example, the multiple sites can be multiple regions in the infrastructure, or multiple sites can be multiple availability zones in the infrastructure, or multiple sites can be at least one edge site and at least one central cloud site in the infrastructure, and so on.
[0058] Furthermore, virtual instances can also be presented in various forms, for example, a virtual instance can be a virtual machine (VM) on a physical server, or a container (docker) on a physical server, or a container in a VM on a physical server, etc. It should be noted that the cloud service system can communicate internally, that is, multiple virtual instances dedicated to tenants can communicate with each other. Since these virtual instances are deployed with multiple microservices specified by the tenants, the communication between multiple virtual instances dedicated to tenants can also be understood as the communication between multiple microservices specified by the tenants (also called mutual calls).
[0059] Since the cloud management platform can accurately deploy multiple microservices in a certain application specified by the user in the same site according to the instructions of the tenant, it is helpful for the cloud management platform to more accurately complete the tenant's cross-regional deployment requirements for the application. In order to further understand the workflow of the cloud management platform, the following will introduce the process through multiple embodiments. Figure 2 A flow chart of a microservice management method based on a cloud management platform provided in an embodiment of the present application is as follows: Figure 2 As shown, a first embodiment of the method includes:
[0060] 201. Acquire microservice configuration information input by a tenant from a microservice configuration interface, where the microservice configuration information is used to indicate a regional group and an SLA constraint for the regional group, where the regional group includes a plurality of first microservices, and the SLA constraint includes a first SLA parameter that the plurality of first microservices need to satisfy.
[0061] In this embodiment, when a tenant needs to deploy an application, the tenant can obtain the microservice relationship template of the application (also called a microservice directed acyclic graph). The microservice relationship template of the application includes all the microservices that make up the application (also called all components of the application, assuming that all microservices of the application are tenant-defined microservices) and the calling relationship between these microservices. The calling relationship between these microservices can be presented through multiple unidirectional paths, each of which represents a business of the application, and each unidirectional path contains at least two microservices.
[0062] Among the multiple unidirectional paths included in the microservice relationship template of the application, the tenant can select a unidirectional path as the key path based on its own business needs. The key path can include multiple first microservices (also called multiple specific microservices, such as business logic components and intermediate components in the key path) and at least one second microservice (also called general microservice, such as the entry component in the key path).
[0063] After determining the critical path, the tenant can log in to the cloud management platform through the client used by the tenant. The cloud management platform can provide a microservice configuration interface (for example, the configuration input bar of the microservice management interface, etc.) to the client used by the tenant, so the tenant can send microservice configuration information to the microservice configuration interface through the client, so that the cloud management platform receives the microservice configuration information sent by the tenant's client through the microservice configuration interface. The microservice configuration information is used to indicate the region group set by the tenant and the SLA constraints set by the tenant for the region group. The region group set by the tenant includes multiple first microservices in the critical path, and the SLA constraints include the first SLA parameters that need to be met by multiple first microservices. It should be noted that the region group set by the tenant indicates that the tenant needs to deploy multiple first microservices at the same site, and the SLA constraints set by the tenant indicate the tenant's resource requirements for the site where the multiple first microservices are located.
[0064] Specifically, the first SLA parameter may include at least one of the following: a communication delay that needs to be met by multiple first microservices, a throughput that needs to be met by multiple first microservices, and a (data) processing time that needs to be met by multiple first microservices, etc.
[0065] For example, Figure 3 and Figure 4 As shown ( Figure 3 A schematic diagram of a microservice relationship template provided in an embodiment of the present application, Figure 4 A schematic diagram of the microservice configuration information provided in the embodiment of the present application) assumes that a tenant has a web application. The microservice relationship template of the application describes all the microservices in the application and the calling relationships between these microservices. These calling relationships are presented as multiple one-way paths, including a one-way path representing the posting business and a one-way path representing the homepage viewing business, etc. The tenant can regard the one-way path of the posting business as a critical path based on business understanding. Figure 3 It can be seen that the key path includes five microservices: "nginx-web-server", "compose-post-service", "post-storage-service", "post-memc" and "post-mongo". Among them, "nginx-web-server" is the entry component, that is, the general microservice. "compose-post-service" and "post-storage-service" are business logic components, "post-memc" and "post-mongo" are intermediate components, and these four microservices are specific microservices.
[0066] Then, the tenant can log in to the cloud management platform through his browser. The cloud management platform can display the microservice management interface on the tenant's browser. The microservice management interface includes a configuration input field for the microservice. The tenant can enter the microservice configuration information in the configuration input field. Figure 4 It can be seen that the microservice configuration information includes the following:
[0067] (1) The tenant sets up a region group with the ID "post". The region group contains four specific microservices: "compose-post-service", "post-storage-service", "post-memc" and "post-mongo". The region group property (region-group-force) is set to strong binding (true), indicating that these four specific microservices must be set up in the same site.
[0068] (2) The tenant also sets SLA constraints for the zone group, where the SLA constraints include the communication latency (service-latency) of the four specific microservices, which are 20ms, 10ms, 15ms, and 20ms respectively. Of course, the SLA constraints can also include SLA parameters such as the throughput and data processing time of the four specific microservices, which are not shown here one by one.
[0069] In this way, the cloud management platform can receive the microservice configuration information entered by the tenant through the configuration input bar.
[0070] It should be understood that in this embodiment, only the content indicated by the microservice configuration information includes the regional group and the SLA constraints for the regional group for schematic introduction. In actual applications, the microservice configuration information may also include the tenant's personal information (including the tenant's ID, etc.), information about the application that the tenant needs to deploy (including multiple first microservices and images of the second microservice in the application, etc.), price constraints for the regional group (indicating the tenant's price requirements for the sites where the multiple first microservices and the second microservices are located), and capacity constraints for the regional group (indicating the tenant's requirements for communication resources, computing resources, and storage resources at the sites where the multiple first microservices and the second microservices are located), etc.
[0071] 202. Based on the microservice configuration information, select a first site that meets the first SLA parameter from the multiple sites, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0072] After the cloud management platform obtains the microservice configuration information, it can parse the microservice configuration information to obtain the regional group and the SLA constraints for the regional group. Based on the multiple first microservices included in the regional group, the cloud management platform can determine that the multiple first microservices need to be deployed in the same site, and the cloud management platform can use the first SLA parameters that the multiple first microservices included in the SLA constraints need to meet as the site selection criteria. Therefore, the cloud management platform can select a site that meets the first SLA parameters from multiple sites as the first site, create multiple first virtual instances on the physical server of the first site, and deploy multiple first microservices in the multiple first virtual instances (generally, one first virtual instance can deploy one first microservice).
[0073] As in the above example, after obtaining the microservice configuration information, the cloud management platform can select site 1 that can meet the SLA parameters of 20ms, 10ms, 15ms and 20ms from multiple sites, and create containers 1, 2, 3 and 4 in site 1, where container 1 is used to deploy "compose-post-service", container 2 is used to deploy "post-storage-service", container 3 is used to deploy "post-memc", and container 4 is used to deploy "post-mongo". In this way, the cloud management platform deploys these four specific microservices in the same site, that is, site 1.
[0074] It should be understood that in this embodiment, the first site selected by the cloud management platform not only satisfies the first SLA parameter in the SLA constraint, but also usually satisfies the aforementioned price constraint and capacity constraint, etc., which will not be expanded here.
[0075] The above is a detailed description of the first embodiment of the microservice management method based on the cloud management platform provided in the embodiments of the present application. The second embodiment of the method will be introduced below. Figure 5 Another flow chart of the microservice management method based on the cloud management platform provided in the embodiment of the present application is as follows: Figure 5 As shown, the second embodiment of the method includes:
[0076] 501. Obtain microservice configuration information input by the tenant from a microservice configuration interface, where the microservice configuration information is used to indicate a regional group, an SLA constraint for the regional group, and a microservice topology structure, where the regional group includes a plurality of first microservices, the microservice topology structure includes a plurality of first microservices and a second microservice, and the SLA constraint includes a first SLA parameter that needs to be satisfied by the plurality of first microservices, and a second SLA parameter that needs to be satisfied by the plurality of first microservices and the second microservices.
[0077] For an introduction to step 501, please refer to Figure 2 The relevant description of step 201 in the illustrated embodiment is not repeated here. It should be noted that the difference between step 501 and step 201 is that the microservice configuration information is not only used to indicate the regional group set by the tenant and the SLA constraint set by the tenant for the regional group, but also used to indicate the microservice topology set by the tenant.
[0078] Among them, the regional group set by the tenant includes multiple first microservices in the critical path, the microservice topology structure includes multiple first microservices and second microservices (that is, the critical path), and the SLA constraints include first SLA parameters that need to be satisfied by multiple first microservices, and second SLA parameters that need to be satisfied by multiple first microservices and second microservices. It should be noted that the regional group set by the tenant indicates that the tenant needs to deploy multiple first microservices at the same site, the SLA constraints set by the tenant indicate the tenant's resource requirements for the sites where the multiple first microservices are located, and the microservice topology structure set by the tenant indicates that the tenant indicates that the second microservice can be deployed at the same site with the multiple first microservices.
[0079] Specifically, the second SLA parameter may include at least one of the following: the communication delay that needs to be met by multiple first microservices and the second microservices (that is, the communication delay that needs to be met by the critical path), the throughput that needs to be met by multiple first microservices and the second microservices, and the (data) processing time that needs to be met by multiple first microservices and the second microservices, etc.
[0080] For example, Figure 6 As shown ( Figure 6 Another schematic diagram of microservice configuration information provided in an embodiment of the present application, Figure 6 is Figure 4 Tenants can log in to the cloud management platform through their browsers. The cloud management platform can display the microservice management interface on the tenant's browser. The microservice management interface includes a configuration input bar for microservices. Tenants can enter microservice configuration information in the configuration input bar. Figure 6 It can be seen that the microservice configuration information includes the following:
[0081] (1) The tenant sets up a region group with the ID "post". The region group contains four specific microservices: "compose-post-service", "post-storage-service", "post-memc" and "post-mongo". The region group property (region-group-force) is set to strong binding (true), indicating that these four specific microservices must be set up in the same site.
[0082] (2) The tenant also sets up a microservice topology, which includes a key path, which includes the general microservice "nginx-web-server" and four specific microservices: "compose-post-service", "post-storage-service", "post-memc" and "post-mongo".
[0083] (3) The tenant also sets SLA constraints for the regional group. The SLA constraints include the communication delays of the four specific microservices, which are 20ms, 10ms, 15ms, and 20ms. The SLA constraints also include the communication delay of the critical path, which is 100ms. Of course, the SLA constraints can also include the throughput and data processing time of the four specific microservices, the throughput and data processing time of the critical path, etc., which are not shown here one by one.
[0084] In this way, the cloud management platform can receive the microservice configuration information entered by the tenant through the configuration input bar.
[0085] It should be understood that in this embodiment, the microservice topology structure only includes the critical path for schematic introduction. In actual applications, the microservice topology structure may also include one or more paths other than the critical path in the microservice relationship template. Therefore, the microservice topology structure indicates that the tenant indicates that the second microservice and the microservices on the remaining paths can be deployed at the same site with multiple first microservices.
[0086] 502. Based on the microservice configuration information, select a first site that meets the first SLA parameter from the multiple sites, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0087] For an introduction to step 502, please refer to Figure 2 The relevant description of step 202 in the illustrated embodiment will not be repeated here.
[0088] 503. Detect whether there is a site combination that meets the second SLA parameter.
[0089] 504. If the site combination formed by the first site and the second site meets the second SLA parameter, a second virtual instance is created in the second site, and a second microservice is deployed in the second virtual instance, and the multiple sites include the second site.
[0090] 505. If only the first site meets the second SLA parameter, create a second virtual instance in the first site and deploy the second microservice in the second virtual instance.
[0091] After deploying multiple first microservices at the first site, based on the microservice topology, the cloud management platform can determine that the second microservice and the multiple first microservices can be deployed at the first site. Considering the effective use of site resources, the cloud management platform can first detect whether there is a site combination (including the first site) that meets the second SLA parameters. If so, it means that the site combination consisting of the first site and the second site (the remaining sites among the multiple sites except the first site) meets the second SLA parameters. The cloud management platform creates a second virtual instance at the second site and deploys the second microservice in the second virtual instance. If not, only the first site can meet the second SLA parameters. The cloud management platform creates a second virtual instance at the first site and deploys the second microservice in the second virtual instance.
[0092] Still as in the above example, after obtaining the microservice configuration information, the cloud management platform can select site 1 from multiple sites and create containers 1, 2, 3 and 4 in site 1, where container 1 is used to deploy "compose-post-service", container 2 is used to deploy "post-storage-service", container 3 is used to deploy "post-memc", and container 4 is used to deploy "post-mongo".
[0093] Since the microservice topology contains a critical path, and the communication delay of the critical path is 100ms, the cloud management platform can determine whether site 2 exists, so that the communication delay of the critical path deployed on site 2 and site 1 can meet 100ms. If yes, it means that the site combination of site 1 and site 2 can meet the tenant's communication delay requirements for the critical path, so the cloud management platform can create container 5 in site 2, and container 5 is used to deploy "nginx-web-server". If not, it means that 100ms is too large, and only site 1 itself can meet the tenant's communication delay requirements for the critical path, so the cloud management platform can create container 5 in site 1, and container 5 is used to deploy "nginx-web-server".
[0094] It should be understood that in this embodiment, the site combination of the first site and the second site selected by the cloud management platform not only satisfies the second SLA parameter in the SLA constraint, but also usually satisfies the aforementioned price constraint and capacity constraint, etc., which will not be expanded here.
[0095] The above is a detailed description of the second embodiment of the microservice management method based on the cloud management platform provided in the embodiment of the present application. The third embodiment of the method will be introduced below. Figure 7 Another flow chart of the microservice management method based on the cloud management platform provided in the embodiment of the present application is as follows: Figure 7As shown, the third embodiment of the method includes:
[0096] 701. Obtain microservice configuration information input by the tenant from a microservice configuration interface, where the microservice configuration information is used to indicate a regional group, an SLA constraint for the regional group, and a site range, where the regional group includes multiple first microservices, the SLA constraint includes first SLA parameters that the multiple first microservices need to satisfy, and the site range includes at least one site among the multiple sites.
[0097] For an introduction to step 701, please refer to Figure 2 The relevant description of step 201 in the illustrated embodiment is not repeated here. It should be noted that the difference between step 701 and step 201 is that the microservice configuration information is not only used to indicate the regional group set by the tenant and the SLA constraint set by the tenant for the regional group, but also used to indicate the site range set by the tenant.
[0098] The site range set by the tenant includes at least one site among the multiple sites, and the at least one site is a privately designated site of the tenant.
[0099] For example, Figure 8 As shown ( Figure 8 Another schematic diagram of microservice configuration information provided in an embodiment of the present application, Figure 6 is Figure 4 Tenants can log in to the cloud management platform through their browsers. The cloud management platform can display the microservice management interface on the tenant's browser. The microservice management interface includes a configuration input bar for microservices. Tenants can enter microservice configuration information in the configuration input bar. Figure 6 It can be seen that the microservice configuration information includes the following:
[0100] (1) The tenant sets up a region group with the ID "post". The region group contains four specific microservices: "compose-post-service", "post-storage-service", "post-memc" and "post-mongo". The region group property (region-group-force) is set to strong binding (true), indicating that these four specific microservices must be set up in the same site.
[0101] (2) The tenant also sets the site scope (group-region). Based on their business needs, the tenant can set the site scope to "on-promises", that is, the tenant's private or designated site. For example, the tenant's designated site scope is the site in the South China region of the cloud management platform. Another example is that the tenant's designated site scope is the tenant's private site among multiple sites managed by the cloud management platform.
[0102] (3) The tenant also sets SLA constraints for the regional group. The SLA constraints include the communication delays of the four specific microservices, which are 20ms, 10ms, 15ms, and 20ms. The SLA constraints also include the communication delay of the critical path, which is 100ms. Of course, the SLA constraints can also include the throughput and data processing time of the four specific microservices, the throughput and data processing time of the critical path, etc., which are not shown here one by one.
[0103] In this way, the cloud management platform can receive the microservice configuration information entered by the tenant through the configuration input bar.
[0104] 702. Based on the microservice configuration information, select a first site that meets the first SLA parameter from at least one site, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0105] After the cloud management platform obtains the microservice configuration information, it can parse the microservice configuration information to obtain the regional group, the SLA constraints for the regional group, and the site range. Based on the multiple first microservices included in the regional group, the cloud management platform can determine that the multiple first microservices need to be deployed in the same site, and the cloud management platform can use the first SLA parameters that the multiple first microservices included in the SLA constraints need to meet as the site selection criteria, and the cloud management platform can select the site to deploy the multiple first microservices from the site range. Therefore, the cloud management platform can select a site that meets the first SLA parameters from at least one site included in the site range as the first site, create multiple first virtual instances on the physical server of the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0106] Still as in the above example, after obtaining the microservice configuration information, since the site range specified by the tenant is the site in South China, the cloud management platform can select site 1 that can meet the SLA parameters of 20ms, 10ms, 15ms and 20ms from the sites in South China, and create containers 1, 2, 3 and 4 in site 1, where container 1 is used to deploy "compose-post-service", container 2 is used to deploy "post-storage-service", container 3 is used to deploy "post-memc", and container 4 is used to deploy "post-mongo".
[0107] The above is a detailed description of the third embodiment of the microservice management method based on the cloud management platform provided in the embodiments of the present application. The fourth embodiment of the method will be introduced below. Fig. 9Another flow chart of the microservice management method based on the cloud management platform provided in the embodiment of the present application is as follows: Fig. 9 As shown, the fourth embodiment of the method includes:
[0108] 901. Obtain microservice configuration information input by the tenant from a microservice configuration interface, where the microservice configuration information is used to indicate a regional group and an SLA constraint for the regional group. The regional group includes a plurality of first microservices and a third microservice. The SLA constraint includes a first SLA parameter that the plurality of first microservices need to satisfy. The plurality of first microservices are microservices defined by the tenant, and the third microservice is a microservice provided by the cloud management platform to the tenant.
[0109] In this embodiment, when a tenant needs to deploy an application, the tenant can obtain the microservice relationship template of the application (also called a microservice directed acyclic graph). The microservice relationship template of the application includes all the microservices that make up the application (also called all components of the application, assuming that all microservices of the application include tenant-defined microservices and microservices provided to the tenant by the cloud management platform) and the calling relationship between these microservices. The calling relationship between these microservices can be presented through multiple unidirectional paths, each of which represents a business of the application, and each unidirectional path contains at least two microservices.
[0110] Among the multiple unidirectional paths included in the microservice relationship template of the application, the tenant can select a unidirectional path as the key path based on its own business needs. The key path can include multiple first microservices (also called multiple specific microservices, such as business logic components in the key path), at least one second microservice (also called a general microservice, such as an entry component in the key path), and at least one third microservice (also called a cloud microservice, such as an intermediate component in the key path).
[0111] After determining the critical path, the tenant can log in to the cloud management platform through the client used by the tenant. The cloud management platform can provide a microservice configuration interface to the client used by the tenant. Therefore, the tenant can send microservice configuration information to the microservice configuration interface through the client, so that the cloud management platform receives the microservice configuration information sent by the tenant's client through the microservice configuration interface. The microservice configuration information is used to indicate the regional group set by the tenant and the SLA constraints set by the tenant for the regional group. The regional group set by the tenant includes multiple first microservices and third microservices in the critical path, and the SLA constraints include the first SLA parameters that need to be met by multiple first microservices. It should be noted that the regional group set by the tenant indicates that the tenant needs to deploy multiple first microservices and third microservices at the same site, and the SLA constraints set by the tenant indicate the tenant's resource requirements for the sites where the multiple first microservices are located.
[0112] For example, Fig.10 and Fig.11 As shown ( Fig.10 Another schematic diagram of a microservice relationship template provided in an embodiment of the present application, Fig.11 Another schematic diagram of the microservice configuration information provided in the embodiment of the present application) assumes that the tenant has a web application. The microservice relationship template of the application describes all the microservices in the application and the calling relationships between these microservices. These calling relationships are presented as multiple one-way paths, including a one-way path representing the posting business and a one-way path representing the homepage viewing business, etc. The tenant can regard the one-way path of the posting business as a critical path based on business understanding. Fig.10 It can be seen that the key path includes five microservices: "nginx-web-server", "compose-post-service", "post-storage-service", "DCS-memcached", and "Nosql-mongodb". Among them, "nginx-web-server" is the entry component, that is, the general microservice. "compose-post-service" and "post-storage-service" are business logic components, that is, specific microservices, and "DCS-memcached" and "Nosql-mongodb" are intermediate components, that is, cloud microservices (microservices that the cloud management platform can provide on its own).
[0113] Then, the tenant can log in to the cloud management platform through his browser. The cloud management platform can display the microservice management interface on the tenant's browser. The microservice management interface includes a configuration input field for the microservice. The tenant can enter the microservice configuration information in the configuration input field. Fig.11 It can be seen that the microservice configuration information includes the following:
[0114] (1) The tenant sets up a region group with the ID "post". The region group contains two specific microservices, "compose-post-service" and "post-storage-service", as well as two cloud microservices, "DCS-memcached" and "Nosql-mongodb". The region group property (region-group-force) is set to strong binding (true), indicating that these four microservices must be set up in the same site.
[0115] (2) The tenant also sets an SLA constraint for the zone group, where the SLA constraint includes the communication latency (service-latency) of the two specific microservices, which are 20ms and 10ms respectively. Of course, the SLA constraint can also include other SLA parameters such as the throughput and data processing time of the two specific microservices, which are not shown here one by one.
[0116] In this way, the cloud management platform can receive the microservice configuration information entered by the tenant through the configuration input bar.
[0117] It should be understood that in this embodiment, since the third microservice is a microservice provided by the cloud management platform to the tenant, the SLA parameters that the third microservice needs to meet have been set in advance and do not need to be set by the tenant, which can reduce the tenant's operations.
[0118] 902. Based on the microservice configuration information, determine a site that can provide a third microservice from multiple sites, select a site that meets the first SLA parameters from the sites that can provide the third microservice as a first site, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0119] 903. Create a third virtual instance in the first site, and deploy a third microservice in the third virtual instance.
[0120] After the cloud management platform obtains the microservice configuration information, it can parse the microservice configuration information to obtain the regional group and the SLA constraints for the regional group. Based on the multiple first microservices and third microservices included in the regional group, the cloud management platform can determine that the multiple first microservices and the third microservices need to be deployed in the same site, and the cloud management platform can use the first SLA parameters that the multiple first microservices included in the SLA constraints need to meet as the site selection criteria. Since the third microservice is a microservice provided by the cloud management platform to tenants, the cloud management platform can select a site that can provide the third microservice from multiple sites (which part of the multiple sites can provide the third microservice and which part of the sites cannot provide the third microservice are all set in advance by the cloud management platform), and select a site that meets the first SLA parameters from the site that can provide the third microservice as the first site, create multiple first virtual instances on the physical server of the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0121] As in the above example, after obtaining the microservice configuration information, since the sites that can provide the two cloud microservices "DCS-memcached" and "Nosql-mongodb" have been determined among multiple sites, the cloud management platform can select site 1 that can meet the SLA parameters of 20ms, 10ms, etc. from these sites, and create containers 1, 2, 3, and 4 in site 1, where container 1 is used to deploy "compose-post-service", container 2 is used to deploy "post-storage-service", container 3 is used to deploy "DCS-memcached", and container 4 is used to deploy "Nosql-mongodb". In this way, the cloud management platform deploys these four microservices in the same site, that is, site 1.
[0122] The above is a detailed description of the fourth embodiment of the microservice management method based on the cloud management platform provided in the embodiment of the present application. The fourth embodiment of the method will be introduced below. Fig.12 Another flow chart of the microservice management method based on the cloud management platform provided in the embodiment of the present application is as follows: Fig.12 As shown, the fifth embodiment of the method includes:
[0123] 1201. Obtain microservice configuration information input by the tenant from a microservice configuration interface. The microservice configuration information is used to indicate a regional group and an SLA constraint for the regional group. The regional group includes a plurality of first microservices. The SLA constraint includes a first SLA parameter that the plurality of first microservices need to satisfy. The plurality of first microservices are microservices defined by the tenant.
[0124] For an introduction to step 1201, please refer to Fig. 9 The relevant description of step 901 in the illustrated embodiment is not repeated here. It should be noted that the difference between step 1201 and step 901 is that the regional group indicated by the microservice configuration information only includes multiple first microservices, and does not include the third microservice, and the tenant has preset the microservice relationship template of the application in the cloud management platform before sending the microservice configuration information to the cloud management platform.
[0125] For example, Fig.13 As shown ( Fig.13 Another schematic diagram of the microservice configuration information provided in the embodiment of the present application) is shown in Fig.10 Based on the above, tenants can log in to the cloud management platform through their browsers. The cloud management platform can display the microservice management interface on the tenant's browser. The microservice management interface includes a configuration input field for microservices. Tenants can enter microservice configuration information in the configuration input field. Fig.13 It can be seen that the microservice configuration information includes the following:
[0126] (1) The tenant sets up a region group with the ID "post". The region group contains two specific microservices, "compose-post-service" and "post-storage-service". The region group property (region-group-force) is set to strong binding (true), indicating that the two microservices must be set up in the same site.
[0127] (2) The tenant also sets an SLA constraint for the zone group, where the SLA constraint includes the communication latency (service-latency) of the two specific microservices, which are 20ms and 10ms respectively. Of course, the SLA constraint can also include other SLA parameters such as the throughput and data processing time of the two specific microservices, which are not shown here one by one.
[0128] In this way, the cloud management platform can receive the microservice configuration information entered by the tenant through the configuration input bar.
[0129] 1202. Based on the microservice configuration information, determine a third microservice associated with the plurality of first microservices from a preset microservice relationship template derived from the tenant, where the third microservice is a microservice provided by the cloud management platform to the tenant.
[0130] After receiving the microservice configuration information, the cloud management platform can parse the microservice configuration information to obtain the regional group and the SLA constraints for the regional group. Although the regional group set by the tenant does not include the third microservice, the cloud management platform can obtain the preset microservice relationship template and determine the third microservice associated with the multiple first microservices in the regional group from the microservice relationship template (because the multiple first microservices and the third microservice constitute a critical path). Therefore, the cloud management platform can also determine that the multiple first microservices and the third microservice need to be set in the same site.
[0131] As in the above example, after receiving the microservice configuration information, the cloud management platform can determine that the tenant's regional group contains the two specific microservices "compose-post-service" and "post-storage-service". Then, the cloud management platform can Fig.10 In the microservice relationship template shown, the two cloud microservices "DCS-memcached" and "Nosql-mongodb" associated with "compose-post-service" and "post-storage-service" are determined. Therefore, the cloud management platform can determine that these four microservices need to be deployed in the same site.
[0132] 1203. Determine a site that can provide the third microservice from the multiple sites, select a site that meets the first SLA parameters from the sites that can provide the third microservice as the first site, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances.
[0133] 1204. Create a third virtual instance in the first site, and deploy a third microservice in the third virtual instance.
[0134] For an introduction to step 1203 and step 1204, please refer to Fig. 9 The relevant description parts of step 902 and step 903 in the illustrated embodiment will not be repeated here.
[0135] In an embodiment of the present application, when a tenant needs to deploy an application's microservices, the tenant can input microservice configuration information into the microservice configuration interface provided by the cloud management platform, wherein the microservice configuration information is used to indicate a regional group and an SLA constraint for the regional group, the regional group includes multiple first microservices, and the SLA constraint includes the first SLA parameter that the multiple first microservices need to meet. After receiving the microservice configuration information, the cloud management platform can select a first site that meets the first SLA parameter from multiple sites based on the microservice configuration information, then create multiple first virtual instances in the first site, and then deploy multiple first microservices in the multiple first virtual instances. In the aforementioned process, since the regional group indicates that the tenant needs to deploy multiple first microservices in the same site, and the SLA constraint indicates the tenant's resource requirements for the sites where the multiple first microservices are located, it can be seen that the cloud management platform strictly follows the tenant's instructions to select the first site for deploying multiple first microservices, so the cloud management platform can correctly deploy multiple first microservices in the first site, thereby accurately meeting the user's cross-regional deployment requirements for applications.
[0136] Furthermore, in an embodiment of the present application, the microservice configuration information can also be used to indicate a microservice topology structure, and the microservice topology structure includes multiple first microservices and second microservices. Since the microservice topology structure indicates that the tenant indicates that multiple first microservices and second microservices can be deployed in the same site, the cloud management platform can strictly follow the tenant's instructions and flexibly deploy the second microservice in the first site or the second site according to the SLA constraints based on the deployment of multiple first microservices in the first site, which can further accurately meet the user's cross-regional deployment requirements for applications.
[0137] Furthermore, in the embodiment of the present application, the regional group may include multiple first microservices and third microservices, the first microservice is a user-defined microservice, and the third microservice is a microservice provided to the tenant by the cloud management platform. Since the regional group indicates that the tenant needs to deploy multiple first microservices and third microservices in the same site, the cloud management platform can strictly follow the instructions of the tenant, select the first site from the sites that can provide the third microservice, and correctly deploy the multiple first microservices and third microservices in the first site, which can further accurately meet the user's cross-regional deployment requirements for applications.
[0138] Furthermore, in an embodiment of the present application, the site range for selecting the first site can be specified by the tenant, which can not only accurately meet the user's cross-regional deployment requirements for the application, but also meet the user's data security requirements for the application, thereby improving the user experience.
[0139] The above is a detailed description of the microservice management method based on the cloud management platform provided in the embodiment of the present application. The cloud management platform provided in the embodiment of the present application will be introduced below. Fig.14 A schematic diagram of the structure of the cloud management platform provided in the embodiment of the present application is shown in FIG. Fig.14 As shown in the figure, the cloud management platform is used to manage the infrastructure that provides cloud services. The infrastructure includes multiple sites located in different geographical locations. The cloud management platform includes:
[0140] The acquisition module 1401 is used to obtain microservice configuration information input by the tenant from the microservice configuration interface, where the microservice configuration information is used to indicate a regional group and a service level agreement SLA constraint for the regional group, where the regional group includes multiple first microservices, and the SLA constraint includes first SLA parameters that the multiple first microservices need to satisfy; for example, the acquisition module 1401 can be used to implement Figure 2 Step 201 in the illustrated embodiment.
[0141] The first deployment module 1402 is used to select a first site that meets the first SLA parameter from multiple sites based on the microservice configuration information, create multiple first virtual instances in the first site, and deploy multiple first microservices in the multiple first virtual instances. For example, the first deployment module 1402 can be used to implement Figure 2 Step 202 in the illustrated embodiment.
[0142] In an embodiment of the present application, when a tenant needs to deploy an application's microservices, the tenant can input microservice configuration information into the microservice configuration interface provided by the cloud management platform, wherein the microservice configuration information is used to indicate a regional group and an SLA constraint for the regional group, the regional group includes multiple first microservices, and the SLA constraint includes the first SLA parameter that the multiple first microservices need to meet. After receiving the microservice configuration information, the cloud management platform can select a first site that meets the first SLA parameter from multiple sites based on the microservice configuration information, then create multiple first virtual instances in the first site, and then deploy multiple first microservices in the multiple first virtual instances. In the aforementioned process, since the regional group indicates that the tenant needs to deploy multiple first microservices in the same site, and the SLA constraint indicates the tenant's resource requirements for the sites where the multiple first microservices are located, it can be seen that the cloud management platform strictly follows the tenant's instructions to select the first site for deploying multiple first microservices, so the cloud management platform can correctly deploy multiple first microservices in the first site, thereby accurately meeting the user's cross-regional deployment requirements for applications.
[0143] In one possible implementation, the configuration information is also used to indicate a microservice topology structure, the microservice topology structure includes multiple first microservices and second microservices, the SLA constraint also includes multiple first microservices and second microservices that need to jointly meet the second SLA parameters, and the cloud management platform also includes: a second deployment module, used to: if the site combination formed by the first site and the second site meets the second SLA parameters, then create a second virtual instance in the second site and deploy the second microservice in the second virtual instance, and the multiple sites include the second site; if only the first site meets the second SLA parameters, then create a second virtual instance in the first site and deploy the second microservice in the second virtual instance. For example, the acquisition module 1401 can also be used to implement Figure 5 In step 501 of the embodiment shown, the first deployment module 1402 can also be used to implement Figure 5 In step 502 of the illustrated embodiment, the second deployment module may be used to implement Figure 5 Steps 503 to 505 in the illustrated embodiment.
[0144] In a possible implementation, the configuration information is further used to indicate a site range specified by the tenant, the site range includes at least one site among the multiple sites, and the first deployment module 1402 is used to select a first site that meets the first SLA parameter from the at least one site based on the microservice configuration information. Figure 7 In step 701 of the embodiment shown, the first deployment module can also be used to implement Figure 7 Step 702 in the illustrated embodiment.
[0145] In a possible implementation, the regional group further includes a third microservice, the plurality of first microservices are microservices defined by the tenant, the third microservice is a microservice provided by the cloud management platform to the tenant, and the first deployment module 1402 is used to determine a site that can provide the third microservice from a plurality of sites based on the microservice configuration information, and select a site that meets the first SLA parameter from the sites that can provide the third microservice as the first site. For example, the acquisition module 1401 can also be used to implement Fig. 9 In step 901 of the embodiment shown, the first deployment module can also be used to implement Fig. 9 Step 902 in the illustrated embodiment.
[0146] In a possible implementation, the multiple first microservices are microservices defined by the tenant, and the first deployment module is used to: determine a third microservice associated with the multiple first microservices from a preset microservice relationship template from the tenant based on the microservice configuration information, where the third microservice is a microservice provided to the tenant by the cloud management platform; determine a site that can provide the third microservice from multiple sites, and select a site that meets the first SLA parameter from the sites that can provide the third microservice as the first site. For example, the acquisition module 1401 can also be used to implement Fig.12 In step 1201 of the embodiment shown, the first deployment module can also be used to implement Fig.12 Step 1202 in the illustrated embodiment.
[0147] In one possible implementation, the cloud management platform further includes: a third deployment module, which is used to create a third virtual instance in the first site and deploy a third microservice in the third virtual instance. For example, the third deployment module can also be used to implement Fig. 9 Step 903 in the illustrated embodiment or Fig.12 Step 1203 in the illustrated embodiment.
[0148] In a possible implementation, the first virtual instance includes at least one of the following: a virtual machine or a container.
[0149] In one possible implementation, the multiple sites are multiple availability zones, multiple regions, or at least one edge site and at least one central site.
[0150] In a possible implementation manner, the first SLA parameter includes at least one of the following: communication delay, throughput, and processing time.
[0151] It should be noted that the information interaction, implementation process, etc. between the modules / units of the above-mentioned device are based on the same concept as the method embodiment of the present application, and the technical effects they bring are the same as those of the method embodiment of the present application. For specific contents, please refer to the description in the method embodiment shown above in the embodiment of the present application, and will not be repeated here.
[0152] See also Fig.15 , Fig.15 A schematic diagram of a computing device provided in an embodiment of the present application. Fig.15 As shown, the computing device 1500 (which can be used to present the aforementioned cloud management platform) includes: a processor 1501, a memory 1502, a communication interface 1503 and a bus 1504. The processor 1501, the memory 1502 and the communication interface 1503 are coupled via a bus (not marked in the figure). The memory 1502 stores instructions. When the execution instructions in the memory 1502 are executed, the computing device 1500 executes the method executed by the cloud management platform in the above method embodiment.
[0153] The computing device 1500 may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASIC), or one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
[0154] The processor 1501 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.
[0155] The memory 1502 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0156] The memory 1502 stores executable program codes, and the processor 1501 executes the executable program codes to respectively implement the functions of the aforementioned acquisition module and the first deployment module, thereby implementing the aforementioned microservice management method based on the cloud management platform. That is, the memory 1502 stores instructions for executing the aforementioned microservice management method based on the cloud management platform.
[0157] The communication interface 1503 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 1500 and other devices or a communication network.
[0158] In addition to the data bus, the bus 1504 may also include a power bus, a control bus, and a status signal bus. The bus may 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 may be divided into an address bus, a data bus, a control bus, etc.
[0159] See also Fig.16 , Fig.16 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application. Fig.16 As shown, the computing device cluster 1600 includes at least one computing device 1500 .
[0160] like Fig.16 As shown, the computing device cluster 1600 includes at least one computing device 1500. The memory 1502 in one or more computing devices 1500 in the computing device cluster 1600 may store the same instructions for executing the above-mentioned microservice management method based on the cloud management platform.
[0161] In some possible implementations, the memory 1502 of one or more computing devices 1500 in the computing device cluster 1600 may also respectively store some instructions for executing the microservice management method based on the cloud management platform. In other words, the combination of one or more computing devices 1500 can jointly execute the microservice management method based on the cloud management platform.
[0162] It should be noted that the memory 1502 in different computing devices 1500 in the computing device cluster 1600 may store different instructions, which are respectively used to execute part of the functions of the above-mentioned cloud management platform. That is, the instructions stored in the memory 1502 in different computing devices 1500 may implement the functions of one or more modules such as the acquisition module and the first deployment module.
[0163] In some possible implementations, one or more computing devices 1500 in the computing device cluster 1600 may be connected via a network, which may be a wide area network or a local area network.
[0164] See also Fig.17 , Fig.17 A schematic diagram of computer devices in a computer cluster provided in an embodiment of the present application being connected via a network. Fig.17 As shown, two computing devices 1500A and 1500B are connected via a network. Specifically, they are connected to the network via a communication interface in each computing device.
[0165] In a possible implementation, the memory in the computing device 1500A stores instructions for executing functions of the acquisition module and other modules. Meanwhile, the memory in the computing device 1500B stores instructions for executing functions of the first deployment module and other modules.
[0166] It should be understood that Fig.17 The functions of computing device 1500A shown in FIG. 1 may also be completed by multiple computing devices. Similarly, the functions of computing device 1500B may also be completed by multiple computing devices.
[0167] The embodiment of the present application also relates to a computer storage medium, in which a program for signal processing is stored. When the program is run on a computer, the computer executes the following steps: Figure 2 , Figure 5 , Figure 7 , Fig. 9 as well as Fig.12 The steps performed by the cloud management platform in the illustrated embodiment.
[0168] The present application also relates to a computer program product, which stores instructions, which, when executed by a computer, enable the computer to execute the following Figure 2 , Figure 5 , Figure 7 , Fig. 9 as well as Fig.12 The steps performed by the cloud management platform in the illustrated embodiment.
[0169] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0170] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0171] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0172] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0173] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.
Claims
1. A microservice management method based on a cloud management platform, characterized in that: The cloud management platform is used to manage an infrastructure for providing cloud services, wherein the infrastructure includes a plurality of sites located in different geographical locations. The method includes: Acquire microservice configuration information input by the tenant from a microservice configuration interface, where the microservice configuration information is used to indicate a regional group and a service level agreement (SLA) constraint for the regional group, where the regional group includes a plurality of first microservices, and the SLA constraint includes a first SLA parameter that the plurality of first microservices need to satisfy; Based on the microservice configuration information, a first site that meets the first SLA parameter is selected from the multiple sites, multiple first virtual instances are created in the first site, and the multiple first microservices are deployed in the multiple first virtual instances.
2. The method according to claim 1, characterized in that The configuration information is further used to indicate a microservice topology structure, the microservice topology structure includes the plurality of first microservices and the second microservice, the SLA constraint further includes a second SLA parameter that the plurality of first microservices and the second microservice need to satisfy together, and the method further includes: If the site combination formed by the first site and the second site meets the second SLA parameter, creating a second virtual instance in the second site, and deploying the second microservice in the second virtual instance, the multiple sites including the second site; If only the first site meets the second SLA parameter, the second virtual instance is created in the first site, and the second microservice is deployed in the second virtual instance.
3. The method according to claim 1 or 2, characterized in that: The configuration information is further used to indicate a site range specified by the tenant, the site range includes at least one site among the multiple sites, and the selecting, based on the microservice configuration information, a first site that satisfies the first SLA parameter from the multiple sites includes: Based on the microservice configuration information, a first site that meets the first SLA parameter is selected from the at least one site.
4. The method according to any one of claims 1 to 3, characterized in that: The regional group further includes a third microservice, the plurality of first microservices are microservices defined by a tenant, the third microservice is a microservice provided by the cloud management platform to the tenant, and the selecting, based on the microservice configuration information, a first site that meets the first SLA parameter from the plurality of sites includes: Based on the microservice configuration information, a site that can provide the third microservice is determined from the multiple sites, and a site that meets the first SLA parameters is selected as the first site from the sites that can provide the third microservice.
5. The method according to any one of claims 1 to 3, characterized in that: The multiple first microservices are microservices defined by a tenant, and selecting a first site that meets the first SLA parameter from the multiple sites based on the microservice configuration information includes: Based on the microservice configuration information, determine a third microservice associated with the plurality of first microservices from a preset microservice relationship template derived from the tenant, wherein the third microservice is a microservice provided by the cloud management platform to the tenant; A site that can provide the third microservice is determined from the multiple sites, and a site that meets the first SLA parameters is selected as the first site from the sites that can provide the third microservice.
6. The method according to claim 4 or 5, characterized in that: The method further comprises: The third virtual instance is created in the first site, and the third microservice is deployed in the third virtual instance.
7. The method according to any one of claims 1 to 6, characterized in that: The first virtual instance includes at least one of the following: a virtual machine or a container.
8. The method according to any one of claims 1 to 7, characterized in that: The multiple sites are multiple availability zones, multiple regions, or at least one edge site and at least one central site.
9. The method according to any one of claims 1 to 8, characterized in that: The first SLA parameter includes at least one of the following: communication delay, throughput and processing time.
10. A cloud management platform, characterized in that: The cloud management platform is used to manage the infrastructure for providing cloud services, wherein the infrastructure includes multiple sites located in different geographical locations. The cloud management platform includes: an acquisition module, configured to acquire microservice configuration information input by a tenant from a microservice configuration interface, wherein the microservice configuration information is used to indicate a regional group and a service level agreement (SLA) constraint for the regional group, wherein the regional group includes a plurality of first microservices, and the SLA constraint includes a first SLA parameter that the plurality of first microservices need to satisfy; A first deployment module is used to select a first site that meets the first SLA parameters from the multiple sites based on the microservice configuration information, create multiple first virtual instances in the first site, and deploy the multiple first microservices in the multiple first virtual instances.
11. The cloud management platform according to claim 10, characterized in that: The configuration information is further used to indicate a microservice topology structure, the microservice topology structure includes the plurality of first microservices and the second microservice, the SLA constraint further includes a second SLA parameter that the plurality of first microservices and the second microservice need to satisfy together, and the cloud management platform further includes: a second deployment module, which is used to: If the site combination formed by the first site and the second site meets the second SLA parameter, creating a second virtual instance in the second site, and deploying the second microservice in the second virtual instance, the multiple sites including the second site; If only the first site meets the second SLA parameter, the second virtual instance is created in the first site, and the second microservice is deployed in the second virtual instance.
12. The cloud management platform according to claim 10 or 11, characterized in that: The configuration information is also used to indicate the site range specified by the tenant, and the site range includes at least one site among the multiple sites. The first deployment module is used to select a first site that meets the first SLA parameter from the at least one site based on the microservice configuration information.
13. The cloud management platform according to any one of claims 10 to 12, characterized in that: The regional group also includes a third microservice, the multiple first microservices are microservices defined by tenants, the third microservice is a microservice provided to the tenant by the cloud management platform, and the first deployment module is used to determine a site that can provide the third microservice from the multiple sites based on the microservice configuration information, and select a site that meets the first SLA parameters from the sites that can provide the third microservice as the first site.
14. The cloud management platform according to any one of claims 10 to 12, characterized in that: The multiple first microservices are microservices defined by tenants, and the first deployment module is used to: Based on the microservice configuration information, determine a third microservice associated with the plurality of first microservices from a preset microservice relationship template derived from the tenant, wherein the third microservice is a microservice provided by the cloud management platform to the tenant; A site that can provide the third microservice is determined from the multiple sites, and a site that meets the first SLA parameters is selected as the first site from the sites that can provide the third microservice.
15. The cloud management platform according to claim 13 or 14, characterized in that: The cloud management platform also includes: a third deployment module, used to create the third virtual instance in the first site and deploy the third microservice in the third virtual instance.
16. The cloud management platform according to any one of claims 10 to 15, characterized in that: The first virtual instance includes at least one of the following: a virtual machine or a container.
17. The cloud management platform according to any one of claims 10 to 16, characterized in that: The multiple sites are multiple availability zones, multiple regions, or at least one edge site and at least one central site.
18. The cloud management platform according to any one of claims 10 to 17, characterized in that: The first SLA parameter includes at least one of the following: communication delay, throughput and processing time.
19. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device including a processor and a memory: The memory is used to store instructions; The processor is configured to cause the computing device cluster to execute the method according to any one of claims 1 to 9 according to the instructions.
20. A computer storage medium, characterized in that The computer storage medium stores one or more instructions, which, when executed by one or more computers, enable the one or more computers to implement the method of any one of claims 1 to 9.
21. A computer program product, characterized in that The computer program product stores instructions, which, when executed by a computer, enable the computer to implement the method according to any one of claims 1 to 9.
Citation Information
Cited By
Microservice management method based on cloud management platform, and cloud management platform
EP4716193A1
Microservice management method based on cloud management platform, and cloud management platform
WO2024251192A1
