Method, apparatus, computing device cluster and terminal for cloud resource processing

Abstract

The application discloses a cloud resource processing method and device, a computing device cluster and a terminal, and belongs to the technical field of cloud computing. The method comprises the following steps: receiving a first processing request for at least one cloud resource sent by a terminal, wherein the first processing request carries first cloud resource indication information, the identity of a first cloud vendor to which at least one cloud resource belongs, and first processing type indication information, the first cloud resource indication information is used for indicating that the cloud resource to be processed is at least one cloud resource, the terminal logs in a cloud resource management account, and the first cloud vendor is a cloud vendor corresponding to any cloud vendor account in at least one cloud vendor account associated with the cloud resource management account. The cloud resource management device of the first cloud vendor performs the processing indicated by the first processing type indication information on the at least one cloud resource. The application can improve the efficiency of cloud resource processing.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a method, apparatus, computing device cluster and terminal for cloud resource processing. Background Technology

[0002] With the development of cloud computing technology, the types of cloud resources (also known as cloud computing resources) are also increasing, such as Elastic Compute Service (ECS), Elastic Volume Service (EVS), cloud virtual machines, virtual private clouds, etc. At the same time, the number of cloud vendors that can provide cloud resources is also increasing, and users can choose which cloud vendor and which cloud resources to use.

[0003] Currently, each cloud vendor has its own cloud resource management platform. Users who want to manage cloud resources purchased or rented from a particular vendor need to log into that vendor's platform and then process the resources there. If a user has purchased or rented cloud resources from multiple vendors, they will need to frequently switch between these different cloud vendors' resource management platforms when processing resources from multiple vendors, resulting in low cloud resource processing efficiency. Summary of the Invention

[0004] This application provides a method, apparatus, computing device cluster, and terminal for cloud resource processing, which can improve cloud resource processing efficiency. The corresponding technical solution is as follows:

[0005] Firstly, a method for processing cloud resources is provided. This method is applied to a server. In this method, a user can select a cloud provider, at least one cloud resource under that provider to be processed, and the processing type for the selected cloud resource via a terminal. The user then sends a processing request for the selected cloud resource to the server via the terminal. This processing request carries first cloud resource indication information, the identifier of the first cloud provider to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information indicates the cloud resource selected by the user, the first cloud provider is the cloud provider selected by the user, and the first processing type indication information indicates the processing type to be performed on the selected cloud resource. The server processes the cloud resource of the corresponding cloud provider through the cloud resource management device of the corresponding cloud provider according to the processing request. This method eliminates the need for the user to manually log in to the cloud resource management system of each cloud provider to process the cloud resource, effectively saving user time and improving the efficiency of cloud resource processing. Furthermore, this method allows the user to select multiple cloud resources for processing at once, which is more efficient than limiting the user to selecting only one cloud resource at a time.

[0006] In the solution provided in this application, the user logs in to a cloud resource management account on a terminal. This cloud resource management account is associated with at least one cloud vendor account. The cloud resource management account is registered by the user with the aforementioned server through the terminal, while the cloud vendor account is registered by the user with the corresponding cloud vendor's cloud resource management device through the terminal. The user can log in to the corresponding cloud vendor's cloud resource management system through the cloud vendor account to purchase, rent, etc., cloud resources. After the cloud resource management account is associated with at least one cloud vendor account, the server can process the cloud resources selected by the user through the corresponding cloud vendor's cloud resource management device.

[0007] In one possible implementation, if the processing type indicated by the first processing type indication information is resource cleanup, the server can automatically clean up the cloud resources selected by the user. The dependency relationship refers to the necessary order of cleanup. For example, there is a dependency relationship between ECS and EVS. When cleanup, ECS needs to be cleaned up first, and then EVS needs to be cleaned up. Therefore, when cleaning up at least one of the above cloud resources, the cleanup can be carried out in sequence according to the dependency relationship.

[0008] In one possible implementation, when the processing type indicated by the first processing type indication information is resource migration, the user can also select the destination cloud vendor for migration via the terminal. Correspondingly, the first processing request also carries the identifier of the destination cloud vendor for resource migration, where the first cloud vendor is the source cloud vendor for resource migration. In this case, the server performs migration-out processing on at least one cloud resource selected by the user through the cloud resource management equipment of the first cloud vendor, and performs migration-in processing on the aforementioned at least one cloud resource through the cloud resource management equipment of the destination cloud vendor.

[0009] In one possible implementation, if the user selects a virtual machine as the cloud resource, the user can also select a migration mode. Accordingly, the first processing request also carries migration mode indication information. If the migration mode indicated by the migration mode indication information is database migration, when the server performs cloud resource migration, it can first request a first virtual machine as the primary node and a second virtual machine as the backup node from the cloud resource management device of the destination cloud vendor. Then, through the cloud resource management device of the first cloud vendor, data corresponding to at least one cloud resource is migrated out to the cloud sub-source management device of the destination cloud vendor. Finally, through the cloud resource management device of the destination cloud vendor, data corresponding to at least one cloud resource is simultaneously migrated into both the primary and backup nodes.

[0010] In one possible implementation, if the user selects a virtual machine as the cloud resource, the user can also select a migration mode. Accordingly, the first processing request also carries migration mode indication information. If the migration mode indicated by the migration mode indication information is business migration, when the server performs cloud resource migration, it can first use the cloud resource management device of the first cloud vendor to package at least one cloud resource into a target image and migrate it to the cloud sub-source management device of the destination cloud vendor. Then, it requests a third virtual machine from the cloud resource management device of the destination cloud vendor and uses the cloud resource management device of the destination cloud vendor to perform data recovery on the target image within the third virtual machine.

[0011] In one possible implementation, the server can also obtain the processing progress of cloud resources from the cloud vendor's cloud resource management device and send cloud resource processing progress indication information to the terminal. This processing progress indication message indicates the processing progress of each cloud resource selected by the user. Correspondingly, the terminal displays the processing progress of the cloud resources.

[0012] In one possible implementation, the user can configure the price fluctuation threshold of the first cloud resource on the terminal. Correspondingly, the terminal sends a cost management configuration message for the first cloud resource to the server. The cost management configuration message carries the price fluctuation threshold of the first cloud resource and the identifier of the second cloud vendor to which the first cloud resource belongs.

[0013] The server can periodically query the pricing of the first cloud resource from the second cloud provider. When the price fluctuation (both price increases and decreases are considered price fluctuations) reaches a price fluctuation threshold, a price fluctuation message is sent to the terminal. This message carries the latest pricing of the first cloud resource from the second cloud provider. Here, reaching the price fluctuation threshold can mean that the price fluctuation is greater than the price fluctuation threshold, or that the price fluctuation is greater than or equal to the price fluctuation threshold.

[0014] In one possible implementation, the server can also obtain the pricing information of cloud resources from different cloud vendors and feed it back to the terminal. In this way, users can know the pricing information of cloud resources from different cloud vendors more efficiently, and thus formulate corresponding migration strategies.

[0015] In one possible implementation, the server can also compare the pricing of cloud resources from different cloud vendors and recommend migration suggestions to the terminal. Specifically, the server determines the lowest price among the multiple cloud vendors' pricing for the second cloud resource and sends a migration suggestion message for the second cloud resource to the terminal. The migration suggestion message carries the current cloud vendor's pricing for the second cloud resource, the lowest price, and the identifier of the cloud vendor corresponding to the lowest price.

[0016] In one possible implementation, a user can add a cloud vendor account via a terminal. The terminal sends an account access message to the server, carrying the identifier of the first cloud vendor, the first cloud vendor account, and the password. The server then sends an account access request to the first cloud vendor's cloud resource management device, carrying the first cloud vendor account and its password. Next, the server receives cloud resource information corresponding to the first cloud vendor account from the cloud resource management device. This information may include cloud resource type, specifications, project affiliation, and payment type. Finally, the server can associate the first cloud vendor account with the cloud resource management account.

[0017] Secondly, a method for cloud resource processing is provided, which is applied to a terminal and includes the following:

[0018] The system displays options for various cloud resource processing types, cloud vendor options corresponding to at least one cloud vendor account associated with the cloud resource management account logged into the terminal, and cloud resource options corresponding to the at least one cloud vendor account.

[0019] In response to the selection operation of options for a first cloud resource processing type, a first cloud vendor, and at least one cloud resource belonging to the first cloud vendor, a first processing request for at least one cloud resource is sent to the server. The first processing request carries first cloud resource indication information, the identifier of the first cloud vendor to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information is used to indicate that the cloud resource to be processed is the at least one cloud resource.

[0020] In one possible implementation, the first processing type is resource migration, and the method further includes:

[0021] Detect the selection of the target cloud provider for resource migration;

[0022] The first processing request also carries the identifier of the destination cloud vendor for resource migration.

[0023] In one possible implementation, the at least one cloud resource is a virtual machine, and the method further includes:

