Cloud Instance Allocation Using Spare Capacity Reallocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud service providers face inefficiencies due to excess computing resources sitting idle, while potential clients lack access to affordable computing resources with service guarantees, leading to wasted costs and unsatisfied demands.
Innovation Solution
A cloud resources allocation system (CAS) that maximizes resource usage by matching clients with spare computing capacity through on-demand and spare allocations, offering flexible pricing and service guarantees, and utilizing a system (SAS) to manage instance allocation and reallocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cloud service providers allocate computing resources to clients with service guarantees, then client reliability is improved, but resource utilization efficiency deteriorates due to excess capacity sitting idle
Solution Approach 1:
The patent segments cloud computing resources into two distinct categories: subscribed-to instances with service level guarantees and spare instances without guarantees. This segmentation allows the system to maintain reliable service for subscribed clients while separately managing excess capacity through spot instances, thereby resolving the contradiction between reliability and resource utilization efficiency
Solution Approach 2:
The patent introduces spot instances as an intermediary mechanism that bridges the gap between subscribed-to instances and idle spare capacity. Spot instances serve as a mediator that allows cloud providers to monetize excess resources while maintaining service guarantees for subscribed clients, thus improving overall resource utilization without compromising reliability
2Productivity
If cloud service providers make spare instances available without service guarantees, then resource utilization is improved, but client trust and service quality deteriorate
Solution Approach 1:
The patent applies local quality by providing different service quality levels to different client needs. Subscribed-to instances receive high-quality service with uptime guarantees, while spot instances provide lower-quality service without guarantees. This differentiation allows the system to maximize resource utilization while maintaining service quality for clients who require it
Solution Approach 2:
The patent changes the service guarantee parameter for different instance types. Subscribed-to instances have service level agreements ensuring availability, while spot instances operate without such guarantees. This parameter change enables the system to utilize spare capacity effectively while maintaining trust and service quality for subscribed clients
3Reliability
If cloud service providers reserve computing capacity for subscribed clients, then service reliability is improved, but cost efficiency deteriorates due to paying for unused capacity
Solution Approach 1:
The patent implements discarding and recovering by allowing cloud providers to discard subscribed-to instances that are not fully utilized and recover the underlying physical resources. These recovered resources are then made available as spare capacity for spot instances, enabling the provider to maintain service reliability for subscribed clients while reducing costs by utilizing discarded capacity for other purposes
Data Source
AI summary
Disclosed herein are various embodiments for a cloud resources allocation system. An embodiment operates by determining that an application requests a plurality of instances to execute across one or more processors of a cloud services platform. One or more spare instances are requested to fulfill at least a portion of the plurality of instances, and an allocation of at least a subset of the requested one or more spare instances is received. An execution of the application is directed to the allocated subset of the one or more spare instances, including a first spare instance. A notification is received from the cloud services platform that the first spare instance is to be reallocated to a different process. A subsequent execution of the application is redirected to an on demand instance of the cloud services platform.