Cloud resource receiving and managing method

Abstract

The invention relates to a cloud resource receiving and managing method. The method comprises the following steps: under the condition that target cloud resources need to be managed, determining a target task type and management attribute information of a target management task for the target cloud resources; wherein the target task type is an incremental nano-management task or a total nano-management task; if a candidate nano-management task identical to the management attribute information exists in nano-management tasks in a nano-management processing stage in the cloud management system, determining a task execution strategy of the target nano-management task according to a target task type of the target nano-management task and a candidate task type of the candidate nano-management task; and according to the task execution strategy and the management attribute information of the target management task, performing management on the target cloud resource. By adopting the method, the cloud resources can be efficiently managed.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for managing cloud resources. Background Technology

[0002] With the rapid development of cloud computing technology, more and more application systems are moving to the cloud, and the number of cloud resources being used is constantly increasing. As a result, cloud computing management systems (hereinafter referred to as "cloud management systems") have emerged. Through unified monitoring and dynamic scheduling, they can integrate heterogeneous resources from different service providers to provide users with more efficient and faster services.

[0003] When new service providers' heterogeneous resources need to be integrated into the cloud management system, the cloud management system needs to retrieve the resource details from the lower-level cloud infrastructure and synchronize them back to its own database. This operation is called reverse management. After synchronizing the resources of this cloud infrastructure, there may be scenarios where platform administrators bypass the upper-level cloud management system and directly create cloud resources through the API interface provided by the lower-level cloud infrastructure, resulting in inconsistencies between the upper and lower layers of data. Therefore, how to correctly and efficiently manage these resources into the cloud management system has become an urgent problem for the cloud management system to solve. Summary of the Invention

[0004] Therefore, it is necessary to provide a cloud resource management method that can efficiently manage cloud resources, addressing the aforementioned technical issues.

[0005] Firstly, this application provides a cloud resource management method, applied to a cloud management system, comprising:

[0006] When it is necessary to manage a target cloud resource, determine the target task type and management attribute information for the target management task of the target cloud resource; wherein, the target task type is an incremental management task or a full management task.

[0007] If there is a candidate task with the same management attribute information among the tasks in the management process of the cloud management system, then the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0008] Based on the task execution strategy and the management attribute information of the target managed task, the target cloud resource is managed.

[0009] In one embodiment, when the target task type is a full-scale managed task, the task execution strategy for the target managed task is determined based on the target task type of the target managed task and the candidate task types of the candidate managed tasks, including:

[0010] When all candidate tasks for inclusion in the management system are incremental management tasks, or when the candidate task types for inclusion in the management system include full management tasks and incremental management tasks, the task execution strategy for the target management task is determined based on the management processing stage in which the candidate management task is located; wherein, the management processing stage includes a pre-management stage, a management supplementation stage, and a management confirmation stage.

[0011] When all candidate managed tasks are full managed tasks, the task execution strategy for the target managed task is determined based on the execution status of the candidate managed tasks.

[0012] In one embodiment, the task execution strategy for the target managed task is determined based on the management processing stage in which the candidate managed task is located, including:

[0013] If all the candidate management tasks are in the management supplementation stage, then the task execution strategy is determined to be immediate execution.

[0014] If a first managed task exists among the candidate managed tasks, then the task execution strategy is determined to be wait for wake-up execution; wherein, the managed processing stage of the first managed task is not the managed supplement stage.

[0015] In one embodiment, determining the task execution strategy for the target task based on the execution status of the candidate managed tasks includes:

[0016] If all the candidate managed tasks are second managed tasks, then the task execution strategy for the target managed task is determined to be to cancel task execution; wherein, the execution status of the second managed task is in progress.

[0017] If the candidate managed tasks include both the second managed task and the third managed task, the execution of the third managed task is cancelled, and the task execution strategy of the target managed task is determined according to the managed processing stage of the second managed task; wherein, the execution status of the third managed task is not executed.

[0018] In one embodiment, determining the task execution strategy of the target managed task based on the managed processing stage in which the second managed task is located includes:

[0019] If the second management task is in the management processing stage, the task execution strategy of the target management task is determined to be immediate execution.

[0020] If none of the second managed tasks are in the managed supplementation phase, then the task execution strategy for the target managed task is determined to be wait for wake-up execution.

[0021] In one embodiment, when the target task type is an incremental management task, determining the task execution strategy for the target management task based on the target task type of the target management task and the candidate task types of the candidate management tasks includes:

[0022] When all candidate managed tasks are incremental managed tasks, the task execution strategy of the target managed task is determined based on the first resource instance to which the candidate managed task belongs and the target cloud resource instance to which the target managed task belongs.

[0023] When all candidate tasks for inclusion in the management system are full-scale management tasks, the task execution strategy for the target management task is determined based on the execution status and management processing stage of the candidate management tasks; wherein, the management processing stage includes a pre-management stage, a management supplementation stage, and a management confirmation stage.

[0024] When the candidate task types of the candidate managed tasks include full managed tasks and incremental managed tasks, the task execution strategy of the target managed task is determined based on the target cloud resource instance, the first resource instance of the candidate managed task with the candidate task type of incremental managed task, and the execution status and management processing stage of the candidate managed task with the candidate task type of full managed task.

[0025] In one embodiment, determining the task execution strategy of the target managed task based on the first resource instance to which the candidate managed task belongs and the target cloud resource instance to which the target managed task belongs includes:

[0026] The first resource instance to which the candidate managed task belongs is deduplicated to obtain the second resource instance;

[0027] If the second resource instance includes the target cloud resource instance, then the task execution strategy for the target managed task is determined to be wait-to-be-wake-up execution;

[0028] If the target cloud resource instance is not included in the second resource instance, then the task execution strategy for the target managed task is determined to be immediate execution.

[0029] In one embodiment, determining the task execution strategy of the target task based on the execution status and current stage of the candidate managed tasks includes:

[0030] If there is a managed task in the candidate managed task whose execution status is not executed, then the task execution strategy of the target managed task is determined to be waiting to be woken up for execution;

[0031] If there are no managed tasks in the candidate managed tasks that are in an inactive state, then the task execution strategy of the target managed task is determined according to the managed processing stage of the candidate managed tasks.

[0032] In one embodiment, the task execution strategy for the target managed task is determined based on the management processing stage in which the candidate managed task is located, including:

[0033] If the candidate managed task is in the pre-management stage of the management process, then the task execution strategy of the target managed task is determined to be wait for wake-up execution.

[0034] If the candidate managed task is in the management processing stage of management supplementation stage or management confirmation stage, then the task execution strategy of the target managed task is determined according to the target cloud resource instance and the third resource instance to which the candidate managed task belongs.

[0035] In one embodiment, when the candidate management task is in the management processing stage of the management supplementation stage, the third resource instance includes a resource instance that does not need to be supplemented with data, a resource instance that has been supplemented with data, and a resource instance that needs to be supplemented with data.

[0036] Based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs, the task execution strategy for the target managed task is determined, including:

[0037] If the target cloud resource instance is included in the resource instance that does not require supplemented data or the resource instance that has been supplemented with data, then the task execution strategy for the target managed task is determined to be wait for wake-up execution.

[0038] If neither the resource instance requiring supplementary data nor the resource instance with supplementary data includes the target cloud resource instance, but the resource instance to be supplemented with data includes the target cloud resource instance, then the task execution strategy for the target managed task is determined to be immediate execution.

[0039] If the target cloud resource instance is not included in the third resource instance, then the task execution strategy for the target managed task is determined to be immediate execution.

