Multi-Cluster Tenant Migration Using Resource Quota Planning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing kubernetes cluster failure migration methods lack flexibility, support for per-tenant migration, resource reuse, and efficient resource utilization, leading to complex configurations and resource waste.
Innovation Solution
A multi-cluster application failure migration method and system that supports multiple tenants by creating a multi-cluster environment with a management cluster and worker clusters, deploying applications with failure migration strategies, generating resource quota information tables, and optimizing failure migration solutions to facilitate automatic migration and resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If point-to-point migration is performed between clusters, then migration from one cluster to another is supported, but flexible adjustments cannot be realized and strategies need to be reconfigured for each adjustment
Solution Approach 1:
The patent implements a hub-and-spoke migration architecture where a central hub cluster can receive applications from any spoke cluster. This universal migration path replaces the need for multiple point-to-point configurations, allowing any cluster to migrate to the hub without requiring specific pairwise setup, thereby achieving flexible adjustments with a single standardized strategy.
Solution Approach 2:
The hub cluster serves as an intermediary node that mediates migration between spoke clusters. Instead of direct point-to-point migration requiring complex configuration between each pair, the hub acts as a universal intermediary that simplifies the migration path, enabling flexible adjustments through a single centralized configuration point rather than multiple distributed configurations.
2Adaptability or versatility
If overall cluster migration or single application failure migration is performed without tenant involvement, then migration can be executed, but per-tenant migration is not supported and tenant resource measurement is not utilized
Solution Approach 1:
The patent segments the migration process by tenant, allowing independent migration decisions and resource allocation for each tenant within the cluster. This segmentation enables per-tenant migration support while utilizing existing tenant resource measurement mechanisms, avoiding the need for a completely new migration management system and thus not increasing overall complexity.
3Adaptability or versatility
If cluster failure migration configuration is performed after cluster failure occurs, then migration can be executed, but strategies need to be readjusted to adapt to new cluster environment and flexibility is poor
Solution Approach 1:
The patent establishes migration strategies and hub cluster configurations in advance, before any failure occurs. The hub-and-spoke architecture is pre-configured with standardized migration paths, so when a failure occurs, the system can immediately execute the pre-planned migration without needing to readjust strategies or prepare configurations, thereby eliminating adaptation delays.
4Ease of operation
If many parameters need to be configured by user to control failure migration process, then migration control is achieved, but use difficulty and threshold increase and holistic strategy implementation is not facilitated
Solution Approach 1:
The patent merges multiple migration control parameters into a single standardized hub configuration. Instead of requiring users to configure separate parameters for each point-to-point migration path, all migration control is consolidated into the hub cluster's configuration, which automatically manages the standardized spoke-to-hub migration paths, thereby simplifying operation while maintaining control.
5Reliability
If new backup cluster is built to accommodate migrated application, then application failure overall migration is satisfied, but resource waste occurs and enterprise costs increase
Solution Approach 1:
The patent enables recovery and reuse of resources from failed clusters by migrating applications to the hub cluster. Instead of discarding the failed cluster's resources or building new backup clusters that duplicate resources, the system recovers applications and their resource allocations from the failed spoke cluster and redeploys them to the hub, thereby eliminating resource waste while maintaining application availability.
Data Source
AI summary
The present application discloses a multi-cluster application failure migration method and system supporting multiple tenants, and relates to the field of cluster application failure migration technologies. The method includes: creating a multi-cluster environment by using kubernetes application software; for each worker cluster in the multi-cluster environment, creating the tenants in the worker cluster; for each tenant, deploying an application in the tenant and configuring a failure migration strategy associated with the application; generating a resource quota information table according to the failure migration strategy and state information of the worker cluster; and generating a failure migration solution according to the resource quota information table, for providing a technical guidance after a certain worker cluster fails, so as to facilitate the tenants, the applications and components in the failed worker cluster which can be migrated to be migrated to other non-failed worker clusters and redeployed.