Unified Container for Hyper-Converged Infrastructure Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing and deploying hyper-converged infrastructure (HCI) data center components are complex and inefficient, as they often require manual processes and result in isolated infrastructure components, making it difficult to upgrade or manage multiple data centers effectively.
Innovation Solution
An automated continuous integration and continuous deployment (CI/CD) pipeline is used to version, package, and bundle individual infrastructure components into a distributable container, allowing for over-the-air deployment and incremental upgrades without disrupting existing systems, using an artifact repository that bundles heterogeneous components with floating tags for versioning and updating.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If infrastructure components are converted into separate software containers, then each component is isolated and can be distributed independently, but the management of multiple containers becomes extremely complex and inefficient
Solution Approach 1:
The patent combines multiple separate infrastructure component containers into a single unified container that includes all necessary components (compute, storage, networking, security). This merging approach maintains the independence and isolatability of components while eliminating the management complexity of handling multiple separate containers, as the unified container can be deployed and managed as a single unit.
Solution Approach 2:
The unified container is designed to be universal, containing multiple types of infrastructure components (virtual machines, storage volumes, network interfaces, security policies) that can serve different functions within a single data center deployment. This multi-functionality allows the single container to replace multiple specialized containers while maintaining component independence through internal structuring.
2Ease of manufacture
If infrastructure components are archived into a single distributed file, then the file can be distributed to remote data centers, but upgrading requires recreating the entire unified workspace with all components
Solution Approach 1:
The patent segments the unified container into distinct, independently upgradable components (compute resources, storage resources, networking resources, security resources). Each component is packaged as a separate module within the unified container structure, allowing individual components to be updated without requiring recreation of the entire container or workspace. This segmentation enables incremental upgrades while maintaining the simplicity of single-file distribution.
Solution Approach 2:
The unified container is designed with dynamic update capabilities, where components can be added, removed, or modified after initial deployment. The container structure supports version control and incremental updates, allowing the system to evolve from a static single-file archive to a dynamic, continuously upgradable infrastructure without requiring complete recreation.
3Adaptability or versatility
If manual processes are used for versioning, packaging, and distributing infrastructure components, then flexibility in customization is maintained, but the process becomes complex and time-consuming
Solution Approach 1:
The patent implements preliminary automated actions for versioning, packaging, and validating infrastructure components before deployment. Templates and configuration files are pre-prepared with version metadata, dependency information, and validation rules. This preliminary automation handles the time-consuming manual tasks of version control and packaging while preserving customization flexibility through configurable template parameters and user-defined component specifications.
Solution Approach 2:
The system incorporates automated feedback mechanisms that validate component compatibility, version dependencies, and configuration correctness during the packaging and deployment process. This automated feedback replaces manual verification steps, reducing time loss while maintaining the ability to customize components. The feedback loop ensures that customizations meet system requirements without requiring manual checking of each component.
Data Source
AI summary
An application management platform comprising at least a packaging and bundling component, a deployment management component, and an update component. The packaging and bundling component versions, packages, and bundles a plurality of infrastructure components for a remote data center. The deployment management component provisions one or more nodes of the remote data center with the plurality of infrastructure components for an application. The update component monitors available updates to one or more of the plurality of infrastructure components used by the remote data center and facilitates update of the one or more of the plurality of infrastructure components at the remote data center.