[0040] Secondly, this application also provides a cloud resource management device, configured in a cloud management system, comprising:

[0041] The information determination module is used to determine the target task type and management attribute information of the target cloud resource management task when it is necessary to manage the target cloud resource; wherein, the target task type is an incremental management task or a full management task.

[0042] The strategy determination module is used to determine the task execution strategy of the target managed task based on the target task type of the target managed task and the candidate task type of the candidate managed task if there is a candidate managed task with the same management attribute information among the managed tasks in the managed task stage of the cloud management system.

[0043] The resource management module is used to manage the target cloud resources according to the task execution strategy and the management attribute information of the target managed task.

[0044] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0045] When it is necessary to manage a target cloud resource, determine the target task type and management attribute information for the target management task of the target cloud resource; wherein, the target task type is an incremental management task or a full management task.

[0046] If there is a candidate task with the same management attribute information among the tasks in the management process of the cloud management system, then the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0047] Based on the task execution strategy and the management attribute information of the target managed task, the target cloud resource is managed.

[0048] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0049] When it is necessary to manage a target cloud resource, determine the target task type and management attribute information for the target management task of the target cloud resource; wherein, the target task type is an incremental management task or a full management task.

[0050] If there is a candidate task with the same management attribute information among the tasks in the management process of the cloud management system, then the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0051] Based on the task execution strategy and the management attribute information of the target managed task, the target cloud resource is managed.

[0052] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0053] When it is necessary to manage a target cloud resource, determine the target task type and management attribute information for the target management task of the target cloud resource; wherein, the target task type is an incremental management task or a full management task.

[0054] If there is a candidate task with the same management attribute information among the tasks in the management process of the cloud management system, then the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0055] Based on the task execution strategy and the management attribute information of the target managed task, the target cloud resource is managed.

[0056] The aforementioned cloud resource management method, when requiring the management of a target cloud resource, determines the target task type and management attribute information for the target management task. The target task type is either an incremental management task or a full management task. If, among the management tasks in the cloud management system currently undergoing management processing, there are candidate management tasks with the same management attribute information, the task execution strategy for the target management task is determined based on the target task type and the candidate task types of the candidate management tasks. The target cloud resource is then managed based on the task execution strategy and the management attribute information of the target management task. This solution, based on a dual-dimensional decision-making process using management attribute information and task type, solves the data conflict and resource waste problems caused by the parallel execution of multiple tasks on the same resource in traditional management tasks. Furthermore, it designs differentiated execution rules for different combinations of full and incremental tasks, rather than simply covering or rejecting execution, adapting to diverse management scenarios, avoiding ineffective decisions, and improving task scheduling efficiency. Attached Figure Description

[0057] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0058] Figure 1 This is a flowchart illustrating a cloud resource management method in one embodiment;

[0059] Figure 2This is a flowchart illustrating the task execution strategy for determining a target managed task in one embodiment;

[0060] Figure 3 This is a flowchart illustrating the task execution strategy for determining the target managed task in another embodiment;

[0061] Figure 4 This is a schematic representation of the resource status during the management compensation phase in one embodiment;

[0062] Figure 5 This is a structural block diagram of a cloud resource management device in one embodiment;

[0063] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0065] The cloud resource management method provided in this application can be applied to application environments that manage cloud resources. The cloud resource management method provided in this application can be executed by a cloud management system.

[0066] In one exemplary embodiment, such as Figure 1 As shown, a method for cloud resource management is provided. Taking the application of this method to a cloud management system as an example, the specific steps include:

[0067] S101, when it is necessary to manage the target cloud resources, determine the target task type and management attribute information of the target management task for the target cloud resources.

[0068] The target task type is either an incremental or full-scale management task. The target cloud resource is the cloud resource to be included in the cloud management system for unified monitoring, scheduling, and operation and maintenance, such as virtual machines, containers, storage instances, and network devices. Management is the process of connecting dispersed cloud resources to the cloud management system to achieve unified control over resource information collection, status monitoring, and lifecycle management. The target management task is a specific task instance created for the target cloud resource to perform the management operation. The target task type is the execution scope type of the management task; the management attribute information is a set of core attributes used to uniquely identify the management scope of the management task.

[0069] In this embodiment, the management attribute information for a full-scale management task includes service type and cloud infrastructure, while the management attribute information for an incremental management task includes service type, cloud infrastructure, and resource identifier. The resource identifier is a unique identifier for the underlying resource, and an incremental management task can customize the management attribute information for these cloud resources.

[0070] The pre-management phase is responsible for retrieving data from the cloud infrastructure for cloud resources in full and incremental management tasks, comparing it with the cloud resource data already stored in the cloud management system, and generating comparison results. During this phase, the status of each resource instance will change along with the overall management task status, indicating success or failure. The management supplementation phase is responsible for data compensation processing for cloud resources with missing management attribute data. Administrators can supplement the management attribute information of cloud resources during this phase. If the management attributes of cloud resources have already been defined at the management entry point, this phase is skipped. Specific resource instances in this phase can be canceled individually; canceled resource instances will not proceed to the next process. The management confirmation phase is responsible for adjusting the data obtained from the comparison results in the pre-management phase. In this process, each cloud management resource provider writes data to the database for any discrepancies in the cloud resources. Each resource instance in this phase executes in parallel, and its status changes to success or failure based on the specific execution results.

[0071] Optionally, when a new service provider's heterogeneous resources (i.e., target cloud resources) need to be integrated by the cloud management system, the cloud management system initiates a management task based on the target cloud resources. The cloud management system collects basic information about the target cloud resources (resource identifier, resource type, tenant, region, etc.) and determines the target task type based on business needs (e.g., initial management / updated management). For example, if the target cloud resource is being managed for the first time, the target task type is a full management task; if there is an update to the existing management record for the target cloud resource, the target task type is an incremental management task. Furthermore, management attribute information is generated based on the target cloud resource information.

[0072] S102, If there are candidate management tasks with the same management attribute information among the management tasks in the management process of the cloud management system, then the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0073] Among them, candidate managed tasks are existing managed tasks in the cloud management system that are in the management processing stage and whose management attribute information is completely consistent with the target managed task. The task execution strategy is the execution rule for the target managed task, such as direct execution, termination execution, and waiting for wake-up execution. The management processing stage is one of the life states of the managed task, including the pre-management stage, the management supplementation stage, and the management confirmation stage.

[0074] Optionally, the cloud management system can call the task status query interface to filter out managed tasks that are in the management processing stage and whose management attribute information completely matches the target managed task, as candidate managed tasks. It should be noted that the filtering results include four scenarios: Scenario 1: No candidate managed tasks, i.e., no full-scale managed tasks or incremental managed tasks are in the management processing stage; Scenario 2: All candidate managed tasks are incremental managed tasks, i.e., no full-scale managed tasks but incremental managed tasks are in the management processing stage; Scenario 3: All candidate managed tasks are full-scale managed tasks, i.e., there are full-scale managed tasks but no incremental managed tasks are in the management processing stage; Scenario 4: The candidate managed tasks include both full-scale and incremental managed tasks, i.e., both full-scale and incremental managed tasks are in the management processing stage.

[0075] In scenario one, if the query returns empty (meaning no candidate tasks exist), then the target task has no task conflicts and can be directly allowed to enter the pre-management stage. For the other three scenarios, the task execution strategy for the target task can be determined based on its target task type and the candidate task types of the candidate tasks.

