Message processing method based on cloud management platform, and cloud management platform

Abstract

Disclosed in the present application are a message processing method based on a cloud management platform, and a cloud management platform. By means of the present application, the service processing efficiency can be improved, and the quality of service which can be provided by a cloud management platform can be improved. The method of the present application is implemented by means of a cloud management platform. The cloud management platform is used for managing infrastructure that provides cloud services, wherein the infrastructure includes a consumer instance and a producer instance. The method comprises: a cloud management platform receiving from a tenant a message processing policy for a consumer instance by means of a configuration interface, wherein the message processing policy includes a matching relationship between a grayscale message label and a grayscale instance label; and the cloud management platform configuring the message processing policy in the consumer instance, wherein the message processing policy is used for instructing the consumer instance to perform detection on a message from a producer instance, and if the message includes the grayscale message label and the consumer instance includes the grayscale instance label, the consumer instance processing the message to obtain a processing result of the message.

Description

A message processing method based on cloud management platform and cloud management platform

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 1, 2023, with application number 202311443256.5, and with the invention name “A message processing method based on a cloud management platform and a cloud management platform”, and claims priority to the Chinese patent application filed with the State Intellectual Property Office on January 23, 2024, with application number 202410094520.7, and with the invention name “A message processing method based on a cloud management platform and a cloud management platform”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of cloud technology, and in particular to a message processing method based on a cloud management platform and a cloud management platform. Background Art

[0003] With the rapid development of cloud technology, cloud vendors can use message queue (MQ) instances as the message transmission medium between producer instances and consumer instances. In this way, the producer instance that provides messages and the consumer instance that consumes messages are unaware of each other. Both are oriented to the MQ instance, which can ensure the information security between the producer instance and the consumer instance.

[0004] In related cloud service systems, since consumer instances can switch between non-grayscale and grayscale instances, a grayscale message queue can be created in the MQ instance, and a grayscale switch can be created in the producer and consumer instances. The producer instance can then use the grayscale switch to determine whether to produce grayscale messages, and the consumer instance can correspondingly use the grayscale switch to determine whether to subscribe to the grayscale message queue to receive grayscale messages from the producer instance.

[0005] In the above process, grayscale message processing requires the participation of the producer instance, MQ instance, and consumer instance. This grayscale message processing architecture means that all three instances are aware of this process. Since these three instances also need to process regular messages, the grayscale message processing process may affect the processing of regular messages, resulting in reduced business processing efficiency. Therefore, this grayscale message processing architecture comes at a cost.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a message processing method and a cloud management platform based on a cloud management platform, which can improve business processing efficiency and enhance the service quality that the cloud management platform can provide.

[0008] A first aspect of an embodiment of the present application provides a message processing method based on a cloud management platform. The cloud management platform implementing the method can be used to manage infrastructure that provides cloud services. The infrastructure may include consumer instances and producer instances. The method includes:

[0009] When a tenant needs to configure a message processing policy for a consumer instance, the cloud management platform can provide a configuration interface to the tenant. The tenant can then send the customized message processing policy for the consumer instance to the configuration interface, allowing the cloud management platform to receive the tenant's message processing policy through the configuration interface. The message processing policy includes a matching relationship between the tags of the tenant-defined grayscale messages and the tags of the grayscale instances. This matching relationship means that if a message carries a message tag that matches the tag of the grayscale message set by the tenant, the message is a grayscale message. Furthermore, if a consumer instance carries a version tag that matches the tag of the grayscale instance set by the tenant, the consumer instance is a grayscale instance. In this case, the two match.

[0010] After obtaining the message processing policy from the tenant, the cloud management platform can deploy the message processing policy in the tenant's consumer instance. At this point, the consumer instance has the ability to process grayscale messages. Then, when a consumer instance of the tenant receives a message from the producer instance (forwarded via the MQ instance), the consumer instance can parse the message tag carried by the message from the message and obtain the version tag carried by the consumer instance. It then detects whether the message tag of the message is the tag of the grayscale message and whether the version tag of the consumer instance is the tag of the grayscale instance. If the message tag of the message is the tag of the grayscale message and the version tag of the consumer instance is the tag of the grayscale instance, it means that the message is a grayscale message and the consumer instance is a grayscale instance. The two are a match, so the consumer instance can process the message, obtain the processing result of the message, and return it to the producer instance (forwarded via the MQ instance). At this point, the processing of the message is completed.

[0011] From the above method, we can see that since the tenant defines new grayscale rules, such as grayscale message tags, grayscale instance tags, and the matching relationship between the two, and deploys them in the tenant's consumer instance, the consumer instance can determine whether a message is a grayscale message based on the grayscale message tags, and whether it is a grayscale instance based on the grayscale instance tags. If the message is a grayscale message and the consumer instance is a grayscale instance, it indicates that it matches the message, so the consumer instance can directly process the message, thus completing the grayscale message processing independently. Therefore, the new grayscale rules are only deployed in the consumer instance, and the consumer instance completes the grayscale message processing based on the grayscale rules. The producer instance and MQ instance are unaware of this processing process. The producer instance and MQ instance only need to execute according to the regular message processing process (producer instance produces messages, MQ instance forwards messages). This can reduce the impact of the grayscale message processing process on the regular message processing process to a certain extent, thereby improving business processing efficiency and enhancing the service quality provided by the cloud management platform.

[0012] In one possible implementation, a message processing policy instructs a consumer instance to evaluate a message from a producer instance and obtain an evaluation value. If the evaluation value is less than a preset threshold, the consumer instance performs a check on the message. In the aforementioned implementation, after receiving a message from a producer instance, the consumer instance may first evaluate the message to obtain an evaluation value. The producer instance may then determine whether the evaluation value is greater than or equal to a preset threshold. If the evaluation value is less than the preset threshold, the message has passed the Quality of Service (QoS) evaluation. The consumer instance can then determine whether the message tag is a grayscale message tag and whether the version tag of the consumer instance is a grayscale instance tag. Thus, before determining whether to perform grayscale control on the message, the consumer instance can perform a QoS evaluation on the message in advance. If the QoS evaluation passes, the consumer instance can then perform subsequent grayscale control. This allows for a more comprehensive consideration of factors during the entire message processing process, helping to maintain the stable operation of the entire cloud service system and further improve the quality of service it can provide.

