Compute Instance Attribute Selection Across Regions and Architectures

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud computing providers face challenges in launching compute instances when user-specified attributes cannot be met, even if functional equivalents are available in different regions or architectures, leading to instance creation failures.

Innovation Solution

A system that configures compute instances with system-selected attribute values based on user-specified criteria, ensuring availability and resource sufficiency for launching multiple instances with consistent attributes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the cloud computing service requires users to specify exact attribute values for compute instances, then the user's control over instance configuration is improved, but the ability to launch instances fails when exact values are unavailable in the requested region

Engineering Contradiction:

ImproveUser control over instance configurationVSAvoidInstance launch success rate

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system changes the parameter specification approach from requiring exact attribute values to accepting constraint criteria. When a user requests a compute instance with specific attributes (e.g., processor type, memory), the system evaluates available instances against these constraints and automatically selects the best matching instance, allowing parameter flexibility while maintaining user intent.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The system enables self-service by automatically selecting compute instance attributes that satisfy user-defined constraints without requiring manual specification of every parameter. The cloud computing service autonomously evaluates available instances, compares them against user criteria, and launches the most appropriate instance, reducing user burden while ensuring reliability.

Inventive Principle:

Principle #25Self-service

2Adaptability or versatility

If the system allows flexible attribute selection for compute instances, then the availability of functional equivalents across regions is improved, but the consistency of instance attributes may be compromised

Engineering Contradiction:

ImproveAvailability of functional equivalentsVSAvoidInstance attribute consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system transforms rigid attribute matching into flexible constraint-based selection. Instead of requiring exact matches for all attributes, the system identifies functional equivalents by evaluating instances against user-defined constraint criteria, allowing the same logical specification to map to different physical instances across regions while maintaining attribute consistency within the constraint framework.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The constraint-based selection mechanism serves multiple functions: it enables flexible matching across different regions and processor architectures, maintains attribute consistency through systematic evaluation, and adapts to varying availability conditions. This universal approach allows the same user specification to successfully launch instances regardless of regional differences.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If the cloud computing service launches instances with system-selected attribute values, then the productivity of instance deployment is improved, but the user's ability to specify exact configurations is reduced

Engineering Contradiction:

ImproveInstance deployment speedVSAvoidUser configuration control

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The system applies partial user specification combined with automatic attribute selection. Users define constraint criteria for the attributes they care about, and the system automatically selects specific values for those attributes while maintaining user-defined constraints. This partial action approach accelerates deployment by eliminating manual configuration of all parameters while preserving user control over critical attributes.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system incorporates feedback mechanisms where user constraints guide automatic attribute selection. The cloud computing service evaluates available instances against user-defined criteria, selects the best matching instance, and can provide feedback to users about the selected configuration. This feedback loop maintains user control while enabling rapid automated deployment.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12474935B2System selected fungible configurable attributes for a compute instance

Publication Date: 2025.11.18 ORACLE INT CORP

AI summary

Techniques for configuring and creating a compute instance are disclosed. A system may receive a request to launch a compute instance where the compute instance defined by a configurable attribute, The request comprises one or more user-specified criteria for the configurable attribute without including a specific value for the configurable attribute. The system determines a set of candidate values for the configurable attribute. The system selects the specific value for the configurable attribute from the set of candidate values for the configurable attribute, based on the one or more user-specified criteria. The system stores the specific value in association with the configurable attribute; and launches the compute instance based on the system-selected specific value for the configurable attribute of the compute instance.