Cloud Infrastructure Testing Tags for On-Demand Experiment Generation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Establishing and maintaining testing operations for cloud infrastructure resources is complex due to their dynamic and distributed nature, making it difficult to predict and control variables, manage dependencies, and coordinate testing across interconnected services, leading to inefficiencies and resource wastage.

Innovation Solution

Implementing testing tags as metadata for infrastructure resources to encode testing information, enabling automatic generation of experiments using a testing management device that scans for resources with these tags, obtains relevant information, and generates experiments on-demand, thus optimizing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If testing operations are established for cloud infrastructure resources, then testing coverage is improved, but device complexity and resource consumption increase due to the dynamic and distributed nature of cloud infrastructure

Engineering Contradiction:

Improvetesting coverageVSAvoidtesting operation management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The testing management device automatically scans for infrastructure resources with testing tags, retrieves their information, and generates appropriate testing experiments without manual intervention. This self-service mechanism reduces the complexity of managing testing operations across dynamic cloud infrastructure while maintaining comprehensive testing coverage.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system uses testing tags as parameters to identify and differentiate infrastructure resources requiring testing. By changing the parameter representation from manual configuration to tag-based identification, the system simplifies the management of testing operations while improving coverage across diverse cloud resources.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If comprehensive testing is performed across all infrastructure resources, then testing thoroughness is improved, but resource wastage increases due to generating experiments for resources that do not require testing

Engineering Contradiction:

Improvetesting thoroughnessVSAvoidprocessing and computing resource wastage

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system applies different qualities of testing by using tags to identify which infrastructure resources require testing and which do not. This local differentiation ensures that processing and computing resources are allocated only to resources that need testing, preventing waste while maintaining thoroughness for relevant resources.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

Instead of performing testing operations on all infrastructure resources (excessive action), the system performs testing only on resources marked with appropriate tags (partial action). This approach maintains testing thoroughness for necessary resources while avoiding resource wastage on unnecessary testing operations.

Inventive Principle:

Principle #16Partial or excessive action

3Productivity

If testing experiments are generated on-demand based on tag scanning, then resource efficiency is improved, but time consumption increases due to the scanning and generation process

Engineering Contradiction:

Improveresource efficiencyVSAvoidtesting experiment generation time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The testing management device performs preliminary scanning of infrastructure resources for testing tags before generating testing experiments. This preliminary action identifies target resources in advance, allowing the system to generate only the necessary experiments efficiently, thus improving resource efficiency while minimizing time consumption compared to generating experiments for all resources.

Inventive Principle:

Principle #10Preliminary action

4Measurement precision

If manual management of testing operations is used, then control precision is improved, but productivity decreases due to the complexity of coordinating testing across interconnected services

Engineering Contradiction:

Improvetesting control precisionVSAvoidtesting operation coordination efficiency

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The testing management device acts as an intermediary between infrastructure resources and testing execution. It automatically scans for resources with testing tags, retrieves their information, and generates appropriate experiments, thereby maintaining control precision while significantly improving the productivity of coordinating testing across interconnected cloud services.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12423174B2Tag-facilitated testing for cloud infrastructure

Publication Date: 2025.09.23 CAPITAL ONE SERVICES LLC

AI summary

In some implementations, a device may scan infrastructure of a cloud computing system for one or more infrastructure resources having respective tags associated with testing. The device may obtain for each infrastructure resource of the one or more infrastructure resources and based on the tags, testing information for respective infrastructure resources of the one or more resources. The device may generate, via a testing platform, experiments for respective infrastructure resources based on the testing information. The device may cause the experiments to be performed for the one or more infrastructure resources.