[0013] In one possible implementation, the message processing strategy is also used to indicate that if the evaluation value is greater than or equal to a preset threshold, the consumer instance processes the message and obtains the processing result of the message. In the aforementioned implementation, if the evaluation value of the message is greater than or equal to the preset threshold, it means that the message has not passed the QoS evaluation, so the consumer instance does not need to determine whether the message matches the consumer instance, but directly processes the message to obtain the processing result of the message, so as to quickly complete the processing of the message. It can be seen from this that before determining whether to perform grayscale control on the message, the consumer instance can perform QoS evaluation on the message in advance, and give priority to reliable distribution and processing of the message under the premise that the QoS evaluation fails. In this way, in the entire processing process of the message, the factors considered are more comprehensive, which is conducive to maintaining the stable operation of the entire cloud service system and further improving the service quality that the entire cloud service system can provide.

[0014] In one possible implementation, the message processing strategy is also used to indicate that if the message contains a tag of a non-grayscale message and the consumer instance contains a tag of a grayscale instance, the consumer instance does not process the message and returns the message. In the aforementioned implementation, if the message tag of the message is the tag of a non-grayscale message and the version tag of the consumer instance is the tag of a grayscale instance, it means that the message is a non-grayscale message and the consumer instance is a grayscale instance, so the two are mismatched. The consumer instance does not process the message and returns the message to the MQ instance. Therefore, the MQ instance can re-forward the message to the remaining consumer instances to have the non-grayscale instances among the remaining consumer instances process the message.

[0015] In one possible implementation, the message processing strategy is also used to indicate that if the message contains a label of a non-grayscale message and the consumer instance contains a label of a non-grayscale instance, the consumer instance processes the message to obtain a processing result of the message. In the aforementioned implementation, if the message label of the message is the label of a non-grayscale message, and the version label of the consumer instance is the label of a non-grayscale instance, it means that the message is a non-grayscale message and the consumer instance is a non-grayscale instance, and the two are matched by default, so the consumer instance processes the message to obtain a processing result of the message. Then, the consumer instance can return the processing result of the message to the producer instance that produced the message, and at this point, the processing of the message is completed.

[0016] In one possible implementation, the message processing strategy is also used to indicate that if the message contains a grayscale message tag and the consumer instance contains a non-grayscale instance tag, the consumer instance determines whether the remaining consumer instances contain the grayscale instance tag. If the remaining consumer instances contain the grayscale instance tag, the consumer instance updates the message evaluation value, does not process the message, and returns the message. In the aforementioned implementation, if the message tag of the message is the grayscale message tag, and the version tag of the consumer instance is the non-grayscale instance tag, it means that the message is a grayscale message and the consumer instance is a non-grayscale instance, and the two are mismatched. Therefore, the consumer instance can determine whether the version tag of the remaining consumer instances is the grayscale instance tag. If the version tag of the remaining consumer instances is the grayscale instance tag, it means that the message can be handed over to the grayscale instances in the remaining consumer instances for processing. Therefore, the consumer instance can update the message evaluation value in real time, does not process the message, and returns the message to the MQ instance. Then, the MQ instance can re-forward the message to the remaining consumer instances to have the grayscale instances in the remaining consumer instances process the message.

[0017] In one possible implementation, the message processing policy also instructs the consumer instance to process the message and obtain a processing result if the remaining consumer instances do not contain the grayscale instance's tag. In the aforementioned implementation, if the version tags of the remaining consumer instances are not grayscale instance tags, the message cannot be handed over to the remaining consumer instances for processing. Therefore, the consumer instance can directly process the message and obtain a processing result. The consumer instance can then return the message processing result to the producer instance that produced the message, thus completing the processing of the message.

[0018] In a possible implementation, the evaluation value includes at least one of the following: the number of returns and the message processing delay.

[0019] In one possible implementation, the tag of the grayscale message includes at least one of the following: information set by the tenant for users who use the producer instance, and information set by the tenant for the microservice or application running on the producer instance.

[0020] In one possible implementation, the label of the grayscale instance is the label of the new version set by the tenant for the consumer instance, and the label of the non-grayscale instance is the label of the old version set by the tenant for the consumer instance.

[0021] In one possible implementation, a consumer instance includes any of the following: a physical server, a bare metal server, a virtual machine, a micro-VM, and a container.

[0022] The second aspect of an embodiment of the present application provides a cloud management platform, which is used to manage the infrastructure that provides cloud services. The infrastructure includes consumer instances and producer instances. The cloud management platform includes: a receiving module, which is used to receive message processing policies for consumer instances from tenants through a configuration interface, and the message processing policies include a matching relationship between the labels of grayscale messages and the labels of grayscale instances; a configuration module, which is used to configure message processing policies in consumer instances, and the message processing policies are used to instruct consumer instances to detect messages from producer instances. If the message contains the label of the grayscale message and the consumer instance contains the label of the grayscale instance, the consumer instance processes the message to obtain a processing result of the message.

[0023] In one possible implementation, the message processing strategy is used to instruct the consumer instance to evaluate the message from the producer instance and obtain an evaluation value of the message. If the evaluation value of the message is less than a preset threshold, the consumer instance detects the message.

[0024] In one possible implementation, the message processing strategy is further used to indicate that if the evaluation value is greater than or equal to a preset threshold, the consumer instance processes the message to obtain a message processing result.

[0025] In one possible implementation, the message processing policy is further used to indicate that if the message contains a tag of a non-grayscale message and the consumer instance contains a tag of a grayscale instance, the consumer instance does not process the message and returns the message.

[0026] In one possible implementation, the message processing strategy is further used to indicate that if the message contains a non-grayscale message tag and the consumer instance contains a non-grayscale instance tag, the consumer instance processes the message to obtain a message processing result.

[0027] In one possible implementation, the message processing strategy is also used to indicate that if the message contains the label of a grayscale message and the consumer instance contains the label of a non-grayscale instance, the consumer instance determines whether the remaining consumer instances contain the label of the grayscale instance. If the remaining consumer instances contain the label of the grayscale instance, the consumer instance updates the evaluation value of the message, does not process the message, and returns the message.

[0028] In a possible implementation, the message processing strategy is further used to indicate that if other consumer instances do not contain the label of the grayscale instance, the consumer instance processes the message to obtain a processing result of the message.

[0029] In a possible implementation, the evaluation value includes at least one of the following: the number of returns and the message processing delay.

