Task Execution System with Dual Remote and Local Modes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current task execution methods in computer technology are limited in flexibility and efficiency, as they often rely on encapsulating open-source tools like Ansible or SaltStack, which do not support multiple execution modes, leading to inflexibility and potential performance bottlenecks in large-scale concurrency.
Innovation Solution
A task execution method and system that supports two execution modes: remote execution, where a control device controls a task execution device, and local execution, where the task execution device executes tasks independently, allowing for more flexible task processing and improved concurrency without relying on underlying tool systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a control device remotely controls task execution devices to execute tasks, then task execution can be centralized and managed, but the system lacks flexibility and cannot support local autonomous execution
Solution Approach 1:
The task execution device is designed to perform multiple functions: it can execute tasks remotely controlled by a control device (first execution mode) and independently execute tasks obtained from a task queue (second execution mode). This multi-functionality resolves the contradiction by making the system adaptable to different execution scenarios without requiring completely separate systems for each mode.
Solution Approach 2:
The task execution system is segmented into distinct operational modes: remote control mode where the control device manages execution, and autonomous mode where the task execution device independently executes tasks from a task queue. This segmentation allows flexibility in execution modes while managing complexity through clear mode separation.
2Productivity
If open-source tools like Ansible or SaltStack are used for task execution, then existing tools can be leveraged, but they do not support multiple execution modes and have performance bottlenecks in large-scale concurrency
Solution Approach 1:
The system dynamically switches between different execution modes based on task requirements. Task execution devices can transition between remote control mode and autonomous execution mode, allowing the system to adapt to varying productivity needs and execution mode requirements without being constrained by fixed tool limitations.
Solution Approach 2:
A task queue serves as an intermediary mechanism that enables autonomous task execution. Instead of relying solely on remote control or existing open-source tools, the patent introduces a task queue that task execution devices can independently access, thereby supporting multiple execution modes and improving large-scale concurrency performance.
3Ease of operation
If remote control execution mode is used, then centralized management is achieved, but operational and maintenance costs increase
Solution Approach 1:
Task execution devices can independently obtain tasks from the task queue and execute them autonomously without requiring continuous remote control intervention. This self-service capability reduces operational and maintenance costs while maintaining centralized management through the task queue, resolving the contradiction between ease of operation and resource consumption.
Data Source
AI summary
The present disclosure relates to a task execution method, apparatus, device and system, and a storage medium, wherein same relate to the technical field of computers. The method comprises: acquiring a plurality of tasks to be processed; acquiring a first task in the plurality of tasks to be processed, and controlling a task execution device associated with a current control device to execute the first task; and when a task request of any task execution device is received, acquiring, from the plurality of tasks to be processed, a second task when a target task execution device is the any task execution device, and sending the second task to the any task execution device.


