Tag-Based Compute Resource Allocation in Cloud Hosts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud automation systems, the conventional method of providing additional resources to a user group requires synchronization between two administrators, which is time-consuming and inefficient.

Innovation Solution

A tag-based control system allows a single administrator to modify compute resources by adding or deleting tags associated with hosts and reservations, enabling dynamic resource allocation without the need for synchronization between host-side and user-side administrators.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If two administrators synchronize to provide increased resources to a user group, then resource allocation reliability is improved, but the time required for resource allocation increases

Engineering Contradiction:
Improveresource allocation reliabilityVSAvoidresource allocation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces tags as an intermediary mechanism that enables automated resource allocation. Instead of requiring direct synchronization between host-side and user-side administrators, tags serve as a common language that both parties use to define resource requirements and availability. The system automatically matches user tag requirements with host tag capabilities, eliminating the need for manual coordination while maintaining allocation reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service resource allocation through automated tag matching. When resources become available, the system automatically detects the match between host tags and user tags, and provisions resources without requiring administrator intervention. This self-service mechanism reduces allocation time while maintaining reliability through automated validation of tag compatibility.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If a single administrator manages resource allocation without synchronization, then the ease of operation is improved, but the reliability of resource allocation may deteriorate

Engineering Contradiction:
Improveadministrator operation simplicityVSAvoidresource allocation reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system enables a single administrator to perform resource allocation by simply adding or removing tags from hosts or user groups. The automated tag-matching engine then handles the complex logic of resource provisioning, capacity validation, and compatibility checking. This approach maintains ease of operation while ensuring reliability through automated validation mechanisms that prevent invalid allocations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides automated feedback through the tag-matching mechanism. When a single administrator modifies tags, the system automatically validates the changes against existing resource allocations and capacity constraints, providing immediate feedback on whether the modification is valid. This feedback loop ensures reliability by preventing conflicting or invalid resource allocations while maintaining operational simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10936373B2Tag-based control of hosted compute resources
Publication Date: 2021.03.02 VMWARE INC
  • US10936373B2 patent drawing
  • US10936373B2 patent drawing
  • US10936373B2 patent drawing

AI summary

A computer system includes hosts for hosting virtual infrastructures. Compute resources provided by the hosts are allocated to user groups (e.g., departments, projects) in the form of reservations that define amounts of resources available to the user groups. Tags can be associated with both hosts and with reservations. A reservation has access to resources of a host having a host tag that matches a user tag associated with the reservation. Thus, to make a host available to a reservation, either 1) a tag can be added to the reservation to match a tag of the host, or 2) a tag can be added to the host to match a tag of a reservation. This can be more convenient than a case in which both a host and a reservation must be configured to give the reservation access to the host.