[0030] In one possible implementation, the tag of the grayscale message includes at least one of the following: information set by the tenant for users who use the producer instance, and information set by the tenant for the microservice or application running on the producer instance.

[0031] In one possible implementation, the label of the grayscale instance is the label of the new version set by the tenant for the consumer instance, and the label of the non-grayscale instance is the label of the old version set by the tenant for the consumer instance.

[0032] In one possible implementation, a consumer instance includes any of the following: a physical server, a bare metal server, a virtual machine, a micro-VM, and a container.

[0033] A third aspect of an embodiment of the present application provides a computing device cluster, which 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 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.

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

[0035] 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.

[0036] In an embodiment of the present application, when a tenant needs to configure a message processing policy for a consumer instance, the tenant can send the tenant's message processing policy for the consumer instance to the cloud management platform through the configuration interface provided by the cloud management platform. The message processing policy contains the matching relationship between the label of the grayscale message and the label of the grayscale instance. Then, the cloud management platform can configure the message processing policy in the tenant's consumer instance so that the consumer instance has the processing function for the grayscale message. Then, after the consumer instance receives the message from the producer instance, the consumer can detect the message. If the message contains the label of the grayscale message and the consumer instance contains the label of the grayscale instance, the consumer instance directly processes the message to obtain the processing result of the message. In the aforementioned process, since the tenant defines new grayscale rules, such as the grayscale message label, the grayscale instance label, and the matching relationship between the two, and deploys them in the tenant's consumer instance, the consumer instance can determine whether a message is a grayscale message based on the grayscale message label, and determine whether it is a grayscale instance based on the grayscale instance label. If the message is a grayscale message and the consumer instance is a grayscale instance, it means that it matches the message, so the consumer instance can directly process the message, thereby completing the grayscale message processing on its own. Therefore, the new grayscale rule is only deployed in the consumer instance, and the consumer instance completes the grayscale message processing based on the grayscale rule alone. The producer instance and MQ instance are unaware of this processing process. The producer instance and MQ instance only need to execute according to the regular message processing process (producer instance produces messages, MQ instance forwards messages). This can reduce the impact of the grayscale message processing process on the regular message processing process to a certain extent, thereby improving business processing efficiency and enhancing the service quality provided by the cloud management platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] FIG1 is a schematic diagram of the structure of a cloud service system provided in an embodiment of the present application;

[0038] FIG2 is a schematic diagram of the structure of a cloud management platform provided in an embodiment of the present application;

[0039] FIG3 is a schematic diagram of a structure of a consumer example provided in an embodiment of the present application;

[0040] FIG4 is a flow chart of a message processing method based on a cloud management platform according to an embodiment of the present application;

[0041] FIG5 is a schematic diagram of an application example of a message processing method based on a cloud management platform provided in an embodiment of the present application;

[0042] FIG6 is another schematic diagram of the structure of the cloud management platform provided in an embodiment of the present application;

[0043] FIG7 is a schematic diagram of a structure of a computing device provided in an embodiment of the present application;

[0044] FIG8 is a schematic diagram of a structure of a computing device cluster provided in an embodiment of the present application;

[0045] FIG9 is a schematic diagram of computer devices in a computer cluster provided by an embodiment of the present application being connected via a network. DETAILED DESCRIPTION

[0046] The embodiments of the present application provide a message processing method and a cloud management platform based on a cloud management platform, which can improve business processing efficiency and enhance the service quality that the cloud management platform can provide.

[0047] 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 are not necessarily 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, and this is merely a way of distinguishing the objects of the same attributes when describing them 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.

[0048] With the rapid development of cloud technology, cloud vendors can use MQ instances as the message transmission medium between producer instances and consumer instances. In this way, the producer instance that provides messages and the consumer instance that consumes messages are unaware of each other. Both are oriented to the MQ instance, which can ensure the information security between the producer instance and the consumer instance.

[0049] In the cloud service system of the related art, since the consumer instance can be updated from a non-grayscale instance to a grayscale instance (a grayscale instance is an instance of a new version, and a non-grayscale instance is an instance of an old version), a grayscale message queue can be created in the MQ instance, and a grayscale switch can be created in the producer instance and the consumer instance. Then, the producer instance can use the grayscale switch to decide whether to produce grayscale messages, and correspondingly, the consumer instance can use the grayscale switch to decide whether to subscribe to the grayscale message queue to receive grayscale messages from the producer instance (for example, these grayscale messages are usually used to test new versions of instances, i.e., grayscale instances, to determine whether the version update of the instance is feasible).

[0050] In the above process, grayscale message processing requires the participation of the producer instance, MQ instance, and consumer instance. This grayscale message processing architecture means that all three instances are aware of this process. Since these three instances also need to process regular messages, the grayscale message processing process may affect the processing of regular messages, resulting in reduced business processing efficiency. Therefore, this grayscale message processing architecture comes at a cost.

[0051] Furthermore, the grayscale message processing architecture often relies on the producer instance and consumer instance to determine whether to generate and receive grayscale messages through grayscale switches. The factors considered are relatively one-sided, resulting in a lack of reliability in the processing of grayscale messages, which is not conducive to maintaining the stable operation of the entire cloud service system and the service quality that the entire cloud service system can provide.

[0052] To address the above issues, an embodiment of the present application provides a message processing method based on a cloud management platform. This method can be implemented through a cloud service system. FIG1 is a schematic structural diagram of the cloud service system provided by an embodiment of the present application. As shown in FIG1 , the cloud service system includes: an infrastructure capable of providing cloud services and a cloud management platform for managing such infrastructure. The cloud management platform and the infrastructure are first introduced separately below:

[0053] The cloud management platform can coordinate the management of all cloud instances included in the infrastructure of the entire cloud service system (for example, the cloud management platform can create exclusive cloud instances for tenants, and these cloud instances are used to run the tenants' applications or microservices. For example, messages can be transmitted between tenants' cloud instances. The cloud instance that produces messages can be used as a producer instance, and the cloud instance that consumes messages can be used as a consumer instance. Then, the cloud management platform can deploy an MQ instance between the producer instance and the consumer instance to serve as a medium for transmitting messages between the two). It 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 login interfaces and configuration interfaces for access by tenants' clients (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. For another example, the cloud management platform can also send preset templates to the tenant's client through the editing interface, so the tenant's client can display the preset templates for the tenant to watch and use, so that the tenant can formulate elastic scaling policies for its exclusive scaling group on its client, and send the elastic scaling policies to the cloud management platform through the editing interface. For another example, the cloud management platform can also allow the tenant to send the message processing policy formulated by the tenant for its exclusive consumer instance to the cloud management platform through the client through the editing interface (the message processing policy usually includes a matching relationship between the label of the grayscale message and the label of the grayscale instance). Then the cloud management platform can configure the message processing policy in the tenant's consumer instance. Therefore, after the consumer instance receives the message forwarded by the MQ node from the producer instance, the consumer instance can determine whether the message is a grayscale message and whether it is a grayscale instance based on the message processing policy to determine whether it can process the message. This will not be expanded here.

