Snapshot management method based on cloud computing technology and cloud management platform

Abstract

A snapshot management method based on cloud computing technology includes: obtaining a target instance identifier input by a user, the target instance identifier indicating multiple target cloud instances in a cloud instance set; obtaining association attributes input by the user, the association attributes indicating the association relationships between the multiple target cloud instances; and creating a first snapshot based on the target instance identifier and the association attributes. In this application, the method constructs a snapshot for executing a target task by receiving multiple cloud instances selected by the user and the association relationships between them. The snapshot created by this method can quickly complete the creation and restoration of resources in a specified cloud instance and establish the association relationships between cloud instances, ensuring that the resources in the specified cloud instance can execute the target business. When executing the target business, this method does not orchestrate the resources of the corresponding cloud instance, allowing the resources of the corresponding cloud instance to execute other businesses after completing the target business.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, and in particular to a snapshot management method and cloud management platform based on cloud computing technology. Background Technology

[0002] In the cloud computing field, cloud services can execute related business operations by calling one or more cloud instances. However, in areas such as disaster recovery and backup, each disaster recovery or backup technology can only perform disaster recovery or backup on one cloud instance within the cloud service. For example, Cloud Backup and Recovery (CBR) can only back up cloud instances of Scalable File Server (SFS) Turbo, and cannot back up other cloud instances. If users use multiple backup technologies to back up multiple cloud instances within the cloud service, problems such as slow backup speeds and susceptibility to failures may occur. Summary of the Invention

[0003] To address the aforementioned issues, embodiments of this application provide a snapshot management method based on cloud computing technology. This method, when executing business operations based on created snapshots, does not orchestrate resources across different cloud instances, allowing resources on different cloud instances to execute arbitrary business operations. Furthermore, this application also provides a cloud management platform based on cloud computing technology corresponding to this snapshot management method.

[0004] Therefore, the following technical solutions are adopted in the embodiments of this application:

[0005] In a first aspect, this application provides a snapshot management method based on cloud computing technology. This method is applied to a cloud management platform, which manages infrastructure including at least one node. The at least one node has a user's set of cloud instances deployed on it. The method includes: obtaining a first target instance identifier input by the user, the first target instance identifier indicating a first target cloud instance in the set of cloud instances; obtaining a second target instance identifier input by the user, the second target instance identifier indicating a second target cloud instance in the set of cloud instances; obtaining a related attribute input by the user, the related attribute indicating the relationship between the first target cloud instance and the second target cloud instance; and creating a first snapshot based on the first target instance identifier, the second target instance identifier, and the related attribute.

[0006] In this implementation, the method is typically executed by a cloud management platform. It constructs a snapshot of the target task by receiving multiple cloud instances selected by the user and the relationships between them. The snapshot created by this method can quickly create and restore resources within the specified cloud instances and establish relationships between them, ensuring that the resources in the specified cloud instances can execute the target service. This method does not orchestrate the resources of the corresponding cloud instances while executing the target service, allowing the resources of the corresponding cloud instances to execute other services after completing the target service.

[0007] In one implementation, the first target cloud instance and the second target cloud instance are different types of cloud instances.

[0008] In this implementation, the method can associate different types of cloud instances through snapshots, ensuring that different types of cloud instances can jointly perform the same task, thereby improving the application scenarios of cloud instances.

[0009] In one implementation, the first snapshot is stored in the infrastructure, and the method further includes: obtaining a snapshot deployment request input by a user, the snapshot deployment request including a first snapshot identifier; and deploying the first snapshot according to the snapshot deployment request.

[0010] In this implementation, when the snapshot is stored in the infrastructure, the method can deploy the snapshot in the cloud management platform according to the snapshot deployment request input by the user to build the corresponding cloud instance and configure the relationship between the cloud instances, so as to realize that different cloud instances can automatically form a complete and runnable business system to execute the corresponding business.

[0011] In one implementation, the first snapshot includes parameters of a first target cloud instance and parameters of a second target cloud instance. Deploying the first snapshot according to a snapshot deployment request specifically includes: creating a third target cloud instance and a fourth target cloud instance according to the snapshot deployment request. The parameters of the third target cloud instance and the first target cloud instance are the same, and the parameters of the fourth target cloud instance and the second target cloud instance are the same.

[0012] In one implementation, the first snapshot also includes the association between the first target cloud instance and the second target cloud instance. Deploying the first snapshot according to the snapshot deployment request specifically includes: configuring the third target cloud instance and the fourth target cloud instance to be associated according to the association between the first target cloud instance and the second target cloud instance.

[0013] In one implementation, the method further includes: detecting the availability status of a first snapshot; and when the first snapshot is unavailable, creating a second snapshot based on a first target instance identifier, a second target instance identifier, and associated attributes.

[0014] In this implementation, the method needs to check whether the snapshot of the target service is available before executing the target service, so as to ensure that the resources of the cloud instance executing the target service are successfully invoked and established.

[0015] In one implementation, the method further includes: sending feedback information; the feedback information is used to indicate the progress of deploying the first snapshot.

[0016] In this implementation, the method can send feedback information to the user, allowing the user to know the progress of deploying the first snapshot in real time.

[0017] Secondly, this application provides a cloud management platform based on cloud computing technology, comprising: a first processing unit for acquiring a first target instance identifier input by a user, the first target instance identifier indicating a first target cloud instance in a cloud instance set; a second processing unit for acquiring a second target instance identifier input by a user, the second target instance identifier indicating a second target cloud instance in the cloud instance set; a third processing unit for acquiring an association attribute input by a user, the association attribute indicating the association relationship between the first target cloud instance and the second target cloud instance; and a fourth processing unit for creating a first snapshot based on the first target instance identifier, the second target instance identifier, and the association attribute.

[0018] In one implementation, the first target cloud instance and the second target cloud instance are different types of cloud instances.

[0019] In one implementation, the fourth processing unit, while the first snapshot is stored in the infrastructure, is further configured to obtain a snapshot deployment request input by the user, the snapshot deployment request including a first snapshot identifier; and deploy the first snapshot according to the snapshot deployment request.

[0020] In one implementation, when the first snapshot includes parameters of the first target cloud instance and parameters of the second target cloud instance, the fourth processing unit is specifically used to create a third target cloud instance and a fourth target cloud instance according to the snapshot deployment request. The parameters of the third target cloud instance and the first target cloud instance are the same, and the parameters of the fourth target cloud instance and the second target cloud instance are the same.

[0021] In one implementation, when the first snapshot also includes the association between the first target cloud instance and the second target cloud instance, the fourth processing unit is specifically configured to associate the third target cloud instance and the fourth target cloud instance according to the association between the first target cloud instance and the second target cloud instance.

[0022] In one implementation, the fourth processing unit is further configured to detect the availability status of the first snapshot; when the first snapshot is unavailable, to create a second snapshot based on the first target instance identifier, the second target instance identifier, and the associated attributes.

[0023] In one implementation, the fourth processing unit is further configured to send feedback information; the feedback information is used to indicate the progress of deploying the first snapshot.

[0024] Thirdly, embodiments of this application provide a computing device, including: at least one memory; and at least one processor, the processor being configured to execute instructions stored in the memory to cause the computing device to perform the various possible implementations of the first aspect.

[0025] Fourthly, embodiments of this application provide a computer-readable storage medium including computer program instructions, which, when executed by a computing device, perform the various possible implementations of the first aspect.

[0026] Fifthly, this application provides a computer program product containing instructions, characterized in that the computer program product stores instructions that, when executed by a computing device, cause the computing device to implement various possible implementations of the first aspect.

[0027] In a sixth aspect, embodiments of this application provide a computing device cluster, including at least one computing device, each computing device including 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, such that the computing device cluster performs the various possible implementations of the first aspect.

[0028] In a seventh aspect, embodiments of this application provide a computer-readable storage medium including computer program instructions that, when executed by a cluster of computing devices, perform the various possible implementations of the first aspect.

[0029] Eighthly, this application provides a computer program product containing instructions, characterized in that the computer program product stores instructions that, when executed by a cluster of computing devices, cause the cluster of computing devices to implement various possible implementations of the first aspect. Attached Figure Description

[0030] The accompanying drawings used in the description of the embodiments or prior art are briefly introduced below.

[0031] Figure 1 This is a schematic diagram illustrating a user scenario using the cloud management platform as provided in the embodiments of this application;

[0032] Figure 2 This is a flowchart illustrating a snapshot management method based on cloud computing technology provided in an embodiment of this application.

[0033] Figure 3 This is an interface diagram for selecting resources provided in an embodiment of this application;

[0034] Figure 4 This is an interface diagram illustrating the establishment of relationships between resources, as provided in an embodiment of this application.

[0035] Figure 5 This is an interface diagram of a snapshot parameter provided in an embodiment of this application;

[0036] Figure 6 This is an interface diagram of a snapshot record resource provided in an embodiment of this application;

[0037] Figure 7 This is a schematic diagram illustrating the process of business distribution performed by the cloud management platform provided in this embodiment of the application;

[0038] Figure 8 This is a schematic diagram of the structure of a cloud management platform based on cloud computing technology provided in the embodiments of this application;

[0039] Figure 9 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application;

[0040] Figure 10 This is a schematic diagram of the architecture of a computing device cluster provided in an embodiment of this application;

[0041] Figure 11 This is a schematic diagram of another computing device cluster architecture provided in the embodiments of this application. Detailed Implementation

[0042] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0043] In this article, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The symbol " / " in this article indicates that the related objects are in an "or" relationship; for example, A / B means A or B.

[0044] The terms "first" and "second," etc., used in the specification and claims herein are used to distinguish different objects, not to describe a specific order of objects. For example, "first response message" and "second response message," etc., are used to distinguish different response messages, not to describe a specific order of response messages.

[0045] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0046] In the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more, for example, multiple processing units means two or more processing units, multiple elements means two or more elements, etc.

[0047] Before introducing the technical solution protected by this application, several technical terms involved in the technical solution protected by this application will be explained in advance, namely:

[0048] Cloud services refer to the provision of resources, such as computing power, storage space, databases, and networks, on demand using cloud computing technology, allowing users to access and manage them via the internet. Cloud services enable users to avoid the complexities of traditional data centers and can specifically meet their business needs.

[0049] A cloud instance is an independent service unit created within a cloud service. It has its own business resources and configurations and is used to run applications, process data, and perform tasks. Therefore, a cloud service can also be referred to as a "collection of cloud instances".

[0050] When creating a cloud instance in a cloud service, users can access the cloud service management console and select "Create Cloud Instance." During creation, users can select appropriate computing resources (such as processor type, model, and size), storage resources (such as memory type, model, and size), network settings (such as Virtual Private Cloud (VPC), subnet, and Internet Protocol (IP)), and other basic resources based on their task requirements. They can also configure security type, business function type (such as the issue management system provided by advanced cloud services). After configuring the cloud instance, the instance is created, and users can call it to execute related tasks.

[0051] A snapshot is a data protection and backup technology used to create a static copy of a cloud instance, system, virtual machine, file system, or storage volume at a specific point in time. Snapshots help users quickly restore to the state at the time of snapshot creation, making them ideal for data protection, system recovery, and business continuity management. In cloud services, snapshots can record the resource parameters of multiple cloud instances and the relationships between them. The resource parameters of each cloud instance refer to the computing resources, storage resources, network settings, etc., that the cloud instance uses when executing a task. The relationships between each cloud instance refer to how data is transmitted and network connections are established between the resources of one cloud instance and resources in other cloud instances when executing a task. For example, the backend of an Elastic Load Balancer (ELB) may contain the port number of a specific IP address (i.e., the network interface IP address of an Elastic Cloud Server (ECS)).

[0052] Next, the technical solution provided in this application will be introduced.

[0053] Take backup services as an example. When multiple cloud instances are backed up, each instance uses its own dedicated backup technology. Because different cloud instances are independent and isolated, their backup processes lack necessary coordination. This prevents the backup data from automatically forming a complete and functional system during recovery. Related technologies can orchestrate the resources used for backup across multiple cloud instances during the backup process, associating their backup operations. This allows for the automatic formation of a complete and functional system during data recovery. However, orchestrating these resources restricts their ability to perform backups to other functions.

[0054] Based on this, embodiments of this application provide a snapshot management method based on cloud computing technology. This method can generate a snapshot of the target service based on the resources of the cloud instances invoked when different cloud instances execute the target service, as well as the relationships between the cloud instances. After the cloud service receives the target service, it can directly issue a snapshot of the target service, allowing the cloud service to quickly create and restore resources in the specified cloud instance and establish relationships between cloud instances based on the snapshot, ensuring that the resources in the specified cloud instance can execute the target service. This method does not orchestrate the resources of the corresponding cloud instance when executing the target service, allowing the resources of the corresponding cloud instance to execute other services after completing the target service.

[0055] Figure 1This is a schematic diagram illustrating a user scenario using the cloud management platform as provided in the embodiments of this application. Figure 1 As shown, the interaction between the user and the cloud management platform 100 mainly includes: the user logs into the cloud management platform 100 through a web page on the client side; the user selects and purchases cloud services related to the snapshot management method based on cloud computing technology (i.e., the snapshot management service based on cloud computing technology) on the cloud management platform 100; after purchase, the user can generate snapshot management methods based on cloud computing technology on the cloud management platform 100 based on the functions provided by the snapshot management service based on cloud computing technology. The cloud management platform 100 is primarily used to manage the infrastructure for running the snapshot management service based on cloud computing technology. For example, the infrastructure for the snapshot management service based on cloud computing technology may include multiple data centers located in different regions, each data center including multiple servers. Data centers can provide basic resources for the snapshot management service based on cloud computing technology, such as computing resources and storage resources. Therefore, when purchasing and using the snapshot management service based on cloud computing technology, the user mainly pays for the resources used. When using the cloud-based snapshot management service, users can input their needs for the cloud-based snapshot management service through the configuration interface, application program interface (API), or user interaction interface provided by the cloud management platform 100. The cloud management platform 100 can then generate a cloud-based snapshot management service that matches the user's (or other software / hardware, etc.) needs.

[0056] In this embodiment, the cloud management platform 100, based on the functionality of a snapshot management method based on cloud computing technology, can be divided into a snapshot server and a cloud service. The cloud service can create multiple cloud instances, namely cloud instance 1, cloud instance 2, ..., cloud instance N. The cloud instances can be ECS, ELB, SFS Turbo, CBR, etc., depending on their execution functions.

[0057] A snapshot server refers to a service that manages snapshots, which can be a cloud instance created by a cloud management platform. In this embodiment, after receiving a business instruction, the snapshot server can determine the target business corresponding to the instruction. The snapshot server can detect whether there is a snapshot of the target business locally. In one scenario, if the snapshot server detects that there is no snapshot of the target business locally, it can collaborate with the user to create a snapshot of the target business. In another scenario, if the snapshot server detects that there is a snapshot of the target business locally, it can invoke a specified cloud instance in the cloud service to execute the target business based on the snapshot of the target business.

[0058] Snapshots not only record resource parameters and relationships between multiple cloud instances, but also attribute information such as the snapshot's identifier, description, tags, and creation time. The snapshot identifier is a unique identifier used to identify and distinguish different snapshots, facilitating quick search and selection during management and recovery. The snapshot description provides a detailed explanation or annotation, offering more background information to help users understand the snapshot's purpose and related information. Snapshot tags are keywords or categories assigned by users to organize and manage snapshots, allowing them to be filtered and categorized based on specific tags. The snapshot creation time is the timestamp when the snapshot was generated, helping users understand the snapshot's validity and timeliness, and aiding in determining the point in time to recover data.

[0059] Cloud instances in cloud services are independent computing units with specific functions created by users according to their needs, such as ECS, ELB, SFS Turbo, and CBR. ECS is a service that provides on-demand computing capabilities, allowing users to flexibly create, manage, and scale virtual machine cloud instances as needed. ECS is one of the core components of cloud computing, used to run applications and services. ELB is a service that automatically distributes traffic to multiple backend cloud instances, designed to improve application availability and scalability. ELB can automatically distribute user requests across multiple ECS cloud instances, thereby balancing the load. SFS Turbo is a high-performance, scalable file storage service suitable for application scenarios requiring high throughput and low latency. SFS Turbo provides a shared file storage solution that allows data to be shared across multiple cloud instances. CBR is a service that backs up data to the cloud, providing data protection and disaster recovery capabilities. CBR can periodically back up data from local systems or cloud resources to cloud storage for recovery in case of data loss or system failure.

[0060] In this embodiment, the cloud management platform 100 can further be divided into a snapshot control terminal. The snapshot control terminal generally refers to a service that interacts with the user and can be a cloud instance created by the cloud management platform. The snapshot control terminal can display content on the user's client through virtual machines, web pages, etc., to achieve interaction with the user. The user can operate on the screen based on the displayed services, selecting the target service to be executed, the target resource, and the relationships between resources. The snapshot control terminal can generate corresponding instructions based on the operation commands entered by the user on the screen and send the instructions to the snapshot server.

[0061] Optionally, if the functions implemented by the snapshot control terminal can be implemented on the user's client, the cloud management platform 100 may not need to deploy the snapshot control terminal. In this case, the user's client can establish a communication connection with the cloud management platform 100 through wireless fidelity (Wi-Fi), 3G / 4G / 5G / 6G mobile networks, the Internet, or other communication methods, enabling the user's client to implement the aforementioned snapshot control terminal functions.

[0062] Figure 2 This is a flowchart illustrating a snapshot management method based on cloud computing technology provided in an embodiment of this application. Figure 2 As shown, this method can be executed by the aforementioned cloud management platform 100, and the specific implementation process is as follows:

[0063] Step S201: Obtain the first target instance identifier input by the user. The first target instance identifier indicates the first target cloud instance in the cloud instance set.

[0064] Step S201: Obtain the second target instance identifier input by the user. The second target instance identifier indicates the second target cloud instance in the cloud instance set.

[0065] Specifically, the cloud management platform 100 can store configuration parameters such as the operating system, cloud instance type, storage type, memory size, and network settings of each cloud instance created in the cloud service. The cloud instances in the cloud service may include the aforementioned first target instance and second target instance.

[0066] When creating a snapshot, the cloud management platform 100 can send the configuration parameters of each cloud instance stored locally to the user's client. After receiving the configuration parameters, the user's client can provide them, allowing the user to select the target cloud instance for their desired service. The user's client also inputs the selection command into the cloud management platform 100. Based on the selection command, the cloud management platform 100 determines the identifier of the selected target instance.

[0067] For example, when creating a snapshot, the user's client can provide an interface for logging into their cloud account. After the user logs into their cloud account, the cloud management platform 100 can obtain the set of cloud service resources authorized by that cloud account based on the user's currently logged-in cloud account. The set of cloud service resources includes configuration parameters for multiple cloud instances.

[0068] The cloud management platform 100 can send the configuration parameters of multiple cloud instances from the cloud service resource set to the user's client. The user can select the target cloud instance and target resource of the target cloud instance to perform the target task on the client. After receiving the input selection command, the user's client determines the selected target cloud instance and target resource, and sends the target cloud instance identifier and target resource identifier to the cloud management platform 100. After receiving the target cloud instance identifier and target resource identifier, the cloud management platform 100 can record them. Simultaneously, the cloud management platform 100 can send data regarding the data transmission, network connections, and other relationships that need to be established between the target resources to the user's client.

[0069] In one embodiment, when a user performs large-scale website service distribution, they can log in to their cloud account on their client. After the cloud management platform 100 confirms that the user has successfully logged into their cloud account, it can send the cloud instance identifier authorized by that cloud account to the user's client, so that the user can create a snapshot of the service distribution.

[0070] The user's client can provide sections for "Select Resources," "Cloud Service Resources," and "Select Status." The "Select Resources" section includes four options: "ECS," "ELB," "SFS Turbo," and "CBR." Figure 3 As shown, after the user selects "ECS" in the "Select Resources" section, the "Resources of Cloud Services" section can provide various available resources in ECS, and the "Select Status" section can provide various statuses of various available resources in ECS.

[0071] Step S203: Obtain the association attributes input by the user. These association attributes indicate the relationship between the first target cloud instance and the second target cloud instance.

[0072] Specifically, users can select the relationships that need to be established for each resource in order to perform the target task on the client. After receiving the user's selection instructions, the client determines the relationships that need to be established for each target resource and sends the relationship attributes to the cloud management platform 100. After receiving the relationship attributes, the cloud management platform 100 can record the relationships between the target resources indicated by the relationship attributes.

[0073] In one embodiment, such as Figure 4As shown, the user's client can provide two "Select Resource" sections and multiple "Select Association" sections. The two "Select Resource" sections correspond to the two objects establishing an association. For example, when a user needs to mount an ECS instance to the backend of an ELB, they can select "ECS" in one "Select Resource" section and "ELB" in the other. The "Select Association" sections can automatically or manually select the association between "ECS" and "ELB". Users can manually configure the association parameters between target resources, that is, select the service port to be mounted to the ELB and specify which network interface card (NIC) of the ECS instance.

[0074] Step S204: Create a first snapshot based on the first target instance identifier, the second target instance identifier, and associated attributes.

[0075] Specifically, when creating a snapshot, the cloud management platform 100 can add the recorded target cloud instance identifier, target resource identifier, and the association relationships between target resources to the snapshot to form a snapshot for executing the corresponding business. The cloud management platform 100 can store the created snapshot in a snapshot database so that when executing the corresponding business later, it can directly retrieve the snapshot from the snapshot database and quickly form a complete and runnable business system based on the snapshot to execute the corresponding business.

[0076] After receiving a snapshot deployment request from a user, the cloud management platform 100 can retrieve the corresponding snapshot from the snapshot database based on the snapshot identifier carried in the deployment request. Once the snapshot is obtained, the cloud management platform 100 can create various cloud instances based on the cloud instance identifiers recorded in the snapshot. Based on the parameters of the cloud instances recorded in the snapshot, the cloud management platform 100 can configure the computing resources, storage resources, network settings, etc., to be invoked when executing a specific task for each created cloud instance, enabling each cloud instance to perform corresponding operations. Based on the resource relationships recorded in the snapshot, the cloud management platform 100 can configure how each resource in each cloud instance transmits data and connects with resources in other cloud instances when executing a specific task, forming a complete and runnable business system among the cloud instances to execute the corresponding business. The cloud management platform 100 does not orchestrate the resources of the corresponding cloud instances during snapshot deployment, ensuring that the resources of the corresponding cloud instances can execute other business operations after completing the target business.

[0077] During the snapshot deployment process, the cloud management platform 100 can send feedback information to the user's client, allowing the user to know the progress of the first snapshot deployment in real time. For example, after the cloud management platform 100 creates each cloud instance, it can send feedback information to the user's client, letting the user know that the cloud instances have been successfully created during the snapshot deployment process. As another example, after the cloud management platform 100 configures the corresponding resources for each cloud instance, it can send feedback information to the user's client, letting the user know that the corresponding resources have been successfully configured for each cloud instance during the snapshot deployment process. Furthermore, after the cloud management platform 100 configures the relationships between resources, it can send feedback information to the user's client, letting the user know that the corresponding relationships have been successfully configured for each resource during the snapshot deployment process.

[0078] After creating a snapshot, the cloud management platform 100 can check its availability status. If the snapshot is unavailable, the cloud management platform 100 can recreate a snapshot based on the cloud instance identifiers and associated attributes selected by the user, ensuring that the snapshot created for the user is valid.

[0079] In this embodiment, the method constructs a snapshot for executing the target task by receiving multiple cloud instances selected by the user and the relationships between these cloud instances. The snapshot created by this method can quickly complete the creation and restoration of resources in the specified cloud instances and establish the relationships between the cloud instances, ensuring that the resources in the specified cloud instances can execute the target service. When executing the target service, this method does not orchestrate the resources of the corresponding cloud instances, allowing the resources of the corresponding cloud instances to execute other services after completing the target service.

[0080] In this embodiment of the application, the cloud management platform 100 can manage various snapshots stored locally, such as taking snapshots, viewing snapshots, editing snapshots, deleting snapshots, etc.

[0081] When the cloud management platform 100 lists snapshots, it can send the snapshot parameters of each snapshot to the user's client. Snapshot parameters can include the service name corresponding to the snapshot, the information recorded in the snapshot, the snapshot's usage status, and other parameters. Upon receiving these snapshot parameters, the user's client can provide the corresponding snapshot parameters, allowing the user to promptly obtain the snapshot status and effectively execute the services associated with each snapshot.