[0024] Detect the selection operation for the database migration mode;

[0025] The first processing request also carries database migration mode indication information.

[0026] In one possible implementation, the at least one cloud resource is a virtual machine, and the method further includes:

[0027] Detect the selection of the business migration mode.

[0028] The first processing request also carries business migration mode indication information.

[0029] In one possible implementation, the method further includes:

[0030] The server receives processing progress indication information for at least one cloud resource, wherein the processing progress indication message is used to indicate the processing progress of each cloud resource among the at least one cloud resource.

[0031] Displays the processing progress of each of the at least one cloud resources.

[0032] In one possible implementation, the method further includes:

[0033] Obtain the price fluctuation threshold of the first cloud resource input by the user;

[0034] Send a cost management configuration message for the first cloud resource to the server, wherein the cost management configuration message carries the price fluctuation threshold;

[0035] The server receives a price fluctuation message, wherein the price fluctuation message is sent by the server when the price fluctuation of the pricing of the first cloud resource by the cloud provider to which the first cloud resource belongs reaches the price fluctuation threshold.

[0036] In one possible implementation, the method further includes:

[0037] The server receives a migration suggestion message for the second cloud resource, wherein the migration suggestion message carries the pricing of the second cloud resource by the cloud vendor currently owning the cloud resource, the minimum pricing, and the identifier of the cloud vendor corresponding to the minimum pricing.

[0038] In one possible implementation, the method further includes:

[0039] Obtain the first cloud vendor account and the password entered by the user;

[0040] Send an account access message to the server, wherein the account access message carries the identifier of the first cloud vendor, the account of the first cloud vendor, and the password of the account of the first cloud vendor.

[0041] Thirdly, a cloud resource processing apparatus is provided, which is applied to a server. The apparatus includes at least one module for implementing the cloud resource processing method provided in the first aspect or any implementable manner of the first aspect.

[0042] Fourthly, a cloud resource processing apparatus is provided, the apparatus being applied to a terminal, the apparatus comprising at least one module for implementing the cloud resource processing method provided by any of the first or second aspects or the second aspect described above.

[0043] Fifthly, a computing device cluster is provided, including at least one computing device, each computing device including a processor and memory;

[0044] 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 cloud resource processing method provided as described in the first aspect or any of the implementable methods of the first aspect.

[0045] Sixthly, a terminal is provided, including a processor and a memory;

[0046] The processor is configured to execute instructions stored in the memory to cause the terminal to perform the cloud resource processing method provided by the first aspect or any of the implementable methods of the first aspect.

[0047] In a seventh aspect, a cloud resource processing system is provided, the system comprising a terminal as described in the sixth aspect above and a cluster of computer devices as described in the fifth aspect above.

[0048] Eighthly, a computer program product containing instructions is provided, which, when executed by a cluster of computing devices, cause the cluster of computing devices to perform a cloud resource processing method as provided in the first aspect or any implementable manner of the first aspect.

[0049] In a ninth aspect, a computer program product comprising instructions is provided, which, when executed by a terminal, causes the terminal to perform a cloud resource processing method as provided in the second aspect or any of the implementable methods of the second aspect.

[0050] In a tenth aspect, a computer-readable storage medium is provided, comprising computer program instructions that, when executed by a cluster of computing devices, perform a cloud resource processing method as provided in the first aspect or any implementable manner of the first aspect.

[0051] Eleventhly, a computer-readable storage medium is provided, including computer program instructions that, when executed by a terminal, enable the terminal to perform a cloud resource processing method as provided in the second aspect or any of the implementable methods of the second aspect. Attached Figure Description

[0052] Figure 1This is a flowchart of a cloud resource processing method provided in this application;

[0053] Figure 2 This is a flowchart of a cloud resource processing method provided in this application;

[0054] Figure 3 This is a schematic diagram of a cloud resource processing interface provided in this application;

[0055] Figure 4 This is a schematic diagram of a cloud resource processing interface provided in this application;

[0056] Figure 5 This is a flowchart of a cloud resource processing method provided in this application;

[0057] Figure 6 This is a schematic diagram of a cloud resource processing interface provided in this application;

[0058] Figure 7 This is a schematic diagram of a cloud resource processing interface provided in this application;

[0059] Figure 8 This is a schematic diagram of a cloud resource processing interface provided in this application;

[0060] Figure 9 This is a flowchart of a cloud resource processing method provided in this application;

[0061] Figure 10 This is a schematic diagram of a cloud resource processing interface provided in this application;

[0062] Figure 11 This is a flowchart of a cloud resource processing method provided in this application;

[0063] Figure 12 This is a flowchart of a cloud resource processing method provided in this application;

[0064] Figure 13 This is a flowchart of a cloud resource processing method provided in this application;

[0065] Figure 14 This is a schematic diagram of a cloud resource processing interface provided in this application;

[0066] Figure 15 This is a schematic diagram of a cloud resource processing device provided in this application;

[0067] Figure 16 This is a schematic diagram of a cloud resource processing device provided in this application;

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

[0069] Figure 18 This is a schematic diagram illustrating a connection method between computing device clusters provided in an embodiment of this application. Detailed Implementation

[0070] This application provides a method for processing cloud resources, which can process cloud resources from multiple different cloud vendors. In this method, a user can select a cloud vendor, the cloud resources to be processed under that vendor, and the processing type of the cloud resources via a terminal. This triggers the terminal to send a processing request for the selected cloud resources to a server. The server, based on the processing request, processes the cloud resources of the corresponding cloud vendor through the cloud resource management device of that vendor. This method eliminates the need for users to manually log into the cloud resource management systems of each cloud vendor to process their respective cloud resources, effectively saving user time and improving the efficiency of cloud resource processing.

[0071] The aforementioned terminals can be devices such as mobile phones, tablets, desktop computers, and laptops, while the server can be a server, server cluster, etc. In the following embodiments, both the terminal and the server mentioned are devices used to implement the cloud resource processing method provided in this application.

[0072] The method provided in this application will be described below with reference to the accompanying drawings.

[0073] See Figure 1 The cloud resource processing method provided in this application may include the following steps:

[0074] Step 101: The terminal displays options for various cloud resource processing types, cloud vendor options corresponding to at least one cloud vendor account associated with the cloud resource management account logged into the terminal, and cloud resource options corresponding to at least one cloud vendor account.

[0075] The following section explains the cloud resource management cloud resource account and the accounts of various cloud vendors:

[0076] The cloud resource management account and the accounts of various cloud vendors can be independent of each other. That is, users can register a cloud resource management account with the server through a terminal, or they can register cloud vendor accounts with various cloud vendors through a terminal. These accounts are independent of each other. In this application, before processing cloud resources, users need to associate their cloud resource management account with the cloud vendor accounts they have registered with each cloud vendor to enable unified management of cloud resources under each cloud vendor. The specific association method will be exemplarily described in the following embodiments and will not be elaborated here.

[0077] Furthermore, in one possible implementation, the cloud resource management account and the accounts of various cloud vendors can be shared accounts across multiple systems. That is, this shared account can be used to log in to both the server described in this application and the cloud resource management systems provided by various cloud vendors. In this implementation, after the user logs in to the shared account via a terminal, the server can send a cloud resource information retrieval request to the cloud resource management devices of various cloud vendors using the shared account and password, carrying the shared account and password in the request. After the cloud vendor's cloud resource management device verifies the match between the shared account and password, it sends the cloud resource information corresponding to the shared account to the server. The server can then return the cloud resource information sent by each cloud vendor to the terminal. Here, the cloud resources corresponding to the shared account are the cloud resources purchased (or rented) by the user from the corresponding cloud vendor using the shared account.

[0078] After a user logs into their cloud resource management account through an application, webpage, or mini-program on their terminal, the terminal can display options for various cloud resource processing types, cloud vendor options corresponding to the cloud vendor accounts associated with the cloud resource management account, and cloud resource options corresponding to each cloud vendor account. There are multiple ways to display these options; they can be displayed on the same page or on different pages. The display methods may also differ depending on the cloud resource processing type. This application does not limit the specific display method. For ease of understanding, the display methods of the above options will be illustrated by example for different cloud resource processing types in the following embodiments.

[0079] Step 102: In response to the selection operation of the first cloud resource processing type, the first cloud vendor, and the option of at least one cloud resource belonging to the first cloud vendor, send a first processing request for at least one cloud resource to the server.

[0080] The first processing request carries first cloud resource indication information, the identifier of the first cloud vendor to which at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information is used to indicate that the cloud resource to be processed is at least one cloud resource.

