Data processing method of cloud technology, cloud management platform and cluster

Abstract

The invention discloses a data processing method of a cloud technology, a cloud management platform and a cluster. The method comprises the steps that second metadata of each service instance in a plurality of service instances is backed up to resource nodes associated with the service instances in a cloud infrastructure, different service instances in the plurality of service instances are associated with different resource nodes, and the second metadata of the service instances are subsets of first metadata of the service instances; and when the storage device loses the second metadata of the first service instance in the plurality of service instances, acquiring the second metadata of the first service instance from the resource node associated with the first service instance, and storing the acquired second metadata of the first service instance into the storage device. According to the method, the metadata recovery duration of the service instance can be shortened, and online recovery of the metadata can be realized.

Description

Technical Field

[0001] The present application relates to the field of cloud technology, and in particular to a data processing method, a cloud management platform and a cluster of cloud technology. Background Art

[0002] With the development of cloud technology, cloud vendors can create multiple service instances on the cloud to provide services to different tenants. For example, a database instance is created on the cloud to provide data storage services to tenants. In order to ensure that the service instance can run normally, cloud vendors provide service instance management services to manage and control the service instance.

[0003] The service instance management service needs to use the metadata of the service instance to manage the service instance. Currently, the metadata of multiple service instances is centrally stored in a metadata database. In order to restore the metadata after it is lost, the metadata database is fully backed up and regularly backed up to obtain backup data. When metadata is lost in the metadata database, the backup data is used to restore the lost data in the metadata database.

[0004] Since the backup data is obtained by performing a full backup and regular incremental backup of the metadata database, the recovery of the metadata database using the backup data is a complete recovery of the metadata database. During the complete recovery of the metadata database, the service instance management service needs to be interrupted. In addition, the complete recovery of the metadata database takes a long time, so the service instance management service needs to be interrupted for a long time. Summary of the invention

[0005] The present application provides a cloud technology data processing method, a cloud management platform and a cluster, which can shorten the metadata recovery time of a service instance and realize online recovery of metadata.

[0006] In a first aspect, a data processing method based on cloud technology is provided, the method is applied to a cloud management platform connected to a cloud infrastructure, the cloud infrastructure is deployed with multiple service instances, the cloud management platform includes a storage device and a computing device, wherein the storage device is used to store first metadata of each service instance in the multiple service instances, and the computing device is used to manage the service instances based on the first metadata of the service instances, the cloud infrastructure includes at least one cloud data center, each cloud data center is provided with multiple servers, each of the multiple servers is used as a resource node or is used to run one or more resource nodes, and each of the multiple service instances is deployed in at least one resource node of the cloud infrastructure, the method includes: backing up second metadata of each service instance in the multiple service instances to a resource node associated with the service instance in the cloud infrastructure, wherein different service instances in the multiple service instances are associated with different resource nodes, and the second metadata of the service instance is a subset of the first metadata of the service instance; when the storage device loses the second metadata of the first service instance in the multiple service instances, obtaining the second metadata of the first service instance from the resource node associated with the first service instance, and storing the obtained second metadata of the first service instance in the storage device.

[0007] This method stores the metadata of different service instances in different resource nodes respectively, thus realizing separate storage of metadata of different service instances. In this way, when the storage device loses the metadata of a service instance, the metadata of the service instance can be obtained from the resource node associated with the service instance, and the obtained data can be restored to the storage device, thus realizing metadata recovery at the service instance granularity. Compared with the overall recovery of the metadata database, the time required for metadata recovery at the service instance granularity is shorter, and there is no need to interrupt the management and control services of other service instances, thus realizing online recovery of metadata.

[0008] In a possible implementation, the resource node associated with the first service instance is a resource node on which the first service instance is deployed. The storage space in the resource node used to store the second metadata of the first service instance is independent of the storage space in the resource node used to deploy the first service instance. In this way, a failure of the first service instance does not affect the acquisition of the metadata of the first service instance from the resource node.

[0009] In this implementation, the metadata of the first service instance can be stored in the resource node where the first service instance is located, without the need for a dedicated resource node to store the metadata of the first service instance, thereby improving the utilization of the resource node and reducing the cost of metadata backup.

[0010] In one possible implementation, the method also includes: recording the resource nodes associated with the first service instance in an association list; saving the association list; obtaining the second metadata of the first service instance from the resource nodes associated with the first service instance, including: obtaining the resource nodes associated with the first service instance based on the association list, and obtaining the second metadata of the first service instance from the resource nodes associated with the first service instance.

[0011] In the association list, the association relationship between the service instance identifier and the address of the resource node is recorded. In this way, when the metadata of a service instance needs to be obtained, the resource node associated with the service instance can be queried in the association list based on the service instance identifier, and then the metadata of the service instance can be obtained from the resource node.

[0012] In addition, the association list is specifically stored in a storage space outside the storage device, which can prevent the association list from being lost due to a storage device failure.

[0013] In one possible implementation, the multiple service instances also include a second service instance and a third service instance, wherein the priority level of the second service instance is greater than the priority level of the third service instance; the method also includes: when the storage device loses the second metadata of the second service instance and loses the second metadata of the third service instance, obtaining the second metadata of the second service instance from the resource node associated with the second service instance, and storing the obtained metadata of the second service instance in the storage device; then, obtaining the second metadata of the third service instance from the resource node associated with the third service instance, and storing the obtained second metadata of the third service instance in the storage device.

[0014] Different service instances may have different priority levels, for example, service instances of tenants with different priority levels may have different priority levels. In this implementation, when service instances with different priority levels are lost at the same time, metadata with a higher priority level is restored first, so that the management and control services of the service instances with a higher priority level can be restored to normal first.

[0015] In one possible implementation, the multiple service instances include at least two service instances belonging to the same tenant; the method also includes: when the storage device loses all or part of the second metadata of the service instances of at least two service instances, obtaining the second metadata of the at least two service instances from resource nodes associated with the at least two service instances, and storing the obtained second metadata of the at least two service instances in the storage device.

[0016] In this implementation, the metadata of the tenant's service instance can be restored according to the tenant granularity. In this way, the metadata of the tenant's service instance can be restored by the tenant's identifier. In addition, when a tenant has multiple service instances that need to restore metadata, there is no need to trigger the metadata restoration operation of each service instance separately, making the metadata restoration operation more convenient.

