Tag-Based Resource Quotas in Cloud Infrastructure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud infrastructure environments lack the ability to restrict resource usage at a granular level, leading to potential overconsumption of resources by authorized users, as existing mechanisms only allow for high-level control without visibility into specific user, resource, or container-level usage.
Innovation Solution
Implementing tag-based resource limits and quotas that allow administrators to set fine-grained restrictions on resource usage across multiple containers, enabling compartment administrators to limit consumption and define acceptable use boundaries, with clients and customers customizing these limits via consoles, SDKs, or APIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If high-level resource control mechanisms are used, then ease of operation is improved, but manufacturing precision (granularity of control) deteriorates
Solution Approach 1:
The patent segments resource control into multiple hierarchical levels: account-level quotas, compartment-level quotas, and tag-level quotas. This segmentation allows administrators to apply different granularity levels to different resource groups, achieving both ease of operation at higher levels and precise control at lower levels without requiring a single control mechanism to handle all scenarios.
2Manufacturing precision
If fine-grained resource limits are implemented, then manufacturing precision (control granularity) is improved, but device complexity increases
Solution Approach 1:
The patent implements a universal tag-based quota system that can be applied across multiple resource types, compartments, and accounts. The same tag mechanism serves multiple functions: organizing resources, applying quotas, and enabling hierarchical control. This multi-functionality reduces the need for separate control mechanisms for different scenarios, thereby limiting the increase in system complexity while maintaining fine-grained control capabilities.
3Measurement precision
If resource usage is monitored at container level, then measurement precision is improved, but loss of time (processing overhead) increases
Solution Approach 1:
The patent merges container-level resource usage monitoring with the existing tag-based quota system. Instead of implementing a separate monitoring mechanism, the system combines usage data collection with the quota enforcement infrastructure already in place. This merging allows precise measurement of resource usage at the container level while reusing existing processing pipelines, thereby reducing the additional processing overhead that would result from a completely separate monitoring system.
Data Source
AI summary
Systems and methods described herein support tag based resource limits or quotas in a cloud infrastructure environment. Cloud administrators do not generally have the ability to restrict resource usage in existing clouds. Granting a user permission to create resources allows them to create any number of resources up to a predefined account limit. Tags are associated with resources for allowing administrators to restrict a user's resource usage to the appropriate level by allowing fine-tuned cost control. A usage of resources in a tenancy associated with a resource tag corresponding to a request characteristic of a request to provision a resource is determined and compared against a plurality of tag-based quotas, wherein the request to provision the resource is dropped based on the determined usage exceeding one of the plurality of tag-based quotas.