[0081] In implementation, users can select at least one cloud resource to be processed, the cloud vendor to which the at least one cloud resource belongs, and the cloud resource processing type according to their actual needs. This triggers the terminal to send a processing request for the at least one cloud resource to the server. Here, in different display methods of the above options, the selection operations for the first cloud resource processing type, the first cloud vendor, and the at least one cloud resource belonging to the first cloud vendor can have different order. For example, the cloud vendor option can be selected first, then the cloud resource option, and finally the cloud resource processing type option. Alternatively, the cloud resource processing type option can be selected first, then the cloud vendor option, and finally the cloud resource option. For ease of understanding, the selection operation order of the above options will be illustrated in the following embodiments for different cloud resource processing types.

[0082] Step 103: The server performs the processing indicated by the first processing type indication information on at least one cloud resource through the cloud resource management equipment of the first cloud vendor.

[0083] In implementation, cloud resource processing types may include resource cleanup, resource migration, resource freezing, and resource unfreezing. The server-side processing may differ depending on the cloud resource processing type. The following embodiments will provide illustrative examples of the server-side processing for different cloud resource processing types.

[0084] In one possible implementation, the cloud resource processing method provided in this application can also perform cloud resource price comparison. Users can configure price fluctuation thresholds for each cloud resource. When the price fluctuation of a corresponding cloud resource reaches the user-configured fluctuation threshold, the server can notify the terminal. Furthermore, the server can compare the pricing of the same cloud resource across different cloud vendors and recommend migration suggestions to the user, advising them to migrate their cloud resources to a cloud vendor with lower pricing. The specific processing of cloud resource price comparison will be exemplarily described in the following embodiments.

[0085] Account association (also known as account access)

[0086] See Figure 2 Account association processing may include the following steps:

[0087] Step 201: The terminal displays the account access interface.

[0088] In implementation, to enable access to accounts from different cloud providers, the terminal can have a cloud resource processing application installed, or the user can access a cloud resource processing webpage through the terminal, or a cloud resource processing mini-program provided by an application installed on the terminal. Users can first log in to their registered cloud resource management account through the aforementioned application, webpage, or mini-program. Furthermore, the aforementioned application, webpage, or mini-program can provide an account access interface.

[0089] For example, see Figure 3 The document illustrates a possible account access interface. This interface may include a "New Access" option, which users can select when adding a new cloud vendor account. Specific selection methods may include clicking, long-pressing, swiping, etc., which are not limited in this application. Furthermore, the account access interface may also display the names and access status of already connected cloud vendors, as well as account operation options, including edit and delete options. The edit option can be used to modify the cloud vendor's name, account name, password, etc., while the delete option can be used to delete an already connected cloud vendor account.

[0090] Step 202: The terminal responds to the user's selection of the new access option by displaying the account addition window.

[0091] In implementation, after a user selects the "Add Access" option, the terminal can display an account addition window. For example, see... Figure 4 The account addition window can float on the account access interface. Users can move the window; in one possible implementation, users can long-press and drag any position within the window to move it. The window displays input boxes for the cloud provider name, cloud provider account, and account password, as well as confirmation and cancellation options. The confirmation option can be highlighted with a background color. Users enter the name of the target cloud provider in the cloud provider name input box, the user's registered account with the first cloud provider in the cloud provider account input box, and the password for that account in the account password input box. After entering the cloud provider name, account, and password, users can select the confirmation option if they confirm the input is correct. If users decide not to continue inputting for any reason, they can select the cancellation option or the close option in the upper right corner of the account addition window. The terminal responds to the user's selection of the cancellation or close option and closes the account addition window.

[0092] Step 203: The terminal sends an account access message to the server. The account access message carries the identifier of the first cloud vendor, the first cloud vendor account, and the password of the first cloud vendor account.

[0093] In practice, in response to the user's selection of the confirmation option, the terminal obtains the target cloud vendor's name, first cloud vendor's account and password entered by the user, and encapsulates the target cloud vendor's name, first cloud vendor's account and password in the account access message and sends it to the server.

[0094] Step 204: The server sends an account access request to the cloud resource management device of the first cloud vendor.

[0095] The account access request includes the First Cloud vendor's account and password.

[0096] In practice, each cloud vendor can set up its own cloud resource management device to receive user requests for processing cloud resources. In this application, the cloud resource management device can also be used to execute requests sent by the server of the cloud resource management system.

[0097] After receiving the account access message from the terminal, the server retrieves the identifier, account, and password of the first cloud vendor carried in the message, and encapsulates the account and password in the account access request. Then, the server sends the account access request to the cloud resource management device of the first cloud vendor.

[0098] Upon receiving an account access request from the server, the cloud resource management device of the first cloud vendor verifies whether the first cloud vendor's account and password match. If the account and password match, it retrieves the cloud resource information corresponding to the first cloud vendor's account and sends this information to the server. Here, the cloud resources corresponding to the first cloud vendor refer to the cloud resources purchased or rented by the user through the first cloud vendor's account. The cloud resource information may include the type of cloud resource, its name, specifications, the name of the project it belongs to, and the billing type. The name of the cloud resource and the name of the project can be customized by the user after purchasing the cloud resource.

[0099] Step 205: After receiving the cloud resource information of the cloud resources corresponding to the first cloud vendor's account sent by the cloud resource management device of the first cloud vendor, the server associates the cloud resource management account with the first cloud vendor's account.

[0100] Cloud resource processing

[0101] Cloud resource processing can include resource cleanup, resource migration, resource freezing, and resource unfreezing. These methods are explained below:

[0102] The following section explains the different types of cloud resource processing.

[0103] I. Cloud Resource Cleanup

[0104] See Figure 5 Resource cleanup can include the following steps:

[0105] Step 501: In response to the user's selection of resource cleanup options, the terminal displays options from multiple cloud vendors.

[0106] During implementation, the terminal can display a cloud resource processing interface, which includes options for multiple cloud resource processing types, such as resource migration, resource cleanup, resource freezing, and resource unfreezing. When a user needs to clean up cloud resources, they can select the resource cleanup option. After detecting the user's selection of the resource cleanup option, the terminal displays the cloud vendor options corresponding to the cloud vendor accounts associated with the currently logged-in cloud resource management account.

[0107] Step 502: In response to the user's selection of the first cloud provider's options, the terminal displays the first cloud provider's resource cleanup interface.

[0108] In implementation, this application offers two options: full cleanup and customized cleanup, for users to choose from. For example, see... Figure 6 The resource cleanup interface of the first cloud provider includes two function options: "Clean Up All" and "Custom Cleanup." "Clean Up All" allows for the automated orchestration and cleanup of cloud resources purchased on demand by the user, while "Custom Cleanup" allows for the cleanup of cloud resources selected by the user. Here, cloud resources purchased on demand refer to those charged by the hour or by the minute; these resources can be called on-demand resources. The following sections explain "Clean Up All" and "Custom Cleanup" separately.

[0109] 1. Clean up completely

[0110] A complete cleanup may include the following steps:

[0111] Step 503: In response to the user's selection of the full cleanup option, the terminal sends a full cleanup request to the server. The full cleanup request carries a first resource processing type indication information, a first cleanup type indication information, and the identifier of the first cloud vendor. The first resource processing type indication information is used to indicate that the resource processing type is cloud resource cleanup, and the first cleanup type indication information is used to indicate that the cleanup type is full cleanup.

[0112] Step 504: The server performs a compliance check on the First Cloud vendor account.

[0113] In practice, compliance checks may include balance checks, tax checks, etc.

[0114] For balance verification, the server sends a balance query request for the First Cloud vendor's account to the resource management device of the First Cloud vendor. Upon receiving the request, the resource management device returns the account balance information to the server. The server then determines whether the balance verification passes based on this information. Specifically, if the balance is positive, the First Cloud vendor's account is not in arrears, and the balance verification passes; if the balance is negative, the account is in arrears, and the balance verification fails.

[0115] For tax verification, the server sends a tax query request for the First Cloud vendor's account to the resource management device of the First Cloud vendor. Upon receiving the request, the resource management device retrieves the tax information for the First Cloud vendor's account and sends it back to the server. The server then determines whether the tax verification passes based on the tax information. Specifically, if the tax information indicates that the user has paid taxes normally, the tax verification for the First Cloud vendor's account is considered successful; if the tax information indicates that the user has not paid taxes normally, the tax verification for the First Cloud vendor's account is considered unsuccessful.

[0116] Step 505: If the server determines that the compliance verification of the First Cloud vendor account has failed, it sends a cleanup failure message to the terminal.

[0117] The message indicating a failed cleanup includes information about outstanding fees and / or failure to pay taxes.

[0118] During implementation, if the balance verification fails, the server will add an overdue payment instruction to the cleanup failure message; if the tax verification fails, the server will add an instruction that taxes have not been paid properly to the cleanup failure message.

[0119] Step 506: After receiving the cleanup failure message, the terminal displays a cleanup failure reminder message, which is used to remind the user of the cleanup failure and the reason for the failure.

[0120] During implementation, the terminal can use a pop-up window to display a notification message indicating that the cleanup failed.