[0054] As shown in Figure 2 (Figure 2 is a structural diagram of the cloud management platform provided by an embodiment of the present application), the cloud management platform includes an interface module, a control module and a storage module, wherein the interface module includes the aforementioned login interface and editing interface, etc. The interface module can be used to receive the message processing strategy formulated by the tenant for the consumer instance and the new version of the consumer instance. The control module is used to deploy the new version and the label of the new version to some consumer instances of the tenant. Then, the consumer instance with the new version deployed is the grayscale instance, and the consumer instance without the new version deployed is the non-grayscale instance (whose version is the old version). It is worth noting that the grayscale instance also has the label of the new version, that is, the label of the grayscale instance, and the non-grayscale instance has the label of the old version, that is, the label of the non-grayscale instance. The control module can also be used to deploy the message processing strategy in the sidecar of the consumer instance. The sidecar can determine whether to forward the message from the producer instance forwarded by the MQ instance based on the message processing strategy, and further forward it to the consumer process of the consumer instance for processing. The storage module can be used to store the version labels of each consumer instance (for example, the label of the new version and the label of the old version, etc.) and the message processing strategy for each consumer instance, etc.

[0055] The infrastructure may include multiple cloud instances, which may include producer instances that produce messages, MQ instances that cache and forward messages, and consumer instances that consume messages, etc. It should be noted that the embodiments of the present application mainly relate to consumer instances, and the consumer instances will be introduced in detail below. As shown in Figure 3 (Figure 3 is a structural diagram of a consumer instance provided by the embodiment of the present application), the consumer instance may include a sidecar (or agent) and a consumer process. One end of the sidecar of the consumer instance may be connected to the MQ instance for communication, and the other end of the sidecar of the consumer instance may be connected to the consumer process of the consumer instance for communication. Then, after the cloud management platform deploys the message processing strategy on the sidecar, it is equivalent to configuring the sidecar with a processing function for grayscale messages. When the sidecar receives a message forwarded by the MQ instance from the producer instance, the sidecar can detect whether the message contains the label of the grayscale message and whether the consumer instance contains the label of the grayscale instance (that is, determine whether the message is a grayscale message and whether it is a grayscale instance), so as to determine whether to forward the message to the consumer for processing based on the detection result.

[0056] It should be noted that the producer instance and consumer instance can belong to the same tenant (here, the tenant can be understood as the developer of the application or microservice) or different tenants. In addition, the messages produced by the producer instance usually come from its users (here, the users can be understood as the users of the application or microservice). Therefore, the message tag contained in the message usually contains user information. This user information can be used by the sidecar to determine whether the message tag is a grayscale message tag, that is, whether the message is a grayscale message.

[0057] Furthermore, producer instances, MQ instances, and consumer instances can essentially be understood as cloud instances, which can be presented in a variety of ways. For example, these cloud instances can be physical servers designated by the cloud management platform. For another example, these cloud instances can also be virtual machines (VMs) created by the cloud management platform on physical servers through virtualization technology. For another example, these cloud instances can also be containers (docker) created by the cloud management platform on physical servers through virtualization technology. For another example, these cloud instances can also be micro virtual machines (microVMs) created by the cloud management platform on physical servers through virtualization technology. For another example, these cloud instances can also be containers (docker) created by the cloud management platform on physical servers through virtualization technology. For another example, these cloud instances can also be bare metal servers designated by the cloud management platform, and so on.

[0058] Furthermore, cloud instances such as producer instances, MQ instances, and consumer instances can be set up at one or more sites, and the sites can be presented in various forms. For example, one or more sites can be multiple regions in the infrastructure, or one or more sites can be multiple availability zones in the infrastructure, or one or more sites can be at least one edge site and at least one central cloud site in the infrastructure, and so on.

[0059] Based on the above cloud service system, it can be known that the cloud management platform deploys a message processing strategy in the consumer instance under the instruction of the tenant, so that the consumer instance has the processing function for grayscale messages. After the consumer instance receives a message from the producer instance, it can judge whether the message is a grayscale message and whether it is a grayscale instance to determine whether it is suitable for processing the message. It can be seen that the processing of grayscale messages does not require the participation of producer instances and MQ instances. This can avoid the impact of grayscale message processing on conventional message processing to a certain extent, thereby ensuring business processing efficiency. In order to further understand the process, the following is a further introduction to the process in conjunction with Figure 4 (Figure 4 is a flow chart of a message processing method based on a cloud management platform provided in an embodiment of the present application). As shown in Figure 4, the method can be applied to the cloud service system shown in Figure 1. The cloud service provider includes a cloud management platform and an infrastructure for providing cloud services. These infrastructures include consumer instances and producer instances. The method includes:

[0060] 401. The cloud management platform receives a message processing policy for a consumer instance from a tenant through a configuration interface. The message processing policy includes a matching relationship between a label of a grayscale message and a label of a grayscale instance.

[0061] In this embodiment, when the tenant needs to configure a message processing policy for a consumer instance, the cloud management platform can provide a configuration interface to the tenant's client (for example, a message processing policy input field on the tenant interface, etc.), so the tenant can send the message processing policy customized by the tenant for the consumer instance to the configuration interface through the client, so that the cloud management platform receives the message processing policy through the configuration interface. It should be noted that the message processing policy may include a matching relationship between the label of the grayscale message set by the tenant for the consumer instance and the label of the grayscale instance. This matching relationship means that if the message label carried by a message is the label of the grayscale message set by the tenant, it means that the message is a grayscale message, and if the version label (also called instance label) carried by a consumer instance is the label of the grayscale instance set by the tenant, it means that the consumer instance is a grayscale instance. In other words, the message and the consumer instance are matched, so the message can be handed over to the consumer instance for processing.

[0062] Specifically, the label of the grayscale message can be presented in the following ways:

[0063] Since the messages received by the sender instance all come from the producer instance, the tenant can set labels for grayscale messages around the producer instance. The labels for grayscale messages can include one or more of the information set by the tenant for users using the producer instance and the information set by the tenant for the microservices or applications running on the producer instance. Among them, the information set by the tenant for users using the producer instance can include one or more of the following: a specific level set by the tenant for users using the producer instance, a specific identity document (ID) set by the tenant for users of the producer instance, a specific type set by the tenant for messages from the producer instance, a specific ID set by the tenant for applications or microservices running on the producer instance, etc.

[0064] Based on this, if a message's message tag contains one or more of the above information, the message tag can be considered a grayscale message tag, that is, the message is a grayscale message. If a message's message tag does not contain one or more of the above information, but contains other information, the message tag can be considered a non-grayscale message tag, that is, the message is a non-grayscale message.

[0065] For example, a tenant can set the label of a grayscale message to the specific level of the user using the producer instance, such as the label of a grayscale message to the user's level v0. Then, after the consumer instance receives the message forwarded by the MQ instance from the producer instance, the consumer instance can parse the message label carried by the message. If the message label indicates that the user's level is v0, the consumer instance can determine that the message label is the label of a grayscale message, that is, the message carries the label of a grayscale message, and therefore can determine that the message is a grayscale message. If the message label indicates that the user's level is v1, the consumer instance can determine that the message label is the label of a non-grayscale message, that is, the message carries the label of a non-grayscale message, and therefore can determine that the message is a non-grayscale message.

[0066] More specifically, the labels of grayscale instances can be presented in the following ways:

[0067] Since tenants can update consumer instances through the cloud management platform, for new versions of consumer instances, tenants can set a new version label in the consumer instance through the cloud management platform and use it as the label of the grayscale instance. For old versions of consumer instances, tenants can also set the old version label in the consumer instance through the cloud management platform and use it as the label of the non-grayscale instance.

[0068] Based on this, if a consumer instance's version tag is a new version tag, this version tag can be considered a tag for a grayscale instance. In other words, this consumer instance is a grayscale instance. If a consumer instance's version tag is a new version tag, this version tag can be considered a tag for a grayscale instance. In other words, this consumer instance is a grayscale instance.

[0069] For example, a tenant can set the tag of a grayscale instance to use the tag of version 2 of a consumer instance. Then, after the consumer instance receives a message forwarded by the MQ instance from the producer instance, it can obtain its own version tag. If the version tag is version 2, the consumer instance can determine that it is the tag of the grayscale instance, indicating that it is a grayscale instance. If the version tag is version 1, the consumer instance can determine that it is the tag of a non-grayscale instance, indicating that it is a non-grayscale instance.

[0070] 402. The cloud management platform configures a message processing strategy in the consumer instance. The message processing strategy is used to instruct the consumer instance to detect the message from the producer instance. If the message contains a grayscale message label and the consumer instance contains a grayscale instance label, the consumer instance processes the message and obtains the message processing result.

[0071] After obtaining the message processing strategy from the tenant, the cloud management platform can deploy the message processing strategy in the tenant's consumer instance. At this point, the consumer instance has the ability to process grayscale messages. Therefore, all subsequent operations performed by the consumer instance on the producer instance's messages can be understood as being implemented based on this functionality. Then, when a tenant's consumer instance receives a message from the producer instance forwarded by the MQ instance, the consumer instance can parse the message tag carried by the message from the message and obtain the version tag carried by the consumer instance. It can then detect whether the message tag of the message is the tag of the grayscale message and whether the version tag of the consumer instance is the tag of the grayscale instance.

[0072] If the message tag matches the grayscale message tag, and the consumer instance's version tag matches the grayscale instance tag, the message is a grayscale message and the consumer instance is a grayscale instance. Therefore, the two match, and the consumer instance processes the message to obtain the message processing result. Subsequently, the consumer instance can return the message processing result to the producer instance through the MQ instance, completing the message processing.

[0073] Specifically, before detecting whether the message tag of the message is a tag for a grayscale message and whether the version tag of the consumer instance is a tag for a grayscale instance, the consumer instance may perform the following operations:

[0074] After the consumer instance receives the message forwarded by the MQ instance from the producer instance, the consumer instance can first evaluate the message to obtain the evaluation value of the message. Then, the message sender instance can determine whether the evaluation value of the message is greater than or equal to the preset threshold (the size of the threshold can be set according to actual needs and is not limited here). If the evaluation value of the message is less than the preset threshold, it means that the message has passed the business performance evaluation and is a message in the normal processing flow. Then, the consumer instance can detect whether the message tag of the message is the tag of the grayscale message, and whether the version tag of the consumer instance is the tag of the grayscale instance.

[0075] It should be noted that the evaluation value of the message may include one or more of the number of times the message is returned by the (consumer instance) and the processing delay of the message, etc. For example, if the number of times the message is returned is less than the preset number, the consumer instance can detect whether the message tag of the message is the tag of the grayscale message, and whether the version tag of the consumer instance is the tag of the grayscale instance. For another example, if the processing delay of the message is less than the preset delay, the consumer instance can detect whether the message tag of the message is the tag of the grayscale message, and whether the version tag of the consumer instance is the tag of the grayscale instance, etc.

[0076] More specifically, after the consumer instance determines whether the evaluation value of the message is greater than or equal to a preset threshold, the consumer instance may further perform the following operations:

[0077] If the evaluation value of the message is greater than or equal to the preset threshold, it means that the message has not passed the business performance evaluation and is a message in the emergency processing process. In this case, the consumer instance does not need to determine whether the message matches the consumer instance, but directly processes the message to obtain the processing result of the message, so as to quickly complete the processing of the message.

[0078] It should be noted that the message evaluation value may include one or more of the number of times the message was returned and the processing delay of the message. For example, if the number of times the message was returned is greater than or equal to a preset number, the consumer instance may directly process the message to obtain the processing result of the message. For another example, if the processing delay of the message is greater than or equal to a preset delay, the consumer instance may directly process the message to obtain the processing result of the message, etc.

[0079] More specifically, after the consumer instance detects whether the message tag of the message is the tag of the grayscale message and whether the version tag of the consumer instance is the tag of the grayscale instance, the consumer instance may further perform the following operations:

