Cloud service characteristic management method based on cloud management platform and cloud management platform

Abstract

The invention discloses a cloud service characteristic management method based on a cloud management platform and the cloud management platform, which can ensure smooth online and subsequent availability of characteristics of cloud services so as to improve the experience of tenants. The method comprises the following steps that: when a tenant needs to be online with a first characteristic of a first cloud service, the tenant can send an online request for the first characteristic of the first cloud service to a management interface provided by a cloud management platform; then, the cloud management platform can detect whether a second characteristic dependent on the first characteristic and a third characteristic dependent on the first characteristic exist or not based on the online request, if the second characteristic exists, the cloud management platform needs to be online after determining that the second characteristic is online, and if the third characteristic exists, the cloud management platform needs to be online after determining that the second characteristic is online; and the cloud management platform needs to perform online operation on the first characteristic and then perform online operation on the third characteristic.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of cloud technology, and particularly relate to a cloud service feature management method based on a cloud management platform and the cloud management platform. BACKGROUND

[0002] With the rapid development of cloud technology, more and more tenants choose cloud services provided by cloud vendors to complete the business of tenants. In order to meet the needs of tenants, these cloud services facing tenants usually exhibit a variety of optional features (which can also be referred to as functions) for tenants to customize the features of the cloud services they need, so that cloud vendors can online the features of the cloud services required by tenants to meet the business needs of tenants.

[0003] In the related art, when a tenant needs to online a certain feature of a certain cloud service, the tenant can find the switch provided by the cloud management platform about the feature, and send a setting request for the switch of the feature to the cloud management platform, so that the cloud management platform sets the switch of the feature to the on state based on the setting request, to online the feature, so that the cloud service has the feature, and the cloud service with the feature can meet the business needs of the tenant.

[0004] In the above process, when the tenant needs to set the feature of the cloud service, the cloud management platform directly sets the feature to on or off based on the state of the switch of the feature, and the considered factors are relatively single, which may cause the feature to be unavailable in practice, resulting in poor tenant experience. SUMMARY

[0005] Embodiments of the present application provide a cloud service feature management method based on a cloud management platform and the cloud management platform, which can ensure the smooth online of the features of the cloud service and the subsequent availability, thereby improving the tenant experience.

[0006] A first aspect of embodiments of the present application provides a cloud service feature management method based on a cloud management platform. The cloud management platform used to implement the method can manage the infrastructures deployed in the cloud, and these infrastructures are used to provide a plurality of cloud services for tenants. The method comprises:

[0007] When a tenant needs to online a first feature of a first cloud service, the cloud management platform can provide a management interface to the tenant. Then, the tenant can input a online request for the first feature set by the tenant to the management interface, and the online request is used to indicate the first feature to be online. In this way, the cloud management platform can receive the online request sent by the tenant through the management interface. The first cloud service is any one of the plurality of cloud services facing the tenant.

[0008] After obtaining the online request, the cloud management platform can detect, based on the online request, whether the second characteristic relied on by the first characteristic and the third characteristic relying on the first characteristic exist in the characteristic dependency topology of the first characteristic. If the second characteristic exists, the cloud management platform must perform the online operation on the first characteristic after determining that the second characteristic has been online. If the third characteristic exists, the cloud management platform performs the online operation on the first characteristic first, and then performs the online operation on the third characteristic. At this point, the cloud management platform successfully online the first characteristic.

[0009] As can be seen from the above method, after determining that the tenant needs to online the first characteristic, the cloud management platform can determine the remaining characteristics associated with the first characteristic, i.e., the second characteristic and the third characteristic, through the characteristic dependency topology of the first characteristic, to ensure that the second characteristic and the third characteristic do not affect the online of the first characteristic in the online process of the first characteristic. As can be seen, the cloud management platform not only considers the influence of the first characteristic itself, but also considers the influence of the second characteristic and the third characteristic on the first characteristic. The considered factors are more comprehensive, which can ensure the smooth online of the first characteristic and the subsequent availability, thereby improving the tenant experience.

[0010] In a possible implementation manner, the second characteristic belongs to the first cloud service or the second cloud service, and the second cloud service is located downstream of the first cloud service in the plurality of cloud services. In the foregoing implementation manner, for the second characteristic, it can be arranged in the first cloud service together with the first characteristic, or it can be arranged in the second cloud service other than the first cloud service. In the latter case, the second cloud service is usually located downstream of the first cloud service.

[0011] In a possible implementation manner, the third characteristic belongs to the first cloud service or the third cloud service, and the third cloud service is located upstream of the first cloud service in the plurality of cloud services. In the foregoing implementation manner, for the third characteristic, it can be arranged in the first cloud service together with the first characteristic, or it can be arranged in the third cloud service other than the first cloud service. In the latter case, the third cloud service is usually located upstream of the first cloud service.

[0012] In a possible implementation, the cloud management platform performing the on-boarding operation on the first feature includes: the cloud management platform determining a plurality of microservices for implementing the first feature, the first cloud service containing at least one microservice in the plurality of microservices; and the cloud management platform changing configuration items of the plurality of microservices so that the first feature is on-boarded. In the foregoing implementation, when the on-boarding operation needs to be performed on the first feature, the cloud management platform can first determine a plurality of microservices for implementing the first feature, at least one microservice in the plurality of microservices being arranged in the first cloud service. Then, the cloud management platform can arrange a configuration change scheme of the plurality of microservices, and since the scheme contains the configuration change order of the plurality of microservices, the cloud management platform can change the configuration items of the plurality of microservices in the order contained in the scheme, so as to implement the on-boarding of the first feature. As can be seen, when the first feature is on-boarded, the cloud management platform additionally considers the configuration change order of the plurality of microservices for implementing the first feature, considers more factors, and is beneficial to further ensure the smooth on-boarding and availability of the first feature.

[0013] In a possible implementation, the plurality of microservices includes a first microservice and a second microservice, the first microservice being arranged in the first cloud service and the second microservice being arranged in the fourth cloud service, and the cloud management platform changing the configuration items of the plurality of microservices so that the first feature is on-boarded includes: the cloud management platform obtaining a first priority of the first cloud service and a second priority of the fourth cloud service; if the first priority is higher than the second priority, the cloud management platform changing the configuration item of the first microservice and then changing the configuration item of the second microservice so that the first feature is on-boarded; and if the second priority is higher than the first priority, the cloud management platform changing the configuration item of the second microservice and then changing the configuration item of the first microservice so that the first feature is on-boarded. In the foregoing implementation, the plurality of microservices for implementing the first feature can include the first microservice arranged in the first cloud service and the second microservice arranged in the fourth cloud service, and therefore the cloud management platform can first obtain the first priority of the first cloud service and the second priority of the fourth cloud service as a configuration change scheme for the first microservice and the second microservice. In the configuration change scheme, if the first priority is higher than the second priority, the cloud management platform changes the configuration item of the first microservice first and then changes the configuration item of the second microservice; or if the second priority is higher than the first priority, the cloud management platform changes the configuration item of the second microservice first and then changes the configuration item of the first microservice, so as to implement the on-boarding of the first feature. As can be seen, when the plurality of microservices for implementing the first feature are distributed in a plurality of cloud services (i.e., the first cloud service and the second cloud service), the cloud management platform can arrange the configuration change order of the plurality of microservices by using the priorities of the plurality of cloud services, and change the configuration items of the plurality of microservices in the order, so as to ensure the smooth on-boarding of the first feature and the availability of the first feature in the future.

