Multi-Deployment Engine Workflow Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The orchestration of software solutions using multiple deployment engines is time-consuming and error-prone, requiring knowledge of different deployment engines' capabilities, specific deployment actions for each component, parameter passing between engines, and flow control steps, which existing technologies struggle to automate effectively.
Innovation Solution
The technique involves modeling operational units corresponding to deployment engines, selecting appropriate engines, ordering and grouping these units, mapping output parameters of one engine to input parameters of another, inserting transitional units for engine transitions, and storing the multi-deployment engine workflow for execution, utilizing a Multiple Deployment Engine Modeling Tool (MDEMT) to automate the process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple deployment engines are used to deploy software solutions, then deployment capability and versatility are improved, but deployment time and complexity increase
Solution Approach 1:
The patent pre-configures deployment templates with predefined sequences of multiple deployment engines, parameter mappings, and transition logic before actual deployment execution. This preliminary setup allows the system to automatically orchestrate complex multi-engine deployments without requiring time-consuming manual configuration during the deployment process itself.
Solution Approach 2:
The patent introduces a deployment orchestration layer that acts as an intermediary between multiple deployment engines. This intermediary automatically manages the sequencing, parameter passing, and coordination between different engines (such as IBM PureScale, Trivoli Provisioning Manager, and Rational Automation Framework), eliminating the need for manual intervention and reducing overall deployment time.
2Reliability
If multiple deployment engines are orchestrated manually, then deployment control is improved, but error rate and complexity increase
Solution Approach 1:
The patent implements self-service automation where the deployment system automatically discovers available deployment engines, selects appropriate engines based on deployment requirements, configures parameter mappings, and executes the deployment sequence without human intervention. This self-service capability maintains precise control while eliminating the complexity of manual orchestration.
Solution Approach 2:
The patent dynamically transforms and maps parameters between different deployment engines automatically. The system converts parameters from one engine's format to another's format based on predefined mappings, ensuring seamless integration and control across multiple engines without requiring manual parameter management or increasing orchestration complexity.
3Ease of operation
If deployment automation is implemented across multiple engines, then standardization is improved, but initial setup time and complexity increase
Solution Approach 1:
The patent pre-configures deployment templates that encapsulate the entire multi-engine deployment process, including engine selection criteria, parameter mappings, sequencing logic, and transition handlers. This preliminary template creation establishes standardized deployment patterns that can be reused across multiple deployments, achieving standardization while minimizing the complexity of initial setup through template reuse.
Data Source
AI summary
Provided are techniques for modeling operational units, each operational unit corresponding to an operational workflow and to one or more deployment engines of a plurality of deployment engines; selecting, for each of the plurality of operational units, one of the corresponding deployment engines; ordering the operational units with respect to the operational workflow; grouping the ordered operation units according to the selected deployment engines into deployment engine groupings; mapping output parameters corresponding to a first operational unit that concludes a first deployment engine grouping to input parameters corresponding to a second operational unit that initiates a second deployment engine grouping, inserting between the first operational unit and the second operational unit a transitional operational unit for transitioning between a first deployment engine corresponding to the first deployment engine grouping and a second deployment engine corresponding to the second deployment engine grouping to generate a multi-deployment engine operational workflow.