[0080] If the message tag of the message is the tag of a non-grayscale message, and the version tag of the consumer instance is the tag of a grayscale instance, it means that the message is a non-grayscale message and the consumer instance is a grayscale instance, so the two are mismatched. The consumer instance does not process the message and returns the message to the MQ instance. Therefore, the MQ instance can re-forward the message to other consumer instances so that the other consumer instances perform the same operations as the consumer instance. I will not go into details here.

[0081] More specifically, after the consumer instance detects whether the message tag of the message is the tag of the grayscale message and whether the version tag of the consumer instance is the tag of the grayscale instance, the consumer instance may further perform the following operations:

[0082] If the message tag of the message matches the tag of a non-grayscale message, and the version tag of the consumer instance matches the tag of a non-grayscale instance, the message is a non-grayscale message and the consumer instance is a non-grayscale instance. Therefore, the two are matched by default. The consumer instance processes the message and obtains the processing result. Subsequently, the consumer instance can return the processing result of the message to the producer instance through the MQ instance, thus completing the processing of the message.

[0083] More specifically, after the consumer instance detects whether the message tag of the message is the tag of the grayscale message and whether the version tag of the consumer instance is the tag of the grayscale instance, the consumer instance may further perform the following operations:

[0084] If the message tag of the message is the tag of a grayscale message, and the version tag of the consumer instance is the tag of a non-grayscale instance, it means that the message is a grayscale message and the consumer instance is a non-grayscale instance, so the two are mismatched. The consumer instance can determine whether the version tags of the remaining consumer instances are the tags of grayscale instances (i.e., whether there are grayscale instances among the remaining consumer instances). If the version tags of the remaining consumer instances (any one of the consumer instances) are the tags of grayscale instances (i.e., there are grayscale instances among the remaining consumer instances), it means that the message can be handed over to the remaining consumer instances for processing. Therefore, the consumer instance can update the evaluation value of the message in real time, and does not process the message, and returns the message to the MQ instance. Then, the MQ instance can re-forward the message to the remaining consumer instances so that the remaining consumer instances perform the same operations as the consumer instance. This will not be repeated here.

[0085] It should be noted that since the evaluation value of the message may include one or more of the number of times the message is returned and the processing delay of the message, when the consumer instance updates the evaluation value of the message, it can be achieved by adding one to the number of times the message is returned and appropriately increasing the processing delay of the message.

[0086] More specifically, after determining whether the version tags of other consumer instances are the tags of the grayscale instance, the consumer instance may further perform the following operations:

[0087] If the version tags of the remaining consumer instances are not the same as the grayscale instance's, the message cannot be passed to other consumer instances for processing. Therefore, the consumer instance can directly process the message and obtain the message processing result. Subsequently, the consumer instance can return the message processing result to the producer instance through the MQ instance, thus completing the message processing.

[0088] In order to further understand the message processing method based on the cloud management platform provided by the embodiment of the present application, the following is a further introduction to the method in conjunction with a specific application example. Figure 5 is a schematic diagram of an application example of the message processing method based on the cloud management platform provided by the embodiment of the present application. As shown in Figure 5, the application example includes:

[0089] Assume that a sidecar of a consumer instance receives a message forwarded by an MQ instance from a producer instance. The sidecar can perform the following steps:

[0090] (1) Evaluate the message (e.g., QoS evaluation, etc.) to obtain an evaluation value for the message. Based on the evaluation value of the message, determine whether the message passes the evaluation (e.g., whether the evaluation value of the message is less than a certain threshold). If not, execute step (7). If passed, execute step (2).

[0091] (2) The sidecar determines whether the message is a grayscale message. If so, it executes step (3); if not, it executes step (5).

[0092] (3) The sidecar determines whether the consumer instance is a grayscale instance. If so, it executes step (7); if not, it executes step (4).

[0093] (4) The sidecar determines whether there is a grayscale instance among the other consumer instances. If not, it executes step (7); if so, it executes step (6).

[0094] (5) The sidecar determines whether the consumer instance is a non-grayscale instance. If so, it executes step (10); if not, it executes step (6).

[0095] (6) The sidecar updates the evaluation value of the message and returns the message to the MQ instance.

[0096] (7) The sidecar forwards the message to the consumer process of the consumer instance for processing.

[0097] In an embodiment of the present application, when a tenant needs to configure a message processing policy for a consumer instance, the tenant can send the tenant's message processing policy for the consumer instance to the cloud management platform through the configuration interface provided by the cloud management platform. The message processing policy contains the matching relationship between the label of the grayscale message and the label of the grayscale instance. Then, the cloud management platform can configure the message processing policy in the tenant's consumer instance so that the consumer instance has the processing function for the grayscale message. Then, after the consumer instance receives the message from the producer instance, the consumer can detect the message. If the message contains the label of the grayscale message and the consumer instance contains the label of the grayscale instance, the consumer instance directly processes the message to obtain the processing result of the message. In the aforementioned process, since the tenant defines new grayscale rules, such as the grayscale message label, the grayscale instance label, and the matching relationship between the two, and deploys them in the tenant's consumer instance, the consumer instance can determine whether a message is a grayscale message based on the grayscale message label, and determine whether it is a grayscale instance based on the grayscale instance label. If the message is a grayscale message and the consumer instance is a grayscale instance, it means that it matches the message, so the consumer instance can directly process the message, thereby completing the grayscale message processing on its own. Therefore, the new grayscale rule is only deployed in the consumer instance, and the consumer instance completes the grayscale message processing based on the grayscale rule alone. The producer instance and MQ instance are unaware of this processing process. The producer instance and MQ instance only need to execute according to the regular message processing process (producer instance produces messages, MQ instance forwards messages). This can reduce the impact of the grayscale message processing process on the regular message processing process to a certain extent, thereby improving business processing efficiency and enhancing the service quality provided by the cloud management platform.

[0098] Furthermore, in an embodiment of the present application, the processing of grayscale messages can be divided into two stages, the first stage is a comprehensive evaluation of the message, and the second stage is grayscale control of the message. Before the sidecar of the consumer instance determines whether to forward the message to the consumer process of the consumer instance for processing (i.e., grayscale control), it can conduct a comprehensive evaluation of the message in advance, so as to further implement subsequent grayscale control under the premise of ensuring the reliable distribution of the message. In this way, in the process of processing grayscale messages, the factors considered are more comprehensive, which is conducive to maintaining the stable operation of the entire cloud service system and further improving the service quality that the entire cloud service system can provide.