[0014] In a possible implementation, the plurality of microservices includes a first microservice and a second microservice, the first microservice is disposed in the first cloud service, and the second microservice is disposed in the fourth cloud service. The cloud management platform changes the configuration items of the plurality of microservices to complete online of the first feature includes: the cloud management platform acquires a third priority of the first microservice and a fourth priority of the second microservice; if the third priority is higher than the fourth priority, the cloud management platform changes the configuration items of the first microservice and then changes the configuration items of the second microservice to complete online of the first feature; and if the fourth priority is higher than the third priority, the cloud management platform changes the configuration items of the second microservice and then changes the configuration items of the first microservice to complete online of the first feature. In the foregoing implementation, the plurality of microservices for implementing the first feature can include the first microservice disposed in the first cloud service and the second microservice disposed in the fourth cloud service. Therefore, the cloud management platform can acquire the third priority of the first microservice and the fourth priority of the second microservice as a configuration change scheme for the first microservice and the second microservice. In the configuration change scheme, if the third priority is higher than the fourth priority, the cloud management platform changes the configuration items of the first microservice first and then changes the configuration items of the second microservice to implement online of the first feature. If the fourth priority is higher than the third priority, the cloud management platform changes the configuration items of the second microservice first and then changes the configuration items of the first microservice to implement online of the first feature. It can be seen that when the plurality of microservices for implementing the first feature are distributed in the plurality of cloud services (i.e., the first cloud service and the second cloud service), the cloud management platform can use the priorities of the plurality of microservices in the plurality of cloud services to arrange the configuration change order of the plurality of microservices, and change the configuration items of the plurality of microservices in the order to ensure smooth online of the first feature and availability of the first feature in the future.

[0015] In a possible implementation, the first microservice is used to implement a fourth feature of the first cloud service, the second microservice is used to implement a fifth feature of the fourth cloud service, and the fourth feature and the fifth feature constitute the first feature. In the foregoing implementation, the first feature is a combined feature of the first cloud service, which is composed of the fourth feature of the first cloud service and the fifth feature of the fourth cloud service. Both of the features are original features. Accordingly, the first microservice in the plurality of microservices for implementing the first feature is used to implement the fourth feature, and the second microservice is used to implement the fifth feature.

[0016] In a possible implementation, if the second characteristic exists, the cloud management platform, after determining that the second characteristic has been online, performs the online operation on the first characteristic, including: if the second characteristic exists and the second characteristic is a characteristic that is mutually exclusive with the first characteristic, the cloud management platform, after determining that the second characteristic has been online, performs an offline operation on the second characteristic, and then performs the online operation on the first characteristic.

[0017] In a possible implementation, the infrastructure includes a plurality of cloud instances, the plurality of cloud instances are used to run a plurality of cloud services, and the plurality of cloud instances include physical servers, virtual machines, containers, micro virtual machines, and bare metal servers.

[0018] A second aspect of the embodiment of the present application provides a cloud management platform, the cloud management platform being used to manage an infrastructure, the infrastructure being used to provide a plurality of cloud services for tenants, and the cloud management platform including: a receiving module, configured to receive, through a management interface, an online request sent by a tenant, the online request being used to indicate a first characteristic of a first cloud service to be online, and the plurality of cloud services including the first cloud service; a detecting module, configured to detect, based on the online request, whether a second characteristic relied on by the first characteristic and a third characteristic relying on the first characteristic exist; and an online module, configured to, if the second characteristic exists, perform an online operation on the first characteristic after determining that the second characteristic has been online, and configured to, if the third characteristic exists, perform the online operation on the first characteristic and then perform the online operation on the third characteristic.

[0019] In a possible implementation, the second characteristic belongs to the first cloud service or a second cloud service, and the second cloud service is located downstream of the first cloud service in the plurality of cloud services.

[0020] In a possible implementation, the third characteristic belongs to the first cloud service or a third cloud service, and the third cloud service is located upstream of the first cloud service in the plurality of cloud services.

[0021] In a possible implementation, the online module is configured to: determine a plurality of microservices used to implement the first characteristic, the first cloud service including at least one microservice in the plurality of microservices; and change configuration items of the plurality of microservices, so that the first characteristic is completed online.

[0022] In a possible implementation, the plurality of microservices include a first microservice and a second microservice, the first microservice being arranged in the first cloud service and the second microservice being arranged in a fourth cloud service, and the online module is configured to: obtain a first priority of the first cloud service and a second priority of the fourth cloud service; if the first priority is higher than the second priority, change the configuration items of the first microservice and then change the configuration items of the second microservice, so that the first characteristic is completed online; and if the second priority is higher than the first priority, change the configuration items of the second microservice and then change the configuration items of the first microservice, so that the first characteristic is completed online.

[0023] In a possible implementation, the plurality of microservices includes a first microservice and a second microservice, the first microservice is deployed in the first cloud service, and the second microservice is deployed in the fourth cloud service. The online module is configured to: obtain a third priority of the first microservice and a fourth priority of the second microservice; if the third priority is higher than the fourth priority, change a configuration item of the first microservice, and then change a configuration item of the second microservice, so that the first feature is completed online; or if the fourth priority is higher than the third priority, change a configuration item of the second microservice, and then change a configuration item of the first microservice, so that the first feature is completed online.

[0024] In a possible implementation, the first microservice is configured to implement a fourth feature of the first cloud service, and the second microservice is configured to implement a fifth feature of the fourth cloud service. The fourth feature and the fifth feature constitute the first feature.

[0025] In a possible implementation, the online module is configured to, if there is a second feature and the second feature is a feature that is mutually exclusive with the first feature, perform an offline operation on the second feature before performing an online operation on the first feature after determining that the second feature is online.

[0026] In a possible implementation, the infrastructure includes a plurality of cloud instances, and the plurality of cloud instances are configured to run a plurality of cloud services. The plurality of cloud instances includes a physical server, a virtual machine, a container, a micro virtual machine, and a bare metal server.

[0027] A third aspect of the embodiments of the present application provides a computing device cluster, which includes at least one computing device. Each computing device includes a processor and a memory. The memory is configured to store instructions. The processor is configured to execute the instructions, so that the computing device cluster performs the method in the first aspect or any possible implementation manner of the first aspect.

[0028] A fourth aspect of the embodiments of the present application provides a computer storage medium, which stores one or more instructions. The instructions, when executed by one or more computers, cause the one or more computers to implement the method in the first aspect or any possible implementation manner of the first aspect.

[0029] A fifth aspect of the embodiments of the present application provides a computer program product, which stores instructions. The instructions, when executed by a computer, cause the computer to implement the method in the first aspect or any possible implementation manner of the first aspect.