[0121] Step 507: After confirming that the compliance verification of the First Cloud vendor account has passed, the server determines the dependency relationship between each on-demand resource corresponding to the First Cloud vendor account, and processes each on-demand resource through the First Cloud vendor's cloud resource management device according to the dependency relationship.

[0122] In implementation, once the compliance verification of the first cloud provider's account is passed, the server can obtain the cloud resource information corresponding to the first cloud provider's account from the first cloud provider's cloud resource management device. Based on the cloud resource information, it can determine the resources included in the subscription period (specifically, monthly subscription resources, annual subscription resources, etc.) and on-demand resources (hourly paid resources). For on-demand resources, based on the pre-stored dependencies between various types of cloud resources, the dependencies of each on-demand resource are determined. Then, according to the dependencies, the server sequentially calls the resource cleanup interface corresponding to the cloud resource type provided by the first cloud provider, instructing the first cloud provider's cloud resource management device to clean up the on-demand resources.

[0123] The aforementioned dependencies refer to the necessary order of operations during cleanup. For example, if there is a dependency between ECS and EVS, the ECS must be cleaned up first, followed by the EVS. Therefore, when calling the resource cleanup interface, the resource cleanup interface for ECS provided by the first cloud provider must be called first to clean up each ECS instance, and then the cleanup interface for EVS provided by the first cloud provider must be called to clean up each EVS instance.

[0124] Step 508: The server sends packet periodic resource information to the terminal.

[0125] In practice, for recurring resources, the server can send the corresponding recurring resource information to the terminal for manual cleanup by the user. This recurring resource information may include the cloud resource type, name, specifications, project name, and billing type of each recurring resource.

[0126] Step 509: In response to the user's selection of at least one package-period resource option, the terminal sends a cleanup request for the at least one package-period resource to the server, wherein the cleanup request carries package-period resource indication information, the identifier of the first cloud vendor, and the first resource processing type indication information.

[0127] In implementation, such as Figure 7 As shown, after receiving the packet recurring resource information sent by the server, the terminal can display options for each packet recurring resource. It can also display packet recurring resource processing prompts to encourage the user to manually clean up the packet recurring resources.

[0128] Users can select at least one packet-cycle resource that they want to clean up, and the terminal will send a cleanup request to the server for the selected packet-cycle resource.

[0129] Step 510: The server processes at least one of the above-mentioned package periodic resources through the cloud resource management equipment of the first cloud vendor.

[0130] In practice, after receiving a request to clean up at least one of the above-mentioned package-period resources, the server calls the resource cleanup interface corresponding to the cloud resource type of the package-period resources provided by the first cloud vendor, and instructs the cloud resource management device of the first cloud vendor to clean up the package-period resources.

[0131] 2. Custom Cleanup

[0132] Custom cleanup can include the following steps:

[0133] Step 511: In response to the user's selection of custom cleanup options, the terminal displays the options for each cloud resource corresponding to the first cloud vendor account.

[0134] In implementation, if a user wants to manually clean up cloud resources, they can select the custom cleanup option. After the terminal detects this selection, it displays the options for each cloud resource corresponding to the first cloud provider's account. Specifically, this step can involve the terminal responding to the user's selection by sending a request to the server to retrieve the cloud resource information corresponding to the first cloud provider's account. Upon receiving this request, the server retrieves the cloud resource information corresponding to the first cloud provider's account from the first cloud provider's cloud resource management device and returns it to the terminal. The terminal then displays the options for each cloud resource based on the returned information.

[0135] Furthermore, cloud resources may be deployed in different regions, and correspondingly, such as Figure 8 As shown, the terminal can display cloud resource options based on the region where the cloud resource is located. Figure 8 The system displays five region options: Region 1, Region 2, Region 3, Region 4, and Region 5. Users can select the region they want to clear cloud resources from, which will then display the cloud resource options for that region for the user to choose from.

[0136] Step 512: In response to the user's selection of at least one cloud resource, the terminal sends a cleanup request for the at least one cloud resource to the server. The cleanup request carries cloud resource indication information, the identifier of the first cloud vendor, first resource processing type indication information, and second cleanup type indication information. The cloud resource indication information is used for at least one cloud resource selected by the user, and the second cleanup type indication information is used to indicate that the cleanup type is custom cleanup.

[0137] Step 513: The server performs a compliance check on the First Cloud vendor account.

[0138] Step 514: If the server determines that the compliance verification of the First Cloud vendor account has failed, it sends a cleanup failure message to the terminal. This message includes information on outstanding fees and / or non-payment of taxes.

[0139] Step 515: After receiving the cleanup failure message, the terminal displays a cleanup failure reminder message, which is used to remind the user of the cleanup failure and the reason for the failure.

[0140] Here, the specific processing of steps 513, 514, and 515 is the same as that of steps 504, 505, and 506 above, and will not be repeated here.

[0141] Step 516: After confirming that the compliance verification of the first cloud vendor's account has passed, the server cleans up the cloud resources indicated by the above cloud resource indication information through the cloud resource management equipment of the first cloud vendor.

[0142] In implementation, the server calls the resource cleanup interface corresponding to the cloud resource type of at least one cloud resource provided by the first cloud vendor, instructing the cloud resource management device of the first cloud vendor to clean up the at least one cloud resource.

[0143] In one possible implementation, the server can periodically query the cleanup progress of each cloud resource and report it back to the terminal. The terminal can then display the processing progress of each cloud resource. Furthermore, the server can calculate the total processing progress of the target cloud provider for the target account based on the processing progress of each cloud resource. Specifically, it can take the average of the processing progress of each cloud resource to obtain the total processing progress. This total processing progress is also reported back to the terminal, allowing the terminal to display it as well.

[0144] In one possible implementation, since resource cleanup is a high-risk operation, to prevent malicious attacks, in steps 507, 510, and 516 above, the server can first call the resource freeze interface for the corresponding cloud resource type to freeze the cloud resources that need to be cleaned up. After the protection period, the corresponding resource cleanup interface can then be called to clean up the cloud resources. The protection period can be configured by technical personnel according to the actual situation, for example, 30 days.

[0145] II. Resource Migration

[0146] See Figure 9 Resource migration can include the following steps:

[0147] Step 901: In response to the user's selection of resource migration options, the terminal displays the source cloud vendor selection options and the destination cloud vendor selection options for resource migration.

[0148] During implementation, after detecting the selection operation of resource migration options, the terminal can display the source cloud vendor selection option and the destination cloud vendor selection option, which can be used to select the source cloud vendor and the destination cloud vendor for this resource according to actual needs. The source cloud vendor refers to the cloud vendor to which the cloud resource currently belongs, and the destination cloud vendor refers to the cloud vendor to which the user wants to migrate the cloud resource from the source cloud vendor.

[0149] In one possible implementation, resource migration can be achieved through object storage. That is, first, source OBS buckets and destination OBS buckets are applied for from the source cloud provider and the destination cloud provider, respectively. Then, the data to be migrated is first put into the source OBS bucket, and then migrated from the source OBS bucket to the destination OBS bucket. Finally, the data to be migrated is retrieved from the destination OBS bucket and the data is restored on the designated cloud resources of the destination cloud provider.

[0150] In this scenario, in response to the user's selection of resource migration options, the terminal can display the object storage configuration interface. See also... Figure 10 The document illustrates an object storage configuration interface, which includes options for migration mode, source cloud vendor selection, source Object Storage Service (OBS) bucket name, source cloud vendor access key ID (AK), source cloud vendor secret access key (SK), destination cloud vendor selection, destination OBS bucket name, destination cloud vendor AK, destination cloud vendor SK, destination OBS bucket name, confirmation, and cancellation.

[0151] Users can select or enter the corresponding content from the above options according to their actual needs. After selecting or entering the content, users can confirm that it is correct. Then, the terminal sends an object storage configuration message to the server. This object storage configuration information carries the source cloud vendor's identifier, source cloud vendor's AK, source cloud vendor's SK, source OBS bucket name, destination cloud vendor's identifier, destination cloud vendor's AK, destination cloud vendor's SK, and destination OBS bucket name.

[0152] Upon receiving the object storage configuration message, the server sends a source OBS bucket request to the source cloud vendor's cloud resource management device. This request includes the source OBS bucket name, the source cloud vendor's access key (AK), and the source cloud vendor's search key (SK). Additionally, a destination OBS bucket request is sent to the destination cloud vendor, also including the destination OBS bucket name, the destination cloud vendor's AK, and the destination cloud vendor's search key (SK).

[0153] Step 902: The terminal displays the options for each cloud resource corresponding to the source cloud vendor account.

[0154] In practice, after a user selects a source cloud provider, the terminal can display options for various cloud resources corresponding to the source cloud provider's account for the user to choose from. The source cloud provider account is the cloud provider account that the user registered with the source cloud provider.