[0076] For example, if both the target task type and the candidate task type are full-data management tasks, all candidate tasks can be terminated, and the target full-data management task can be executed to avoid duplicate full-data collection. The target task has higher priority, ensuring the latest collected data. If both the target task type and the candidate task type are incremental tasks, all incremental candidate tasks can be terminated, and the target full-data management task can be executed. Full-data collection covers the scope of incremental collection, eliminating the need to retain incremental tasks and prioritizing data integrity. If both the target task type and the candidate task type are incremental tasks, the target incremental task can be executed automatically after the candidate full-data management tasks are completed. This is because full-data collection is the foundation, while incremental collection must be based on the latest full-data, avoiding data omissions or conflicts. If both the target task type and the candidate task type are incremental tasks, all candidate incremental tasks and the target incremental task can be merged and executed in chronological order (or the latest instruction can be retrieved). This avoids duplicate incremental collection, and merging reduces resource consumption and improves execution efficiency.

[0077] S103, manages the target cloud resources according to the task execution strategy and the management attribute information of the target managed task.

[0078] Optionally, if the task execution strategy is immediate execution, the task scheduling module is invoked to create the target managed task, allocate execution resources, and enter the managed processing stage. If the task execution strategy is wait for wake-up execution, the target managed task can be sent to the queuing stage to wait for a wake-up command before execution. If the task execution strategy is cancel task execution, the target managed task can be directly deleted.

[0079] In the aforementioned cloud resource management method, when it is necessary to manage a target cloud resource, the target task type and management attribute information of the target management task for the target cloud resource are determined. The target task type is either an incremental management task or a full management task. If there are candidate management tasks with the same management attribute information among the management tasks in the management process of the cloud management system, the task execution strategy for the target management task is determined based on the target task type of the target management task and the candidate task types of the candidate management tasks. Based on the task execution strategy and the management attribute information of the target management task, the target cloud resource is managed. This solution, based on a dual-dimensional decision-making process using management attribute information and task type, solves the data conflict and resource waste problems caused by the parallel execution of multiple tasks with the same resource in traditional management tasks. Furthermore, it designs differentiated execution rules for different combinations of full and incremental tasks, rather than simply covering or rejecting execution, adapting to diverse management scenarios, avoiding ineffective decisions, and improving task scheduling efficiency.

[0080] Optionally, in the case where the target task type is a full-scale managed task, in one embodiment, such as Figure 2 As shown, a method for determining the task execution strategy for a target managed task is provided, which specifically includes the following steps:

[0081] S201, when all candidate tasks for the candidate management tasks are incremental management tasks, or when the candidate task types for the candidate management tasks include both full management tasks and incremental management tasks, determine the task execution strategy for the target management task based on the management processing stage of the candidate management tasks.

[0082] The process of inclusion in the management system includes the pre-inclusion stage, the supplementary inclusion stage, and the confirmation inclusion stage.

[0083] Optionally, if all candidate tasks are incremental tasks (i.e., Case 2 above), all candidate tasks can be traversed, and the management stage of each candidate task can be recorded; the number of candidate tasks can be counted by stage.

[0084] For example, if there is at least one candidate inclusion task in the confirmation and inclusion phase, and the data verification in the confirmation phase is nearing completion to avoid repeated data collection after termination, the target inclusion task can be executed immediately after all candidate incremental tasks have been completed. If only candidate inclusion tasks in the pre-inclusion phase exist, all candidate incremental tasks can be terminated directly, and the full target task can be executed immediately. If only candidate inclusion tasks in the inclusion supplement phase exist, all candidate incremental tasks can be terminated directly, and the full target task can be executed immediately. If a mixture of candidate inclusion tasks in the pre-inclusion and supplement phases exists, all candidate incremental tasks can be terminated directly, and the full target task can be executed immediately.

[0085] S202, when all candidate tasks for inclusion are full-scale inclusion tasks, determine the task execution strategy for the target inclusion task based on the execution status of the candidate tasks.

[0086] Optionally, when all candidate managed tasks are full managed tasks, the execution strategy for the target managed task can be determined based on the execution status of the candidate managed tasks. For example, if at least one candidate managed task is executing, all candidate full managed tasks can be terminated, and the full target task can be executed immediately. If only candidate managed tasks are pending execution, all candidate managed tasks and the target managed task can be merged to generate a new full managed task, and resources can be allocated to execute the new task first. If only candidate managed tasks are paused, all paused candidate managed tasks can be terminated, and the full target managed task can be executed immediately. If a mix of pending and paused candidate tasks exist, all candidate managed tasks can be terminated, and the full target task can be executed immediately.

[0087] In this embodiment, differentiated strategies are designed based on the management and processing stage and execution status for different candidate task combination scenarios, so as to solve the problems of resource waste and data conflict caused by the traditional solution of executing all tasks in one go.

[0088] Optionally, when all candidate tasks for inclusion are incremental tasks, or when the candidate tasks for inclusion include both full and incremental tasks, the task execution strategy for the target task can be determined in the following ways depending on the specific circumstances.

[0089] Optionally, if all candidate managed tasks are in the managed supplementation stage, the task execution strategy is determined to be immediate execution. If a first managed task exists among the candidate managed tasks, the task execution strategy is determined to be waiting for wake-up execution; wherein, the managed processing stage of the first managed task is not the managed supplementation stage. Specifically, it is determined whether all candidate managed tasks are in the managed supplementation stage. If so, since this stage is a human intervention stage, there is a possibility of human-induced lag. Newly initiated full tasks will also undergo the same data supplementation operation, so the above incremental tasks can be canceled, and the target managed task can be set to allow, i.e., immediate execution. If not, the target managed task is set to wait, i.e., waiting for wake-up execution. Differentiated strategies are designed for the managed supplementation stage and non-managed supplementation stage of incremental candidate tasks, solving the problem of unreasonable strategies caused by traditional solutions that only make decisions based on task type and ignore the stage. Without manual intervention, the system automatically monitors the status of the first managed task and triggers the start of the target task, realizing the coordinated execution of full tasks and incremental tasks and improving the level of automation.

[0090] Optionally, if all candidate managed tasks are full managed tasks, the task execution strategy for the target managed task can be determined in the following ways depending on the specific circumstances.

[0091] Optionally, if all candidate managed tasks are second managed tasks, the execution strategy for the target managed task is to cancel task execution; the execution status of the second managed task is "in execution". If there are second and third managed tasks among the candidate managed tasks, the execution of the third managed task is canceled, and the execution strategy for the target managed task is determined according to the management processing stage of the second managed task; the execution status of the third managed task is "not executed". Specifically, it is determined whether there are any full managed tasks of the same type being executed within a specified time. If so, there is no need for multiple full managed tasks to be initiated in a short period of time, so the execution of the target managed task can be canceled; if not, the third managed task is first set to cancel, and then it is determined whether the second managed task is in the management compensation stage. If the management processing stage of the second managed task is the management supplement stage, the execution strategy for the target managed task is to execute immediately; if none of the second managed tasks are in the management supplement stage, the execution strategy for the target managed task is to wait for wake-up execution. That is, if it is in the state, the second managed task is canceled and the target managed task is allowed; if it is not in the state, the target managed task is put into the waiting state.

[0092] Optionally, in the case where the target task type is an incremental management task, in one embodiment, such as Figure 3 As shown, a method for determining the task execution strategy for a target managed task is provided, which specifically includes the following steps:

[0093] S301, when all candidate managed tasks are incremental managed tasks, determine the task execution strategy of the target managed task based on the first resource instance to which the candidate managed task belongs and the target cloud resource instance to which the target managed task belongs.