[0030] In the embodiments of the present application, when the tenant needs to online the first feature of the first cloud service, the tenant can send an online request for the first feature of the first cloud service to the management interface provided by the cloud management platform. Then, the cloud management platform can detect whether there is a second feature relied on by the first feature and a third feature relying on the first feature based on the online request. If the second feature exists, the cloud management platform needs to online the first feature after determining that the second feature has been online. If the third feature exists, the cloud management platform needs to perform online operation on the first feature and then perform online operation on the third feature. In the foregoing process, after determining that the tenant needs to online the first feature, the cloud management platform can determine the remaining features associated with the first feature, i.e., the second feature and the third feature, through the feature dependency topology of the first feature, so as to ensure that the second feature and the third feature do not affect the online of the first feature in the online process of the first feature. As can be seen, the cloud management platform not only considers the influence of the first feature itself, but also considers the influence of the second feature and the third feature on the first feature. The considered factors are more comprehensive, which can ensure the smooth online and subsequent availability of the first feature, thereby improving the tenant experience. BRIEF DESCRIPTION OF DRAWINGS

[0031] Figure 1 A structural schematic diagram of a cloud service system provided by the embodiments of the present application;

[0032] Figure 2 A flowchart of a cloud service feature management method based on a cloud management platform provided by the embodiments of the present application;

[0033] Figure 3 An application example schematic diagram of a cloud service feature management method based on a cloud management platform provided by the embodiments of the present application;

[0034] Figure 4 A structural schematic diagram of a cloud management platform provided by the embodiments of the present application;

[0035] Figure 5 A structural schematic diagram of a computing device provided by the embodiments of the present application;

[0036] Figure 6 A structural schematic diagram of a computing device cluster provided by the embodiments of the present application;

[0037] Figure 7 A schematic diagram of network connection of computer devices in a computer cluster provided by the embodiments of the present application. DETAILED DESCRIPTION

[0038] The embodiments of the present application provide a cloud service feature management method based on a cloud management platform and a cloud management platform, which can ensure the smooth online and subsequent availability of the features of the cloud service, thereby improving the tenant experience.

[0039] The terms "first", "second", and the like in the description and in the claims of the present application and in the above figures are used for distinguishing between similar objects and not necessarily for describing a specific sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and that the embodiments of the present application are capable of functioning in other sequences than the one explicitly described. Moreover, the terms "comprise", "have" and any variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises, has or includes a list of elements is not necessarily limited to those elements, but can include other elements not expressly listed or inherent to such process, method, system, article, or apparatus.

[0040] With the rapid development of cloud technology, more and more tenants choose cloud services provided by cloud vendors to complete the business of the tenants, such as various cloud services of cloud computing, cloud storage, and cloud network. In order to meet the needs of tenants, these cloud services usually exhibit a variety of optional features to tenants for tenants to customize the features of the cloud services they need, so that cloud vendors can online the features of the cloud services required by tenants to meet the business needs of tenants.

[0041] In the related art, when a tenant needs to online a certain feature of a certain cloud service, it can find the switch provided by the cloud management platform about the feature, and send a setting request for the switch of the feature to the cloud management platform, so that the cloud management platform sets the switch of the feature to the on state based on the setting request, to online the feature, so that the cloud service has the feature, and the cloud service with the feature can meet the business needs of the tenant. For example, when a tenant needs to online the data processing function of cloud computing, the tenant can send a setting request for the switch of the data processing function to the cloud management platform, and the cloud management platform can open the switch based on the setting request, so that the cloud computing serving the tenant has the data processing function, thereby providing data processing services for the tenant.

[0042] In the above process, when the tenant needs to set the feature of the cloud service, the cloud management platform directly sets the feature to on or off based on the state of the switch of the feature, and the considered factors are relatively single, which may cause the feature to be unavailable in practice, resulting in poor tenant experience.

[0043] Further, the feature of the cloud service can usually be implemented by multiple microservices, so when the cloud management platform online the feature, it often does not consider the online order between the multiple microservices, and does not consider various factors, and cannot ensure the smooth online of the feature.

[0044] To solve the above problems, the embodiments of the present application provide a cloud service feature management method based on a cloud management platform, which can be implemented by a cloud service system,Figure 1 A structural schematic diagram of a cloud service system provided by an embodiment of the present application is shown in FIG. 1. As shown in FIG. 1, the cloud service system includes infrastructures that can provide cloud services and a cloud management platform that manages the infrastructures. The cloud management platform and the infrastructures are introduced respectively as follows: Figure 1

[0045] The cloud management platform can comprehensively manage the infrastructures in the entire cloud service system (for example, in the infrastructures, multiple cloud instances serving a tenant are created for the tenant, the cloud instances are used to run multiple cloud services for the tenant, and the multiple cloud services can satisfy the business requirements of the tenant, etc.), and the cloud management platform can also be open to tenants outside the cloud service system and respond to their requests. For example, the cloud management platform can provide various interfaces such as a login interface and a management interface for access by a client of a tenant (for example, a terminal device used by the tenant or a browser on the terminal device, etc.). The cloud management platform can authenticate the client of the tenant through the login interface, and allow the client of the tenant to log in to the cloud management platform after successful authentication. For another example, the cloud management platform can also allow the client of the tenant to send an online request for a certain feature of a certain cloud service to the cloud management platform through the management interface. Based on the online request, the cloud management platform can obtain a feature dependency topology of the feature from a feature model of the cloud service, and detect whether there is a feature that the feature depends on and a feature that depends on the feature from the feature dependency topology of the feature. If there is a feature that the feature depends on, the cloud management platform needs to perform an online operation on the feature after determining that the feature that the feature depends on has been online, thereby completing the online of the feature. If there is a feature that depends on the feature, the cloud management platform needs to perform an online operation on the feature first, and then perform an online operation on the feature that depends on the feature.

[0046] It is worth noting that the cloud management platform is provided with multiple feature models of cloud services. For any feature model of a cloud service, the feature model of the cloud service can be presented in the following way:

[0047]

[0048]

[0049] The feature model of the cloud service is further introduced in combination with Table 1 as follows:

[0050] Table 1

[0051]

[0052]

[0053] ​

[0054]

[0055] Based on Table 1, the characteristic model of the cloud service pre-defines all characteristics contained in the cloud service, including original characteristics of the cloud service and combined characteristics of the cloud service. When a tenant needs to use the cloud service, each original characteristic and each combined characteristic of the cloud service can be online through the cloud management platform. Generally, when a tenant needs to online a certain original characteristic of the cloud service, the cloud management platform can first determine the (other) characteristics dependent on the original characteristic and the characteristics dependent on the original characteristic, to ensure the smooth online of the original characteristic. When the online operation of the original characteristic is performed, the cloud management platform can change the configuration items of a plurality of microservices (located in the cloud service) used to implement the original characteristic according to a certain configuration change scheme (which will not be expanded here), so that the original characteristic is completed online. When a tenant needs to online a certain combined characteristic of the cloud service, the cloud management platform can first determine the characteristics dependent on the combined characteristic and the characteristics dependent on the combined characteristic, to ensure the smooth online of the combined characteristic. When the online operation of the combined characteristic is performed, since the combined characteristic can contain a certain (or certain) original characteristic of the cloud service and a certain (or certain) original characteristic of other cloud service, the cloud management platform can change the configuration items of all microservices (located in the cloud service and other cloud service) used to implement these original characteristics according to a certain configuration change scheme (which will not be expanded here), so that the combined characteristic is completed online.