[0017] In a possible implementation, the second metadata is metadata that cannot be reproduced in the first metadata, or the reproduction time of the second metadata is greater than the reproduction time of other metadata in the first metadata.

[0018] The second metadata may also be referred to as key metadata, and the data in the first metadata other than the second metadata is referred to as non-key metadata. Key metadata cannot be regenerated or takes a long time to regenerate. Non-key metadata can be regenerated in a short time. When non-key metadata is lost, it can be quickly obtained by regenerating it.

[0019] In this implementation, when the key metadata of the service instance is backed up instead of the full metadata of the service instance, the amount of backed up data can be reduced.

[0020] In a second aspect, a cloud management platform is provided, wherein the cloud management platform is connected to a cloud infrastructure, wherein the cloud infrastructure is deployed with multiple service instances, the cloud management platform includes a storage device and a computing device, wherein the storage device is used to store first metadata of each service instance in the multiple service instances, and the computing device is used to manage the service instances based on the first metadata of the service instances, the cloud infrastructure includes at least one cloud data center, each cloud data center is provided with multiple servers, each of the multiple servers is used as a resource node or is used to run one or more resource nodes, and each of the multiple service instances is deployed in at least one resource node of the cloud infrastructure, and the cloud management platform includes: a backup module, used to back up second metadata of each service instance in the multiple service instances to a resource node associated with the service instance in the cloud infrastructure, wherein different service instances in the multiple service instances are associated with different resource nodes, and the second metadata of the service instance is a subset of the first metadata of the service instance; an acquisition module, used to acquire the second metadata of the first service instance from the resource node associated with the first service instance when the storage device loses the second metadata of the first service instance in the multiple service instances, and store the acquired second metadata of the first service instance in the storage device.

[0021] In a possible implementation manner, the resource node associated with the first service instance is a resource node on which the first service instance is deployed.

[0022] In one possible implementation, the cloud management platform also includes a recording module and a saving module; the recording module is used to: record the resource nodes associated with the first service instance in the association list; the saving module is used to: save the association list; the acquisition module is used to: obtain the resource nodes associated with the first service instance based on the association list, and obtain the second metadata of the first service instance from the resource nodes associated with the first service instance.

[0023] In one possible implementation, the multiple service instances also include a second service instance and a third service instance, wherein the priority level of the second service instance is greater than the priority level of the third service instance; the acquisition module is used to: when the storage device loses the second metadata of the second service instance and loses the second metadata of the third service instance, obtain the second metadata of the second service instance from the resource node associated with the second service instance, and store the obtained metadata of the second service instance in the storage device; then, obtain the second metadata of the third service instance from the resource node associated with the third service instance, and store the obtained second metadata of the third service instance in the storage device.

[0024] In one possible implementation, the multiple service instances include at least two service instances belonging to the same tenant; the acquisition module is used to: when the storage device loses all or part of the second metadata of the service instances of at least two service instances, obtain the second metadata of the at least two service instances from the resource nodes associated with the at least two service instances, and store the obtained second metadata of the at least two service instances in the storage device.

[0025] In a possible implementation, the second metadata is metadata that cannot be reproduced in the first metadata, or the reproduction time of the second metadata is greater than the reproduction time of other metadata in the first metadata.

[0026] In a third aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the method provided in the first aspect.

[0027] In a fourth aspect, a computer-readable storage medium is provided, comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method provided in the first aspect.

[0028] In a fifth aspect, a computer program product comprising instructions is provided. When the instructions are executed by a computer device cluster, the computer device cluster executes the method provided in the first aspect.

[0029] The beneficial effects of the second to fifth aspects can be referred to the above introduction to the beneficial effects of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A schematic diagram of a system architecture provided for an embodiment of the present application;

[0031] Figure 2 A schematic diagram of a system architecture provided for an embodiment of the present application;

[0032] Figure 3 A schematic diagram of an association list provided in an embodiment of the present application;

[0033] Figure 4 A schematic diagram of a system architecture provided for an embodiment of the present application;

[0034] Figure 5 A flowchart of a data processing method provided in an embodiment of the present application;

[0035] Figure 6 A schematic diagram of the structure of a cloud management platform provided in an embodiment of the present application;

[0036] Figure 7 A schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0037] Figure 8 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0038] Fig. 9 A schematic diagram of a structure of a computing device cluster connected via a network provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The scheme provided by the embodiment of the present application will be described below in conjunction with the accompanying drawings. In the embodiment of the present application, "multiple" means two or more, and "multiple" means two or more. "First", "second", etc. are only used to distinguish similar objects and are not necessarily used to describe a specific order or number of objects.

[0040] To facilitate understanding of the solutions provided by the embodiments of the present application, the technical terms that may be involved in the embodiments of the present application are first introduced.

[0041] Cloud technology refers to a hosting service that unifies hardware, software, network and other resources within a wide area network or local area network to achieve data computing, storage, processing and sharing.

[0042] Cloud infrastructure: also known as infrastructure, is the facility that supports cloud computing services, including at least one data center. Each data center includes multiple servers. Cloud instances such as virtual machines (VMs) or containers run on the servers to achieve elastic cloud computing services. For example, when the cloud infrastructure includes multiple data centers, the multiple data centers can be distributed in different geographical areas, and the data centers can be remotely connected through a backbone network.

[0043] Tenant: A user who rents infrastructure. Tenants can register accounts on the cloud management platform operated by the cloud service provider through a browser or other client. The cloud service provider will record the accounts of different tenants, isolate the cloud service instances of different tenants based on the accounts, and have full access to the cloud service instances they own.

[0044] Virtual private cloud (VPC): used to build an isolated and private virtual network environment for cloud resources such as cloud servers, cloud containers, and cloud databases.

[0045] Subnet: It is an Internet Protocol (IP) address block in a virtual private cloud. At least one subnet is deployed in a virtual private cloud, and all cloud resources in the virtual private cloud are deployed in the subnet.

[0046] Cloud instance: also known as virtual computing device or virtual computing instance, refers to a complete computer system with a complete hardware system that is simulated by software and runs in a completely isolated environment. The hardware system of the computing instance is a virtual hardware system obtained by virtualizing the physical hardware. A complete computing instance has an independent virtual computing system (such as a central processing unit (CPU)) and a virtual disk. The computing instance that needs to communicate with the outside world also has an independent virtual network card.

[0047] Resource node: A node that has computing, storage and other resources and can process and store data. A resource node can be a physical machine, such as a server. A resource node can also be a cloud instance.

[0048] Service instance: A collection of programs or processes used to provide services such as data storage and data computing. Common service instances include database instances, data warehouse service instances, containers, etc. A service instance can be deployed in at least one resource node.

[0049] Cloud management platform: A platform provided by cloud service providers for interacting with users. Users can register accounts on the cloud management platform and rent cloud services with their accounts, thereby becoming tenants of cloud services. The cloud management platform is also used to manage cloud infrastructure and isolate computing, network, and / or storage resources rented by different tenants based on their accounts. Typically, a cloud management platform can be implemented as one or more microservice clusters. For example, a cloud management platform can be implemented as a distributed management and control system consisting of multiple microservice clusters.

[0050] Microservice cluster: also known as microservice architecture, is a service-oriented architecture (SOA) that divides complex systems into multiple small services or applications. Small services or applications are called microservices. Each microservice is responsible for implementing an independent business logic. Microservices are built around business functions and can be deployed independently. Microservices are interdependent and can provide a range of functions. Microservices are easy to understand and modify, bringing flexibility in language and framework selection. Microservices can run in containers. Among them, containers containing multiple microservices with high mutual dependence can constitute a container group. Among them, in the K8S (kubernetes) system, container groups can be encapsulated into pods.

[0051] Service instance management and control service: It is a service provided by the cloud management platform to manage and control service instances deployed in the cloud infrastructure. The cloud service management and control service can provide tenants with fine-grained service instance full life cycle management and operation and maintenance services. For example, the database management and control service can provide tenants with fine-grained database instance full life cycle management and operation and maintenance services.

[0052] Metadata of service instances: data used to describe service instances, including parameters of the domain model involved in the service instance, attribute information of the service instance, status information of the service instance in its life cycle, etc. The parameters of the domain model include CPU specifications, disk specifications, memory specifications, etc. Attribute information includes the IP address of the resource node where the service instance is located, the identifier (ID) of the service instance, the name of the service instance, computing resource ID, volume ID, network resource ID, etc. Status information includes: specification changing, failure, creation, deletion, etc.

[0053] Key metadata: mainly refers to metadata that is required by cloud service management and control services, which is non-renewable or takes a long time to regenerate. Metadata regeneration refers to repeated generation or repeated acquisition. Key metadata can be used by tenants to perform basic life cycle-related operations on service instances, such as viewing service instances, expanding the volume of service instances, and changing the CPU specifications of service instances. Common key metadata include: service instance identifier (ID), service instance name, computing resource ID, volume ID, network resource ID, management tenant ID, business tenant ID, instance parameter group ID, availability zone (AZ) number, etc. Among them, the computing resource ID may include the server ID, server group ID, and the ID of the resource node where the service instance is located. Among them, the ID of the resource node where the service instance is located may specifically be the IP address of the resource node. Volume ID may include system volume ID, backup volume ID, log volume ID, data volume ID, etc. Network resource ID may include management VPC ID, business VPC ID, business subnet ID, business network card ID, business network card IP address, business network card virtual IP (virtualIP, VIP) address, etc. Among them, the service instance ID is non-renewable metadata. This is because the service instance ID is the unique identifier of the service instance. The tenant may have reserved the service instance ID in a third system. If the service instance ID is regenerated, data inconsistency will occur. Therefore, the service instance ID is listed as non-renewable data. Management tenant ID, business tenant ID, instance parameter group ID, availability zone number, etc. are renewable, but the regeneration takes a long time. Specifically, relevant data can be queried in cloud infrastructure-related services through relevant interfaces, and computing resource IDs, volume IDs, and network resource IDs can be generated based on the data.

[0054] Non-key metadata: metadata of service instances other than key metadata. Common non-key metadata include periodic indicator data, instance parameter group data, workflow data, temporary data, etc.

[0055] Association list: A file used to record the association between a service instance and a resource node. The association list specifically records the association between the service instance ID and the resource node IP. The association list can be implemented as a data packet or a JavaScript object notation (JSON) file. The resource node is a resource node for storing backup data of the metadata of the service instance. Through the association list, the resource node where the backup data of the metadata of the service instance is located can be quickly queried, so that the backup data of the metadata of the service instance can be obtained from the resource node. In an embodiment of the present application, the backup data of the metadata of the service instance can be referred to as the backup data of the service instance.

[0056] Management and control metadata database: a database used to store metadata of service instances. The management and control metadata database is usually a relational database, such as a MySQL (my structured query language) database, a PostgreSQL database, etc. The cloud management platform uses the metadata in the management and control metadata database to implement service instance management and control services. For example, the state transition of the database instance is recorded in the management and control metadata. For another example, the resource node where the service instance is located is started using the metadata in the management and control metadata database to start the service instance. In addition, the cloud management platform can provide a console interface or interface (for example, an application programming interface (API)) for tenants to query relevant data in the management and control metadata database.

[0057] Typically, metadata of service instances deployed in cloud infrastructure are centrally stored in a control metadata database, which is often implemented as a traditional relational database such as MySQL and PostgreSQL. If a failure of such a database results in metadata loss, the recovery point objective (RPO) is greater than zero.

[0058] In one solution, a database backup technology is used to back up the management and control metadata database. Specifically, the metadata database is fully backed up and regularly backed up incrementally. Among them, regular incremental backup refers to backing up the data added within a preset time interval, and storing the obtained backup data and the backup data of the previous incremental backup and the backup data of the full backup in the backup database of the management and control metadata database. When data is lost in the management and control database, even if a small amount of metadata of the service implementation example is lost, the backup database is used to restore the lost data. This solution is a comprehensive recovery of the database. During the overall recovery, the metadata database cannot provide metadata for the service instance management service, so the service instance management service needs to be interrupted. In addition, the overall recovery of the database takes a long time (often more than 30 minutes), so the service instance management service needs to be interrupted for a long time. In addition, the backup data of the incremental backup may not include the latest metadata, resulting in the inability to restore the latest metadata.