[0094] Here, a resource instance is a specific instance of a cloud resource (such as a single virtual machine, a single container, or a single storage volume), and each resource instance has a unique identifier. The target cloud resource instance is an instance of the target managed resource corresponding to the target managed task; the first resource instance is an instance of the resource corresponding to the candidate managed task.

[0095] For example, if all candidate management tasks are incremental management tasks, and the target cloud resource instance is exactly the same as the first resource instance, the collection instructions of the target management task and all candidate management tasks (sorted by creation time) can be merged, and the merged task can be executed sequentially to collect all new / changed data. If the target cloud resource instance is not exactly the same as the first resource instance, there is no need to process the candidate management tasks; the target management task can be started directly to collect the new / changed data of the target cloud resource instance.

[0096] S302, when all candidate tasks for inclusion in the management system are full-scale management tasks, determine the task execution strategy for the target management task based on the execution status and management process stage of the candidate tasks.

[0097] The process of inclusion in the management system includes the pre-inclusion stage, the supplementary inclusion stage, and the confirmation inclusion stage.

[0098] For example, if all candidate management tasks are full management tasks, and the execution status of a candidate management task is "in progress," and it is in the management processing stage of supplementation or confirmation, then the target management task can be started after all full candidate management tasks have completed execution, and new / changed content can be collected based on the full data. If the execution status of a candidate management task is "pending execution" or "suspended execution," and it is in the management processing stage of pre-management, then there is no need to wait for all candidate management tasks; the target management task can be started directly, and new / changed data can be collected based on historical full records.

[0099] S303, when the candidate task types of the candidate managed tasks include full managed tasks and incremental managed tasks, determine the task execution strategy of the target managed task based on the target cloud resource instance, the first resource instance of the candidate managed task with the candidate task type of incremental managed task, and the execution status and management processing stage of the candidate managed task with the candidate task type of full managed task.

[0100] For example, when the candidate task types for the candidate managed tasks include full managed tasks and incremental managed tasks, it is determined whether there are any full candidate managed tasks that are not yet executed. If so, adhering to the principle of full priority, the target managed task is set to wait. Then, according to S301, it is determined whether the target managed task should be released if there are no full tasks, and then according to S302, it is determined whether the target managed task should be released if there are no incremental tasks. Only when both of the above situations are released will the target managed task be released; otherwise, it is set to wait.

[0101] In this embodiment, strategies are designed for three types of candidate task combinations based on resource instance consistency, execution status, management stage, and hybrid dimensions to solve the conflict or inefficiency problems caused by the single strategy of traditional incremental tasks.

[0102] Optionally, when all candidate managed tasks are incremental managed tasks, the task execution strategy for the target managed task can be determined in the following ways depending on the specific circumstances.

[0103] Optionally, the first resource instance to which the candidate managed task belongs is deduplicated to obtain the second resource instance. If the second resource instance includes the target cloud resource instance, the task execution strategy for the target managed task is determined to be wait-to-be-wake-up execution; if the second resource instance does not include the target cloud resource instance, the task execution strategy for the target managed task is determined to be immediate execution. Specifically, all first resource instances in the management process are deduplicated and aggregated. Since an incremental task may contain multiple resource instances, resource instances that have ended or been canceled in the planned execution phase need to be filtered before aggregation. If all resource instances of the target managed task (i.e., the target cloud resource instance) do not belong to the aggregated set of resource instances (i.e., the second resource instance), the task is allowed; otherwise, if there is a management conflict with the same resource, the target task is set to wait.

[0104] Optionally, if all candidate managed tasks are full managed tasks, the task execution strategy for the target managed task can be determined in the following ways depending on the specific circumstances.

[0105] Optionally, if there are any managed tasks in the candidate managed tasks that are not yet executed, then the task execution strategy for the target managed task is determined to be waiting for wake-up. In other words, if there are any managed tasks in the candidate managed tasks that are not yet executed, then following the principle of prioritizing all tasks, the target managed task is set to wait.

[0106] If none of the candidate managed tasks are in an inactive state, the execution strategy for the target managed task is determined based on the stage of the candidate managed tasks' management process. It should be noted that even when none of the candidate managed tasks are in an inactive state, different execution strategies need to be determined based on the stage of the candidate managed tasks' management process. Optionally, if the candidate managed task is in the pre-management stage, the execution strategy for the target managed task is determined to be "wait to be woken up and executed." The pre-management phase is divided into resource retrieval and resource comparison. Specifically, if all candidate management tasks are in the pre-management phase, during resource retrieval, it's impossible to perceive all resource instances across all tasks, making it impossible to identify conflicting resource instances. Therefore, the target management task is placed on hold. During resource comparison, all resource instances across all tasks have been obtained. If resource instances without conflicts are allowed in incremental tasks, it could lead to a chaotic comparison across all tasks. For example, if resource 'a' in an incremental task is allowed and correctly managed and created in the subsequent process (without going through the underlying layer), but the comparison across all tasks is not yet complete, and the retrieved resource instances do not contain resource 'a', then resource 'a' in the cloud management system would be considered invalid and needs to be managed and deleted, resulting in a comparison error and confusion. Therefore, the target management task is placed on hold. In other words, if all candidate management tasks are in the pre-management phase, the target management task is placed on hold.

[0107] If the candidate managed tasks are in the managed supplementation stage or the managed confirmation stage, then the task execution strategy for the target managed task is determined based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs. Optionally, if all candidate managed tasks are in the managed supplementation stage, such as... Figure 4 The diagram illustrates the resource status representation during the management compensation phase. Resources include those requiring no data replenishment, those awaiting replenishment, those already replenished, cancelled resources, and resources not requiring management. It's important to note that cancelled and unmanaged resources will not continue execution. Therefore, the third resource instance includes resource instances requiring no data replenishment, resource instances already replenished, and resource instances awaiting replenishment. If the resource instance requiring no data replenishment or the resource instance already replenished includes the target cloud resource instance, the task execution strategy for the target management task is determined to be "wait for wake-up execution." If neither the resource instance requiring no data replenishment nor the resource instance already replenished includes the target cloud resource instance, but the resource instance awaiting replenishment includes the target cloud resource instance, the task execution strategy for the target management task is determined to be "execute immediately." If the third resource instance does not include the target cloud resource instance, the task execution strategy for the target management task is determined to be "execute immediately."

[0108] In other words, there are three scenarios based on resource conflict: Scenario 1: The resource instance that does not need data supplementation or the resource instance that has already had data supplementation includes the target cloud resource instance; Scenario 2: Neither the resource instance that does not need data supplementation nor the resource instance that has already had data supplementation includes the target cloud resource instance, and the resource instance to be supplemented includes the target cloud resource instance; Scenario 3: The third resource instance does not include the target cloud resource instance. It should be noted that for Scenario 2, since the state transition to supplementing data resources requires manual control and may result in prolonged delays, if a conflict occurs, the conflicting resources in the state to be supplemented will be canceled, allowing the target management task to proceed. For Scenario 3, it is assumed that there is no conflict between the target management task and the candidate management tasks, allowing the target management task to proceed.

[0109] Optionally, if the candidate management task is in the management processing stage of confirming management, the task execution strategy of the target management task can be determined in the following ways depending on the situation.

[0110] If the third resource instance does not include the target cloud resource instance, the task execution strategy for the target managed task is determined to be no queuing; if the third resource instance includes the target cloud resource instance, the task execution strategy for the target managed task is determined to be queuing.