[0056] The infrastructure can contain a plurality of cloud instances, which can be used to run a plurality of cloud services for tenants. For any one of the plurality of cloud services, the cloud service can contain a plurality of characteristics, and a tenant can perform online operation on a certain or certain characteristics (whether original characteristics or combined characteristics) of the cloud service through the cloud management platform, so that the cloud service after online of these characteristics can provide more services for the tenant, thereby meeting various business needs of the tenant.

[0057] Further, for the plurality of cloud instances serving the tenant, the cloud instances can be presented in various forms, for example, the cloud instances can be physical servers selected by the cloud management platform in the infrastructure, for another example, the cloud instances can also be bare metal servers selected by the cloud management platform in the infrastructure, for another example, the cloud instances can also be virtual machines (VMs) created by the cloud management platform in the physical servers or bare metal servers through virtualization technology, for another example, the cloud instances can also be containers (docker) created by the cloud management platform in the physical servers through virtualization technology, for another example, the cloud instances can also be micro VMs created by the cloud management platform in the physical servers through virtualization technology, and the like.

[0058] Further, for the plurality of cloud instances serving the tenant, the cloud instances can be deployed in the same site or different sites, and the site can be presented in various forms, for example, the site can be a region in the infrastructure, for another example, the site can be an availability zone in the infrastructure, for another example, the site can be a data center (DC) in the infrastructure, for another example, the site can be a room in the infrastructure, for another example, the site can be a rack in the infrastructure, and the like.

[0059] Based on the cloud service system described above, when the tenant needs to go online with a certain feature of a certain cloud service, the tenant can send an online request for the feature of the cloud service to the management interface provided by the cloud management platform. Then, the cloud management platform can detect whether there are features dependent on the feature and features dependent on the feature based on the online request. If there are features dependent on the feature, the cloud management platform needs to determine that the features dependent on the feature have been online before online the feature, and if there are features dependent on the feature, the cloud management platform needs to perform online operation on the feature first, and then perform online operation on the features dependent on the feature. In the foregoing process, after the cloud management platform determines that the tenant needs to go online with the feature, the cloud management platform can determine the remaining features associated with the feature, i.e., the features dependent on the feature and the features dependent on the feature, through the feature dependency topology of the feature, to ensure that these features do not affect the online of the feature in the online process of the feature. As can be seen, the cloud management platform not only considers the impact of the feature itself, but also considers the impact of the remaining features on the feature, and the considered factors are more comprehensive, which can ensure the smooth online of the feature and the subsequent availability, thereby improving the tenant experience. In order to further understand the workflow of the cloud management platform, the following will introduce the workflow in combination with Figure 2 the workflow, Figure 2A flowchart of a cloud service characteristic management method based on a cloud management platform is provided in the embodiments of the present application. The method can be implemented by a cloud service system as shown in Figure 1 The cloud service system includes infrastructures and a cloud management platform for managing the infrastructures. The infrastructures can run a plurality of cloud services for tenants. The method includes the following steps.

[0060] 201. The cloud management platform receives an online request sent by a tenant through a management interface. The online request is used to indicate a first characteristic of a first cloud service to be online. The plurality of cloud services includes the first cloud service.

[0061] 202. The cloud management platform detects whether there is a second characteristic relied on by the first characteristic and a third characteristic relied on by the first characteristic based on the online request.

[0062] In the embodiments, when the tenant needs to online the first characteristic of the first cloud service, the cloud management platform can provide a management interface (for example, a cloud service characteristic management column of a tenant interface, etc.) to a client of the tenant. Then, the tenant can input an online request for the first characteristic set by the tenant to the management interface through the client used by the tenant. The online request is used to indicate the first characteristic to be online. In this way, the cloud management platform can receive the online request sent by the client of the tenant through the management interface. It should be noted that the first cloud service is any one of the plurality of cloud services for tenants, and the first characteristic is any one of the characteristics of the first cloud service.

[0063] After obtaining the online request, the cloud management platform can obtain a characteristic dependency topology of the first characteristic from a characteristic model of the first cloud service and a characteristic model of the remaining cloud services (for example, a third cloud service later), so as to determine whether there is a second characteristic relied on by the first characteristic and a third characteristic relied on by the first characteristic from the characteristic dependency topology.

[0064] Specifically, the second characteristic can be presented in various ways: the second characteristic belongs to the first cloud service or the second cloud service. It should be noted that in the plurality of cloud services, the second cloud service and the first cloud service are two different cloud services, and the second cloud service is usually located downstream of the first cloud service (because a certain characteristic of a certain cloud service depends on another characteristic of another cloud service, the certain cloud service is usually an upstream cloud service, and the other cloud service is usually a downstream cloud service, that is, the characteristic of the cloud service located upstream can depend on the characteristic of the cloud service located downstream).

[0065] For example, assume that the tenant needs to onboard the feature 1 of the cloud service 1, the cloud management platform finds from the feature model of the cloud service 1 that the feature 1 depends on the feature 2 of the cloud service 1. For another example, assume that the tenant needs to onboard the feature 1 of the cloud service 1, the cloud management platform finds from the feature model of the cloud service 1 that the feature 1 depends on the feature 2 of the cloud service 2, at this time, the cloud service 2 is usually located downstream of the cloud service 1.

[0066] More specifically, the third feature can also be presented in multiple ways: the third feature belongs to the first cloud service or the third cloud service. It should be noted that in multiple cloud services, the third cloud service and the first cloud service are two different cloud services, and the third cloud service is usually located upstream of the first cloud service (because when a feature of a cloud service is dependent on another feature of another cloud service, the cloud service is usually a downstream cloud service, and the other cloud service is usually an upstream cloud service, that is, the feature of the cloud service located downstream can be dependent on the feature of the cloud service located upstream). It should also be noted that when the third feature belongs to the third cloud service, because the feature model of the first cloud service usually only contains the features that the first feature depends on, and because the first feature is dependent on the third feature, the cloud management platform can determine from the feature model of the third cloud service that the third feature depends on the first feature.

[0067] For example, assume that the tenant needs to onboard the feature 1 of the cloud service 1, the cloud management platform finds from the feature model of the cloud service 1 that the feature 1 is dependent on the feature 3 of the cloud service 1. For another example, assume that the tenant needs to onboard the feature 1 of the cloud service 1, the cloud management platform finds from the feature model of the cloud service 3 that the feature 1 is dependent on the feature 3 of the cloud service 3, at this time, the cloud service 3 is usually located upstream of the cloud service 1.

[0068] More specifically, the first feature can be presented in multiple ways: (1) the first feature can be a certain combined feature of the first cloud service, that is, the first feature is obtained by combining the fourth feature of the first cloud service and the fifth feature of the fourth cloud service, the fourth feature is a certain original feature of the first cloud service, and the fifth feature is a certain original feature of the fourth cloud service. (2) The first feature can also be a certain original feature of the first cloud service, and so on.

[0069] For example, assume that the tenant needs to onboard the feature 1 of the cloud service 1, the feature 1 is a combined feature of the cloud service 1, which is obtained by combining the feature 4 (original feature) of the cloud service 1 and the feature 5 (original feature) of the cloud service 4. For another example, assume that the tenant needs to onboard the feature 1 of the cloud service 1, the feature 1 is an original feature of the cloud service 1.

[0070] More specifically, the cloud management platform can complete the detection in the following multiple ways when detecting whether the second feature and the third feature exist:

[0071] (1) first detect whether the second feature exists, and perform corresponding operations based on the first detection result, then detect whether the third feature exists, and perform corresponding operations based on the second detection result. (2) first detect whether the third feature exists, and perform corresponding operations based on the first detection result, then detect whether the second feature exists, and perform corresponding operations based on the second detection result. (3) simultaneously detect whether the second feature and the third feature exist, and perform corresponding operations based on the detection result, and the like, which are not limited here.

[0072] 203. If the second feature exists, the cloud management platform performs the online operation on the first feature after determining that the second feature has been online.

[0073] 204. If the third feature exists, the cloud management platform performs the online operation on the first feature, and then performs the online operation on the third feature.

[0074] If the second feature exists, the cloud management platform must perform the online operation on the first feature after determining that the second feature has been online, thereby ensuring the availability of the first feature after being online. If the third feature exists, the cloud management platform performs the online operation on the first feature, and then performs the online operation on the third feature, thereby ensuring the smooth online of the first feature, and laying a foundation for the availability of the third feature after being online.

[0075] More specifically, the cloud management platform can complete the online of the first feature in the following ways:

[0076] When it is necessary to perform the online operation on the first feature, the cloud management platform can determine a plurality of microservices for implementing the first feature from the feature model of the first cloud service, at least one microservice in the plurality of microservices is arranged in the first cloud service, and the number of microservices in the first cloud service is determined based on whether the first feature is a combined feature or an original feature, which is not expanded here.

[0077] After determining the plurality of microservices for implementing the first feature, the cloud management platform can compile a configuration change scheme of the plurality of microservices, since the scheme contains the configuration change order of the plurality of microservices, the cloud management platform can change the configuration items of the plurality of microservices according to the configuration change order of the plurality of microservices contained in the scheme, so as to implement the online of the first feature.

[0078] More specifically, the cloud management platform can change the configuration items of the plurality of microservices in the following ways:

[0079] (1) When the first characteristic is an original characteristic of the first cloud service, the plurality of microservices used to implement the first characteristic are all arranged in the first cloud service, so the cloud management platform can find the relevant information defining the first characteristic from the characteristic model of the first cloud service. Among the information, the cloud management platform can obtain the configuration change priorities (i.e. the aforementioned configuration change scheme) of the plurality of microservices, and change the configuration items of the plurality of microservices in turn according to the high and low of the configuration change priorities (for example, first change the configuration items of the microservices with higher configuration change priorities, and then change the configuration items of the microservices with lower configuration change priorities), so as to implement the online of the first characteristic.

[0080] For example, assuming that the name of the cloud service 1 is IaaS_XX, and the id of the characteristic 1 is IaaSXX.cps-XX-switch, the cloud management platform can obtain the characteristic model of IaaS_XX, and obtain the relevant information about IaaSXX.cps-XX-switch from the characteristic model as shown below:

[0081]

[0082] Among the above information, there are three microservices used to indicate IaaSXX.cps-XX-switch, which are cps-client, ha-agent and cps-server. Since the three microservices are all located in IaaS_XX, the configuration change strategies of the three microservices are all set to MS_KEYS, indicating that the configuration change priorities of the three microservices are used as the configuration change order of the three microservices. Since the configuration change priorities of cps-client, ha-agent and cps-server are 3, 2 and 1 in turn, the cloud management platform can first change the configuration item (enable_cps_hub) of cps-client, then change the configuration item (enable_cps_hub) of ha-agent, and finally change the configuration item (enable_cps_hub) of cps-server, so as to complete the online of IaaSXX.cps-XX-switch.

[0083] (2) When the first characteristic is a combined characteristic of the first cloud service, i.e. the first characteristic is combined from a fourth characteristic of the first cloud service and a fifth characteristic of the fourth cloud service, the microservices used to implement the first characteristic can include a first microservice deployed in the first cloud service and a second microservice deployed in the fourth cloud service, the first microservice is used to implement the fourth characteristic, and the second microservice is used to implement the fifth characteristic. The cloud management platform can find the information defining the fourth characteristic from the characteristic model of the first cloud service, and find the information defining the fifth characteristic from the characteristic model of the fourth cloud service. In these information, the cloud management platform can obtain the first priority of the first cloud service and the second priority of the fourth cloud service (these priorities are the configuration change priorities, which are the aforementioned configuration change schemes). If the first priority is higher than the second priority, the cloud management platform changes the configuration items of the first microservice first, and then changes the configuration items of the second microservice, to implement the online of the first characteristic. If the second priority is higher than the first priority, the cloud management platform changes the configuration items of the second microservice first, and then changes the configuration items of the first microservice, to implement the online of the first characteristic.

[0084] Still as the above example, assume that the characteristic 1 of the cloud service 1 is a combined characteristic, which is combined from the characteristic 4 (original characteristic) of the cloud service 1 and the characteristic 5 (original characteristic) of the cloud service 4, and the microservices used to implement the characteristic 1 include the microservice 1, the microservice 2 and the microservice 3, the microservice 1 and the microservice 2 are used to implement the characteristic 4, and the microservice 3 is used to implement the characteristic 5. Then, the cloud management platform can first find the information of the characteristic 1 from the characteristic model of the cloud service 1 based on the ID of the characteristic 1. In these information, the configuration change strategy set for these microservices used to implement the characteristic 1 is set as CloudSvr_SF_ID, which indicates that the configuration change needs to be performed according to the configuration change priority of the cloud service where these microservices are located, so the cloud management platform can obtain the priority of the cloud service 1 and the priority of the cloud service 4 from these information, and the sub_id is the id of the characteristic 4 and the id of the characteristic 5. Assume that the priority of the cloud service 1 is higher than the priority of the cloud service 4, the cloud management platform can first find the information of the characteristic 4 from the characteristic model of the cloud service 1 based on the id of the characteristic 4, and modify the configuration items of the microservice 1 and the configuration items of the microservice 2 in these information. Then, the cloud management platform finds the information of the characteristic 5 from the characteristic model of the cloud service 4 based on the id of the characteristic 5, and modifies the configuration items of the microservice 3 in these information. In this way, the cloud management platform completes the online of the characteristic 1.

