Multi-tenancy Workload Deployment via Shared System Record
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a cloud environment with multi-tenancy configuration, efficiently managing and deploying workloads across different service plans and resource pools while maintaining data integration and migration capabilities is challenging due to the complexity of managing multiple tenants and resource allocation.
Innovation Solution
A method and system for deploying workloads in a multi-tenancy computing environment using a single shared system-wide record, which generates and stores tenant IDs and plan IDs, allowing for resource pooling and dynamic allocation based on service plan updates, enabling seamless migration and integration of tenants across different resource pools.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple tenants are managed separately in a cloud environment with multi-tenancy configuration, then each tenant can have isolated workspaces and projects, but the complexity of managing multiple tenants and resource allocation increases significantly
Solution Approach 1:
The patent merges the management of multiple tenants into a single shared system-wide record instead of maintaining separate records for each tenant. This consolidation reduces management complexity while maintaining tenant isolation through the tenant ID field within the shared record structure.
Solution Approach 2:
The shared system-wide record serves multiple functions simultaneously: it stores tenant information, service plan details, resource pool associations, and workspace metadata. This universal record structure eliminates the need for multiple separate management systems.
2Adaptability or versatility
If a new workspace is created with all related job artifacts in a new virtual machine instance when a tenant changes service plans, then the tenant gets the required resources for the new plan, but the deployment process becomes time-consuming and resource-intensive
Solution Approach 1:
The system pre-establishes resource pools associated with different service plans in advance. When a tenant changes service plans, the system can quickly allocate resources from the pre-configured pool corresponding to the new plan, avoiding the need to create everything from scratch.
Solution Approach 2:
The system dynamically associates tenants with resource pools based on their current service plan. This dynamic association allows for rapid reassignment of resources when service plans change, reducing deployment time while maintaining flexibility.
3Reliability
If artifacts are exported and imported for each job and project during migration, then data integration capabilities are maintained, but the migration process becomes excessively complex and time-consuming
Solution Approach 1:
The patent combines all job artifacts and project data into a single tenant record within the shared system-wide record. This consolidation allows for atomic migration operations where entire tenant datasets can be moved as one unit rather than requiring separate export-import operations for each artifact.
Solution Approach 2:
The system uses the shared system-wide record as a master copy that can be efficiently replicated and migrated. This single source of truth approach simplifies migration compared to managing multiple separate artifact files that would each need to be exported and imported.
Data Source
AI summary
An approach for deploying workload in a multi-tenancy computing environment is provided. The approach generates, by one or more computer processors, a tenant ID and a plan ID for a tenant based, at least in part, on a tenant registration request. The approach stores, by one or more computer processors, the tenant ID and the plan ID into a shared system record. The approach receives, by one or more computer processors, a request to update a first tenant service plan. The approach determines, by one or more computer processors, one or more resource pools supporting a second tenant service plan based at least in part, on an association between the tenant ID and the plan ID. The approach deploys, by one or more computer processors, one or more resources from the one or more resource pools supporting the second tenant service plan.