CN119603299B - Method, device, equipment and medium for cross-cloud resource operation based on task orchestration - Google Patents
Method, device, equipment and medium for cross-cloud resource operation based on task orchestration Download PDFInfo
- Publication number
- CN119603299B CN119603299B CN202411491045.3A CN202411491045A CN119603299B CN 119603299 B CN119603299 B CN 119603299B CN 202411491045 A CN202411491045 A CN 202411491045A CN 119603299 B CN119603299 B CN 119603299B
- Authority
- CN
- China
- Prior art keywords
- task
- subtask
- execution
- main
- log
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
本发明提供一种基于任务编排的跨云资源操作的方法、装置、设备和介质，方法包括：将接收的调度任务请求抽象为任务编排逻辑，按照所述任务编排逻辑，调用对应云供应商的服务接口，执行所有操作；所述任务编排逻辑包括主任务、子任务及子任务动作的顺序；记录所有的执行情况，记录至设定的日志文件中，不仅能够通过任务编排的方式灵活组合调度多云资源，还能够通过统一的日志追踪系统，确保所有资源操作的可追溯性，并在问题发生时快速定位和解决。
The present invention provides a method, apparatus, device and medium for cross-cloud resource operation based on task orchestration, the method comprising: abstracting a received scheduling task request into a task orchestration logic, calling a corresponding cloud provider's service interface according to the task orchestration logic, and executing all operations; the task orchestration logic comprises a main task, subtasks and the sequence of subtask actions; recording all execution conditions in a set log file, which can not only flexibly combine and schedule multi-cloud resources by means of task orchestration, but also ensure the traceability of all resource operations through a unified log tracking system, and quickly locate and solve problems when they occur.
Description
Technical Field
The invention relates to the technical field of cross-cloud operation, in particular to a method, a device, equipment and a medium for cross-cloud resource operation based on task orchestration.
Background
With the development of cloud computing technology, enterprises widely adopt resources provided by different cloud service providers (such as AWS, azure, alicloud and the like). Because the APIs and management flows of different cloud vendors are different, cross-platform cloud resource management becomes complex and time-consuming, and APIs of each cloud vendor are dispersed and cannot be used in combination.
In the prior art, targeted scheduling processing is performed for a certain cloud manufacturer, an effective task scheduling mechanism is lacked to uniformly schedule operation of cross-cloud resources, and a uniform log tracking system is lacked to perform traceability and problem positioning of operation. This results in inefficiency and high operational costs when performing resource operations in a cloudy environment.
Disclosure of Invention
The invention aims to solve the technical problem of providing a method, a device, equipment and a medium for cross-cloud resource operation based on task arrangement, which greatly improve the working efficiency through unified scheduling processing.
In a first aspect, the present invention provides a method for cross-cloud resource operation based on task orchestration, including the steps of:
step 1, abstracting a received scheduling task request into task scheduling logic, and calling a service interface of a corresponding cloud provider to execute all operations according to the task scheduling logic, wherein the task scheduling logic comprises a main task, a subtask and a sequence of subtask actions;
and step 2, recording all execution conditions and recording the execution conditions into a set log file.
In a second aspect, the present invention provides a device for cross-cloud resource operation based on task orchestration, including the following modules:
The execution operation module is used for abstracting the received scheduling task request into task scheduling logic, and calling a service interface of a corresponding cloud provider to execute all operations according to the task scheduling logic, wherein the task scheduling logic comprises a main task, a subtask and the sequence of the subtask actions;
And the log recording module records all execution conditions and records the execution conditions into a set log file.
In a third aspect, the invention provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of the first aspect when executing the program.
In a fourth aspect, the present invention provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the method of the first aspect.
The one or more technical schemes provided by the invention have at least the following technical effects or advantages:
Business process consistency, namely ensuring that business processes executed in different cloud environments follow the same logic by realizing a unified scheduling mechanism across a plurality of cloud platforms. The consistency enables a developer to write scheduling logic once, is suitable for various cloud services, and reduces learning curves among different platforms;
the operation complexity is reduced, the dependence on specific cloud services is reduced, and the migration of the business among different cloud platforms is easier;
Transparency and traceability the unified logging system ensures the comprehensive monitoring of all task execution conditions. The detailed log of each operation can be obtained, so that the transparency of the operation is improved;
The analysis efficiency is improved, and fault detection becomes more efficient through detailed operation logs. The development tester can rapidly locate the problem source, analyze and optimize the stuck point, and ensure the continuity and stability of the service.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
The invention will be further described with reference to examples of embodiments with reference to the accompanying drawings.
FIG. 1 is a flow chart of a method according to a first embodiment of the invention
Fig. 2 is a schematic structural diagram of a device in a second embodiment of the present invention.
Detailed Description
The embodiment of the application provides a method, a device, equipment and a medium for cross-cloud resource operation based on task arrangement, which not only can flexibly combine and schedule multi-cloud resources in a task arrangement mode, but also can ensure traceability of all resource operations through a unified log tracking system and can rapidly locate and solve problems when the problems occur.
The technical scheme in the embodiment of the application has the following overall thought:
1. task orchestration driven cloud resource operation flow
The invention abstracts the operation in the business service into task scheduling logic and manages the task scheduling logic through the scheduling service. The task orchestration logic includes sequential definitions of main tasks, sub-tasks, and actions of the tasks. When the business service needs to perform resource operation, the scheduling service sequentially calls service interfaces of all cloud providers according to predefined task scheduling logic. Decoupling with different cloud manufacturers is achieved through an adapter mode, and it is ensured that resource operations of the different cloud manufacturers can be executed according to a unified flow.
2. Unified cloud resource operation log tracking
The invention provides a unified log tracking system, which records the execution condition of each task, including the context information of the task and the manufacturer call log. In the log system, not only the execution state of each main task can be checked, but also an alarm can be set according to the log level, and when the system fails to operate, alarm mechanisms such as nails are automatically triggered, so that the operation and maintenance efficiency and the system reliability are improved.
The implementation flow is as follows:
1. Task orchestration logic is defined in the scheduling service:
Defining task orchestration logic in a system, comprising:
a main task, such as an application agency;
Subtasks, wherein each subtask corresponds to specific steps of the main task, such as IP creation, instance creation, network card creation, IP binding, deployment agent and the like;
defining the execution sequence of each subtask to ensure that all necessary operations are completed in sequence;
2. service invocation scheduling service
The business service specifies the provider and the primary task to be performed and invokes the dispatch service. For example, select to perform an agent application task for alicloud.
3. Scheduling service reception processing
And the scheduling service receives the newly added scheduling task request, and extracts and stores the request parameters into the Redis according to the configuration of the newly built main task.
3.1, Distributing the main task, namely, in the main task management process, the dispatching service inquires the main task in the initial state and generates and adds initial subtasks according to the defined task relation;
3.2 subtask_item in the execution of the subtask, the dispatch service first checks if the main task is in error, and if so, cancels the execution of the following subtasks. If the concurrency threshold is reached, execution of the subtasks is delayed. Obtaining the supplier adaptation service and action to be sent, request parameters, asynchronously sending requests, and updating the subtask state into a waiting callback according to the subtask configuration;
4. vendor adapted service reception process
4.1, Firstly, obtaining a manufacturer and an action to be executed according to a requested parameter, wherein the parameter is a parameter set in 3.2, finding an adapter, wherein the adapter is used for realizing interface call of each provider, completing actual action, obtaining the parameter from redis, executing action call of the provider, and sequentially requesting interfaces of external cloud manufacturers according to specific logic in the action call, wherein the logic is an execution step of specific actions of each subtask;
4.2, recording calling information of an external cloud manufacturer by the system through a buried point, generating a sub operation log (calling method, state, starting time, ending time, execution times, parameters, return value and whether the operation is abnormal) and recording an operation result;
5. scheduling service receive callback processing
In the callback processing of the dispatch service manager, callback information is received, and concurrent locking is carried out according to the main task ID at the moment so as to ensure the concurrency safety of tasks, and ensure that only one sub task is allowed to carry out callback processing at the same moment in the running process of the sub task under the same main task. If the locking operation fails, a message is sent that is delayed by 10 seconds to re-attempt the task at a later time. If successful, the result is updated to the Redis cache, and necessary parameter entering information is provided for the subsequent tasks. When completing one subtask, callback processing needs to judge whether to execute the execution of the next subtask;
Then judging the execution condition of the subtasks:
5.1 if the subtask fails and the retry times are reached, marking the error of the main task, updating the state of the subtask into an error, and finally uploading a main operation log (comprising a link ID, an error reason (which subtask is abnormal and causes failure), abnormal information and occurrence time) to finish the flow;
5.2 if the subtask fails but the retry times are not reached, updating the state of the subtask to be in execution, and then the system re-executes the step 3.2, namely, the subtask is called again and the attempt is continued;
5.3 when the subtask is successful, the system checks if all pre-tasks of the next step have been successfully executed. If the pre-task is not completed, the sub-task state is updated to be successful and is directly returned, if the pre-task is completed, the system adds a next sub-task in an initial state and continues to execute the step 3.2;
5.4 if no subsequent subtasks need to be executed, marking the main task as completed, updating the final state of the main task as successful, and completing the whole flow;
6. Through the integral operation log, the problem source can be tracked rapidly, and efficient fault investigation is realized.
Example 1
As shown in fig. 1, the present embodiment provides a method for operating across cloud resources based on task orchestration, including the following steps:
step 1, abstracting a received scheduling task request into task scheduling logic, and calling a service interface of a corresponding cloud provider to execute all operations according to the task scheduling logic, wherein the task scheduling logic comprises a main task, a subtask and a sequence of subtask actions;
and step 2, recording all execution conditions and recording the execution conditions into a set log file.
In this embodiment, preferably, the step 1 specifically includes:
Step 11, abstracting a scheduling task request into task scheduling logic according to the received scheduling task request, wherein the task scheduling logic comprises a main task, a subtask and a sequence of subtask actions;
Step 12, generating and adding initial subtasks according to the main task, wherein each subtask is provided with corresponding task configuration, and the task configuration comprises the steps of sending supplier adaptation service, actions and request parameters to be sent, sending a request mode, and updating the subtask state into a waiting callback;
Step 13, corresponding subtasks are sequentially executed according to the execution sequence of the subtasks, actions corresponding to the tasks are executed according to task configuration, action calling is carried out through the adapter of the cloud manufacturer according to request parameters, a return result is obtained, and calling information of the cloud manufacturer is recorded in a sub operation log;
And 14, if the current sub-task is successfully executed, executing the next sub-task until all the sub-tasks are executed, recording the execution condition into a main task operation log, if the current sub-task is failed to be executed, ending the execution, updating the sub-task state into an error, marking the main task error, and recording the execution condition into the main task operation log.
In this embodiment, preferably, the step 14 specifically includes allowing only one sub-task to perform callback processing at the same time when the main task is executed, performing locking operation according to the main task ID if the current sub-task is executed successfully, delaying the first time when the locking operation fails, performing callback processing again, performing callback processing if the locking is successful, performing unlocking operation after the callback processing is completed, and performing execution of the next sub-task;
And if the current subtask fails to be executed, re-executing the subtask after the set time, ending the execution only after the same subtask fails to be set for times, updating the state of the subtask into an error, marking the error of the main task, and recording the execution condition in the main task operation log.
In this embodiment, preferably, the step 2 specifically includes recording all execution conditions including context information of a task and vendor call, recording the execution conditions into a set log file, where the log file includes a main operation log and a sub operation log, the main operation log includes a link ID, an error cause, exception information and occurrence time, the sub operation log includes a called method, a state, a start time, an end time, execution times, parameters, a return value and whether the operation of the main task or the sub task is abnormal, and triggering an alarm mechanism according to the setting when the operation of the main task or the sub task fails.
Based on the same inventive concept, the application also provides a device corresponding to the method in the first embodiment, and the details of the second embodiment are shown.
Example two
As shown in fig. 2, in this embodiment, an apparatus for cross-cloud resource operation based on task orchestration is provided, including the following modules:
The execution operation module is used for abstracting the received scheduling task request into task scheduling logic, and calling a service interface of a corresponding cloud provider to execute all operations according to the task scheduling logic, wherein the task scheduling logic comprises a main task, a subtask and the sequence of the subtask actions;
And the log recording module records all execution conditions and records the execution conditions into a set log file.
In this embodiment, preferably, the execution operation module specifically includes:
the task scheduling unit abstracts the scheduling task request into task scheduling logic according to the received scheduling task request, wherein the task scheduling logic comprises a main task, a subtask and a sequence of subtask actions;
the subtask setting unit is used for generating and adding initial subtasks according to the main task, and setting corresponding task configuration for each subtask, wherein the task configuration comprises a supplier adaptation service, an action and a request parameter which need to be sent, a request mode is sent, and the subtask state is updated to be a waiting callback;
The execution recording unit sequentially executes corresponding subtasks according to the execution sequence of the subtasks, obtains actions corresponding to the execution of the tasks according to task configuration, performs action calling through the adapter of the cloud manufacturer according to request parameters, obtains a return result, and records calling information of the cloud manufacturer into a sub operation log;
And the final execution unit is used for executing the next subtask until all the subtasks are executed and recording the execution condition into the main task operation log if the current subtask is executed successfully, ending the execution if the current subtask is executed successfully, updating the subtask state into an error, marking the main task error and recording the execution condition into the main task operation log.
In this embodiment, preferably, the final execution unit specifically allows only one sub-task to perform callback processing at the same time when the main task is executed, if the current sub-task is executed successfully, locking operation is performed according to the main task ID, if the locking operation fails, the first time is delayed, callback processing is performed again, and if the locking is successful, callback processing is performed;
And if the current subtask fails to be executed, re-executing the subtask after the set time, ending the execution only after the same subtask fails to be set for times, updating the state of the subtask into an error, marking the error of the main task, and recording the execution condition in the main task operation log.
In this embodiment, the log recording module preferably records all execution conditions including context information of a task and vendor call, and records the execution conditions into a set log file, where the log file includes a main operation log and a sub operation log, the main operation log includes a link ID, an error cause, exception information and occurrence time, the sub operation log includes a calling method, a state, a start time, an end time, execution times, parameters, a return value and whether the operation of the main task or the sub task fails, and triggers an alarm mechanism according to the setting.
Since the device described in the second embodiment of the present invention is a device for implementing the method described in the first embodiment of the present invention, based on the method described in the first embodiment of the present invention, a person skilled in the art can understand the specific structure and the deformation of the device, and thus the detailed description thereof is omitted herein. All devices used in the method according to the first embodiment of the present invention are within the scope of the present invention.
Based on the same inventive concept, the application provides an electronic device embodiment corresponding to the first embodiment, and the details of the third embodiment are shown in the specification.
Example III
The present embodiment provides an electronic device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where any implementation of the first embodiment may be implemented when the processor executes the computer program.
Since the electronic device described in this embodiment is a device for implementing the method in the first embodiment of the present application, those skilled in the art will be able to understand the specific implementation of the electronic device and various modifications thereof based on the method described in the first embodiment of the present application, so how the electronic device implements the method in the embodiment of the present application will not be described in detail herein. The apparatus used to implement the methods of embodiments of the present application will be within the scope of the intended protection of the present application.
Based on the same inventive concept, the application provides a storage medium corresponding to the first embodiment, and the detail of the fourth embodiment is shown in the specification.
Example IV
The present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, can implement any of the implementation modes of the embodiment.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that the specific embodiments described are illustrative only and not intended to limit the scope of the invention, and that equivalent modifications and variations of the invention in light of the spirit of the invention will be covered by the claims of the present invention.
Claims (6)
1. A method for operating cross-cloud resources based on task orchestration is characterized by comprising the following steps:
Step 1, abstracting a received scheduling task request into task scheduling logic, calling a service interface of a corresponding cloud provider according to the task scheduling logic, and executing all operations, wherein the task scheduling logic comprises a main task, a subtask and a sequence of subtask actions, and the step 1 specifically comprises the following steps:
Step 11, abstracting a scheduling task request into task scheduling logic according to the received scheduling task request, wherein the task scheduling logic comprises a main task, a subtask and a sequence of subtask actions;
Step 12, generating and adding initial subtasks according to the main task, wherein each subtask is provided with corresponding task configuration, and the task configuration comprises the steps of sending supplier adaptation service, actions and request parameters to be sent, sending a request mode, and updating the subtask state into a waiting callback;
step 13, corresponding subtasks are sequentially executed according to the execution sequence of the subtasks, actions corresponding to the tasks are executed according to task configuration, action calling is carried out through an adapter of a cloud manufacturer according to request parameters, a return result is obtained, and calling information of the cloud manufacturer is recorded in a sub operation log;
Step 14, when the main task is executed, only one sub task is allowed to carry out callback processing at the same time, if the current sub task is executed successfully, locking operation is carried out according to the ID of the main task, if the locking operation fails, the first set time is delayed, callback processing is carried out, and if the locking operation is successful, callback processing is carried out;
If the current subtask is executed successfully, executing the next subtask until all the subtasks are executed, recording the execution condition in a main task operation log, if the current subtask is executed successfully, re-executing the subtask after a set time, and ending the execution only after the same subtask is failed for a set time, updating the subtask state into an error, marking the main task error, and recording the execution condition in the main task operation log;
and step 2, recording all execution conditions and recording the execution conditions into a set log file.
2. The method for operating the cross-cloud resource based on task arrangement according to claim 1 is characterized in that step 2 specifically includes recording all execution conditions including context information of tasks and vendor calls, recording the execution conditions into a set log file, wherein the log file includes a main operation log and a sub operation log, the main operation log includes a link ID, an error reason, abnormal information and occurrence time, the sub operation log includes a calling method, a state, a starting time, an ending time, execution times, parameters, a return value and whether the operation of the main task or the sub task is abnormal, and triggering an alarm mechanism according to the setting when the operation of the main task or the sub task is failed.
3. The device for cross-cloud resource operation based on task orchestration is characterized by comprising the following modules:
the execution operation module abstracts the received scheduling task request into task scheduling logic, and calls a service interface corresponding to a cloud provider to execute all operations according to the task scheduling logic, wherein the task scheduling logic comprises a main task, a subtask and the sequence of the subtask actions, and the execution operation module specifically comprises:
the task scheduling unit abstracts the scheduling task request into task scheduling logic according to the received scheduling task request, wherein the task scheduling logic comprises a main task, a subtask and a sequence of subtask actions;
the subtask setting unit is used for generating and adding initial subtasks according to the main task, and setting corresponding task configuration for each subtask, wherein the task configuration comprises a supplier adaptation service, an action and a request parameter which need to be sent, a request mode is sent, and the subtask state is updated to be a waiting callback;
The execution recording unit sequentially executes corresponding subtasks according to the execution sequence of the subtasks, obtains actions corresponding to the execution of the tasks according to task configuration, performs action calling through an adapter of a cloud manufacturer according to request parameters, obtains a return result, and records calling information of the cloud manufacturer into a sub operation log;
the final execution unit only allows one subtask to carry out callback processing at the same time when the main task is executed, if the current subtask is executed successfully, locking operation is carried out according to the ID of the main task, if the locking operation fails, the first set time is delayed, callback processing is carried out, and if the locking operation is successful, callback processing is carried out;
If the current subtask is executed successfully, executing the next subtask until all the subtasks are executed, recording the execution condition in a main task operation log, if the current subtask is executed successfully, re-executing the subtask after a set time, and ending the execution only after the same subtask is failed for a set time, updating the subtask state into an error, marking the main task error, and recording the execution condition in the main task operation log;
And the log recording module records all execution conditions and records the execution conditions into a set log file.
4. The device for performing operation across cloud resources based on task orchestration according to claim 3, wherein the log recording module is specifically configured to record all execution conditions including context information of tasks and vendor calls, record the execution conditions into a set log file, wherein the log file comprises a main operation log and a sub operation log, the main operation log comprises a link ID, an error reason, abnormal information and occurrence time, the sub operation log comprises a calling method, a state, a starting time, an ending time, execution times, parameters, a return value and whether the operation of the main task or the sub task is abnormal, and trigger an alarm mechanism according to the setting when the operation of the main task or the sub task fails.
5. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 and 2 when the program is executed by the processor.
6. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 1 and 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411491045.3A CN119603299B (en) | 2024-10-24 | 2024-10-24 | Method, device, equipment and medium for cross-cloud resource operation based on task orchestration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411491045.3A CN119603299B (en) | 2024-10-24 | 2024-10-24 | Method, device, equipment and medium for cross-cloud resource operation based on task orchestration |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN119603299A CN119603299A (en) | 2025-03-11 |
| CN119603299B true CN119603299B (en) | 2025-06-24 |
Family
ID=94827992
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202411491045.3A Active CN119603299B (en) | 2024-10-24 | 2024-10-24 | Method, device, equipment and medium for cross-cloud resource operation based on task orchestration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119603299B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110879756A (en) * | 2019-10-31 | 2020-03-13 | 深圳市泰洲科技有限公司 | Method and device for processing abnormal cooperation process, computer equipment and storage medium |
| CN112839109A (en) * | 2021-03-04 | 2021-05-25 | 广州市品高软件股份有限公司 | A cloud resource orchestration method based on cloud functions and BPMN specifications |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10412192B2 (en) * | 2016-05-10 | 2019-09-10 | International Business Machines Corporation | Jointly managing a cloud and non-cloud environment |
| US11567837B2 (en) * | 2018-08-25 | 2023-01-31 | Panzura, Llc | Journaling data received in a cloud-based distributed computing environment |
| CN116089040A (en) * | 2023-01-06 | 2023-05-09 | 中国工商银行股份有限公司 | Scheduling method of business process and its device, electronic equipment and storage medium |
| CN116719622A (en) * | 2023-06-07 | 2023-09-08 | 中国联合网络通信集团有限公司 | Service flow arranging method and service flow arranging system |
| CN118573679A (en) * | 2024-05-24 | 2024-08-30 | 中国人民解放军国防科技大学 | Inter-cloud computing decentralization FaaS workflow cross-cloud cooperation method and system |
-
2024
- 2024-10-24 CN CN202411491045.3A patent/CN119603299B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110879756A (en) * | 2019-10-31 | 2020-03-13 | 深圳市泰洲科技有限公司 | Method and device for processing abnormal cooperation process, computer equipment and storage medium |
| CN112839109A (en) * | 2021-03-04 | 2021-05-25 | 广州市品高软件股份有限公司 | A cloud resource orchestration method based on cloud functions and BPMN specifications |
Also Published As
| Publication number | Publication date |
|---|---|
| CN119603299A (en) | 2025-03-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10642599B1 (en) | Preemptive deployment in software deployment pipelines | |
| US8412984B2 (en) | Debugging in a cluster processing network | |
| US7779298B2 (en) | Distributed job manager recovery | |
| US9311064B1 (en) | Systems and methods for automated centralized build/merge management | |
| US20150100832A1 (en) | Method and system for selecting and executing test scripts | |
| TW200405202A (en) | Method and apparatus for automatic updating and testing of software | |
| EP4127939B1 (en) | Architecture, method and system for live testing in a production environment | |
| US9983988B1 (en) | Resuming testing after a destructive event | |
| US7877733B2 (en) | Failure test framework | |
| CN114006815B (en) | Automatic deployment method and device for cloud platform nodes, nodes and storage medium | |
| CN115617668A (en) | A compatibility test method, device and equipment | |
| US11074095B2 (en) | Event-based virtual machine that hosts microservices for handling program faults | |
| CN111722853A (en) | A method and device for installation script deployment | |
| CN119603299B (en) | Method, device, equipment and medium for cross-cloud resource operation based on task orchestration | |
| CN118245346B (en) | Automatic operation and maintenance management system and method oriented to operating system | |
| CN117667362B (en) | Method, system, equipment and readable medium for scheduling process engine | |
| CN113485726A (en) | Application environment delivery method and device | |
| CN110188008B (en) | Job scheduling master-slave switching method and device, computer equipment and storage medium | |
| CN115525568A (en) | Inspection method, device, computer equipment and storage medium for code coverage | |
| US20230088318A1 (en) | Remotely healing crashed processes | |
| CN115981662A (en) | Branch code merging method and device, electronic equipment and storage medium | |
| Alourani et al. | T-basir: Finding shutdown bugs for cloud-based applications in cloud spot markets | |
| US12487878B2 (en) | Application assistant for managing application programs in an information processing system | |
| CN114356643B (en) | A method for automatically discovering mission failure and recovery in a remote sensing satellite processing system | |
| CN116506284B (en) | Server remote in-band management system, method, computer device, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |