Deployment Device for Environment-Independent Configuration Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing deployment methods face challenges in applying a configuration definition file created for one environment to system deployment in another environment due to fixed description syntax or formats specific to available deployment tools.
Innovation Solution
A deployment device and method that stores component information independent of deployment tools, identifies deployment processes based on designated tools, determines execution sequences based on dependency relationships, and executes these processes to deploy system constituents across different environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If configuration definition files use fixed description syntax or format specific to deployment tools, then deployment control and automation are improved, but adaptability to different environments deteriorates
Solution Approach 1:
The configuration definition file is segmented into multiple independent sections: a common configuration section containing environment-independent settings, and multiple deployment tool-specific configuration sections (each corresponding to a different deployment tool). This segmentation allows the system to automatically select and use only the relevant deployment tool section for the target environment, thereby maintaining deployment automation while improving environment adaptability without requiring format conversion
Solution Approach 2:
The configuration definition file is designed with universal structure that can serve multiple deployment tools simultaneously. By incorporating multiple deployment tool-specific configuration sections within a single file, the system achieves multi-functionality where one configuration file can be reused across different deployment environments (AWS, Azure, etc.) by simply selecting the appropriate tool section, thus resolving the contradiction between automation and adaptability
2Adaptability or versatility
If configuration definition files are converted to formats defined by deployment tools available in target environments, then adaptability to different environments is improved, but device complexity and conversion requirements worsen
Solution Approach 1:
The configuration definition file is segmented into multiple independent sections: a common configuration section containing environment-independent settings, and multiple deployment tool-specific configuration sections (each corresponding to a different deployment tool). This segmentation allows the system to automatically select and use only the relevant deployment tool section for the target environment, thereby maintaining deployment automation while improving environment adaptability without requiring format conversion
Solution Approach 2:
Instead of converting the entire configuration definition file to a different format for each target environment, the system copies only the relevant deployment tool-specific configuration section from the source file to the target environment. This selective copying approach reduces complexity by avoiding full format conversion while still achieving environment adaptability
3Reliability
If deployment processes are executed according to dependency relationships among constituent elements, then deployment reliability is improved, but execution time and sequence determination complexity worsen
Solution Approach 1:
The system performs preliminary analysis of dependency relationships among constituent elements before executing deployment processes. By pre-determining the execution sequence based on declared dependencies, the system avoids runtime delays caused by dynamic dependency resolution, thus maintaining high deployment reliability while reducing actual execution time
Solution Approach 2:
The configuration definition file itself contains the dependency relationship information needed for sequence determination. The system uses this self-provided information to automatically determine execution sequences without requiring external intervention or complex external scheduling systems, thereby improving reliability while minimizing time loss
Data Source
AI summary
A configuration definition file created for a certain environment is easily applied to system deployment into another environment. A component information storage unit of a deployment device stores component information including, for each constituent element to constitute a system, setting information independent of deployment tools, and for each combination of each constituent element and each deployment tool available for deploying the constituent element, a deployment process for deploying the constituent element by the deployment tool. The component identification unit identifies, for each constituent element, a deployment process associated with a designated deployment tool, based on the component information. The sequence determination unit determines an execution sequence of the identified deployment processes, based on dependency relationships among the constituent elements. The deployment execution unit executes the identified deployment processes according to the execution sequence and applying setting information for the constituent elements, and thereby deploys the constituent elements.