Individual Tenant Move Upgrade in Multi-tenancy Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-tenancy computing systems lack the ability to individually upgrade tenants to a newer software version without affecting all tenants, leading to high costs and increased error likelihood due to simultaneous upgrades, which restricts customer-specific downtime planning and efficiency.
Innovation Solution
A method to upgrade individual tenants by moving them from a source computing system with an older software version to a target system with a newer version, including adjustments to customer-specific data structures, allowing for separate data migration and reduced downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all tenants are upgraded simultaneously in a multi-tenancy computing system, then the system-wide upgrade is completed, but the cost per tenant increases and the likelihood of upgrade failure increases dramatically
Solution Approach 1:
The patent segments the upgrade process by introducing a move coordinator that manages individual tenant upgrades separately rather than upgrading all tenants simultaneously. Each tenant upgrade is handled as an independent unit with its own success/failure isolation, preventing cascading failures across the entire system.
Solution Approach 2:
The move coordinator acts as an intermediary component that orchestrates the upgrade process. It manages the interaction between tenants, target systems, and upgrade operations, enabling controlled individual upgrades while maintaining system-wide coordination and reducing overall failure risk.
2Adaptability or versatility
If manual implementations are used for tenant upgrades, then flexibility in handling individual tenant cases is achieved, but the number of errors in tenant-specific actions increases
Solution Approach 1:
The system enables self-service automated upgrade operations through the move coordinator, which automatically manages tenant migration and upgrade processes. This reduces manual intervention errors while maintaining the ability to handle tenant-specific requirements through automated decision-making and coordination.
3Adaptability or versatility
If individual tenant upgrades are performed by moving to a new system with no tenants, then individual tenant upgrading is achieved, but the cost per tenant becomes very high
Solution Approach 1:
The move coordinator provides universal functionality by managing both individual tenant upgrades and coordinating multiple tenant migrations. It enables the system to handle various upgrade scenarios (individual tenants, multiple tenants, different target systems) through a single coordinated mechanism, reducing the need for separate expensive infrastructure for each upgrade.
Solution Approach 2:
The patent merges multiple tenant upgrade operations into a coordinated system where the move coordinator manages several tenants across different target systems simultaneously. This consolidation reduces per-tenant costs by sharing infrastructure and coordination resources across multiple upgrade operations.
4Productivity
If all tenants are upgraded simultaneously, then the upgrade process is completed in one operation, but customer-specific downtime planning becomes impossible
Solution Approach 1:
The upgrade system becomes dynamic by allowing flexible scheduling of individual tenant upgrades. The move coordinator can adjust upgrade timing for each tenant based on customer requirements, enabling downtime planning during off-peak hours or maintenance windows while maintaining overall system productivity through parallel coordination of multiple upgrades.
Data Source
AI summary
The current subject matter provides a method to upgrade an individual tenant by moving the individual tenant from a source computing system that implements an older software version to a target computing system that implements a newer software version. The movement of the individual tenant incorporates a movement of customer-specific data associated with the moved tenant. Instead of just upgrading a same multi-tenancy computing system implementing the tenant that needs to be upgraded, a new (target) multi-tenancy computing system implementing a newer software version is installed such that this tenant can be moved from the (source) multi-tenancy computing system to the new (target) multi-tenancy computing system. The data associated with the moved tenant is adjusted to new structures associated with the newer software version.