[0099] The above is a detailed description of the message processing 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. Figure 6 is another structural diagram of the cloud management platform provided in the embodiment of the present application. As shown in Figure 6, the cloud management platform is used to manage the infrastructure for providing cloud services. The infrastructure includes consumer instances and producer instances. The cloud management platform includes:

[0100] Receiving module 601 is used to receive a message processing strategy for a consumer instance from a tenant through a configuration interface, where the message processing strategy includes a matching relationship between the label of the grayscale message and the label of the grayscale instance; for example, receiving module 601 is used to implement step 401 in the embodiment shown in FIG4 .

[0101] Configuration module 602 is used to configure a message processing policy in the consumer instance. The message processing policy is used to instruct the consumer instance to detect messages from the producer instance. If the message contains a grayscale message tag and the consumer instance contains the grayscale instance tag, the consumer instance processes the message and obtains a message processing result. For example, configuration module 602 is used to implement step 402 in the embodiment shown in Figure 4.

[0102] In one possible implementation, the message processing strategy is used to instruct the consumer instance to evaluate the message from the producer instance and obtain an evaluation value of the message. If the evaluation value of the message is less than a preset threshold, the consumer instance detects the message.

[0103] In one possible implementation, the message processing strategy is further used to indicate that if the evaluation value is greater than or equal to a preset threshold, the consumer instance processes the message to obtain a message processing result.

[0104] In one possible implementation, the message processing policy is further used to indicate that if the message contains a tag of a non-grayscale message and the consumer instance contains a tag of a grayscale instance, the consumer instance does not process the message and returns the message.

[0105] In one possible implementation, the message processing strategy is further used to indicate that if the message contains a non-grayscale message tag and the consumer instance contains a non-grayscale instance tag, the consumer instance processes the message to obtain a message processing result.

[0106] In one possible implementation, the message processing strategy is also used to indicate that if the message contains the label of a grayscale message and the consumer instance contains the label of a non-grayscale instance, the consumer instance determines whether the remaining consumer instances contain the label of the grayscale instance. If the remaining consumer instances contain the label of the grayscale instance, the consumer instance updates the evaluation value of the message, does not process the message, and returns the message.

[0107] In a possible implementation, the message processing strategy is further used to indicate that if other consumer instances do not contain the label of the grayscale instance, the consumer instance processes the message to obtain a processing result of the message.

[0108] In a possible implementation, the evaluation value includes at least one of the following: the number of returns and the message processing delay.

[0109] In one possible implementation, the tag of the grayscale message includes at least one of the following: information set by the tenant for users who use the producer instance, and information set by the tenant for the microservice or application running on the producer instance.

[0110] In one possible implementation, the label of the grayscale instance is the label of the new version set by the tenant for the consumer instance, and the label of the non-grayscale instance is the label of the old version set by the tenant for the consumer instance.

[0111] In one possible implementation, a consumer instance includes any of the following: a physical server, a bare metal server, a virtual machine, a micro-VM, and a container.

[0112] 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 no further details will be given here.

[0113] Please refer to Figure 7, which is a schematic diagram of the structure of a computing device provided in an embodiment of the present application. As shown in Figure 7, the computing device 700 (which can be used to present the aforementioned cloud management platform) includes: a processor 701, a memory 702, a communication interface 703, and a bus 704. The processor 701, the memory 702, and the communication interface 703 are coupled via a bus (not labeled in the figure). The memory 702 stores instructions. When the execution instructions in the memory 702 are executed, the computing device 700 executes the method executed by the cloud management platform in the above method embodiment.

[0114] The computing device 700 may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For example, when a unit in the apparatus can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0115] The processor 701 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), other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0116] Memory 702 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. Nonvolatile memory may be read-only memory (ROM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may be 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 DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0117] Memory 702 stores executable program code, and processor 701 executes the executable program code to implement the functions of the aforementioned receiving module, configuration module, and other modules, thereby implementing the aforementioned message processing method based on the cloud management platform. In other words, memory 702 stores instructions for executing the aforementioned message processing method based on the cloud management platform.

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

[0119] In addition to the data bus, bus 704 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, an Extended Industry Standard Architecture (EISA) bus, a unified bus (Ubus or UB), a Compute Express Link (CXL), or a Cache Coherent Interconnect for Accelerators (CCIX). Buses can be categorized as address buses, data buses, and control buses.

[0120] Please refer to FIG8 , which is a schematic diagram of a computing device cluster provided in an embodiment of the present application. As shown in FIG8 , the computing device cluster 800 includes at least one computing device 700 .

[0121] 8 , the computing device cluster 800 includes at least one computing device 700. The memory 702 in one or more computing devices 700 in the computing device cluster 800 may store the same instructions for executing the above-mentioned message processing method based on the cloud management platform.

[0122] In some possible implementations, the memory 702 of one or more computing devices 700 in the computing device cluster 800 may also store partial instructions for executing the aforementioned cloud management platform-based message processing method. In other words, the combination of one or more computing devices 700 can jointly execute the aforementioned cloud management platform-based message processing method.

[0123] It should be noted that the memory 702 in different computing devices 700 in the computing device cluster 800 may store different instructions, each for executing a portion of the functions of the aforementioned cloud management platform. In other words, the instructions stored in the memory 702 in different computing devices 700 may implement the functions of one or more modules such as the receiving module and the configuration module.

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

[0125] Please refer to Figure 9, which is a schematic diagram of computer devices in a computer cluster provided by an embodiment of the present application being connected via a network. As shown in Figure 9, two computing devices 700A and 700B are connected via a network. Specifically, each computing device is connected to the network via a communication interface.

[0126] In a possible implementation, the memory of the computing device 700A stores instructions for executing functions of a receiving module and the like. Meanwhile, the memory of the computing device 700B stores instructions for executing functions of a configuration module and the like.

[0127] It should be understood that the functions of the computing device 700A shown in Figure 9 may also be completed by multiple computing devices. Similarly, the functions of the computing device 700B may also be completed by multiple computing devices.

[0128] An embodiment of the present application also relates to a computer storage medium, in which a program for signal processing is stored. When the computer storage medium is run on a computer, the computer executes the steps executed by the cloud management platform in the embodiment shown in Figure 4.