[0085] (3) When the first characteristic is a combined characteristic of the first cloud service, i.e. the first characteristic is combined from a fourth characteristic of the first cloud service and a fifth characteristic of the fourth cloud service, the microservices for implementing the first characteristic can include a first microservice deployed in the first cloud service and a second microservice deployed in the fourth cloud service, the first microservice is used to implement the fourth characteristic, and the second microservice is used to implement the fifth characteristic. The cloud management platform can find the information defining the fourth characteristic from the characteristic model of the first cloud service, and find the information defining the fifth characteristic from the characteristic model of the fourth cloud service. In these information, the cloud management platform can obtain a third priority of the first microservice and a fourth priority of the second microservice (these priorities are configuration change priorities, which are the aforementioned configuration change schemes). If the third priority is higher than the fourth priority, the cloud management platform changes the configuration items of the first microservice first, and then changes the configuration items of the second microservice, to implement the online of the first characteristic. If the fourth priority is higher than the third priority, the cloud management platform changes the configuration items of the second microservice first, and then changes the configuration items of the first microservice, to implement the online of the first characteristic.

[0086] Still as the above example, suppose that the characteristic 1 of the cloud service 1 is a combined characteristic, which is combined from a characteristic 4 (original characteristic) of the cloud service 1 and a characteristic 5 (original characteristic) of the cloud service 4, and the microservices for implementing the characteristic 1 include a microservice 1, a microservice 2 and a microservice 3, the microservice 1 and the microservice 2 are used to implement the characteristic 4, and the microservice 3 is used to implement the characteristic 5. Then, the cloud management platform can first find the information of the characteristic 1 from the characteristic model of the cloud service 1 based on the ID of the characteristic 1. In these information, the configuration change strategy set for these microservices for implementing the characteristic 1 is set as MS_SF_ID, which means that the configuration change needs to be performed according to the configuration change priorities of these microservices respectively, so the cloud management platform can obtain the (configuration change) priority of the microservice 1, the priority of the microservice 2 and the priority of the microservice 3 from these information, and the sub_id is the id of the characteristic 4 and the id of the characteristic 5. Suppose that the priority of the microservice 1 is higher than the priority of the microservice 3, and the priority of the microservice 3 is higher than the priority of the microservice 2, the cloud management platform can first find the information of the characteristic 4 from the characteristic model of the cloud service 1 based on the id of the characteristic 4, and in these information, the configuration items of the microservice 1 are modified first. Then, the cloud management platform finds the information of the characteristic 5 from the characteristic model of the cloud service 4 based on the id of the characteristic 5, and in these information, the configuration items of the microservice 3 are modified. Finally, the cloud management platform continues to find the information of the characteristic 4 from the characteristic model of the cloud service 1 based on the id of the characteristic 4, and in these information, the configuration items of the microservice 2 are modified first. In this way, the cloud management platform completes the online of the characteristic 1.

[0087] More specifically, the cloud management platform can further perform the onboarding operation on the first characteristic by:

[0088] When there is a second characteristic that the first characteristic depends on, if the second characteristic and the first characteristic are mutually exclusive characteristics, the cloud management platform can perform the offboarding operation on the second characteristic first after determining that the second characteristic has been onboarded, and then perform the onboarding operation on the first characteristic.

[0089] Still as the above example, after determining that characteristic 1 depends on characteristic 2, if characteristic 2 and characteristic 1 are mutually exclusive characteristics, the cloud management platform can offboard characteristic 2 first after determining that characteristic 2 has been onboarded, and then onboard characteristic 1, so that characteristic 2 does not affect the smooth onboarding and subsequent availability of characteristic 1.

[0090] To further understand the above process, a specific application example is further introduced below, Figure 3 An application example of the cloud service characteristic management method based on the cloud management platform provided in the embodiments of the present application is shown in FIG. 1. Figure 3 As shown in the figure, the application example includes:

[0091] 1. The tenant specifies a characteristic of a cloud service to be onboarded to the cloud management platform;

[0092] 2. The cloud management platform searches for related information of the characteristic from the characteristic model of the cloud service, and returns a failure to the tenant if the information does not exist, and performs step 3 if the information exists;

[0093] 3. The cloud management platform searches for whether there are other characteristics of the cloud service located upstream that depend on the characteristic in the information, and performs step 5 if the information does not exist, and performs step 4 if the information exists;

[0094] 4. The cloud management platform records the cloud service located upstream and the other characteristics of the cloud service located upstream;

[0095] 5. The cloud management platform searches for whether there are other characteristics of the cloud service located downstream that depend on the characteristic, and performs step 8 if the information does not exist, and performs step 6 if the information exists;

[0096] 6. The cloud management platform queries the onboarding state of the other characteristics of the cloud service located downstream;

[0097] 7. The cloud management platform determines whether the other characteristics of the cloud service located downstream have been onboarded, and returns a failure to the tenant if not, and performs step 8 if yes;

[0098] 8. The cloud management platform performs the onboarding operation on the characteristic;

[0099] 9. After the feature is successfully online, the cloud management platform notifies the cloud service located upstream and performs online operation on the remaining features of the cloud service located upstream.

[0100] In the embodiments of the present application, when the tenant needs to online the first feature of the first cloud service, the tenant can send an online request for the first feature of the first cloud service to the management interface provided by the cloud management platform. Then, the cloud management platform can detect whether there is a second feature relied on by the first feature and a third feature relying on the first feature based on the online request. If the second feature exists, the cloud management platform needs to online the first feature after determining that the second feature has been online. If the third feature exists, the cloud management platform needs to perform online operation on the first feature and then perform online operation on the third feature. In the foregoing process, after determining that the tenant needs to online the first feature, the cloud management platform can determine the remaining features associated with the first feature, i.e., the second feature and the third feature, through the feature dependency topology of the first feature, so as to ensure that the second feature and the third feature do not affect the online of the first feature in the online process of the first feature. As can be seen, the cloud management platform not only considers the influence of the first feature itself, but also considers the influence of the second feature and the third feature on the first feature. The considered factors are more comprehensive, which can ensure the smooth online of the first feature and the subsequent availability, thereby improving the tenant experience.

[0101] Further, in the embodiments of the present application, since the cloud management platform defines the feature model of each cloud service, the feature model of any cloud service contains the related information of each feature of the cloud service. When the tenant needs to online the first feature of the first cloud service, since the first feature is implemented based on multiple microservices, the cloud management platform can obtain the related information of the first feature from the feature model of the first cloud service, so as to obtain the configuration arrangement scheme for the multiple microservices from the information, and change the configuration items of the multiple microservices in the order indicated by the scheme. As can be seen, the cloud management platform also considers the configuration change order of the multiple microservices for implementing the first feature when online the first feature, and considers more factors, thereby ensuring the smooth online of the first feature.

[0102] The above is a detailed description of the cloud service feature management method based on the cloud management platform provided by the embodiments of the present application. The cloud management platform provided by the embodiments of the present application will be introduced below, Figure 4 A structural schematic diagram of the cloud management platform provided by the embodiments of the present application is shown in Figure 4 The cloud management platform is used to manage the infrastructure, and the infrastructure is used to provide multiple cloud services for tenants. The cloud management platform comprises:

