Enterprise Server Image Meta Tagging for Deployment Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
DevOps teams face challenges in ensuring correct versioning and control during continuous integration/continuous deployment (CICD) activities, particularly in TRAIN deployment scenarios, where devices determine component deployment to specific servers using YAML lists, leading to difficulties in accurate and controlled code deployment and monitoring.
Innovation Solution
Implementing a logical tag on components that are surveyed and stored in a database, requiring a matching tag for deployment, with features like version priority to override the default latest version deployment, using a network routing paradigm in conjunction with the TRAIN approach.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If TRAIN deployment scenarios using YAML lists are used to determine component deployment, then deployment automation is improved, but deployment control precision deteriorates
Solution Approach 1:
The patent segments the deployment control into two distinct parts: automated routing decisions based on logical tags and manual override capabilities through version priority settings. This segmentation allows the system to maintain automation for routine deployments while enabling precise control when needed, resolving the contradiction between automation extent and control precision.
Solution Approach 2:
The patent introduces logical tags as an intermediary mechanism between the automated TRAIN deployment system and the deployment control requirements. These tags act as a mediator that enables automated routing decisions while maintaining the ability to exercise precise control through version priority overrides, thus resolving the contradiction.
2Speed
If latest code versions are always deployed first, then deployment speed is improved, but deployment accuracy deteriorates
Solution Approach 1:
The patent applies preliminary action by pre-tagging code versions with logical identifiers before deployment. This allows the system to quickly route deployments based on pre-established tags while maintaining accuracy through the version priority mechanism that can override automatic latest-version deployment when necessary, thus resolving the contradiction between speed and accuracy.
3Manufacturing precision
If tag matching is required for deployment, then deployment control is improved, but system complexity increases
Solution Approach 1:
The patent makes the logical tag system universal by designing it to work with the existing TRAIN deployment framework. The same tagging mechanism serves multiple functions: enabling automated routing, providing version identification, and supporting override capabilities. This multi-functionality reduces the need for separate complex systems, thus resolving the contradiction between control precision and system complexity.
Data Source
AI summary
A system prevents incorrect deployment of computer code in remote enterprise servers. The system includes a source code repository for housing computer code received from developers and housing software that maintains the code and develops version control information (VCI) for same. The system includes a continuous integration/continuous deployment (CICD) pipeline orchestrator and arranges deployment of the computer code by determining servers to which the code will be deployed. A metatag affixing engine and database creates metatag information corresponding to the computer code and stores the metatag information. The metatag information qualifies the code for deployment at the servers, as follows. A code management system schedules deployment. Prior to deployment, each of the servers reads the metatag implemented on the code and compares the metatag on the code to determine whether the metatag matches the metatag stored at the database. When the metatags matches at the server, the computer code is deployed.