Task Modeling Overview
If the built-in standard task scenarios in the automated operation and maintenance management platform cannot fully meet your requirements, the platform provides two types of task modeling methods for on-demand extension of task scenarios:
1. Atomic Job Task Modeling: This method creates single-task scenario templates to implement specific automated operation tasks.
2. Workflow Job Task Modeling: This method assembles and orchestrates multiple task scenario templates in sequence to implement more complex automated task scenarios.
Task Modeling Capabilities
Atomic Job Task Modeling
Atomic job tasks typically correspond to specific automated operation tasks that achieve repeatable standard operational scenarios, such as installing and configuring specific foundational software, expanding host disk capacity, etc.
Users can design atomic job task templates through configuration in the platform's "Model - Task Modeling - Operation Jobs" module, which generally includes the following steps:
1. Create a new atomic job task template.
2. Select the "Orchestration Template" corresponding to the atomic job task template. The "Orchestration Template" represents the type of automated program mounted by this atomic task template, with common types including Playbook, Shell/Python, Ansible API, etc..
3. Define parameters for the atomic job task template.
4. Publish the new atomic job task template to menus or service catalogs.
Workflow Job Task Modeling
Workflow job tasks typically consist of a combination of multiple automated operation tasks with sequential execution order and dependencies, aiming to implement more complex workflows. These may involve cross-system interactions, environmental change operations, notifications, CMDB collection, etc., requiring centralized management of execution sequence, trigger conditions, and verification mechanisms through workflows.
Users can design workflow job task templates through configuration in the platform's "Model - Task Modeling - Workflow Orchestration" module, which generally includes the following steps:
1. Predefine atomic job task templates that the workflow may contain.
2. Create a new workflow job task template.
3. Add workflow nodes to the new template, configure associated atomic job task templates, node trigger conditions, parameters, and output variable registration.
4. Adjust the sequential relationships between multiple workflow nodes.
5. Publish the new workflow job task template to the menus or service catalogs.