[0082] For example, such as Figure 5As shown, the snapshot parameters that a user's client can provide include the "Name / ID" field, the "Number of Resources" field, the "Resources" field, and the "Creation Time" field. The "Name / ID" field represents the business name corresponding to the snapshot, the "Number of Resources" field represents the number of cloud instances invoked by the snapshot, the "Resources" field represents the number of resources in each cloud instance invoked, and the "Creation Time" field represents the time the snapshot was created.

[0083] When viewing a specific snapshot, the cloud management platform 100 can send the snapshot parameters of that snapshot to the user's client, allowing the client to provide these parameters so the user can view them. In one embodiment, the user can view the snapshot parameters of a specific snapshot through the management console, command-line interface (CLI) commands, API calls, backup and recovery tools, etc.

[0084] When the cloud management platform 100 modifies a specified snapshot, it can send the snapshot parameters of that snapshot to the user's client, allowing the client to provide these parameters. The user can then modify the snapshot parameters as needed. Upon receiving the modified snapshot parameters, the cloud management platform 100 can update and store them. Modifying the snapshot parameters of a specified snapshot enables the modified snapshot to call specified resources for similar services corresponding to that snapshot, and to create associations between specified resources.

[0085] When deleting a specified snapshot, the cloud management platform 100 can remove the snapshot parameters of that snapshot stored locally. Deleting a specified snapshot optimizes storage space usage while ensuring that the system's backup strategy and data management meet requirements.

[0086] For example, such as Figure 5 As shown, the snapshot parameters that the user's client can provide also include an "Operation" section. The "Operation" section can include three virtual buttons: "Deploy," "Edit," and "Delete." When the user clicks the "Deploy" button, the user sends a deployment command to the cloud management platform 100, instructing the cloud management platform 100 to distribute the specified snapshot to various cloud instances, thereby enabling the various cloud instances to execute the business corresponding to the specified snapshot.

[0087] When a user clicks the "Edit" button, their client can provide the snapshot parameters for the specified snapshot. After modifying the snapshot parameters, the user sends the modified parameters to the cloud management platform 100. Upon receiving the modified snapshot parameters, the cloud management platform 100 updates the snapshot parameters to store the modified settings. When the user clicks the "Delete" button, they send a delete command to the cloud management platform 100, instructing it to delete the specified snapshot.

[0088] In one embodiment, such as Figure 6 As shown, when a user clicks the "Deploy" button, a resource group deployment page pops up on the user's client, providing information on resource configuration. The resource group deployment page displays three sections: "Resource Type," "Resource Information," and "Description." The "Resource Type" section indicates the resource type, such as Elastic Cloud Server, Elastic Load Balancer, and Elastic File System. The "Resource Information" section displays specific resource information for the three cloud instance types. The "Description" section provides additional supplementary information for each cloud instance type, such as the note for Elastic File System stating "Restored from a backup copy in the repository."

[0089] In this embodiment, the cloud management platform 100 can construct a snapshot for executing the target task by receiving multiple cloud instances selected by the user and the relationships between these instances. The snapshot created by this method can quickly complete the creation and restoration of resources in a specified cloud instance and establish the relationships between cloud instances, ensuring that the resources in the specified cloud instance can execute the target service. This method does not orchestrate the resources of the corresponding cloud instance when executing the target service, allowing the resources of the corresponding cloud instance to execute other services after completing the target service.

[0090] Next, we will take the business distribution business as an example to introduce the technical solution protected by this application.

[0091] For example, Figure 7 This is a schematic diagram illustrating the process of business distribution performed by the cloud management platform provided in this embodiment. Figure 7 As shown, the cloud services of the cloud management platform 100 can include three cloud instances: a first cloud instance, a second cloud instance, and a third cloud instance. The first cloud instance can create ECS instances, the second cloud instance can create ELB instances, and the third cloud instance can create SFS Turbo instances and CBR instances. Optionally, ECS instances, ELB instances, SFS Turbo instances, and CBR instances can reside on one cloud instance, two cloud instances, or other numbers of cloud instances.

[0092] The specific process of business distribution executed by the cloud management platform 100 is as follows:

[0093] In step S701, the cloud management platform 100 receives the business instruction.

[0094] In step S702, the cloud management platform 100 determines the snapshot of the business distribution based on the business instructions and checks whether the snapshot of the business distribution is available.

[0095] In step S703, the cloud management platform 100 sends a feedback instruction.

[0096] Specifically, after receiving a business instruction, the cloud management platform 100 can determine the business distribution based on the instruction. The cloud management platform 100 can then check if a snapshot of the business distribution is stored locally. If the cloud management platform 100 detects that no snapshot of the business distribution is stored locally, it can create a snapshot of the business distribution with the user's client. For details, please refer to [link / reference needed]. Figures 2-6 The content described.

[0097] If the cloud management platform 100 detects a snapshot of the service distribution on-premises, it can check whether that snapshot is available. In one scenario, if the cloud management platform 100 detects that the service distribution snapshot is unavailable, it can establish a new snapshot of the service distribution with the user's client. For details, please refer to [link / reference needed]. Figures 2-6 The content described.

[0098] In another scenario, if the cloud management platform 100 detects that a snapshot of the service distribution is available, it can send a feedback instruction to the user's client. This feedback instruction instructs the cloud management platform 100 to perform service distribution based on the snapshot.

[0099] Step S704: The cloud management platform 100 establishes an information synchronization connection with the user's client.

[0100] Specifically, after receiving feedback instructions, the user's client can establish an information synchronization connection with the cloud management platform 100. When the cloud management platform 100 controls each cloud instance to perform business distribution, it can receive real-time progress information from each cloud instance, such as the progress of configuration resources, the progress of establishing associations, and the progress of business distribution. Then, it transmits the progress information to the user's client through the information synchronization channel, allowing the user to know the progress of business distribution in real time.

[0101] In step S705, if the cloud management platform 100 determines that the snapshot of the target service is available, it sends the corresponding ECS ​​resources recorded in the snapshot of the target service to the first cloud instance.

[0102] In step S706, if the cloud management platform 100 determines that the snapshot of the target service is available, it sends the corresponding ELB resources recorded in the snapshot of the target service to the second cloud instance.

[0103] In step S707, if the cloud management platform 100 determines that the snapshot of the target service is available, it sends the corresponding SFS Turbo resources recorded in the snapshot of the target service to the third cloud instance.

[0104] Optionally, the order of the three steps in steps S705-S707 can be changed randomly.