[0111] It should be noted that, in this application embodiment, a waiting wake-up strategy and a cancellation strategy are also provided, and the specific scenarios are described below. Scenario 1: When a managed task finishes the pre-management stage and enters the management supplementation stage, and the waiting task contains a full set of tasks of the same type: Due to the full task priority processing mechanism, no tasks are woken up. At the same time, all resources in the managed task that do not need to be managed are identified and compared with the resources contained in all incremental tasks of the same type created earlier than this managed task. If there are duplicate resources, it means that the resources contained in this part of the incremental task have already been implemented by this managed task and do not need to be implemented again. The resources marked with duplicate resources are set to cancel, and the reason is set: "Managed task xxx (xxx is the task identifier of the managed task) has been managed for this cloud resource and does not need to be executed again". It is also checked whether all cloud resources of the waiting incremental task are set to cancel. If so, the incremental task is set to cancel; otherwise, the waiting continues.

[0112] Scenario 2: When a managed task finishes the pre-management phase and enters the management supplementation phase, and the waiting task does not contain any full tasks of the same type: Identify all resources that do not need to be managed for this managed task and compare them with the resources contained in all incremental tasks of the same type created earlier than this managed task. If duplicate resources are found, mark the cloud resources marked as duplicates as canceled. Then, identify all cloud resource instances of the same type currently in the resource retrieval phase and subsequent full incremental tasks (excluding resources that do not need to be managed). Compare these executing cloud resources with incremental tasks of the same type in the queue that do not contain canceled cloud resources. Extract the incremental tasks that do not overlap, arrange them in order of creation time from front to back to form a queue, and generate a temporarily empty set of executed cloud resources. Iterate through this queue sequentially. If the managed task being iterated over does not overlap with the generated cloud resource set, mark this managed task as ready and add all resource instances of the ready managed task (excluding those in the canceled state) to the cloud resource set. Otherwise, mark this managed task as waiting until the queue traversal is complete.

[0113] Scenario 3: When a managed task successfully or fails to manage resources during the confirmation phase, and the waiting task contains a full set of tasks of the same type: Due to the priority processing mechanism for full tasks, no tasks are awakened, and waiting tasks are not canceled. Simultaneously, the resource that has completed this process is compared with the resources contained in all incremental tasks of the same type created earlier than this managed task. If duplicates are found, the reason is the same as in Scenario 1: the cloud resource with the duplicate resource identifier is marked as canceled, and the reason is set to "Managed task xxx (xxx is the task identifier of the managed task) has already managed this cloud resource, no need to execute it again." It is also checked whether all cloud resources of any incremental task have been marked as canceled. If so, that incremental task is canceled; otherwise, it continues to queue.

[0114] Scenario 4: When a full-scale management task successfully or fails to manage resources during the confirmation phase, and the waiting task does not contain any full-scale tasks of the same type: Compare the completed resource with the resources contained in all incremental tasks of the same type created earlier than this full-scale task. If there are duplicates, mark the cloud resource with the duplicate resource identifier as canceled, and set the reason "Managed task xxx (xxx is the task identifier of the managed task) has already managed this cloud resource, no need to execute it again". Check if all cloud resources of any incremental task are marked as canceled. If so, mark this incremental task as canceled; otherwise, continue waiting. Similar to Scenario 2, identify queued tasks that do not have overlapping cloud resources between executing tasks and queued tasks, form a queue, and traverse the queue to make the executable managed tasks ready.

[0115] Scenario 5: When the management task is completed and the management phase is confirmed (all cloud resources of the management task have been managed), if the waiting task contains full tasks of the same type: the latest full task of the same type is set from the waiting state to the ready state, and other full tasks of the same type are set to canceled. Due to the full task priority processing mechanism, no incremental tasks of the same type will be woken up.

[0116] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0117] Based on the same inventive concept, this application also provides a cloud resource management device for implementing the cloud resource management method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more cloud resource management device embodiments provided below can be found in the limitations of the cloud resource management method described above, and will not be repeated here.

[0118] In one exemplary embodiment, such as Figure 5 As shown, a cloud resource management device 500 is provided, configured in a cloud management system, including: an information determination module 510, a policy determination module 520, and a resource management module 530, wherein:

[0119] The information determination module 510 is used to determine the target task type and management attribute information of the target cloud resource management task when the target cloud resource needs to be managed; wherein the target task type is an incremental management task or a full management task.

[0120] The strategy determination module 520 is used to determine the task execution strategy of the target managed task based on the target task type of the target managed task and the candidate task type of the candidate managed task if there are candidate managed tasks with the same management attribute information among the managed tasks in the managed task stage of the cloud management system.

[0121] The resource management module 530 is used to manage target cloud resources based on task execution strategies and management attribute information of the target managed tasks.

[0122] In one embodiment, when the target task type is a full-scale management task, the policy determination module 520 includes:

[0123] The first determining unit is used to determine the task execution strategy of the target managed task based on the management processing stage of the candidate managed task when the candidate task types of the candidate managed tasks are all incremental managed tasks, or the candidate task types of the candidate managed tasks include full managed tasks and incremental managed tasks; wherein the management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage.

[0124] The second determining unit is used to determine the task execution strategy of the target managed task based on the execution status of the candidate managed tasks when all candidate managed tasks are full managed tasks.

[0125] In one embodiment, the first determining unit is specifically used for:

[0126] If all candidate managed tasks are in the managed supplementation stage, the task execution strategy is determined to be immediate execution; if there is a first managed task among the candidate managed tasks, the task execution strategy is determined to be waiting to be woken up and executed; wherein, the managed processing stage of the first managed task is not the managed supplementation stage.

[0127] In one embodiment, the second determining unit includes:

[0128] The first determining unit is used to determine the task execution strategy of the target managed task as canceling task execution if all candidate managed tasks are the second managed task; wherein the execution status of the second managed task is in execution.

[0129] The second determining unit is used to cancel the execution of the third managed task if there are a second managed task and a third managed task among the candidate managed tasks, and to determine the task execution strategy of the target managed task according to the managed processing stage of the second managed task; wherein the execution status of the third managed task is not executed.

[0130] In one embodiment, the second determination from the unit is specifically used for:

[0131] If the second managed task is in the managed supplementation stage, the task execution strategy for the target managed task is determined to be immediate execution; if the second managed task is not in the managed supplementation stage, the task execution strategy for the target managed task is determined to be waiting to be woken up for execution.

[0132] In one embodiment, when the target task type is an incremental management task, the policy determination module 520 further includes:

[0133] The third determining unit is used to determine the task execution strategy of the target managed task based on the first resource instance to which the candidate managed task belongs and the target cloud resource instance to which the target managed task belongs, when all candidate managed tasks are incremental managed tasks.

[0134] The fourth determining unit is used to determine the task execution strategy of the target managed task based on the execution status and management processing stage of the candidate managed tasks when all candidate managed tasks are full managed tasks. The management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage.

[0135] The fifth determining unit is used to determine the task execution strategy of the target managed task when the candidate task types of the candidate managed tasks include full managed tasks and incremental managed tasks, based on the target cloud resource instance, the first resource instance of the candidate managed task with the candidate task type of incremental managed task, and the execution status and management processing stage of the candidate managed task with the candidate task type of full managed task.

[0136] In one embodiment, the third determining unit is specifically used for:

[0137] The first resource instance to which the candidate managed task belongs is deduplicated to obtain the second resource instance; if the second resource instance includes the target cloud resource instance, the task execution strategy of the target managed task is determined to be wait for wake-up execution; if the second resource instance does not include the target cloud resource instance, the task execution strategy of the target managed task is determined to be immediate execution.

[0138] In one embodiment, the fourth determining unit includes:

[0139] The third determining unit is used to determine the task execution strategy of the target managed task as waiting to be woken up if there is a managed task with an execution status of not being executed among the candidate managed tasks.