[0155] Step 903: In response to the user's selection of the first cloud resource, the terminal sends a migration request for the first cloud resource to the server.

[0156] The migration request includes the source cloud vendor's identifier, the destination cloud vendor's identifier, the first cloud resource indication information, and the migration mode indication information. The first cloud resource indication information refers to at least the first cloud resource to be migrated, and the migration mode indication information indicates the migration mode to be used, including database migration, business migration, and full migration.

[0157] Step 904: The server performs compliance checks on the source cloud vendor account and the destination cloud vendor account.

[0158] Step 905: If the server determines that the compliance verification of the source cloud vendor account and / or the destination cloud vendor account has failed, it sends a migration failure message to the terminal. The migration failure message includes overdue payment instructions and / or instructions for non-payment of taxes.

[0159] Step 906: After receiving the migration failure message, the terminal displays a migration failure reminder message, which informs the user of the migration failure and the reason for the failure. The reasons for migration failure include account arrears and / or failure to pay taxes properly.

[0160] Here, the specific processing of steps 904, 905, and 906 is similar to that of steps 504, 505, and 506 above, and will not be repeated here.

[0161] Step 907: After confirming that the compliance verification of the source cloud vendor account and / or the destination cloud vendor account has passed, the server migrates the first cloud resource through the cloud resource management devices of the source cloud vendor and the destination cloud vendor.

[0162] In the database migration mode, the server requests a second cloud resource from the target cloud vendor's cloud resource management device. This second cloud resource is the same type as the first cloud resource, such as both being virtual machines. Then, the server calls the first resource migration-out interface provided by the source cloud vendor to store the data corresponding to the first cloud resource in the source OBS bucket. Next, it calls the first resource migration-in interface provided by the target cloud vendor to migrate the data from the source OBS bucket to the target cloud vendor's second cloud resource. In one possible implementation, the second cloud resource may include a primary node and a backup node; in this case, the data in the source OBS bucket needs to be migrated to both the primary and backup nodes simultaneously to achieve primary-backup synchronization.

[0163] In the business migration mode, the server first requests a third cloud resource from the target cloud vendor's cloud resource management device. This third cloud resource and the first cloud resource are of the same type, such as both being virtual machines. Then, the server calls the second resource migration-out interface provided by the source cloud vendor to package the first cloud resource into a disk image (e.g., qcow2) or an optical disc image (e.g., iso) and stores it in the source OBS bucket. Next, the server calls the second resource migration-in interface provided by the target cloud vendor to send the qcow2 or iso image from the source OBS bucket to the target cloud vendor's cloud resource management device. The cloud resource management device then uses the qcow2 or iso image to perform data recovery on the third cloud resource, designating the third cloud resource as the primary node and the first cloud resource as the backup node, and cleans up the first cloud resource.

[0164] When the business migration mode is full migration, the server can perform both the database migration and the business migration described above.

[0165] III. Resource Freeze

[0166] See Figure 11 The process of freezing resources may include the following steps:

[0167] Step 1101: In response to the user's selection of the resource freeze option, the terminal displays options from multiple cloud vendors.

[0168] In practice, after the terminal detects the user's selection of the resource freeze option, the terminal displays the cloud vendor options corresponding to the cloud vendor accounts associated with the currently logged-in cloud resource management account.

[0169] Step 1102: In response to the user's selection of the first cloud provider's options, the terminal displays the cloud resource options corresponding to the first cloud provider's account.

[0170] Step 1103: In response to the user's selection of at least one cloud resource, the terminal sends a freeze request to the server for the at least one cloud resource. The freeze request carries cloud resource indication information, the identifier of the first cloud vendor, and third resource processing type indication information. The cloud resource indication information is used to indicate the at least one cloud resource selected by the user, and the third resource processing type indication information is used to indicate that the resource processing type is resource freeze.

[0171] Step 1104: The server performs a compliance check on the First Cloud vendor account.

[0172] Step 1105: If the server determines that the compliance verification of the First Cloud vendor's account has failed, it sends a freeze failure message to the terminal. This freeze failure message includes information on outstanding fees and / or non-payment of taxes.

[0173] Step 1106: After receiving the freeze failure message, the terminal displays a freeze failure reminder message, which informs the user of the freeze failure and the reason for the failure. Reasons for freeze failure include account arrears and / or failure to pay taxes.

[0174] Step 1107: After confirming that the compliance verification of the first cloud vendor's account has passed, the server freezes the cloud resources indicated by the above cloud resource indication information through the cloud resource management device of the first cloud vendor.

[0175] In implementation, after confirming that the compliance verification of the first cloud vendor's account has passed, the server determines the dependency relationship between at least one of the above-mentioned cloud resources based on the pre-stored dependency relationships between various types of cloud resources. Based on the dependency relationship, the server sequentially calls the resource freezing interface corresponding to the corresponding cloud resource type provided by the first cloud vendor, instructing the cloud resource management device of the first cloud vendor to freeze the cloud resources.

[0176] IV. Resource Unfreezing

[0177] See Figure 12 The process of unfreezing resources may include the following steps:

[0178] Step 1201: In response to the user's selection of resource unfreezing options, the terminal displays options from multiple cloud vendors.

[0179] In practice, after the terminal detects the user's selection of the resource unfreezing option, the terminal displays the cloud vendor options corresponding to the cloud vendor accounts associated with the currently logged-in cloud resource management account.

[0180] Step 1202: In response to the user's selection of the first cloud provider's options, the terminal displays the options for the cloud resources that are in a frozen state corresponding to the first cloud provider's account.

[0181] Step 1203: In response to the user's selection of at least one cloud resource in a frozen state, the terminal sends an unfreezing request to the server for the at least one cloud resource in a frozen state. The unfreezing request carries cloud resource indication information, the identifier of the first cloud vendor, and fourth resource processing type indication information. The cloud resource indication information is used to indicate the at least one cloud resource in a frozen state selected by the user, and the fourth resource processing type indication information is used to indicate that the resource processing type is resource unfreezing.

[0182] Step 1204: The server performs a compliance check on the First Cloud vendor account.

[0183] Step 1205: If the server determines that the compliance verification of the First Cloud vendor account has failed, it sends an unfreezing failure message to the terminal. This unfreezing failure message includes information on outstanding fees and / or non-payment of taxes.

[0184] Step 1206: After receiving the unfreezing failure message, the terminal displays an unfreezing failure reminder message. This message informs the user of the unfreezing failure and the reason for it. Reasons for unfreezing failure include account arrears and / or failure to pay taxes.

[0185] Step 1207: After confirming that the compliance verification of the first cloud vendor's account has passed, the server unfreezes the cloud resources indicated by the above cloud resource indication information through the cloud resource management device of the first cloud vendor.

[0186] In practice, the server calls the resource unfreezing interface corresponding to the cloud resource type of at least one cloud resource provided by the first cloud vendor, and instructs the cloud resource management device of the first cloud vendor to unfreeze the at least one cloud resource.

[0187] Cloud resource price comparison

[0188] See Figure 13 The process of comparing cloud resource prices may include the following steps:

[0189] Step 1301: The terminal obtains the price fluctuation threshold of the first cloud resource input by the user.

[0190] In implementation, the terminal can display a price comparison configuration interface, allowing users to manage the cost of cloud resources purchased or leased from various cloud providers. See also... Figure 14This demonstrates a possible price comparison configuration interface, displaying multiple cloud vendor options such as Cloud A, Cloud H, and Cloud T. If a user needs to configure cost management for cloud resources on Cloud H, they can select the Cloud H option. In response to the user's selection of the Cloud H option, the terminal displays the cost management interface for Cloud H. This interface includes cost management display areas for each cloud resource the user has already purchased from Cloud H. Additionally, the Cloud H cost management interface may display an "Add" option. Selecting this option displays a new cloud resource cost management interface, where the user can choose the cloud vendor, resource type, specifications, payment type (annual, monthly, hourly, etc.), price fluctuation threshold, and difference coefficient. After completing the addition operation, the terminal adds the corresponding cost management display area for the newly added cloud resource to the respective cloud vendor's cost management interface. Each cloud resource's cost management display area includes the cloud resource type, specifications, payment type, price fluctuation threshold, and editing options. Figure 14 As shown, after the user selects the edit option, the cost management configuration window for the cloud resource will be displayed. In this window, the user can modify the payment type, price fluctuation threshold, and difference coefficient. The difference coefficient represents the allowable error range for the price fluctuation threshold and is an optional parameter. For example, if the price fluctuation threshold is 4200 and the difference coefficient is 0.2, the server will send a price fluctuation message to the user's terminal when the price fluctuation reaches 4200 - 4200 * 0.2.

[0191] Using the above method, users can configure cost management for the first cloud resources of the first cloud provider. After the user finishes editing in the cost management configuration window corresponding to the first cloud resource, the price fluctuation threshold and difference coefficient entered by the user are obtained.