[0105] Specifically, when the cloud management platform 100 determines that service distribution is available, it can send the snapshot record information of the service distribution to the corresponding cloud instances. For example, the cloud management platform 100 can send the corresponding resources of the ECS in the snapshot record of the service distribution to the first cloud instance, allowing the first cloud instance to create the ECS. The cloud management platform 100 can send the corresponding resources of the ELB in the snapshot record of the service distribution to the second cloud instance, allowing the second cloud instance to create the ELB. And, the cloud management platform 100 can send the corresponding resources of the SFS Turbo in the snapshot record of the service distribution to the cloud instance where the third cloud instance resides, allowing the third cloud instance to create the SFS Turbo.

[0106] When the first cloud instance creates an ECS instance, it can call relevant local resources based on the corresponding resources recorded in the snapshot of the service distribution, enabling the called resources to execute ECS functions. Optionally, after the first cloud instance creates the ECS instance, it can send feedback information to the cloud management platform 100, instructing the first cloud instance to create the ECS instance. After receiving the feedback information, the cloud management platform 100 can send a progress notification to the user's client through the information synchronization channel, and allow the user's client to notify the cloud management platform 100 that the ECS instance has been created.

[0107] When the second cloud instance creates an ELB, it can call relevant local resources based on the ELB resources recorded in the snapshot of the business distribution, enabling the called resources to execute ELB functions. Optionally, after the second cloud instance creates the ELB, it can send feedback information to the cloud management platform 100, instructing the second cloud instance to create the ELB. After receiving the feedback information, the cloud management platform 100 can send a progress notification to the user's client through the information synchronization channel, and instruct the user's client to notify the cloud management platform 100 to create the ELB.

[0108] When a third cloud instance creates an SFS Turbo instance, it can call relevant local resources based on the SFS Turbo resources recorded in the snapshot of the business distribution, enabling the called resources to execute the SFS Turbo function. Optionally, after creating the SFS Turbo instance, the third cloud instance can send feedback information to the cloud management platform 100, instructing the third cloud instance to create the SFS Turbo instance. After receiving the feedback information, the cloud management platform 100 can send a progress notification to the user's client through the information synchronization channel, and instruct the user's client to notify the cloud management platform 100 to create the SFS Turbo instance.

[0109] Step S708: SFS Turbo creates the file system.

[0110] In step S709, SFS Turbo sends a recovery command to CBR.

[0111] In step S710, CBR sends feedback information to SFS Turbo.

[0112] Specifically, SFS Turbo needs to back up the data in the original file system before performing business distribution.

[0113] SFS Turbo can create a file system and then send a recovery command to the CBR. The CBR can locate the original file system using the identifier of the original file system carried in the recovery command, and then copy the data from the original file system to the created file system. After completing the backup operation, the CBR sends a recovery command to SFS Turbo. Upon receiving the recovery command, SFS Turbo deletes the data in the original file system, freeing up storage space. Optionally, after completing the data backup, SFS Turbo can send feedback information to the cloud management platform 100, instructing the third-party cloud instance to complete the data backup. After receiving the feedback information, the cloud management platform 100 can send a progress notification to the user's client through the information synchronization channel, and allow the user's client to notify the cloud management platform 100 to complete the data backup.

[0114] In step S711, after the cloud management platform 100 determines that the ECS and ELB have completed the corresponding resource configuration, it sends the association relationship of the corresponding ELB resources recorded in the snapshot of the target service to the ELB.

[0115] In step S712, after the cloud management platform 100 determines that ECS and SFS Turbo have completed the corresponding resource configuration, it sends the association relationship of the corresponding ECS ​​resources recorded in the snapshot of the target service to ECS.

[0116] Optionally, the order of the two steps in steps S711-S712 can be changed randomly.

[0117] Optionally, the order of the two processes, S708-S710 and S711-S712, can be changed randomly.

[0118] Specifically, after the cloud management platform 100 determines that each cloud instance has completed the call to the corresponding resources, it can send the association relationship of the snapshot record of the service distribution to the corresponding cloud instance. For example, the cloud management platform 100 can send the association relationship between the ECS and ELB of the snapshot record of the service distribution to the ECS and / or ELB to establish the corresponding association relationship.

[0119] If the association is "ELB designates ECS as a backend server", the cloud management platform 100 can send the "ELB designates ECS as a backend server" association record from the service distribution snapshot to the ELB. Based on the "ELB designates ECS as a backend server" association, the ELB can establish a communication connection between the ELB interface and the ECS interface, allowing the ECS to act as the ELB's backend server.

[0120] Optionally, after establishing the association, the ELB can send feedback information to the cloud management platform 100, instructing the ELB to establish a specified association with the ECS. After receiving the feedback information, the cloud management platform 100 can send a progress notification to the user's client through the information synchronization channel, and allow the user's client to provide the cloud management platform 100 with the creation of the association of "ELB designating ECS ​​as the backend server".

[0121] If the association is "ECS mount SFS Turbo", the cloud management platform 100 can send the "ECS mount SFS Turbo" association record from the service distribution snapshot to the ECS. The ECS can then mount SFS Turbo based on this association.

[0122] Optionally, after the ECS establishes the association, it can send feedback information to the cloud management platform 100, instructing the ECS to establish a specified association with SFSturbo. After receiving the feedback information, the cloud management platform 100 can send a progress notification to the user's client through the information synchronization channel, and allow the user's client to provide the cloud management platform 100 with the creation of the "ECS mounted to SFSturbo" association.

[0123] For example, Figure 8 This is a schematic diagram of the structure of a cloud management platform based on cloud computing technology provided in an embodiment of this application. Figure 8As shown, the cloud management platform 800 based on cloud computing technology can be divided into a first processing unit 810, a second processing unit 820, a third processing unit 830, and a fourth processing unit 840 according to its execution functions. The cloud management platform 800 can be an application, software code, etc., deployed on a computing device or a cluster of computing devices. The computing device can be a server, computer, laptop, tablet, smartphone, etc. The cloud management platform 800 can be deployed on a cloud server. If the cloud management platform 800 is deployed on a cloud service, designers can use local devices to call the cloud server to use the cloud management platform 800 to complete corresponding tasks. The specific implementation process of the cloud management platform 800 is as follows:

[0124] The first processing unit 810 is used to obtain a first target instance identifier input by the user, which indicates a first target cloud instance in the cloud instance set; the second processing unit 820 is used to obtain a second target instance identifier input by the user, which indicates a second target cloud instance in the cloud instance set; the third processing unit 830 is used to obtain an association attribute input by the user, which indicates the association relationship between the first target cloud instance and the second target cloud instance; the fourth processing unit 840 is used to create a first snapshot based on the first target instance identifier, the second target instance identifier, and the association attribute.

[0125] In one implementation, the first target cloud instance and the second target cloud instance are different types of cloud instances.

[0126] In one implementation, when the first snapshot is stored in the infrastructure, the fourth processing unit 840 is further configured to obtain a snapshot deployment request input by the user, the snapshot deployment request including a first snapshot identifier; and deploy the first snapshot according to the snapshot deployment request.

[0127] In one implementation, when the first snapshot includes parameters of the first target cloud instance and parameters of the second target cloud instance, the fourth processing unit 840 is specifically configured to create a third target cloud instance and a fourth target cloud instance according to the snapshot deployment request. The parameters of the third target cloud instance and the first target cloud instance are the same, and the parameters of the fourth target cloud instance and the second target cloud instance are the same.

[0128] In one implementation, when the first snapshot also includes the association between the first target cloud instance and the second target cloud instance, the fourth processing unit 840 is specifically configured to associate the third target cloud instance and the fourth target cloud instance according to the association between the first target cloud instance and the second target cloud instance.

[0129] In one embodiment, the fourth processing unit 840 is further configured to detect the availability status of the first snapshot; when the first snapshot is unavailable, to create a second snapshot based on the first target instance identifier, the second target instance identifier, and the associated attributes.

[0130] In one embodiment, the fourth processing unit 840 is further configured to send feedback information; the feedback information is used to indicate the progress of deploying the first snapshot.

[0131] The first processing unit 810, the second processing unit 820, the third processing unit 830, and the fourth processing unit 840 can all be implemented in software or in hardware. For example, the implementation of the first processing unit 810 will be described below. Similarly, the implementation of the second processing unit 820, the third processing unit 830, and the fourth processing unit 840 can refer to the implementation of the first processing unit 810.

[0132] As an example of a software functional unit, the first processing unit 810 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the aforementioned computing instance may be one or more. For example, the first processing unit 810 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 may be distributed in the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0133] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

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

[0135] The multiple computing devices included in the first processing unit 810 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the first processing unit 810 can be distributed in the same Availability Zone (AZ) or in different AZs. Likewise, the multiple computing devices included in the first processing unit 810 can be distributed in the same Virtual Private Cloud (VPC) or in multiple VPCs. These multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0136] It should be noted that, in other embodiments, the first processing unit 810 can be used to execute any step in the snapshot management method based on cloud computing technology, the second processing unit 820 can be used to execute any step in the snapshot management method based on cloud computing technology, the third processing unit 830 can be used to execute any step in the snapshot management method based on cloud computing technology, and the fourth processing unit 840 can be used to execute any step in the snapshot management method based on cloud computing technology. The steps implemented by the first processing unit 810, the second processing unit 820, the third processing unit 830, and the fourth processing unit 840 can be specified as needed. By implementing different steps in the snapshot management method based on cloud computing technology through the first processing unit 810, the second processing unit 820, the third processing unit 830, and the fourth processing unit 840 respectively, all functions of the cloud management platform based on cloud computing technology can be realized.

[0137] Figure 9 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Figure 9As shown, the computing device 900 includes a bus 910, a processor 920, a memory 930, and a communication interface 940. The processor 920, memory 930, and communication interface 940 communicate with each other via the bus 910. The computing device 900 can be a server, computer, laptop, server rack, etc. It should be understood that this application does not limit the number of processors and memory in the computing device 900.

[0138] The bus 910 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 9 The bus 910 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 910 may include a path for transmitting information between various components of the computing device 900 (e.g., processor 920, memory 930, communication interface 940).

[0139] The processor 920 can be any one or more of the following processors: central processing unit (CPU), graphics processing unit (GPU), microprocessor (MP), or digital signal processor (DSP).

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

[0141] The memory 930 stores executable program code, which the processor 920 executes to implement the functions of the aforementioned modules, such as the first processing unit 810, the second processing unit 820, the third processing unit 830, and the fourth processing unit 840, thereby realizing the snapshot management method based on cloud computing technology. That is, the memory 930 stores instructions for executing the snapshot management method based on cloud computing technology.

[0142] Alternatively, the memory 930 stores executable code, which the processor 920 executes to implement the functions of the aforementioned modules, thereby realizing the snapshot management method based on cloud computing technology. That is, the memory 930 stores instructions for executing the snapshot management method based on cloud computing technology.

[0143] The communication interface 940 uses transceiver modules, such as, but not limited to, network interface cards and transceivers, to enable communication between the computing device 900 and other devices or communication networks.

[0144] This 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 smartphone.

[0145] like Figure 10 As shown, the computing device cluster includes at least one computing device 900. The memory 930 in one or more computing devices 900 in the computing device cluster may store the same instructions for executing a snapshot management method based on cloud computing technology.

[0146] In some possible implementations, the memory 930 of one or more computing devices 900 in the computing device cluster may also store partial instructions for executing the snapshot management method based on cloud computing technology. In other words, a combination of one or more computing devices 900 can jointly execute instructions for executing the snapshot management method based on cloud computing technology.

[0147] It should be noted that the memories 930 in different computing devices 900 within the computing device cluster can store different instructions, which are used to execute parts of the functions of the first processing unit 810, the second processing unit 820, the third processing unit 830, and the fourth processing unit 840. That is, the instructions stored in the memories 930 of different computing devices 900 can implement the functions of one or more modules of the first processing unit 810, the second processing unit 820, the third processing unit 830, and the fourth processing unit 840.

[0148] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 11 One possible implementation is shown. For example... Figure 11As shown, two computing devices, computing device 900A and computing device 900B, are connected via a network. Specifically, they are connected to the network through communication interfaces in each computing device. In this possible implementation, the memory 930 in computing device 900A stores instructions for performing the functions of some modules in the first processing unit 810 and the second processing unit 820. Meanwhile, the memory 930 in computing device 900B stores instructions for performing the functions of another portion of the modules in the third processing unit 830 and the fourth processing unit 840.