[0140] The fourth determination unit is used to determine the task execution strategy of the target managed task based on the management process stage of the candidate managed task if there is no managed task with an execution status of not being executed among the candidate managed tasks.

[0141] In one embodiment, the fourth determination from the unit includes:

[0142] The first determining subunit is used to determine the task execution strategy of the target managed task as waiting to be woken up if the management processing stage of the candidate managed task is the pre-management stage.

[0143] The second determining subunit is used to determine the task execution strategy of the target managed task based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs if the management processing stage of the candidate managed task is the management supplement stage or the management confirmation stage.

[0144] In one embodiment, the second determining subunit is specifically used for:

[0145] If the target cloud resource instance is included in the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, the task execution strategy for the target managed task is determined to be to wait for wake-up execution; if the target cloud resource instance is not included in either the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, and the target cloud resource instance is included in the resource instance that needs to be supplemented with data, the task execution strategy for the target managed task is determined to be to execute immediately; if the target cloud resource instance is not included in the third resource instance, the task execution strategy for the target managed task is determined to be to execute immediately.

[0146] Each module in the aforementioned cloud resource management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0147] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 6 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and databases. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media to run. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a cloud resource management method.

[0148] Those skilled in the art will understand that Figure 6The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0149] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0150] When it is necessary to manage target cloud resources, determine the target task type and management attribute information for the target management task for the target cloud resources; where the target task type is either an incremental management task or a full management task.

[0151] If there are candidate tasks with the same management attribute information among the tasks in the management process of the cloud management system, the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0152] Based on the task execution strategy and the management attribute information of the target managed task, the target cloud resources are managed.

[0153] In one embodiment, when the target task type is a full-scale managed task, when the processor executes the computer program to determine the task execution strategy for the target managed task based on the target task type and the candidate task types of the candidate managed tasks, the following steps are also implemented:

[0154] When all candidate tasks for inclusion in the management system are incremental tasks, or when the candidate tasks for inclusion in the management system include both full and incremental tasks, the task execution strategy for the target task is determined based on the management processing stage of the candidate tasks. The management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage. When all candidate tasks for inclusion in the management system are full tasks, the task execution strategy for the target task is determined based on the execution status of the candidate tasks.

[0155] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the managed processing stage in which the candidate managed tasks are located, it also performs the following steps:

[0156] If all candidate managed tasks are in the managed supplementation stage, the task execution strategy is determined to be immediate execution; if there is a first managed task among the candidate managed tasks, the task execution strategy is determined to be waiting to be woken up and executed; wherein, the managed processing stage of the first managed task is not the managed supplementation stage.

[0157] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target task based on the execution status of the candidate managed tasks, it also performs the following steps:

[0158] If all candidate managed tasks are second managed tasks, the task execution strategy for the target managed task is to cancel task execution; the execution status of the second managed task is "in execution". If there are second and third managed tasks among the candidate managed tasks, the execution of the third managed task is canceled, and the task execution strategy for the target managed task is determined according to the management stage of the second managed task; the execution status of the third managed task is "not executed".

[0159] In one embodiment, when the processor executes a computer program to determine the task execution strategy of the target managed task based on the managed processing stage in which the second managed task is located, it also performs the following steps:

[0160] If the second managed task is in the managed supplementation stage, the task execution strategy for the target managed task is determined to be immediate execution; if the second managed task is not in the managed supplementation stage, the task execution strategy for the target managed task is determined to be waiting to be woken up for execution.

[0161] In one embodiment, when the target task type is an incremental managed task, when the processor executes the computer program to determine the task execution strategy for the target managed task based on the target task type of the target managed task and the candidate task types of the candidate managed tasks, the following steps are also implemented:

[0162] When all candidate tasks for inclusion in the management system are incremental management tasks, the task execution strategy for the target management task is determined based on the first resource instance to which the candidate management tasks belong and the target cloud resource instance to which the target management task belongs. When all candidate tasks for inclusion in the management system are full management tasks, the task execution strategy for the target management task is determined based on the execution status and management processing stage of the candidate management tasks. The management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage. When the candidate task types for inclusion in the management system include full management tasks and incremental management tasks, the task execution strategy for the target management task is determined based on the target cloud resource instance, the first resource instance of the candidate management task of incremental management, and the execution status and management processing stage of the candidate management task of full management.

[0163] In one embodiment, when the processor executes a computer program to determine the task execution strategy of the target managed task based on the first resource instance to which the candidate managed task belongs and the target cloud resource instance to which the target managed task belongs, it also performs the following steps:

[0164] The first resource instance to which the candidate managed task belongs is deduplicated to obtain the second resource instance; if the second resource instance includes the target cloud resource instance, the task execution strategy of the target managed task is determined to be wait for wake-up execution; if the second resource instance does not include the target cloud resource instance, the task execution strategy of the target managed task is determined to be immediate execution.

[0165] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the execution status and the current stage of the managed task, it also performs the following steps:

[0166] If there are any managed tasks in the candidate managed tasks that are in an execution state of not being executed, then the task execution strategy for the target managed task is determined to be to wait for wake-up and execute; if there are no managed tasks in the candidate managed tasks that are in an execution state of not being executed, then the task execution strategy for the target managed task is determined according to the management process stage of the candidate managed tasks.

[0167] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the managed processing stage in which the candidate managed tasks are located, it also performs the following steps:

[0168] If the candidate managed task is in the pre-management stage, the task execution strategy for the target managed task is determined to be wait for wake-up execution; if the candidate managed task is in the supplementary management stage or the confirmed management stage, the task execution strategy for the target managed task is determined based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs.

[0169] In one embodiment, when the candidate managed task is in the managed supplementation stage, the third resource instance includes resource instances that do not require data supplementation, resource instances that have already had data supplemented, and resource instances that need data supplementation. When the processor executes the computer program to determine the task execution strategy of the target managed task based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs, it also implements the following steps:

[0170] If the target cloud resource instance is included in the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, the task execution strategy for the target managed task is determined to be to wait for wake-up execution; if the target cloud resource instance is not included in either the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, and the target cloud resource instance is included in the resource instance that needs to be supplemented with data, the task execution strategy for the target managed task is determined to be to execute immediately; if the target cloud resource instance is not included in the third resource instance, the task execution strategy for the target managed task is determined to be to execute immediately.

[0171] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0172] When it is necessary to manage target cloud resources, determine the target task type and management attribute information for the target management task for the target cloud resources; where the target task type is either an incremental management task or a full management task.

[0173] If there are candidate tasks with the same management attribute information among the tasks in the management process of the cloud management system, the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0174] Based on the task execution strategy and the management attribute information of the target managed task, the target cloud resources are managed.

[0175] In one embodiment, when the target task type is a full-scale managed task, when the processor executes the computer program to determine the task execution strategy for the target managed task based on the target task type and the candidate task types of the candidate managed tasks, the following steps are also implemented:

[0176] When all candidate tasks for inclusion in the management system are incremental tasks, or when the candidate tasks for inclusion in the management system include both full and incremental tasks, the task execution strategy for the target task is determined based on the management processing stage of the candidate tasks. The management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage. When all candidate tasks for inclusion in the management system are full tasks, the task execution strategy for the target task is determined based on the execution status of the candidate tasks.

[0177] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the managed processing stage in which the candidate managed tasks are located, it also performs the following steps:

[0178] If all candidate managed tasks are in the managed supplementation stage, the task execution strategy is determined to be immediate execution; if there is a first managed task among the candidate managed tasks, the task execution strategy is determined to be waiting to be woken up and executed; wherein, the managed processing stage of the first managed task is not the managed supplementation stage.