[0059] In another solution, a full backup of the key metadata in the control database is performed. When key metadata is lost in the control database, even if a small amount of key metadata of the service instance is lost, the lost data is restored using the key metadata of the full backup. This solution is a full recovery of the key metadata in the database, which requires interruption of the service instance control service. In addition, the full recovery of key metadata takes a long time, which requires a long interruption of the service instance control service.

[0060] In particular, both of the above solutions centrally back up the metadata or key metadata of a large number of service instances to the same database or data table. Once the resource node where the database or data table is located fails, the backup data of a large number of service instances will be lost, resulting in the inability to restore the metadata of a large number of service instances.

[0061] The embodiment of the present application provides a data processing method of cloud technology. The method backs up the metadata of different service instances to different resource nodes respectively, and realizes the decentralized storage of backup data. When the metadata of one or some service instances in the management and control database is lost, the backup data can be obtained from the resource node at the granularity of the service instance, and the lost metadata can be restored using the backup data. The method uses the service instance as the granularity to disperse the backup data. Even if the resource node where the backup data of some service instances is located fails, it does not affect the backup data of other service instances, thereby reducing the overall risk of backup data loss. In addition, the backup data is dispersedly stored at the granularity of the service instance. When restoring the metadata, the service instance can be used as the granularity for restoration, which does not affect the management and control of other service instances by the service instance management and control service, that is, there is no need to interrupt the service instance management and control service. In particular, when the metadata of one or some service instances is lost, only the metadata of the service instance can be restored, without the need to restore the entire database or the entire table, thereby reducing the time and resource overhead of metadata recovery.

[0062] Next, the data processing method provided in the embodiment of the present application is introduced in detail.

[0063] Figure 1 1 shows a system architecture 100 provided in an embodiment of the present application. The system architecture 100 can implement the data processing method provided in an embodiment of the present application. Figure 1 As shown, the system architecture 100 includes a cloud management platform 110 and a cloud infrastructure 120 connected to the cloud management platform 110 .

[0064] The cloud infrastructure 120 includes at least one data center, and each data center is provided with a plurality of servers. Through the plurality of servers, a plurality of resource nodes, such as resource node 121, resource node 122, and resource node 123, etc., can be deployed in the cloud infrastructure 120. Specifically, in some embodiments, the server can be used as a resource node. That is, the resource node in the cloud infrastructure 120 can be a server. In some embodiments, the server can run one or more resource nodes. That is, the resource node in the cloud infrastructure 120 can be a cloud instance running on a server, such as a virtual machine, a container, etc.

[0065] Resource nodes can be used to deploy service instances, wherein a service instance can be deployed in at least one resource node. For example, resource node 121 deploys service instance 210, resource node 122 deploys service instance 220, and resource node 123 deploys service instance 230.

[0066] The cloud management platform 110 includes a computing device 111 and a storage device 112. The storage device 112 is used to store metadata of service instances in the cloud infrastructure 120. The computing device 111 is used to manage the service instances in the cloud infrastructure 120 using the metadata of the service instances stored in the storage device 112, that is, the computing device 111 is used to use the metadata of the service instances stored in the storage device 112 to provide service instance management and control services for users.

[0067] The computing device 111 may generate or obtain metadata when managing a service instance in the cloud infrastructure 120. For example, the management of a service instance includes the creation of a service instance, such as Figure 1 As shown, the user can send a service instance creation work order to the computing device 111. The computing device 111 creates a service instance work order and creates a service instance in the cloud infrastructure 120. In the process of creating a service instance, the computing device 111 can generate a service instance ID of the service instance, and obtain the computing resource ID, volume ID, network resource ID, etc. of the service instance. Among them, when creating a service instance, the service instance can be deployed on a resource node, and the computing resource ID, volume ID, and network resource ID of the resource node where the service instance is deployed are used as the computing resource ID, volume ID, and network resource ID of the service instance, respectively. In one example, when creating a service instance, the computing device 120 can select available computing resources, storage volumes, network resources, etc. in the cloud infrastructure 120, and use the selected computing resources, storage volumes, network resources, etc. to create a resource node, and deploy the service instance on the created resource node. In one example, when creating a service instance, if there is an available resource node in the cloud infrastructure 120, the service instance can be deployed on the resource node.

[0068] When managing the service instance in the cloud infrastructure 120, the computing device 111 may modify the metadata of the service instance. For example, if the storage volume of the service instance fails and a new storage volume is allocated for the service instance, the volume ID of the service instance is modified from the ID of the original storage volume to the ID of the new storage volume. The computing device 111 stores the modified metadata of the service instance in the storage device 112.

[0069] The metadata of the service instance may be backed up. In some embodiments, the backup of the metadata of the service instance may be performed by the computing device 111. Specifically, the computing device 111 may copy the metadata of the service instance and use the copy result as the backup data of the service instance. In some embodiments, the computing device 111 may identify the key metadata of the service instance. Exemplarily, the computing device 111 may identify the key metadata of the service instance through a whitelist or a blacklist. The whitelist lists the key metadata, and the computing device 111 identifies the metadata of the service instance that is within the whitelist as the key metadata of the service instance. The blacklist lists the non-key metadata, and the computing device 111 identifies the metadata of the service instance that is outside the blacklist as the key metadata of the service instance. The computing device 111 may copy the key metadata of the service instance and use the copy result as the backup data of the service instance.

[0070] In some embodiments, the computing device 111 may obtain metadata or key metadata of each service instance from the storage device 121 , and use the obtained metadata or key metadata of the service instance as backup data of the service instance.

[0071] In some embodiments, Figure 1As shown, the computing device 111 may include an interception module. The interception module is used to intercept the metadata of the service instance, and copy the metadata of the intercepted service instance to obtain the backup data of the service instance. Wherein, whenever the computing device 111 generates or obtains the metadata of the service instance, the interception module can intercept and copy the metadata generated or obtained by the computing device 111 to obtain the backup data of the service instance. And, whenever the computing device 111 modifies the metadata of the service instance, the interception module can intercept and copy the metadata modified by the computing device 111 to obtain the backup data of the service instance. Alternatively, the interception module can obtain the metadata of the service instance from the storage device 112 to obtain the backup data of the service instance. In one example, the interception module intercepts or obtains the key metadata of the service instance, and accordingly, the backup data of the service instance obtained is the backup data of the key metadata of the service instance. In one example, the cloud management platform 110 is a microservice cluster, and the interception module can be a microservice. The interception module can intercept the metadata of the service instance based on the aspect technology. In one example, the aspect technology can specifically be the aspect-oriented programming (AOP) technology in the Spring framework. In one example, the storage device 112 is specifically a database, and the interception module can be implemented as a trigger of the database. Whenever the metadata in the data table in the database is updated, the interception module triggers a key event, and the key event is used to obtain the updated metadata and obtain the backup data of the service instance. Among them, the data table can be a key table that records key metadata, and accordingly, the obtained metadata is key metadata. In one example, the interception module can be started before other modules in the computing device 111. In one example, the interception module can be started simultaneously with other modules in the computing device 111. In some embodiments, the interception module can be started after other modules in the computing device 111 are started.

[0072] In some embodiments, when the computing device 111 deletes one or some metadata of a service instance from the storage device 112, if the backup data of the service instance includes the deleted metadata, the computing device 111 can delete the metadata from the backup data stored in the resource node through the (remote procedure call, RPC) protocol.

[0073] In the above manner, the backup data of each service instance in the cloud infrastructure 120 can be obtained, for example, the backup data 211 of the service instance 210 can be obtained, the backup data 221 of the service instance 220 can be obtained, and the backup data 231 of the service instance 230 can be obtained.

[0074] The computing device 111 may store the backup data of the service instance in a resource node in the cloud infrastructure 120, wherein the backup data of different service instances are stored in different resource nodes. For ease of description, the resource node for storing the backup data of the service instance may be referred to as a resource node associated with the service instance.

[0075] In some embodiments, Figure 1 As shown, the resource node where the service instance is located and the resource node associated with the service instance are the same resource node. Among them, the resource node where the service instance is located refers to the resource node where the service instance is deployed. That is to say, in this embodiment, the service instance and the backup data of the service instance are in the same resource node, so that the decentralized storage of the backup data of the service instance is achieved without adding additional resource overhead. Exemplarily, in the resource node, the service instance and the backup data of the service instance are independent of each other to prevent the failure of the service instance, which causes the backup data of the service instance to be unreadable.

[0076] In some embodiments, the resource node where the service instance is located and the resource node associated with the service instance are different resource nodes. For example, the resource node where the service instance 210 is located is 121, and the resource node associated with the service instance 210 is resource node 121', the resource node where the service instance 220 is located is 122, and the resource node associated with the service instance 220 is resource node 122', the resource node where the service instance 230 is located is 123, and the resource node associated with the service instance 220 is resource node 123'. In this embodiment, the backup data of the service instance is stored on a resource node other than the resource node where the service instance is located, which can prevent the failure of the resource node where the service instance is located, resulting in the inability to read the backup data of the service instance.

[0077] In some embodiments, the computing device 111 may store the backup data of the service instance in a JSON file, and store the JSON file in a resource node associated with the service instance through an RPC protocol.

[0078] In some embodiments, the computing device 111 may record the resource nodes associated with the service instance in an association list and save the association list. Figure 3As shown, the association relationship between the service instance ID and the IP address of the resource node associated with the service instance can be recorded in the association list. For example, the IP address of the resource node associated with the service instance whose service instance ID is instance001 is 100.64.78.123, the IP address of the resource node associated with the service instance whose service instance ID is instance002 is 100.64.78.124, ... When it is necessary to restore the metadata or key metadata of a service instance, the resource node associated with the service instance can be quickly queried through the association list, so that the backup data of the service instance can be obtained from the resource node in a timely manner.

[0079] Among them, Figure 1 and Figure 2 As shown, the computing device 111 stores the association list in a storage space outside the storage device 112 , that is, does not store the association list in the storage device 112 , to prevent the association list from being lost due to a failure of the storage device 112 or data loss.

[0080] When the storage device 112 loses metadata or key metadata of a service instance, the computing device 111 may obtain backup data of the service instance from a resource node associated with the service instance, and use the backup data to restore the lost data in the storage device 112 . The details are as follows.

[0081] Generally speaking, when the storage device 112 loses metadata of a service instance, the service instance may be abnormal (for example, the service instance cannot be started, the service instance executes business abnormally, etc.). Figure 4 When a user (such as a tenant or an operation and maintenance personnel) finds that a service instance is abnormal, the user can fill in a fault reporting ticket through an interface (such as an operation and maintenance interface or a user interface, etc.) or interface provided by the cloud management platform 110. The service instance ID and / or tenant ID can be filled in the fault reporting ticket.

[0082] The computing device 111 can obtain the fault reporting work order and obtain the service instance ID or tenant ID from the fault reporting work order. When the tenant ID is obtained from the fault reporting work order, the service instance ID associated with the tenant ID can be obtained based on the tenant ID. Exemplarily, the service instance ID associated with the tenant ID can be queried from a third-party system (such as a cloud billing system). The tenant ID represents the tenant, the service instance ID represents the service instance, and the service instance ID associated with the tenant ID represents the tenant represented by the tenant ID.

[0083] The computing device 111 can obtain the resource node associated with the service instance represented by the service instance ID based on the obtained service instance ID. Exemplarily, the computing device 111 can query the resource node associated with the service instance in the association list based on the service instance ID. Specifically, the IP address of the resource node associated with the service instance can be queried.

[0084] After obtaining the resource node associated with the service instance, the computing device 111 may send a backup data acquisition request to the resource node associated with the service instance. The resource node associated with the service instance may respond to the backup data acquisition request and send the backup data of the service instance to the computing device 111. After receiving the backup data of the service instance, the computing device 111 may store the backup data in the storage device 112, thereby restoring the lost data in the storage device 112.