[0149] Figure 11 The connection method between the computing device clusters shown can be such that, considering the need for a large amount of data storage in the snapshot management method based on cloud computing technology provided in this application, the functions implemented by another part of the modules in the first processing unit 810, the second processing unit 820, the third processing unit 830 and the fourth processing unit 840 are delegated to the computing device 900B for execution.

[0150] It should be understood that Figure 11 The functions of the computing device 900A shown can also be performed by multiple computing devices 900. Similarly, the functions of the computing device 900B can also be performed by multiple computing devices 900.

[0151] This application also provides another computing device cluster. The connection relationships between the computing devices in this computing device cluster can be similarly referred to... Figure 9 and Figure 10 The connection method of the computing device cluster is different in that the memory 930 of one or more computing devices 900 in the computing device cluster can store the same instructions for executing the snapshot management method based on cloud computing technology.

[0152] In some possible implementations, the memory 930 of one or more computing devices 900 in the computing device cluster may also store partial instructions for executing the snapshot management method based on cloud computing technology. In other words, a combination of one or more computing devices 900 can jointly execute instructions for executing the snapshot management method based on cloud computing technology.

[0153] It should be noted that the memory 930 in different computing devices 900 within the computing device cluster can store different instructions for executing some functions of the computing device 900. That is, the instructions stored in the memory 930 of different computing devices 900 can implement the functions of one or more modules of the first processing unit 810, the second processing unit 820, the third processing unit 830, and the fourth processing unit 840 mentioned above.

[0154] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions, capable of running on a computing device or stored on any usable medium. When the computer program product runs on at least one computing device, it causes the at least one computing device to execute a snapshot management method based on cloud computing technology.

[0155] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute a snapshot management method based on cloud computing technology.

[0156] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions 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 invention.

Claims

1. A snapshot management method based on cloud computing technology, characterized in that, The method is applied to a cloud management platform for managing infrastructure, the infrastructure including at least one node, on which a user's cloud instance set is deployed, including: Obtain the first target instance identifier input by the user, wherein the first target instance identifier is used to indicate the first target cloud instance in the cloud instance set; Obtain the second target instance identifier input by the user, the second target instance identifier being used to indicate the second target cloud instance in the cloud instance set; Obtain the association attribute input by the user, the association attribute being used to indicate the association relationship between the first target cloud instance and the second target cloud instance; A first snapshot is created based on the first target instance identifier, the second target instance identifier, and the associated attributes.

2. The method according to claim 1, characterized in that, The first target cloud instance and the second target cloud instance are different types of cloud instances.

3. The method according to claim 1 or 2, characterized in that, The first snapshot is stored in the infrastructure, and the method further includes: Obtain the snapshot deployment request input by the user, the snapshot deployment request including the first snapshot identifier; Deploy the first snapshot according to the snapshot deployment request.

4. The method according to claim 3, characterized in that, The first snapshot includes parameters of the first target cloud instance and parameters of the second target cloud instance. Deploying the first snapshot according to the snapshot deployment request specifically includes: Based on the snapshot deployment request, a third target cloud instance and a fourth target cloud instance are created. The parameters of the third target cloud instance are the same as those of the first target cloud instance, and the parameters of the fourth target cloud instance are the same as those of the second target cloud instance.

5. The method according to claim 3 or 4, characterized in that, The first snapshot also includes the association between the first target cloud instance and the second target cloud instance. Deploying the first snapshot according to the snapshot deployment request specifically includes: Based on the association between the first target cloud instance and the second target cloud instance, the third target cloud instance and the fourth target cloud instance are configured to be associated.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Detect the availability status of the first snapshot; When the first snapshot is unavailable, a second snapshot is created based on the first target instance identifier, the second target instance identifier, and the associated attributes.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Send feedback information; the feedback information is used to indicate the progress of deploying the first snapshot.

8. A cloud management platform based on cloud computing technology, characterized in that, include: The first processing unit is configured to obtain the first target instance identifier input by the user, wherein the first target instance identifier is used to indicate the first target cloud instance in the cloud instance set; The second processing unit is configured to obtain the second target instance identifier input by the user, wherein the second target instance identifier is used to indicate the second target cloud instance in the cloud instance set; The third processing unit is used to obtain the association attribute input by the user, the association attribute being used to indicate the association relationship between the first target cloud instance and the second target cloud instance; The fourth processing unit is used to create a first snapshot based on the first target instance identifier, the second target instance identifier, and the associated attributes.

9. The cloud management platform according to claim 8, characterized in that, The first target cloud instance and the second target cloud instance are different types of cloud instances.

10. The cloud management platform according to claim 8 or 9, characterized in that, The fourth processing unit, while the first snapshot is stored in the infrastructure, is also used for... Obtain the snapshot deployment request input by the user, the snapshot deployment request including the first snapshot identifier; Deploy the first snapshot according to the snapshot deployment request.

11. The cloud management platform according to claim 10, characterized in that, The fourth processing unit, when the first snapshot includes parameters of the first target cloud instance and parameters of the second target cloud instance, is specifically used for... Based on the snapshot deployment request, a third target cloud instance and a fourth target cloud instance are created. The parameters of the third target cloud instance are the same as those of the first target cloud instance, and the parameters of the fourth target cloud instance are the same as those of the second target cloud instance.

12. The cloud management platform according to claim 10 or 11, characterized in that, The fourth processing unit, when the first snapshot also includes the association between the first target cloud instance and the second target cloud instance, is specifically used for... Based on the association between the first target cloud instance and the second target cloud instance, the third target cloud instance and the fourth target cloud instance are configured to be associated.

13. The cloud management platform according to any one of claims 8 to 12, characterized in that, The fourth processing unit is also used for Detect the availability status of the first snapshot; When the first snapshot is unavailable, a second snapshot is created based on the first target instance identifier, the second target instance identifier, and the associated attributes.

14. The cloud management platform according to any one of claims 8-13, characterized in that, The fourth processing unit is also used for Send feedback information; the feedback information is used to indicate the progress of deploying the first snapshot.

15. A computing device cluster, characterized in that, It includes at least one computing device, each computing device including a processor and 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 to cause the cluster of computing devices to perform the method as described in any one of claims 1-7.

16. A computer-readable storage medium, characterized in that, It includes computer program instructions, which, when executed by a computing device, cause the computing device to perform the method as described in any one of claims 1-7.

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

Images