[0179] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target task based on the execution status of the candidate managed tasks, it also performs the following steps:

[0180] If all candidate managed tasks are second managed tasks, the task execution strategy for the target managed task is to cancel task execution; the execution status of the second managed task is "in execution". If there are second and third managed tasks among the candidate managed tasks, the execution of the third managed task is canceled, and the task execution strategy for the target managed task is determined according to the management stage of the second managed task; the execution status of the third managed task is "not executed".

[0181] In one embodiment, when the processor executes a computer program to determine the task execution strategy of the target managed task based on the managed processing stage in which the second managed task is located, it also performs the following steps:

[0182] If the second managed task is in the managed supplementation stage, the task execution strategy for the target managed task is determined to be immediate execution; if the second managed task is not in the managed supplementation stage, the task execution strategy for the target managed task is determined to be waiting to be woken up for execution.

[0183] In one embodiment, when the target task type is an incremental managed task, when the processor executes the computer program to determine the task execution strategy for the target managed task based on the target task type of the target managed task and the candidate task types of the candidate managed tasks, the following steps are also implemented:

[0184] When all candidate tasks for inclusion in the management system are incremental management tasks, the task execution strategy for the target management task is determined based on the first resource instance to which the candidate management tasks belong and the target cloud resource instance to which the target management task belongs. When all candidate tasks for inclusion in the management system are full management tasks, the task execution strategy for the target management task is determined based on the execution status and management processing stage of the candidate management tasks. The management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage. When the candidate task types for inclusion in the management system include full management tasks and incremental management tasks, the task execution strategy for the target management task is determined based on the target cloud resource instance, the first resource instance of the candidate management task of incremental management, and the execution status and management processing stage of the candidate management task of full management.

[0185] In one embodiment, when the processor executes a computer program to determine the task execution strategy of the target managed task based on the first resource instance to which the candidate managed task belongs and the target cloud resource instance to which the target managed task belongs, it also performs the following steps:

[0186] The first resource instance to which the candidate managed task belongs is deduplicated to obtain the second resource instance; if the second resource instance includes the target cloud resource instance, the task execution strategy of the target managed task is determined to be wait for wake-up execution; if the second resource instance does not include the target cloud resource instance, the task execution strategy of the target managed task is determined to be immediate execution.

[0187] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the execution status and the current stage of the managed task, it also performs the following steps:

[0188] If there are any managed tasks in the candidate managed tasks that are in an execution state of not being executed, then the task execution strategy for the target managed task is determined to be to wait for wake-up and execute; if there are no managed tasks in the candidate managed tasks that are in an execution state of not being executed, then the task execution strategy for the target managed task is determined according to the management process stage of the candidate managed tasks.

[0189] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the managed processing stage in which the candidate managed tasks are located, it also performs the following steps:

[0190] If the candidate managed task is in the pre-management stage, the task execution strategy for the target managed task is determined to be wait for wake-up execution; if the candidate managed task is in the supplementary management stage or the confirmed management stage, the task execution strategy for the target managed task is determined based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs.

[0191] In one embodiment, when the candidate managed task is in the managed supplementation stage, the third resource instance includes resource instances that do not require data supplementation, resource instances that have already had data supplemented, and resource instances that need data supplementation. When the processor executes the computer program to determine the task execution strategy of the target managed task based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs, it also implements the following steps:

[0192] If the target cloud resource instance is included in the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, the task execution strategy for the target managed task is determined to be to wait for wake-up execution; if the target cloud resource instance is not included in either the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, and the target cloud resource instance is included in the resource instance that needs to be supplemented with data, the task execution strategy for the target managed task is determined to be to execute immediately; if the target cloud resource instance is not included in the third resource instance, the task execution strategy for the target managed task is determined to be to execute immediately.

[0193] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0194] When it is necessary to manage target cloud resources, determine the target task type and management attribute information for the target management task for the target cloud resources; where the target task type is either an incremental management task or a full management task.

[0195] If there are candidate tasks with the same management attribute information among the tasks in the management process of the cloud management system, the task execution strategy of the target management task is determined according to the target task type of the target management task and the candidate task type of the candidate management task.

[0196] Based on the task execution strategy and the management attribute information of the target managed task, the target cloud resources are managed.

[0197] In one embodiment, when the target task type is a full-scale managed task, when the processor executes the computer program to determine the task execution strategy for the target managed task based on the target task type and the candidate task types of the candidate managed tasks, the following steps are also implemented:

[0198] When all candidate tasks for inclusion in the management system are incremental tasks, or when the candidate tasks for inclusion in the management system include both full and incremental tasks, the task execution strategy for the target task is determined based on the management processing stage of the candidate tasks. The management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage. When all candidate tasks for inclusion in the management system are full tasks, the task execution strategy for the target task is determined based on the execution status of the candidate tasks.

[0199] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the managed processing stage in which the candidate managed tasks are located, it also performs the following steps:

[0200] If all candidate managed tasks are in the managed supplementation stage, the task execution strategy is determined to be immediate execution; if there is a first managed task among the candidate managed tasks, the task execution strategy is determined to be waiting to be woken up and executed; wherein, the managed processing stage of the first managed task is not the managed supplementation stage.

[0201] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target task based on the execution status of the candidate managed tasks, it also performs the following steps:

[0202] If all candidate managed tasks are second managed tasks, the task execution strategy for the target managed task is to cancel task execution; the execution status of the second managed task is "in execution". If there are second and third managed tasks among the candidate managed tasks, the execution of the third managed task is canceled, and the task execution strategy for the target managed task is determined according to the management stage of the second managed task; the execution status of the third managed task is "not executed".

[0203] In one embodiment, when the processor executes a computer program to determine the task execution strategy of the target managed task based on the managed processing stage in which the second managed task is located, it also performs the following steps:

[0204] If the second managed task is in the managed supplementation stage, the task execution strategy for the target managed task is determined to be immediate execution; if the second managed task is not in the managed supplementation stage, the task execution strategy for the target managed task is determined to be waiting to be woken up for execution.

[0205] In one embodiment, when the target task type is an incremental managed task, when the processor executes the computer program to determine the task execution strategy for the target managed task based on the target task type of the target managed task and the candidate task types of the candidate managed tasks, the following steps are also implemented:

[0206] When all candidate tasks for inclusion in the management system are incremental management tasks, the task execution strategy for the target management task is determined based on the first resource instance to which the candidate management tasks belong and the target cloud resource instance to which the target management task belongs. When all candidate tasks for inclusion in the management system are full management tasks, the task execution strategy for the target management task is determined based on the execution status and management processing stage of the candidate management tasks. The management processing stage includes the pre-management stage, the management supplementation stage, and the management confirmation stage. When the candidate task types for inclusion in the management system include full management tasks and incremental management tasks, the task execution strategy for the target management task is determined based on the target cloud resource instance, the first resource instance of the candidate management task of incremental management, and the execution status and management processing stage of the candidate management task of full management.

[0207] In one embodiment, when the processor executes a computer program to determine the task execution strategy of the target managed task based on the first resource instance to which the candidate managed task belongs and the target cloud resource instance to which the target managed task belongs, it also performs the following steps:

[0208] The first resource instance to which the candidate managed task belongs is deduplicated to obtain the second resource instance; if the second resource instance includes the target cloud resource instance, the task execution strategy of the target managed task is determined to be wait for wake-up execution; if the second resource instance does not include the target cloud resource instance, the task execution strategy of the target managed task is determined to be immediate execution.