[0103] The receiving module 401 is configured to receive, through the management interface, an online request sent by a tenant, the online request being used to indicate a first characteristic of a first cloud service to be online, and the plurality of cloud services including the first cloud service. Figure 2 The step 201 of the embodiment shown.

[0104] The detecting module 402 is configured to detect, based on the online request, whether there is a second characteristic relied on by the first characteristic and a third characteristic relied on by the first characteristic. Figure 2 The step 202 of the embodiment shown.

[0105] The online module 403 is configured to, if the second characteristic exists, perform an online operation on the first characteristic after determining that the second characteristic has been online. Figure 2 The step 203 of the embodiment shown.

[0106] The online module 403 is further configured to, if the third characteristic exists, perform the online operation on the first characteristic and then perform the online operation on the third characteristic. Figure 2 The step 204 of the embodiment shown.

[0107] In a possible implementation manner, the second characteristic belongs to the first cloud service or a second cloud service, and the second cloud service is located downstream of the first cloud service in the plurality of cloud services.

[0108] In a possible implementation manner, the third characteristic belongs to the first cloud service or a third cloud service, and the third cloud service is located upstream of the first cloud service in the plurality of cloud services.

[0109] In a possible implementation manner, the online module is configured to: determine a plurality of microservices used to implement the first characteristic, the first cloud service including at least one microservice in the plurality of microservices; and change configuration items of the plurality of microservices so that the first characteristic is completed online.

[0110] In a possible implementation manner, the plurality of microservices include a first microservice and a second microservice, the first microservice being arranged in the first cloud service and the second microservice being arranged in a fourth cloud service, and the online module is configured to: obtain a first priority of the first cloud service and a second priority of the fourth cloud service; if the first priority is higher than the second priority, change the configuration items of the first microservice and then change the configuration items of the second microservice so that the first characteristic is completed online; and if the second priority is higher than the first priority, change the configuration items of the second microservice and then change the configuration items of the first microservice so that the first characteristic is completed online.

[0111] In a possible implementation, the plurality of microservices includes a first microservice and a second microservice, the first microservice is deployed in the first cloud service, and the second microservice is deployed in the fourth cloud service. The online module is configured to: obtain a third priority of the first microservice and a fourth priority of the second microservice; if the third priority is higher than the fourth priority, change a configuration item of the first microservice, and then change a configuration item of the second microservice, so that the first feature is completed online; or if the fourth priority is higher than the third priority, change a configuration item of the second microservice, and then change a configuration item of the first microservice, so that the first feature is completed online.

[0112] In a possible implementation, the first microservice is configured to implement a fourth feature of the first cloud service, and the second microservice is configured to implement a fifth feature of the fourth cloud service, and the fourth feature and the fifth feature constitute the first feature.

[0113] In a possible implementation, the online module is configured to, if there is a second feature and the second feature is a feature that is mutually exclusive with the first feature, perform an offline operation on the second feature before performing an online operation on the first feature after determining that the second feature is online.

[0114] In a possible implementation, the infrastructure includes a plurality of cloud instances, and the plurality of cloud instances are configured to run a plurality of cloud services. The plurality of cloud instances includes a physical server, a virtual machine, a container, a micro virtual machine, and a bare metal server.

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

[0116] Please refer to Figure 5 , Figure 5 for a structural schematic diagram of a computing device provided by the embodiments of the present application. As shown in Figure 5 , the computing device 500 (which can be used to present the cloud management platform described above) includes a processor 501, a memory 502, a communication interface 503, and a bus 504. The processor 501, the memory 502, and the communication interface 503 are coupled through a bus (not shown in the figure). The memory 502 stores instructions, and when the instructions in the memory 502 are executed, the computing device 500 performs the method performed by the cloud management platform in the method embodiments described above.

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

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

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

[0120] The executable program code is stored in the memory 502, and the processor 501 executes the executable program code to realize the functions of the aforementioned receiving module, detection module, and online module, etc., thereby realizing the cloud service characteristic management method based on the cloud management platform. That is, the memory 502 stores instructions for executing the cloud service characteristic management method based on the cloud management platform.

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

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

[0123] Referring to Figure 6 , Figure 6 A structural diagram of a computing device cluster provided by an embodiment of the present application is shown. As Figure 6 shown, the computing device cluster 600 includes at least one computing device 500.

[0124] As Figure 6 shown, the computing device cluster 600 includes at least one computing device 500. The memory 502 in one or more computing devices 500 in the computing device cluster 600 can have the same instructions for executing the cloud service characteristic management method based on the cloud management platform described above.

[0125] In some possible implementations, the memory 502 in one or more computing devices 500 in the computing device cluster 600 can also respectively have partial instructions for executing the cloud service characteristic management method based on the cloud management platform described above. In other words, the combination of one or more computing devices 500 can collectively execute the cloud service characteristic management method based on the cloud management platform described above.

[0126] It should be noted that the memory 502 in different computing devices 500 in the computing device cluster 600 can store different instructions, respectively, for executing part of the functions of the cloud management platform described above. That is, the instructions stored in the memory 502 in different computing devices 500 can implement the functions of one or more of the receiving module, the detecting module, and the online module, etc.

[0127] In some possible implementations, one or more computing devices 500 in the computing device cluster 600 can be connected through a network. The network can be a wide area network or a local area network, etc.

[0128] Referring to Figure 7 ,Figure 7 A schematic diagram of a computer cluster provided by an embodiment of the present application is shown in FIG. 5. As shown in FIG. 5, two computer devices 500A and 500B are connected through a network. Specifically, the computer devices are connected to the network through a communication interface in each computer device. Figure 7

[0129] In a possible implementation, the memory in the computer device 500A stores instructions for performing the functions of the receiving module and other modules. Meanwhile, the memory in the computer device 500B stores instructions for performing the functions of the detecting module, the online module and other modules.

[0130] It should be understood that the functions of the computer device 500A shown in FIG. 5 can also be completed by multiple computer devices. Similarly, the functions of the computer device 500B can also be completed by multiple computer devices. Figure 7

[0131] The embodiments of the present application also relate to a computer storage medium, which stores a program for performing signal processing, and when the program is run on a computer, the computer is enabled to perform the steps performed by the cloud management platform in the embodiments shown in FIG. 6. Figure 2

[0132] The embodiments of the present application also relate to a computer program product, which stores instructions, and when the instructions are executed by a computer, the computer is enabled to perform the steps performed by the cloud management platform in the embodiments shown in FIG. 6. Figure 2

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

[0134] In the several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. The division of the units is only a logical function division. There can be another division manner for actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or in other forms.

[0135] ​​​​The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0136] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0137] If the integrated unit is implemented as 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 this application, in essence, 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. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A cloud service characteristic management method based on a cloud management platform, characterized by, The cloud management platform is used for managing an infrastructure, the infrastructure is used for providing a plurality of cloud services for a tenant, and the method comprises: The cloud management platform receives an online request sent by the tenant through a management interface, the online request is used for indicating a first characteristic of a first cloud service to be online, and the plurality of cloud services comprises the first cloud service; The cloud management platform detects whether a second characteristic relied on by the first characteristic and a third characteristic relying on the first characteristic exist based on the online request; If the second characteristic exists, the cloud management platform performs an online operation on the first characteristic after determining that the second characteristic has been online; If the third characteristic exists, the cloud management platform performs an online operation on the first characteristic and then performs an online operation on the third characteristic.

