Multi-Tenant Cloud Deployment Orchestration with Aggregate Version Maps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Orchestrating operations such as provisioning and deploying services in a datacenter on cloud platforms is complex, prone to errors, and leads to downtime, especially in multi-tenant systems, affecting a large number of users.
Innovation Solution
A system that uses a cloud platform independent declarative specification to generate datacenters, which compiles version maps and aggregate pipelines to automate operations, reducing manual steps and human errors, and ensures efficient deployment across multiple cloud platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual steps are used for provisioning and deploying services in cloud platforms, then flexibility and control are improved, but error rate increases and reliability deteriorates
Solution Approach 1:
The patent introduces version maps as an intermediary artifact that bridges manual operational control and automated execution. Version maps contain structured service definitions, dependencies, and configuration data that enable automated orchestration while preserving the ability to control deployment behavior through version selection and map configuration.
Solution Approach 2:
The system changes the parameter of operation mode from purely manual to automated by transforming service provisioning data into structured version map formats. This parameter change enables automated processing while maintaining control through version map configuration, resolving the contradiction between manual control and automation reliability.
2Adaptability or versatility
If version maps are maintained separately for each cloud platform, then platform-specific customization is improved, but device complexity and storage requirements increase
Solution Approach 1:
The patent segments version map information into hierarchical components: core service definitions that are platform-agnostic, and platform-specific adaptations that can be selectively applied. This segmentation allows the same base version map to serve multiple cloud platforms while maintaining necessary customizations through modular additions rather than complete separate versions.
Solution Approach 2:
The version map structure is designed with universal applicability across different cloud platforms. By defining services, dependencies, and configurations in a platform-agnostic manner with optional platform-specific extensions, a single version map can be reused across multiple cloud environments, reducing complexity while maintaining adaptability.
3Reliability
If comprehensive version tracking is implemented for all services, then reliability and version control are improved, but storage requirements and system complexity increase
Solution Approach 1:
Instead of storing complete service configurations and dependency graphs for every version, the patent uses version maps that contain structured references and metadata. The system stores compact version map files that can be efficiently copied and distributed, containing only the essential versioning information and relationships rather than full service definitions.
Solution Approach 2:
The system performs preliminary organization of version information during the service definition phase, creating structured version maps before deployment. This preliminary action consolidates version data in an optimized format, reducing the need for extensive storage during operational phases while maintaining comprehensive version control capabilities.
Data Source
AI summary
Computing systems, for example, multi-tenant systems deploy software artifacts in datacenters created in a cloud platform. The system receives multiple version maps. Each version map provides version information for a particular context associated with the datacenter. The context may specify a target environment, a target datacenter entity, or a target action to be performed on the cloud platform. The system generates an aggregate pipeline comprising a hierarchy of pipelines. The system generates an aggregate version map associating datacenter entities of the datacenter with versions of software artifacts targeted for deployment on the datacenter entities and versions of pipelines. The system executes the aggregate pipeline in conjunction with the aggregate version map to perform requested operations on the datacenter configured on the cloud platform, for example, provisioning resources or deploying services.