[0085] In some embodiments, the backup data acquisition request may specifically be a metadata parsing request. The computing device 111 may parse the backup data stored in the resource node using the metadata parsing request through the RPC protocol to obtain a parsing result. The backup data may be parsed into metadata that meets the format requirements of the storage device 112, that is, the data format of the parsing result meets the format requirements of the storage device 112. The computing device 111 may store the parsing result in the storage device 112, thereby restoring the lost data in the storage device 112.

[0086] The above example introduces the system architecture 100 provided by the embodiment of the present application. Next, in conjunction with the system architecture 100, the implementation process of the data processing method provided by the embodiment of the present application is introduced.

[0087] The method is applied to a cloud management platform 110 connected to a cloud infrastructure 120, wherein the cloud infrastructure 120 is deployed with multiple service instances, and the cloud management platform 110 includes a storage device 112 and a computing device 111, wherein the storage device 112 is used to store the first metadata of each service instance in the multiple service instances, and the computing device 111 is used to manage the service instance based on the first metadata of the service instance, and the cloud infrastructure 120 includes at least one cloud data center, each cloud data center is provided with multiple servers, and the servers in the multiple servers are used as resource nodes or used to run one or more resource nodes, and each service instance in the multiple service instances is deployed in at least one resource node of the cloud infrastructure. The first metadata of the service instance includes key metadata and non-key metadata of the service instance.

[0088] like Figure 5 As shown, the method comprises the following steps. Exemplarily, Figure 5 The method shown may be executed by the computing device 111 .

[0089] Step 501, backs up the second metadata of each service instance in the multiple service instances to a resource node associated with the service instance in the cloud infrastructure, wherein different service instances in the multiple service instances are associated with different resource nodes, and the second metadata of the service instance is a subset of the first metadata of the service instance.

[0090] The second metadata of different service instances are backed up to different resource nodes respectively, so as to achieve the decentralized storage of the second metadata of multiple service instances. In this way, when metadata recovery is needed, metadata recovery can be performed based on the granularity of service instances.

[0091] In some embodiments, the second metadata of the service instance may be key metadata of the service instance. In other words, the second metadata of the service instance is a proper subset of the first metadata of the service instance, the second metadata of the service instance is metadata that cannot be regenerated in the first metadata of the service instance, or the regeneration time of the second metadata of the service instance is greater than the regeneration time of other metadata in the first metadata of the service instance.

[0092] In some embodiments, the second metadata of the service instance may be the full set of the first metadata of the service instance, that is, the second metadata of the service instance is equal to the first metadata of the service instance.

[0093] In some embodiments, the resource node associated with the service instance is the resource node where the service instance is deployed. That is, the second metadata of the service instance is backed up to the resource node where the service instance is deployed. In this way, the decentralized storage of the second metadata of the service instance is achieved without increasing resource overhead.

[0094] Step 502: When the storage device 112 loses the second metadata of the first service instance among the multiple service instances, the second metadata of the first service instance is obtained from the resource node associated with the first service instance, and the obtained second metadata of the first service instance is stored in the storage device 112. The second metadata is a subset of the first metadata, so the loss of the second metadata may refer to the loss of only the second metadata, or may refer to the loss of the first metadata.

[0095] When the storage device 112 loses the second metadata of the first service instance, the second metadata of the first service instance can be restored by simply storing the second metadata of the first service instance in the storage device 112. That is, in step 502, metadata recovery can be performed based on the service instance as the granularity, and there is no need to perform overall or whole-table recovery of the storage device 112 for the loss of metadata of one or some service instances, thereby reducing the metadata recovery time. During the period of restoring metadata for the service instance with lost metadata, the storage device 112 can still provide the computing device 111 with metadata of other service instances, without affecting the management and control of other service instances by the computing device 111, thereby achieving online recovery of metadata.

[0096] In some embodiments, the resource nodes associated with the service instance can be recorded in an association list, and the association list can be saved. In this way, when it is necessary to obtain the second metadata of the service instance, the resource nodes associated with the service instance can be quickly obtained through the association list, and the second metadata of the service instance can be obtained from the resource nodes. In addition, by recording the resource nodes associated with the service instance through the association list, the acquisition of the resource nodes associated with the service instance is not affected by the loss of data in the storage device 112, that is, in the case where the storage device 112 loses the resource nodes associated with the service instance, the resource nodes associated with the service instance can also be obtained through the association list.

[0097] In some embodiments, the priority levels of different service instances may be different. For example, if the priority level of tenant A1 is greater than the priority level of tenant A2, then the priority level of the service instance of tenant A1 is also greater than the priority level of the service instance of tenant A2. For another example, the priority levels of different service instances of the same tenant may also be different. Among them, the priority level of a service instance with high real-time requirements (such as a service instance that provides game screen rendering services) is greater than the priority level of a service instance with low real-time requirements (such as a service instance that provides email services). When it is necessary to restore the metadata of service instances with different priority levels, the service instances with higher priority levels are restored first.

[0098] Specifically, the plurality of service instances may include a second service instance and a third service instance, wherein the priority level of the second service instance is greater than the priority level of the third service instance. When the storage device 112 loses the second metadata of the second service instance and loses the second metadata of the third service instance, the second metadata of the second service instance is first obtained from the resource node associated with the second service instance, and the obtained metadata of the second service instance is stored in the storage device 112; then, the second metadata of the third service instance is obtained from the resource node associated with the third service instance, and the obtained second metadata of the third service instance is stored in the storage device 112.

[0099] In some embodiments, metadata recovery of service instances can be performed at the tenant granularity. For a tenant with at least two service instances, when the storage device 112 loses the second metadata of all or part of the service instances of the tenant, the tenant can enter the tenant ID in the fault reporting work order. Based on the tenant ID, the service instance of the tenant can be queried, and metadata recovery can be performed on the service instance of the tenant. That is, the second metadata of the service instance of the tenant can be obtained from the resource node of the service instance of the tenant, and the obtained second metadata can be stored in the storage device 112, thereby realizing metadata recovery of the service instance at the tenant granularity.

[0100] In some embodiments, after completing the metadata recovery of the service instance, the user can operate the service instance through the interface or interface provided by the cloud management platform 110 to verify the metadata recovery effect. For example, when the user finds that the service instance cannot be started, the user fills out a fault report ticket. The metadata of the corresponding service instance can be restored based on the service instance ID or tenant ID in the fault report ticket. After the metadata recovery is completed, the user can try to start the service instance to test whether the service instance can be started normally.