[0192] Step 1302: The terminal sends a cost management configuration message for the first cloud resource to the server.

[0193] The cost management configuration message includes a price fluctuation threshold and the identifier of the cloud vendor to which the first cloud resource belongs. If the user has configured a difference coefficient, the cost management configuration message can also include the difference coefficient.

[0194] Step 1303: When the server determines that the price fluctuation of the cloud provider's pricing for the first cloud resource has reached the price fluctuation threshold, it sends a price fluctuation message to the terminal. This price fluctuation message carries the pricing information for the first cloud resource from the cloud provider.

[0195] In implementation, when the cost management configuration message includes a variance coefficient, the server periodically queries the price of the first cloud resource. When the price fluctuation reaches the actual price fluctuation threshold, it sends a price fluctuation message for that cloud resource to the terminal. The actual price fluctuation threshold is XX*Y, where X represents the price fluctuation threshold and Y represents the variance coefficient.

[0196] Without including a difference coefficient in the cost management configuration message, the server periodically queries the price of the first cloud resource. When the price fluctuation reaches the price fluctuation threshold, it sends a price fluctuation message for that cloud resource to the terminal.

[0197] In one possible implementation, the server periodically queries the latest pricing of cloud resources purchased or rented by the user from various cloud providers and sends it to the terminal. For example, if a user rents an ECS instance with a monthly subscription fee and a C1.8xlarge.linux specification from cloud provider A, the server can periodically obtain the latest pricing of the same ECS instance with a monthly subscription fee and a C1.8xlarge.linux specification from cloud providers such as cloud provider A, cloud provider T, and cloud provider H, and send it to the terminal.

[0198] Correspondingly, the terminal can also display a price comparison interface, which can be used to compare the pricing of cloud resources of the same type, specifications, and payment type from different cloud vendors. As shown in Table 1 below.

[0199] Table 1

[0200] Cloud resource types Specification Paid type A Cloud pricing T Cloud pricing H Cloud pricing ECS C1.8xlarge.linux Monthly subscription X1 Y1 Z1 ECS C1.4xlarge.linux Monthly subscription X2 Y2 Z2 …… …… …… …… …… ……

[0201] Furthermore, after determining the pricing of the primary cloud resource across various cloud vendors, if the lowest price is not offered by the cloud vendor currently hosting the primary cloud resource, the server sends a migration suggestion message to the terminal. This message includes the pricing of the primary cloud resource from the cloud vendor currently hosting it, the lowest price, and the identifier of the cloud vendor corresponding to the lowest price. For example, if a user has subscribed to the first-tier EVS plan on Cloud A, and the server determines that Cloud H offers the lowest price for the first-tier EVS plan, it can send a migration suggestion message to the terminal. This message includes Cloud A's current monthly pricing for the first-tier EVS plan, Cloud H's identifier, and Cloud H's current monthly pricing for the first-tier EVS plan. This suggests that the user switch from the first-tier EVS plan on Cloud A to the first-tier EVS plan on Cloud B. Additionally, this migration strategy message can be sent to the user's registered mobile phone number or email address.

[0202] Figure 15 This application provides a cloud resource processing device, see [link to application]. Figure 15 The device can be the aforementioned server, and the device includes:

[0203] The receiving module 1510 is configured to receive a first processing request for at least one cloud resource sent by a terminal, wherein the first processing request carries first cloud resource indication information, the identifier of a first cloud vendor to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information is used to indicate that the cloud resource to be processed is the at least one cloud resource. The terminal is logged into a cloud resource management account, and the first cloud vendor is the cloud vendor corresponding to any one of the at least one cloud vendor accounts associated with the cloud resource management account.

[0204] The processing module 1520 is used to perform the processing indicated by the first processing type indication information on the at least one cloud resource through the cloud resource management device of the first cloud vendor.

[0205] In one possible implementation, the processing type indicated by the first processing type indication information is resource cleanup, and the processing module 1520 is used for:

[0206] Determine the dependencies between the at least one cloud resource;

[0207] Based on the dependencies, resource cleanup is performed sequentially on the at least one cloud resource.

[0208] In one possible implementation, the processing type indicated by the first processing type indication information is resource migration, and the first processing request also carries the identifier of the destination cloud vendor for resource migration, wherein the first cloud vendor is the source cloud vendor for resource migration.

[0209] The processing module 1520 is used for:

[0210] The first cloud provider's cloud resource management equipment is used to perform a migration process on the at least one cloud resource.

[0211] The at least one cloud resource is migrated in using the cloud resource management equipment of the target cloud vendor.

[0212] In one possible implementation, the at least one cloud resource is a virtual machine, and the first processing request further carries migration mode indication information. If the migration mode indicated by the migration mode indication information is a database migration, the processing module 1520 is configured to:

[0213] Apply to the cloud resource management equipment of the target cloud vendor for a first virtual machine as the master node and apply for a second virtual machine as the backup node;

[0214] The data corresponding to the at least one cloud resource is migrated to the cloud sub-source management device of the destination cloud vendor through the cloud resource management device of the first cloud vendor.

[0215] The data corresponding to the at least one cloud resource is simultaneously migrated to the primary node and the backup node using the cloud resource management equipment of the target cloud vendor.

[0216] In one possible implementation, the at least one cloud resource is a virtual machine, and the first processing request further carries migration mode indication information. If the migration mode indicated by the migration mode indication information is a business migration, the processing module 1520 is configured to:

[0217] The first cloud provider's cloud resource management device is used to package the at least one cloud resource into a target image and migrate it to the target cloud provider's cloud sub-source management device.

[0218] Request a third virtual machine from the cloud resource management equipment of the target cloud vendor;

[0219] Data recovery of the target image is performed on the third virtual machine using the cloud resource management equipment of the target cloud vendor.

[0220] In one possible implementation, the device further includes a transmitting module for:

[0221] Determine the processing progress of the at least one cloud resource;

[0222] Send processing progress indication information of the at least one cloud resource to the terminal, wherein the processing progress indication message is used to indicate the processing progress of each cloud resource in the at least one cloud resource.

[0223] In one possible implementation, the receiving module 1510 is further configured to:

[0224] The terminal sends a cost management configuration message for a first cloud resource, wherein the cost management configuration message carries a price fluctuation threshold for the first cloud resource.

[0225] It also includes a sending module, used for:

[0226] When the price fluctuation of the cloud provider to which the first cloud resource belongs reaches the price fluctuation threshold, a price fluctuation message is sent to the terminal, wherein the price fluctuation message carries the pricing of the first cloud resource by the cloud provider to which the first cloud resource belongs.

[0227] In one possible implementation, the device further includes a transmitting module for:

[0228] For each cloud resource corresponding to each cloud vendor account associated with the cloud resource management account, obtain the pricing of the cloud resource from multiple cloud vendors;

[0229] Send pricing information for the cloud resources from the multiple cloud providers to the terminal.

[0230] In one possible implementation, the device further includes a transmitting module for:

[0231] Determine the lowest price among multiple cloud vendors for the second cloud resource;

[0232] A migration suggestion message for the second cloud resource is sent to the terminal, wherein the migration suggestion message carries the pricing of the second cloud resource by the cloud vendor currently owning the cloud resource, the minimum pricing, and the identifier of the cloud vendor corresponding to the minimum pricing.

[0233] In one possible implementation, the receiving module 1510 is further configured to:

[0234] Receive an account access message sent by the terminal, wherein the account access message carries the identifier of the first cloud vendor, the account of the first cloud vendor, and the password of the account of the first cloud vendor;

[0235] The device further includes a transmitting module for:

[0236] Send an account access request to the cloud resource management device of the first cloud vendor, wherein the account access request carries the first cloud vendor account and the password of the first cloud vendor account;

[0237] The receiving module 1510 is also used to receive cloud resource information corresponding to the first cloud vendor account sent by the cloud resource management device of the first cloud vendor.

[0238] Associate the first cloud vendor account with the cloud resource management account.

[0239] Both the receiving module 1510 and the processing module 1520 can be implemented in software or in hardware. For example, the implementation of the processing module 1520 will be described below. Similarly, the implementation of the receiving module 1510 can be referenced to that of the processing module 1520.

[0240] As an example of a software functional unit, processing module 1520 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, or a container. Further, the aforementioned computing instance may be one or more. For example, processing module 1520 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 within the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed within 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.

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

[0242] As an example of a hardware functional unit, the processing module 1520 may include at least one computing device, such as a server. Alternatively, the processing module 1520 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.

[0243] The processing module 1520 includes multiple computing devices that can be distributed within the same region or in different regions. Similarly, the processing module 1520 can be distributed within the same Availability Zone (AZ) or in different AZs. Likewise, the processing module 1520 can be distributed within 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.