[0129] An embodiment of the present application also relates to a computer program product, which stores instructions that, when executed by a computer, enable the computer to execute the steps performed by the cloud management platform in the embodiment shown in FIG4 .

[0130] Those skilled in the art will 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.

[0131] In the several embodiments provided in this 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 merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.

[0132] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0133] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0134] 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 for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Claims

1. A message processing method based on a cloud management platform, characterized in that: The cloud management platform is used to manage the infrastructure for providing cloud services, the infrastructure including consumer instances and producer instances, and the method includes: The cloud management platform receives a message processing policy for the consumer instance from the tenant through a configuration interface, wherein the message processing policy includes a matching relationship between a label of a grayscale message and a label of a grayscale instance; The cloud management platform configures the message processing strategy in the consumer instance, and the message processing strategy is used to instruct the consumer instance to detect the message from the producer instance. If the message contains the label of the grayscale message and the consumer instance contains the label of the grayscale instance, the consumer instance processes the message to obtain the processing result of the message.

2. The method according to claim 1, characterized in that The message processing strategy is used to instruct the consumer instance to evaluate the message from the producer instance to obtain an evaluation value of the message. If the evaluation value of the message is less than a preset threshold, the consumer instance detects the message.

3. The method according to claim 2, characterized in that The message processing strategy is also used to indicate that if the evaluation value is greater than or equal to the preset threshold, the consumer instance processes the message to obtain a processing result of the message.

4. The method according to any one of claims 1 to 3, characterized in that: The message processing strategy is also used to indicate that if the message contains a tag of a non-grayscale message and the consumer instance contains a tag of the grayscale instance, the consumer instance does not process the message and returns the message.

5. The method according to any one of claims 1 to 4, characterized in that: The message processing strategy is also used to indicate that if the message contains the tag of the non-grayscale message and the consumer instance contains the tag of the non-grayscale instance, the consumer instance processes the message to obtain the processing result of the message.

6. The method according to any one of claims 1 to 5, characterized in that: The message processing strategy is also used to indicate that if the message contains the label of the grayscale message and the consumer instance contains the label of the non-grayscale instance, the consumer instance determines whether the remaining consumer instances contain the label of the grayscale instance. If the remaining consumer instances contain the label of the grayscale instance, the consumer instance updates the evaluation value of the message, does not process the message, and returns the message.

7. The method according to claim 6, characterized in that The message processing strategy is also used to indicate that if the remaining consumer instances do not contain the label of the grayscale instance, the consumer instance processes the message to obtain a processing result of the message.

8. The method according to any one of claims 1 to 7, characterized in that: The evaluation value includes at least one of the following: the number of returns and the processing delay of the message.

9. The method according to any one of claims 1 to 8, characterized in that: The tag of the grayscale message includes at least one of the following: information set by the tenant for a user who uses the producer instance, and information set by the tenant for a microservice or application running on the producer instance.

10. The method according to any one of claims 1 to 9, characterized in that: The label of the grayscale instance is the label of the new version set by the tenant for the consumer instance, and the label of the non-grayscale instance is the label of the old version set by the tenant for the consumer instance.

11. The method according to any one of claims 1 to 10, characterized in that: The consumer instance includes any one of the following: a physical server, a bare metal server, a virtual machine, a micro virtual machine, and a container.

12. A cloud management platform, characterized in that: The cloud management platform is used to manage the infrastructure for providing cloud services, the infrastructure including consumer instances and producer instances, and the cloud management platform includes: A receiving module, configured to receive a message processing strategy for the consumer instance from the tenant through a configuration interface, wherein the message processing strategy includes a matching relationship between a label of a grayscale message and a label of a grayscale instance; A configuration module is used to configure the message processing strategy in the consumer instance, and the message processing strategy is used to instruct the consumer instance to detect the message from the producer instance. If the message contains the label of the grayscale message and the consumer instance contains the label of the grayscale instance, the consumer instance processes the message to obtain the processing result of the message.

13. The cloud management platform according to claim 12, characterized in that: The message processing strategy is used to instruct the consumer instance to evaluate the message from the producer instance to obtain an evaluation value of the message. If the evaluation value of the message is less than a preset threshold, the consumer instance detects the message.

14. The cloud management platform according to claim 13, characterized in that: The message processing strategy is also used to indicate that if the evaluation value is greater than or equal to the preset threshold, the consumer instance processes the message to obtain a processing result of the message.

15. The cloud management platform according to any one of claims 12 to 14, characterized in that: The message processing strategy is also used to indicate that if the message contains a tag of a non-grayscale message and the consumer instance contains a tag of the grayscale instance, the consumer instance does not process the message and returns the message.

16. The cloud management platform according to any one of claims 12 to 15, characterized in that: The message processing strategy is also used to indicate that if the message contains the tag of the non-grayscale message and the consumer instance contains the tag of the non-grayscale instance, the consumer instance processes the message to obtain the processing result of the message.

17. The cloud management platform according to any one of claims 12 to 16, characterized in that: The message processing strategy is also used to indicate that if the message contains the label of the grayscale message and the consumer instance contains the label of the non-grayscale instance, the consumer instance determines whether the remaining consumer instances contain the label of the grayscale instance. If the remaining consumer instances contain the label of the grayscale instance, the consumer instance updates the evaluation value of the message, does not process the message, and returns the message.

18. The cloud management platform according to claim 17, characterized in that: The message processing strategy is also used to indicate that if the remaining consumer instances do not contain the label of the grayscale instance, the consumer instance processes the message to obtain a processing result of the message.

19. The cloud management platform according to any one of claims 12 to 18, characterized in that: The evaluation value includes at least one of the following: the number of returns and the processing delay of the message.

20. The cloud management platform according to any one of claims 12 to 19, characterized in that: The tag of the grayscale message includes at least one of the following: information set by the tenant for a user who uses the producer instance, and information set by the tenant for a microservice or application running on the producer instance.

21. The cloud management platform according to any one of claims 12 to 20, characterized in that: The label of the grayscale instance is the label of the new version set by the tenant for the consumer instance, and the label of the non-grayscale instance is the label of the old version set by the tenant for the consumer instance.

22. The cloud management platform according to any one of claims 12 to 21, characterized in that: The consumer instance includes any one of the following: a physical server, a bare metal server, a virtual machine, a micro virtual machine, and a container.

23. 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 11 according to the instructions.

24. 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 11.

25. 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 11.

Images