[0209] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the execution status and the current stage of the managed task, it also performs the following steps:

[0210] If there are any managed tasks in the candidate managed tasks that are in an execution state of not being executed, then the task execution strategy for the target managed task is determined to be to wait for wake-up and execute; if there are no managed tasks in the candidate managed tasks that are in an execution state of not being executed, then the task execution strategy for the target managed task is determined according to the management process stage of the candidate managed tasks.

[0211] In one embodiment, when the processor executes a computer program to determine the task execution strategy for the target managed task based on the managed processing stage in which the candidate managed tasks are located, it also performs the following steps:

[0212] If the candidate managed task is in the pre-management stage, the task execution strategy for the target managed task is determined to be wait for wake-up execution; if the candidate managed task is in the supplementary management stage or the confirmed management stage, the task execution strategy for the target managed task is determined based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs.

[0213] In one embodiment, when the candidate managed task is in the managed supplementation stage, the third resource instance includes resource instances that do not require data supplementation, resource instances that have already had data supplemented, and resource instances that need data supplementation. When the processor executes the computer program to determine the task execution strategy of the target managed task based on the target cloud resource instance and the third resource instance to which the candidate managed task belongs, it also implements the following steps:

[0214] If the target cloud resource instance is included in the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, the task execution strategy for the target managed task is determined to be to wait for wake-up execution; if the target cloud resource instance is not included in either the resource instance that does not require supplementation of data or the resource instance that has been supplemented with data, and the target cloud resource instance is included in the resource instance that needs to be supplemented with data, the task execution strategy for the target managed task is determined to be to execute immediately; if the target cloud resource instance is not included in the third resource instance, the task execution strategy for the target managed task is determined to be to execute immediately.

[0215] It should be noted that the data involved in this application (including but not limited to data used for analysis, data stored, data displayed, etc.) are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0216] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0217] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0218] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A cloud resource management method, characterized in that, The method is applied to a cloud management system, and the method comprises: In a case where a target cloud resource needs to be managed, a target task type and management attribute information of a target management task for the target cloud resource are determined; the target task type is an incremental management task or a full-amount management task; If there is a candidate management task with the same management attribute information in management tasks in a management processing stage in the cloud management system, a task execution strategy of the target management task is determined according to the target task type of the target management task and a candidate task type of the candidate management task; The target cloud resource is managed according to the task execution strategy and the management attribute information of the target management task.

2. The method of claim 1, wherein, In a case where the target task type is a full-amount management task, the task execution strategy of the target management task is determined according to the target task type of the target management task and a candidate task type of the candidate management task, comprising: In a case where the candidate task type of the candidate management task is an incremental management task or the candidate task type of the candidate management task comprises a full-amount management task and an incremental management task, the task execution strategy of the target management task is determined according to a management processing stage of the candidate management task; the management processing stage comprises a pre-management stage, a management supplement stage and a confirmation management stage; In a case where the candidate task type of the candidate management task is a full-amount management task, the task execution strategy of the target management task is determined according to an execution state of the candidate management task.

3. The method of claim 2, wherein, The task execution strategy of the target management task is determined according to the management processing stage of the candidate management task, comprising: If the management processing stage of the candidate management task is the management supplement stage, the task execution strategy is determined to be executed immediately; If there is a first management task in the candidate management task, the task execution strategy is determined to be executed after being woken up; the management processing stage of the first management task is not the management supplement stage.

4. The method of claim 2, wherein, The task execution strategy of the target management task is determined according to the execution state of the candidate management task, comprising: If the candidate management task is a second management task, the task execution strategy of the target management task is determined to be cancelled; the execution state of the second management task is in execution; If there are the second management task and a third management task in the candidate management task, the third management task is cancelled, and the task execution strategy of the target management task is determined according to a management processing stage of the second management task; the execution state of the third management task is not executed.

5. The method of claim 4, wherein, The task execution strategy of the target management task is determined according to the management processing stage of the second management task, comprising: If the management processing stage of the second management task is the management supplement stage, the task execution strategy of the target management task is determined to be executed immediately; If none of the second sub-tasks is in the sub-task supplement stage, the task execution strategy of the target sub-task is determined as waiting for wake-up execution.

6. The method of claim 1, wherein, In a case where the target task type is an incremental sub-task, the task execution strategy of the target sub-task is determined according to the target task type of the target sub-task and the candidate task type of the candidate sub-task, including: In a case where the candidate task type of the candidate sub-task is an incremental sub-task, the task execution strategy of the target sub-task is determined according to the first resource instance to which the candidate sub-task belongs and the target cloud resource instance to which the target sub-task belongs. In a case where the candidate task type of the candidate sub-task is an incremental sub-task, the task execution strategy of the target sub-task is determined according to the first resource instance to which the candidate sub-task belongs and the target cloud resource instance to which the target sub-task belongs. In a case where the candidate task type of the candidate sub-task includes an incremental sub-task and a full sub-task, the task execution strategy of the target sub-task is determined according to the target cloud resource instance, the first resource instance of the candidate sub-task with the candidate task type of an incremental sub-task, and the execution state and the sub-task processing stage of the candidate sub-task with the candidate task type of a full sub-task.

7. The method of claim 6, wherein, The task execution strategy of the target sub-task is determined according to the first resource instance to which the candidate sub-task belongs and the target cloud resource instance to which the target sub-task belongs, including: The first resource instance to which the candidate sub-task belongs is de-duplicated to obtain a second resource instance. If the target cloud resource instance is included in the second resource instance, the task execution strategy of the target sub-task is determined as waiting for wake-up execution. If the target cloud resource instance is not included in the second resource instance, the task execution strategy of the target sub-task is determined as immediate execution.

8. The method of claim 6, wherein, The task execution strategy of the target sub-task is determined according to the execution state of the candidate sub-task and the sub-task processing stage in which the candidate sub-task is located, including: If there is a sub-task with an execution state of unexecuted in the candidate sub-task, the task execution strategy of the target sub-task is determined as waiting for wake-up execution. If there is no sub-task with an execution state of unexecuted in the candidate sub-task, the task execution strategy of the target sub-task is determined according to the sub-task processing stage in which the candidate sub-task is located.

9. The method of claim 8, wherein, The task execution strategy of the target sub-task is determined according to the sub-task processing stage in which the candidate sub-task is located, including: If the sub-task processing stage in which the candidate sub-task is located is a pre-sub-task stage, the task execution strategy of the target sub-task is determined as waiting for wake-up execution. If the sub-task processing stage in which the candidate sub-task is located is a sub-task supplement stage or a confirmation sub-task stage, the task execution strategy of the target sub-task is determined according to the target cloud resource instance and the third resource instance to which the candidate sub-task belongs.

10. The method of claim 9, wherein, In a case where a processing stage where the candidate task is located is a data supplement stage, the third resource instance includes a resource instance without data to be supplemented, a resource instance with data to be supplemented, and a resource instance with data to be supplemented; According to the target cloud resource instance and the third resource instance to which the candidate task belongs, a task execution strategy of the target task is determined, including: If the target cloud resource instance is included in the resource instance without data to be supplemented or the resource instance with data to be supplemented, the task execution strategy of the target task is determined as waiting for wake-up execution; If the target cloud resource instance is not included in the resource instance without data to be supplemented or the resource instance with data to be supplemented, and the target cloud resource instance is included in the resource instance with data to be supplemented, the task execution strategy of the target task is determined as immediate execution; If the target cloud resource instance is not included in the third resource instance, the task execution strategy of the target task is determined as immediate execution.

Images