[0244] It should be noted that, in other embodiments, the processing module 1520 can be used to execute any step in the cloud resource processing method, and the receiving module 910 can be used to execute any step in the cloud resource processing method. The steps implemented by the processing module 1520 and the receiving module 1510 can be specified as needed. The processing module 1520 and the receiving module 1510 respectively implement different steps in the cloud resource processing method to realize all the functions of the cloud resource processing device.

[0245] Figure 16 This application provides a cloud resource processing device, see [link to application]. Figure 16 The device can be the aforementioned terminal, and the device includes:

[0246] Display module 1610 is used to display options for multiple cloud resource processing types, cloud vendor options corresponding to at least one cloud vendor account associated with the cloud resource management account logged in by the terminal, and cloud resource options corresponding to the at least one cloud vendor account.

[0247] The sending module 1620 is configured to send a first processing request for at least one cloud resource to the server in response to a selection operation of an option for a first cloud resource processing type, an option for a first cloud vendor, and an option for at least one cloud resource belonging to the first cloud vendor. The first processing request carries first cloud resource indication information, an identifier of the first cloud vendor to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information is used to indicate that the cloud resource to be processed is the at least one cloud resource.

[0248] In one possible implementation, the first processing type is resource migration, and the apparatus further includes a detection module for:

[0249] Detect the selection of the target cloud provider for resource migration;

[0250] The first processing request also carries the identifier of the destination cloud vendor for resource migration.

[0251] In one possible implementation, the at least one cloud resource is a virtual machine, and the apparatus further includes a detection module for:

[0252] Detect the selection operation for the database migration mode;

[0253] The first processing request also carries database migration mode indication information.

[0254] In one possible implementation, the at least one cloud resource is a virtual machine, and the apparatus further includes a detection module for:

[0255] Detect the selection of the business migration mode.

[0256] The first processing request also carries business migration mode indication information.

[0257] In one possible implementation, the device further includes a receiving module for:

[0258] The server receives processing progress indication information for at least one cloud resource, wherein the processing progress indication message is used to indicate the processing progress of each cloud resource among the at least one cloud resource.

[0259] The display module 1610 is also used to display the processing progress of each cloud resource in the at least one cloud resource.

[0260] In one possible implementation, the sending module 1620 is further configured to:

[0261] Obtain the price fluctuation threshold of the first cloud resource input by the user;

[0262] Send a cost management configuration message for the first cloud resource to the server, wherein the cost management configuration message carries the price fluctuation threshold;

[0263] The device further includes a receiving module for:

[0264] The server receives a price fluctuation message, wherein the price fluctuation message is sent by the server when the price fluctuation of the pricing of the first cloud resource by the cloud provider to which the first cloud resource belongs reaches the price fluctuation threshold.

[0265] In one possible implementation, the device further includes a receiving module for:

[0266] The server receives a migration suggestion message for the second cloud resource, wherein the migration suggestion message carries the pricing of the second cloud resource by the cloud vendor currently owning the cloud resource, the minimum pricing, and the identifier of the cloud vendor corresponding to the minimum pricing.

[0267] In one possible implementation, the apparatus further includes an acquisition module for:

[0268] Obtain the first cloud vendor account and the password entered by the user;

[0269] Send an account access message to the server, wherein the account access message carries the identifier of the first cloud vendor, the account of the first cloud vendor, and the password of the account of the first cloud vendor.

[0270] It should be noted that the cloud resource processing apparatus provided in the above embodiments is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the terminal can be divided into different functional modules to complete all or part of the functions described above. In addition, the cloud resource processing apparatus and the cloud resource processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0271] This application also provides a computing device 1700. For example... Figure 17 As shown, the computing device 1700 includes a bus 1702, a processor 1704, a memory 1706, and a communication interface 1708. The processor 1704, the memory 1706, and the communication interface 1708 communicate with each other via the bus 1702. The computing device 1700 can be a server or a terminal. It should be understood that this application does not limit the number of processors and memories in the computing device 1700.

[0272] The 1702 bus 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 17 The bus 1702 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 1702 may include a path for transmitting information between various components of the computing device 1700 (e.g., memory 1706, processor 1704, communication interface 1708).

[0273] Processor 1704 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

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

[0275] The memory 1706 stores executable program code, which the processor 1704 executes to implement the aforementioned cloud resource processing methods. That is, the memory 1706 stores instructions for executing the cloud resource processing methods.

[0276] Alternatively, the memory 1706 may store executable code, which the processor 1704 executes to implement the functions of the aforementioned cloud service-based data analysis device, thereby realizing the cloud resource processing method. That is, the memory 1706 stores instructions for executing the cloud resource processing method.

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

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

[0279] like Figure 18 As shown, the computing device cluster includes at least one computing device 1700. The memory 1706 of one or more computing devices 1700 in the computing device cluster may store the same instructions for executing cloud-based data analysis methods.

[0280] In some possible implementations, the memory 1706 of one or more computing devices 1700 in the computing device cluster may also store partial instructions for executing cloud-based data analysis methods. In other words, a combination of one or more computing devices 1700 can jointly execute instructions for executing cloud-based data analysis methods.

[0281] It should be noted that the memory 1706 in different computing devices 1700 within the computing device cluster can store different instructions, each used to execute a portion of the functions of the cloud-based data analysis device. That is, the instructions stored in the memory 1706 of different computing devices 1700 perform the aforementioned cloud resource processing functions.

[0282] 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. One possible implementation involves two computing devices, 1700A and 1700B, being connected via a network. Specifically, they are connected to the network through communication interfaces on each computing device.

[0283] It should be understood that the functions of computing device 1700A can also be performed by multiple computing devices 1700. Similarly, the functions of computing device 1700B can also be performed by multiple computing devices 1700.

[0284] In one possible implementation, the aforementioned account access, cloud resource price comparison, and resource cleanup can be performed by the same computer device or by different computer devices.

[0285] 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 is run on at least one computing device, it causes the at least one computing device to perform a cloud-based data analysis method.

[0286] 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 that includes 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 cloud-based data analysis method.

[0287] 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 method for processing cloud resources, characterized in that, The method is applied to the server side, and the method includes: A receiving terminal sends a first processing request for at least one cloud resource, wherein the first processing request carries first cloud resource indication information, the identifier of a first cloud vendor to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information is used to indicate that the cloud resource to be processed is the at least one cloud resource. The terminal is logged into a cloud resource management account. The first cloud vendor is the cloud vendor corresponding to any one of the at least one cloud vendor accounts associated with the cloud resource management account. If the processing type indicated by the first processing type indication information is resource migration, the first processing request also carries the identifier of the destination cloud vendor for resource migration and migration mode indication information. The first cloud vendor is the source cloud vendor for resource migration. The receiving terminal sends an object storage configuration message and sends a source object storage OBS bucket application request to the cloud resource management device of the source cloud vendor in order to apply for a source object storage bucket from the source cloud vendor. When the migration mode indicated by the migration mode indication information is database migration, a first virtual machine is requested from the cloud resource management device of the destination cloud vendor as the master node, and a second virtual machine is requested as the backup node; through the cloud resource management device of the first cloud vendor, the data corresponding to the first cloud resource is stored in the source OBS bucket, and through the cloud resource management device of the destination cloud vendor, the data corresponding to the first cloud resource stored in the source OBS bucket is migrated to the master node and the backup node; When the migration mode indicated by the migration mode indication information is business migration, the first cloud vendor's cloud resource management device packages the at least one cloud resource into a target image and stores it in the source OBS bucket; a third virtual machine is requested from the target cloud vendor's cloud resource management device, and the target image stored in the OBS bucket is obtained through the target cloud vendor's cloud resource management device, and data recovery is performed on the target image in the third virtual machine.

2. The method according to claim 1, characterized in that, The processing type indicated by the first processing type indication information is resource cleanup, and the method further includes: Determine the dependencies between the at least one cloud resource; The execution of the processing indicated by the first processing type indication information on the at least one cloud resource includes: Based on the dependencies, resource cleanup is performed sequentially on the at least one cloud resource.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Determine the processing progress of the at least one cloud resource; Send processing progress indication information of the at least one cloud resource to the terminal, wherein the processing progress indication message is used to indicate the processing progress of each cloud resource among the at least one cloud resource.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The terminal sends a cost management configuration message for a first cloud resource, wherein the cost management configuration message carries a price fluctuation threshold for the first cloud resource. When the price fluctuation of the cloud provider to which the first cloud resource belongs reaches the price fluctuation threshold, a price fluctuation message is sent to the terminal, wherein the price fluctuation message carries the pricing of the first cloud resource by the cloud provider to which the first cloud resource belongs.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: For each cloud resource corresponding to each cloud vendor account associated with the cloud resource management account, obtain the pricing of the cloud resource from multiple cloud vendors; Send pricing information for the cloud resources from the multiple cloud providers to the terminal.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Determine the lowest price among multiple cloud vendors for the second cloud resource; Send a migration suggestion message for the second cloud resource to the terminal, wherein the migration suggestion message carries the pricing of the second cloud resource by the cloud vendor currently owning the cloud resource, the minimum pricing, and the identifier of the cloud vendor corresponding to the minimum pricing.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive an account access message sent by the terminal, wherein the account access message carries the identifier of the first cloud vendor, the account of the first cloud vendor, and the password of the account of the first cloud vendor; Send an account access request to the cloud resource management device of the first cloud vendor, wherein the account access request carries the first cloud vendor account and the password of the first cloud vendor account; Receive cloud resource information corresponding to the first cloud vendor's account sent by the cloud resource management device of the first cloud vendor; Associate the first cloud vendor account with the cloud resource management account.