[0101] In summary, the data processing method provided by the embodiment of the present application stores the backup data of different service instances in a dispersed manner, and performs metadata recovery at the granularity of the service instance when performing metadata recovery. Compared with the overall recovery of the database or the entire table, the metadata recovery at the granularity of the service instance takes less time, and there is no need to interrupt the service instance management service, and online recovery is achieved.

[0102] See also Figure 6, the embodiment of the present application also provides a cloud management platform 600. The cloud management platform 600 is connected to a cloud infrastructure, and the cloud infrastructure is deployed with multiple service instances. The cloud management platform 600 includes a storage device (such as a storage device 112) and a computing device (such as a computing device 111), wherein the storage device is used to store the first metadata of a service instance in the multiple service instances, and the computing device is used to manage the service instance based on the first metadata of the service instance. The cloud infrastructure includes at least one cloud data center, and each cloud data center is provided with multiple servers, and the servers are used as resource nodes or for running one or more resource nodes. The service instance is deployed in at least one resource node of the cloud infrastructure. Figure 6 As shown, the cloud management platform 600 includes:

[0103] A backup module 610, configured to back up second metadata of a service instance among the multiple service instances to a resource node associated with the service instance in the cloud infrastructure, wherein different service instances among the multiple service instances are associated with different resource nodes, and the second metadata of the service instance is a subset of the first metadata of the service instance;

[0104] The acquisition module 620 is used to acquire the second metadata of the first service instance among the multiple service instances from the resource node associated with the first service instance when the storage device loses the second metadata of the first service instance, and store the acquired second metadata of the first service instance in the storage device.

[0105] In some embodiments, the resource node associated with the first service instance is a resource node on which the first service instance is deployed.

[0106] In some embodiments, the cloud management platform 600 also includes a recording module and a saving module; the recording module is used to: record the resource nodes associated with the first service instance in an association list; the saving module is used to: save the association list; the acquisition module 620 is used to: obtain the resource nodes associated with the first service instance based on the association list, and obtain the second metadata of the first service instance from the resource nodes associated with the first service instance.

[0107] In some embodiments, the multiple service instances also include a second service instance and a third service instance, wherein the priority level of the second service instance is greater than the priority level of the third service instance; the acquisition module 620 is used to: when the storage device loses the second metadata of the second service instance and loses the second metadata of the third service instance, obtain the second metadata of the second service instance from the resource node associated with the second service instance, and store the obtained metadata of the second service instance in the storage device; then, obtain the second metadata of the third service instance from the resource node associated with the third service instance, and store the obtained second metadata of the third service instance in the storage device.

[0108] In some embodiments, the multiple service instances include at least two service instances belonging to the same tenant; the acquisition module 620 is used to: when the storage device loses the second metadata of all or part of the service instances of the at least two service instances, obtain the second metadata of the at least two service instances from the resource nodes associated with the at least two service instances, and store the obtained second metadata of the at least two service instances in the storage device.

[0109] In some embodiments, the second metadata is metadata that cannot be reproduced in the first metadata, or the reproduction time of the second metadata is greater than the reproduction time of other metadata in the first metadata.

[0110] The backup module 610 and the acquisition module 620 can be implemented by software or hardware. For example, the implementation of the backup module 610 is described below by taking the backup module 610 as an example. Similarly, the implementation of the acquisition module 620 can refer to the implementation of the backup module 610.

[0111] As an example of a software functional unit, the backup module 610 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the backup module 610 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code can be distributed in the same region or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code can be distributed in the same availability zone AZ or in different AZs, and each AZ includes a data center or multiple data centers with close geographical locations. Among them, usually a region can include multiple AZs.

[0112] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same VPC or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

[0113] As an example of a hardware functional unit, the backup module 610 may include at least one computing device, such as a server, etc. Alternatively, the backup module 610 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0114] The multiple computing devices included in the backup module 610 can be distributed in the same region or in different regions. The multiple computing devices included in the backup module 610 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the backup module 610 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0115] It should be noted that, in other embodiments, the backup module 610 may be used to execute Figure 5 In any step of the method shown, the acquisition module 620 can be used to perform Figure 5 The steps implemented by the backup module 610 and the acquisition module 620 can be specified as needed, and the steps implemented by the backup module 610 and the acquisition module 620 can be specified as needed. Figure 5 The different steps in the method shown implement the full functionality of the cloud management platform 600 .

[0116] The present application also provides a computing device 700. Figure 7As shown, computing device 700 includes: bus 702, processor 704, memory 706 and communication interface 708. Processor 704, memory 706 and communication interface 708 communicate through bus 702. Computing device 700 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in computing device 700.

[0117] The bus 702 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 The bus 702 may include a path for transmitting information between various components of the computing device 700 (eg, the memory 706, the processor 704, and the communication interface 708).

[0118] The processor 704 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0119] The memory 706 may include a volatile memory, such as a random access memory (RAM). The memory 706 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0120] The memory 706 stores executable program codes, and the processor 704 executes the executable program codes to respectively implement the functions of the backup module 610 and the acquisition module 620, thereby implementing Figure 5 That is, the memory 706 stores the method for executing Figure 5 Instructions for the method shown.

[0121] The communication interface 708 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 communication networks.

[0122] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0123] like Figure 8 As shown, the computing device cluster includes at least one computing device 700. The memory 706 in one or more computing devices 700 in the computing device cluster may store the same Figure 5 Instructions for the method shown.

[0124] In some possible implementations, the memory 706 of one or more computing devices 700 in the computing device cluster may also store a memory for executing Figure 5 In other words, the combination of one or more computing devices 700 can jointly execute instructions for executing Figure 5 Instructions for the method shown.

[0125] It should be noted that the memory 706 in different computing devices 700 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the cloud management platform 600. That is, the instructions stored in the memory 706 in different computing devices 700 may implement the functions of one or more modules in the backup module 610 and the acquisition module 620.

[0126] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig. 9 A possible implementation is shown. Fig. 9 As shown, two computing devices 700A and 700B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 706 in the computing device 700A stores instructions for executing the functions of the backup module 610. At the same time, the memory 706 in the computing device 700B stores instructions for executing the functions of the acquisition module 620.

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

