Multi-Cluster Tenant Provisioning for Controlled Cloud Releases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-cloud orchestration frameworks are either cloud-specific or require significant user expertise and do not effectively manage the deployment and adaptation of new versions of workloads, applications, or services across multiple clusters with the necessary efficiency and security.
Innovation Solution
A system and method for tenant provisioning that includes creating a tenant in a cloud using user metadata, generating a tenant key based on metadata, and enabling controlled and staged deployment across multiple clusters through Domain Name System record mapping, license uploading, and admin credential creation, utilizing a processor and memory unit to manage tenant information and resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing multi-cloud orchestration frameworks are used, then cloud-specific deployment is achieved, but adaptability across different cloud platforms is limited
Solution Approach 1:
The patent implements a universal orchestration framework that can deploy applications across multiple cloud platforms (AWS, Azure, GCP, OpenStack) through a single interface. The system abstracts cloud-specific details behind a unified API, allowing the same deployment pipeline to operate on different cloud infrastructures without requiring separate cloud-specific frameworks, thus achieving multi-functionality and cross-cloud adaptability.
Solution Approach 2:
The patent introduces an intermediary orchestration layer that mediates between the application deployment requests and the underlying cloud-specific infrastructure. This intermediary translates high-level deployment commands into cloud-specific operations, enabling seamless cross-cloud deployment while shielding users from platform-specific complexities. The intermediary handles authentication, resource provisioning, and lifecycle management across different cloud providers.
2Adaptability or versatility
If existing orchestration frameworks require significant user expertise, then advanced deployment scenarios are achieved, but ease of operation deteriorates
Solution Approach 1:
The patent implements self-service automation that eliminates the need for manual intervention in complex deployment scenarios. The system automatically discovers cloud resources, configures networking, manages authentication credentials, and handles failure recovery without requiring user expertise. The automated provisioning system performs actions that would otherwise require deep knowledge of cloud infrastructure, making the system accessible to users with minimal technical background while still supporting advanced deployment scenarios.
Solution Approach 2:
The patent performs preliminary actions by pre-configuring deployment templates, authentication mechanisms, and resource allocation policies before actual application deployment. The system pre-establishes connectivity between clouds, pre-generates security credentials, and pre-validates deployment configurations. This preliminary setup eliminates the need for users to perform complex manual configuration during deployment, reducing the expertise required while maintaining support for advanced scenarios through pre-built templates.
3Reliability
If controlled and staged deployment is implemented, then deployment reliability is improved, but deployment time increases
Solution Approach 1:
The patent segments the deployment process into controlled stages: validation phase (syntax and schema checking), simulation phase (dry-run without actual deployment), incremental deployment phase (rolling updates with rollback capability), and full deployment phase. Each stage is independently executable and can be aborted without affecting other stages. This segmentation allows the system to maintain high reliability through staged validation while reducing overall deployment time by allowing parallel execution of independent validation tasks and enabling selective skipping of stages for trusted deployments.
Data Source
AI summary
An embodiment herein provides a system and method for performing tenant provisioning to enable controlled and staged deployment of new versions of workload, application, or service across the multiple clusters. The method includes (a) creating a tenant in a cloud using a user metadata received from a plurality of user devices, (b) generating a tenant key based on tenant information and tenant metadata, (c) mapping a snapshot of the tenant database comprising the tenant metadata to the tenant key, (d) creating Domain Name System record, (e) uploading license and generating Key Management Service key simultaneously, and (f) enabling the controlled and staged deployment of the new versions of the workload, application, or service across multiple clusters by creating admin credentials. This system and method can be implemented in EKS—Elastic Kubernetes Service, GKE—Google Kubernetes Engine, and AKS—Azure Kubernetes Service managed services.