8. A method for processing cloud resources, characterized in that, The method is applied to a terminal, and the method includes: The system displays options for various cloud resource processing types, options for cloud vendors corresponding to at least one cloud vendor account associated with the cloud resource management account logged into the terminal, and options for cloud resources corresponding to the at least one cloud vendor account. In response to the selection operation of options for a first cloud resource processing type, a first cloud vendor, and at least one cloud resource belonging to the first cloud vendor, a first processing request for at least one cloud resource is sent to the server. The first processing request carries first cloud resource indication information, the identifier of the first cloud vendor to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information is used to indicate that the cloud resource to be processed is the at least one cloud resource. If the processing type indicated by the first processing type indication information is resource migration, the first processing request also carries the identifier of the destination cloud vendor for resource migration and migration mode indication information. The first cloud vendor is the source cloud vendor for resource migration. Send an object storage configuration message to the server to instruct the server to send a source object storage OBS bucket application request to the cloud resource management device of the source cloud vendor in order to apply for a source object storage bucket from the source cloud vendor. The first processing request instructs the server, when the migration mode indicated by the migration mode indication information is database migration, to apply to the cloud resource management device of the destination cloud vendor as a first virtual machine as a master node and a second virtual machine as a backup node; through the cloud resource management device of the first cloud vendor, store the data corresponding to the first cloud resource in the source OBS bucket, and through the cloud resource management device of the destination cloud vendor, migrate the data corresponding to the first cloud resource stored in the source OBS bucket to the master node and the backup node; when the migration mode indicated by the migration mode indication information is business migration, through the cloud resource management device of the first cloud vendor, package the at least one cloud resource into a target image and store it in the source OBS bucket; apply to the cloud resource management device of the destination cloud vendor, and through the cloud resource management device of the destination cloud vendor, obtain the target image stored in the OBS bucket, and perform data recovery on the target image in the third virtual machine.

9. The method according to claim 8, characterized in that, The first processing type is resource migration, and the method further includes: Detect the selection of the target cloud provider for resource migration; The first processing request also carries the identifier of the destination cloud vendor for resource migration.

10. The method according to any one of claims 8-9, characterized in that, The method further includes: The server receives processing progress indication information for at least one cloud resource, wherein the processing progress indication message is used to indicate the processing progress of each cloud resource among the at least one cloud resource. Displays the processing progress of each of the at least one cloud resources.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: Obtain the price fluctuation threshold of the first cloud resource input by the user; Send a cost management configuration message for the first cloud resource to the server, wherein the cost management configuration message carries the price fluctuation threshold; The server receives a price fluctuation message, wherein the price fluctuation message is sent by the server when the price fluctuation of the pricing of the first cloud resource by the cloud provider to which the first cloud resource belongs reaches the price fluctuation threshold.

12. The method according to any one of claims 8-11, characterized in that, The method further includes: The server receives a migration suggestion message for the second cloud resource, wherein the migration suggestion message carries the pricing of the second cloud resource by the cloud provider currently owning the cloud resource, the minimum pricing, and the identifier of the cloud provider corresponding to the minimum pricing.

13. The method according to any one of claims 8-12, characterized in that, The method further includes: Obtain the first cloud vendor account and the password entered by the user; Send an account access message to the server, wherein the account access message carries the identifier of the first cloud vendor, the account of the first cloud vendor, and the password of the account of the first cloud vendor.

14. A cloud resource processing apparatus, characterized in that, The device includes: The receiving module is configured to receive a first processing request for at least one cloud resource sent by a terminal, wherein the first processing request carries first cloud resource indication information, the identifier of a first cloud vendor to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information indicates that the cloud resource to be processed is the at least one cloud resource. The terminal is logged into a cloud resource management account, and the first cloud vendor is the cloud vendor corresponding to any one of the at least one cloud vendor accounts associated with the cloud resource management account. If the processing type indicated by the first processing type indication information is resource migration, the first processing request also carries the identifier of the destination cloud vendor and migration mode indication information for the resource migration, wherein the first cloud vendor is the source cloud vendor for the resource migration. The module also receives an object storage configuration message sent by the terminal and sends a source object storage (OBS) bucket application request to the cloud resource management device of the source cloud vendor to apply for a source object storage bucket from the source cloud vendor. The processing module is configured to: request a first virtual machine as a primary node and a second virtual machine as a backup node from the cloud resource management device of the destination cloud vendor when the migration mode indicated by the migration mode indication information is database migration; store the data corresponding to the first cloud resource in the source OBS bucket through the cloud resource management device of the first cloud vendor, and migrate the data corresponding to the first cloud resource stored in the source OBS bucket to the primary node and the backup node through the cloud resource management device of the destination cloud vendor; when the migration mode indicated by the migration mode indication information is business migration, package the at least one cloud resource into a target image through the cloud resource management device of the first cloud vendor and store it in the source OBS bucket; request a third virtual machine from the cloud resource management device of the destination cloud vendor, obtain the target image stored in the OBS bucket through the cloud resource management device of the destination cloud vendor, and perform data recovery on the target image in the third virtual machine.

15. A cloud resource processing apparatus, characterized in that, The device is used in a terminal, and the device includes: The display module is used to display options for multiple cloud resource processing types, cloud vendor options corresponding to at least one cloud vendor account associated with the cloud resource management account logged in by the terminal, and cloud resource options corresponding to the at least one cloud vendor account. The sending module is configured to, in response to the selection operations of options for a first cloud resource processing type, a first cloud vendor, and at least one cloud resource belonging to the first cloud vendor, send a first processing request for at least one cloud resource to the server. The first processing request carries first cloud resource indication information, an identifier of the first cloud vendor to which the at least one cloud resource belongs, and first processing type indication information. The first cloud resource indication information indicates that the cloud resource to be processed is the at least one cloud resource. If the processing type indicated by the first processing type indication information is resource migration, the first processing request also carries an identifier of the destination cloud vendor for resource migration and migration mode indication information, where the first cloud vendor is the source cloud vendor for resource migration. The module also sends an object storage configuration message to the server, instructing the server to send a source object storage (OBS) bucket application request to the cloud resource management device of the source cloud vendor, thereby applying for a source object storage bucket from the source cloud vendor. The first processing request instructs the server, when the migration mode indicated by the migration mode indication information is database migration, to apply to the cloud resource management device of the destination cloud vendor as a first virtual machine as a master node and a second virtual machine as a backup node; through the cloud resource management device of the first cloud vendor, store the data corresponding to the first cloud resource in the source OBS bucket, and through the cloud resource management device of the destination cloud vendor, migrate the data corresponding to the first cloud resource stored in the source OBS bucket to the master node and the backup node; when the migration mode indicated by the migration mode indication information is business migration, through the cloud resource management device of the first cloud vendor, package the at least one cloud resource into a target image and store it in the source OBS bucket; apply to the cloud resource management device of the destination cloud vendor, and through the cloud resource management device of the destination cloud vendor, obtain the target image stored in the OBS bucket, and perform data recovery on the target image in the third virtual machine.

16. 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 computing device cluster to perform the cloud resource processing method as described in any one of claims 1-7.

17. A terminal, characterized in that, Including processor and memory; The processor is configured to execute instructions stored in the memory to cause the terminal to perform the cloud resource processing method as described in any one of claims 8-12.

18. A system for processing cloud resources, characterized in that, The system includes the terminal as described in claim 16 and the computer equipment cluster as described in claim 15.

19. A computer program product containing instructions, characterized in that, When the instruction is executed by the computing device cluster, the computing device cluster performs the cloud resource processing method as described in any one of claims 1-7.

20. A computer program product containing instructions, characterized in that, When the instruction is executed by the terminal, the terminal performs the cloud resource processing method as described in any one of claims 8-13.

21. A computer-readable storage medium, characterized in that, It includes computer program instructions, which, when executed by a cluster of computing devices, enable the cluster of computing devices to perform the cloud resource processing method as described in any one of claims 1-7.

22. A computer-readable storage medium, characterized in that, It includes computer program instructions, which, when executed by a terminal, enable the terminal to perform the cloud resource processing method as described in any one of claims 8-13.

Images