Tenant Service Deployment via Dynamic Partitioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network service deployment methods face challenges in scalability and efficient configuration, particularly in managing co-hosted services and dynamically updating service clients with changing network service locations.
Innovation Solution
A system that employs a tenant management service and fleet management service to dynamically deploy and manage tenant services across a pool of host computers, allowing for flexible execution and routing of service requests based on various factors, including resource availability and demand, without requiring all hosts in a hostclass to execute the same services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network services are deployed to all hosts within a hostclass, then service consistency is maintained, but scalability and flexibility are limited
Solution Approach 1:
The patent segments the traditional hostclass into multiple partitions, where each partition can independently host specific network services. This allows selective deployment of services to specific partitions rather than requiring all hosts in a hostclass to run the same services, thereby improving deployment flexibility while maintaining manageable complexity through structured organization.
Solution Approach 2:
The patent introduces dynamic service routing that can redirect service requests between different partitions based on current system state, service availability, and load conditions. This dynamic approach enables the system to adapt service deployment and routing in real-time, improving versatility without requiring complex static configuration management.
2Quantity of substance
If services are co-hosted on the same hosts, then resource utilization improves, but the number of co-hosted services is limited
Solution Approach 1:
The patent divides the hosting infrastructure into multiple partitions, each capable of hosting services. This segmentation allows more services to be distributed across the infrastructure without overloading a single host, increasing the total number of co-hosted services while reducing service interference through spatial separation in the partitioning structure.
Solution Approach 2:
The patent introduces a service routing layer that acts as an intermediary between service clients and the actual service instances. This routing layer manages service requests intelligently, directing them to appropriate partitions and handling service discovery, which reduces direct service interference while enabling higher density of co-hosted services through efficient request management.
3Productivity
If partitioning is used to scale network services, then service capacity increases, but independent scaling of individual services becomes difficult
Solution Approach 1:
The patent implements fine-grained partitioning where individual services or service instances can be assigned to specific partitions. This segmentation enables independent scaling of individual services by adding or removing partitions dedicated to specific services, while maintaining the overall partitioned architecture that provides scaling capacity. Each service can be scaled independently by modifying its partition assignments without affecting other services.
Solution Approach 2:
The patent introduces dynamic partition assignment and service routing that allows services to be moved between partitions and scaled independently based on demand. The routing layer can dynamically adjust service distribution across partitions, enabling individual services to be scaled up or down independently while maintaining system-wide productivity and scaling capability.
4Loss of information
If configuration files are deployed to service clients, then service location information is provided, but maintenance becomes difficult when service deployment changes
Solution Approach 1:
The patent introduces a service routing layer that acts as an intermediary between service clients and service instances. Instead of deploying configuration files to clients, the routing layer maintains service location information centrally and provides dynamic service discovery and routing. This eliminates configuration file maintenance while ensuring clients always receive current service location information through the routing intermediary.
Solution Approach 2:
The patent implements a feedback mechanism where the service routing layer continuously monitors service deployment changes and automatically updates service routing information. Service clients query the routing layer for current service locations, and the routing layer provides real-time updates without requiring configuration file re-deployment, thereby eliminating maintenance difficulties while preserving accurate service location information.
Data Source
AI summary
Host computers in a host pool are configured to execute a tenant management service. The tenant management service receives a tenant configuration from a fleet management service that defines tenant services that are to be executed on each host computer. When tenant services are deployed, the tenant configuration may be utilized to determine whether deployed tenants are to be executed or not. The fleet management service might also provide commands at a later time to execute deployed but not executing tenant services or to terminate executing tenant services. The determination as to whether to execute or terminate tenant services may be made based, at least in part, on status information provided by the tenant management service to the fleet management service. The fleet management service might also provide a runtime configuration to tenant services in order to configure aspects of the runtime operation of the tenant services.