[0128] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to that of Figure 8 and Fig. 9 The difference is that the memory 706 in one or more computing devices 700 in the computing device cluster may store the same memory for executing Figure 5 Instructions for the method shown.

[0129] In some possible implementations, the memory 706 of one or more computing devices 700 in the computing device cluster may also store a memory for executing Figure 5 In other words, the combination of one or more computing devices 700 can jointly execute instructions for executing Figure 5 Instructions for the method shown.

[0130] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes Figure 5 The method shown.

[0131] The present application also provides a computer-readable storage medium. The computer-readable storage medium may be any available medium that can be stored by a computing device or a host migration device such as a data center that includes one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute Figure 5 The method shown.

[0132] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A data processing method based on cloud technology, characterized in that: The method is applied to a cloud management platform connected to a cloud infrastructure, wherein the cloud infrastructure is deployed with multiple service instances, the cloud management platform includes a storage device and a computing device, wherein the storage device is used to store first metadata of each of the multiple service instances, and the computing device is used to manage the service instances based on the first metadata of the service instances, the cloud infrastructure includes at least one cloud data center, each cloud data center is provided with multiple servers, each of the multiple servers is used as a resource node or is used to run one or more resource nodes, and each of the multiple service instances is deployed in at least one resource node of the cloud infrastructure, the method includes: Backing up the second metadata of each service instance in the multiple service instances to a resource node associated with the service instance in the cloud infrastructure, wherein different service instances in the multiple service instances are associated with different resource nodes, and the second metadata of the service instance is a subset of the first metadata of the service instance; When the storage device loses the second metadata of the first service instance among the multiple service instances, the second metadata of the first service instance is obtained from the resource node associated with the first service instance, and the obtained second metadata of the first service instance is stored in the storage device.

2. The method according to claim 1, characterized in that: The resource node associated with the first service instance is the resource node on which the first service instance is deployed.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: In the association list, record the resource nodes associated with the first service instance; saving the association list; The acquiring the second metadata of the first service instance from the resource node associated with the first service instance includes: Based on the association list, a resource node associated with the first service instance is obtained, and second metadata of the first service instance is acquired from the resource node associated with the first service instance.

4. The method according to any one of claims 1 to 3, characterized in that The multiple service instances further include a second service instance and a third service instance, wherein the priority level of the second service instance is greater than the priority level of the third service instance; the method further includes: When the storage device loses the second metadata of the second service instance and loses the second metadata of the third service instance, the second metadata of the second service instance is obtained from the resource node associated with the second service instance, and the obtained metadata of the second service instance is stored in the storage device; then, the second metadata of the third service instance is obtained from the resource node associated with the third service instance, and the obtained second metadata of the third service instance is stored in the storage device.

5. The method according to any one of claims 1 to 4, characterized in that The multiple service instances include at least two service instances belonging to the same tenant; the method further includes: When the storage device loses all or part of the second metadata of the at least two service instances, the second metadata of the at least two service instances is obtained from the resource nodes associated with the at least two service instances, and the obtained second metadata of the at least two service instances is stored in the storage device.

6. The method according to any one of claims 1 to 5, characterized in that The second metadata is metadata that cannot be reproduced in the first metadata, or a reproduction time length of the second metadata is greater than a reproduction time length of other metadata in the first metadata.

7. A cloud management platform, characterized in that: The cloud management platform is connected to a cloud infrastructure, wherein the cloud infrastructure is deployed with a plurality of service instances, the cloud management platform comprises a storage device and a computing device, wherein the storage device is used to store first metadata of each of the plurality of service instances, and the computing device is used to manage the service instances based on the first metadata of the service instances, the cloud infrastructure comprises at least one cloud data center, each cloud data center is provided with a plurality of servers, each of the plurality of servers is used as a resource node or is used to run one or more resource nodes, each of the plurality of service instances is deployed in at least one resource node of the cloud infrastructure, and the cloud management platform comprises: a backup module, configured to back up the second metadata of each service instance in the multiple service instances to a resource node associated with the service instance in the cloud infrastructure, wherein different service instances in the multiple service instances are associated with different resource nodes, and the second metadata of the service instance is a subset of the first metadata of the service instance; An acquisition module is used to acquire the second metadata of the first service instance from the resource node associated with the first service instance when the storage device loses the second metadata of the first service instance among the multiple service instances, and store the acquired second metadata of the first service instance in the storage device.

8. The cloud management platform according to claim 7, characterized in that: The resource node associated with the first service instance is the resource node on which the first service instance is deployed.

9. The cloud management platform according to claim 7 or 8, characterized in that: The cloud management platform also includes a recording module and a storage module; The recording module is used to: record the resource nodes associated with the first service instance in an association list; The saving module is used to: save the association list; The acquisition module is used to obtain the resource node associated with the first service instance based on the association list, and acquire the second metadata of the first service instance from the resource node associated with the first service instance.

10. The cloud management platform according to any one of claims 7 to 9, characterized in that: The multiple service instances further include a second service instance and a third service instance, wherein the priority level of the second service instance is greater than the priority level of the third service instance; The acquisition module is used to: when the storage device loses the second metadata of the second service instance and loses the second metadata of the third service instance, obtain the second metadata of the second service instance from the resource node associated with the second service instance, and store the obtained metadata of the second service instance in the storage device; then, obtain the second metadata of the third service instance from the resource node associated with the third service instance, and store the obtained second metadata of the third service instance in the storage device.

11. The cloud management platform according to any one of claims 7 to 10, characterized in that: The multiple service instances include at least two service instances belonging to the same tenant; The acquisition module is used to: when the storage device loses the second metadata of all or part of the service instances of the at least two service instances, obtain the second metadata of the at least two service instances from the resource nodes associated with the at least two service instances, and store the obtained second metadata of the at least two service instances in the storage device.

12. The cloud management platform according to any one of claims 7 to 11, characterized in that: The second metadata is metadata that cannot be reproduced in the first metadata, or a reproduction time length of the second metadata is greater than a reproduction time length of other metadata in the first metadata.

13. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 6.

15. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 6.

Images