2. The method of claim 1, wherein, The second characteristic belongs to the first cloud service or a second cloud service, and the second cloud service is located downstream of the first cloud service in the plurality of cloud services.

3. The method according to claim 1 or 2, characterized in that, The third characteristic belongs to the first cloud service or a third cloud service, and the third cloud service is located upstream of the first cloud service in the plurality of cloud services.

4. The method according to any one of claims 1 to 3, characterized in that, The cloud management platform performing the online operation on the first characteristic comprises: The cloud management platform determines a plurality of microservices used for implementing the first characteristic, and the first cloud service comprises at least one microservice in the plurality of microservices; The cloud management platform changes configuration items of the plurality of microservices so that the first characteristic is completed online.

5. The method of claim 4, wherein, The plurality of microservices comprises a first microservice and a second microservice, the first microservice is arranged in the first cloud service, and the second microservice is arranged in the fourth cloud service, and the cloud management platform changing the configuration items of the plurality of microservices so that the first characteristic is completed online comprises: The cloud management platform obtains a first priority of the first cloud service and a second priority of the fourth cloud service; If the first priority is higher than the second priority, the cloud management platform changes the configuration items of the first microservice and then changes the configuration items of the second microservice so that the first characteristic is completed online; If the second priority is higher than the first priority, the cloud management platform changes the configuration items of the second microservice and then changes the configuration items of the first microservice so that the first characteristic is completed online.

6. The method of claim 4, wherein, The plurality of microservices comprises a first microservice and a second microservice, the first microservice is arranged in the first cloud service, and the second microservice is arranged in the fourth cloud service, and the cloud management platform changing the configuration items of the plurality of microservices so that the first characteristic is completed online comprises: The cloud management platform obtains a third priority of the first microservice and a fourth priority of the second microservice; If the third priority is higher than the fourth priority, the cloud management platform changes the configuration items of the first microservice and then changes the configuration items of the second microservice so that the first characteristic is completed online; If the fourth priority is higher than the third priority, the cloud management platform changes a configuration item of the second microservice, and then changes a configuration item of the first microservice, so that the first feature is completed to be online.

7. The method according to claim 5 or 6, characterized in that, The first microservice is used to implement a fourth feature of the first cloud service, and the second microservice is used to implement a fifth feature of the fourth cloud service, and the fourth feature and the fifth feature constitute the first feature.

8. The method according to any one of claims 1 to 7, characterized in that, If the second feature exists, the cloud management platform, after determining that the second feature is online, performs an online operation on the first feature, including: If the second feature exists and the second feature is a feature that is mutually exclusive with the first feature, the cloud management platform, after determining that the second feature is online, performs an offline operation on the second feature, and then performs an online operation on the first feature.

9. The method according to any one of claims 1 to 8, characterized in that, The infrastructure includes a plurality of cloud instances, and the plurality of cloud instances are used to run the plurality of cloud services, and the plurality of cloud instances include physical servers, virtual machines, containers, micro virtual machines, and bare metal servers.

10. A cloud management platform, characterized by, The cloud management platform is used to manage an infrastructure, and the infrastructure is used to provide a plurality of cloud services for tenants, and the cloud management platform includes: A receiving module is configured to receive, through an management interface, an online request sent by the tenant, and the online request is used to indicate a first feature of a first cloud service to be online, and the plurality of cloud services include the first cloud service; A detection module is configured to detect, based on the online request, whether a second feature relied on by the first feature and a third feature relying on the first feature exist; An online module is configured to, if the second feature exists, after determining that the second feature is online, perform an online operation on the first feature. The online module is further configured to, if the third feature exists, perform an online operation on the first feature, and then perform an online operation on the third feature.

11. The cloud management platform of claim 10, wherein, The second feature belongs to the first cloud service or a second cloud service, and in the plurality of cloud services, the second cloud service is located downstream of the first cloud service.

12. The cloud management platform of claim 10 or 11, wherein, The third feature belongs to the first cloud service or a third cloud service, and in the plurality of cloud services, the third cloud service is located upstream of the first cloud service.

13. The cloud management platform of any of claims 10 to 12, wherein, The online module is configured to: Determine a plurality of microservices used to implement the first feature, and the first cloud service includes at least one microservice in the plurality of microservices; Change configuration items of the plurality of microservices, so that the first feature is completed to be online.

14. The cloud management platform of claim 13, wherein, The plurality of microservices include a first microservice and a second microservice, the first microservice is arranged in the first cloud service, and the second microservice is arranged in the fourth cloud service, and the online module is configured to: Obtain a first priority of the first cloud service and a second priority of the fourth cloud service; If the first priority is higher than the second priority, change a configuration item of the first microservice, and then change a configuration item of the second microservice, so that the first feature is completed to be online. If the second priority is higher than the first priority, changing a configuration item of the second microservice, and then changing a configuration item of the first microservice, so that the first feature completes the onlining.

15. The cloud management platform of claim 13, wherein, The multiple microservices include a first microservice and a second microservice, the first microservice is arranged in the first cloud service, and the second microservice is arranged in the fourth cloud service. The onlining module is configured to: obtain a third priority of the first microservice and a fourth priority of the second microservice; if the third priority is higher than the fourth priority, changing a configuration item of the first microservice, and then changing a configuration item of the second microservice, so that the first feature completes the onlining; 16. The cloud management platform of claim 14 or 15, wherein, if the fourth priority is higher than the third priority, changing a configuration item of the second microservice, and then changing a configuration item of the first microservice, so that the first feature completes the onlining.

17. The cloud management platform of any of claims 10 to 16, wherein, The first microservice is configured to implement a fourth feature of the first cloud service, and the second microservice is configured to implement a fifth feature of the fourth cloud service, and the fourth feature and the fifth feature constitute the first feature.

18. The cloud management platform of any of claims 10 to 17, wherein, The onlining module is configured to, if the second feature exists and the second feature and the first feature are mutually exclusive features, after determining that the second feature has been onlined, performing an offlining operation on the second feature first, and then performing an onlining operation on the first feature.

19. A cluster of computing devices, characterized in that, The infrastructure includes multiple cloud instances, and the multiple cloud instances are configured to run the multiple cloud services. The multiple cloud instances include physical servers, virtual machines, containers, micro virtual machines, and bare metal servers. The computing device cluster includes at least one computing device, and each computing device includes a processor and a memory.

20. A computer storage medium, comprising, The memory is configured to store instructions.

21. A computer program product, characterised in that, The processor is configured to execute the instructions to cause the computing device cluster to perform the method in any one of claims 1 to 9. The computer storage medium stores one or more instructions, and the instructions, when executed by one or more computers, cause the one or more computers to implement the method in any one of claims 1 to 9. The computer program product stores instructions, and the instructions, when executed by a computer, cause the computer to implement the method in any one of claims 1 to 9.

Images