Idempotent Cloud Infrastructure Management via Describe State Module

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The management and administration of increasingly complex distributed computing systems have become inefficient, with traditional approaches to automated and semi-automated management and administration becoming impractical due to high computational overheads and complexity.

Innovation Solution

A cloud-infrastructure-management service that includes a describe state module, which generates a configuration file specifying the current state of a target server, allowing users and upstream management systems to define and deploy cloud-based infrastructure such as virtual networks, virtual machines, load balancers, and connection topologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional approaches to automated and semi-automated management and administration are used, then existing management functionalities can be implemented, but computational overheads become excessively high and complexity increases significantly

Engineering Contradiction:

Improveautomation of management and administrationVSAvoidcomplexity of management and administration

Core Design Contradiction:

Extent of automationVSDevice complexity

Solution Approach 1:

The patent uses idempotent configuration specifications that can be repeatedly applied without changing the system state. The describe function generates configuration files that copy the desired state definition, and the apply function repeatedly applies this same specification until the target server reaches the desired state, eliminating the need for complex state tracking and comparison mechanisms.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system automatically generates configuration specifications by calling the describe function on target servers, which retrieves current state information and converts it into actionable configuration files. This self-service approach eliminates the need for manual configuration creation and reduces computational overhead by automating the specification generation process.

Inventive Principle:

Principle #25Self-service

2Extent of automation

If traditional approaches to automated and semi-automated management and administration are used, then existing management functionalities can be implemented, but time and cost become impractical

Engineering Contradiction:

Improveautomation of management and administrationVSAvoidtime required for management and administration

Core Design Contradiction:

Extent of automationVSLoss of time

Solution Approach 1:

The describe function is called beforehand to generate the complete configuration specification before any changes are applied. This preliminary action captures the desired state definition once, and the same specification is then repeatedly applied to the target server without needing to re-analyze the current state, significantly reducing the time required for repeated management operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system creates a reusable configuration specification file that can be applied multiple times. Instead of re-generating and re-processing configuration details on each application cycle, the system copies the pre-generated specification and applies it repeatedly until the desired state is achieved, eliminating redundant computational time.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If cloud infrastructure is deployed using manual configuration methods, then infrastructure can be set up, but scalability and maintainability are limited

Engineering Contradiction:

Improvescalability of cloud infrastructureVSAvoidcomplexity of infrastructure management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments infrastructure management into independent components: the describe function that retrieves server state, the configuration specification that defines desired state, and the apply function that enforces the specification. This segmentation allows each component to be independently developed, tested, and scaled, improving overall system scalability while reducing management complexity through modular design.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The idempotent configuration specification acts as a reusable template that can be applied across multiple servers and infrastructure components. By copying and reusing the same specification definition, the system achieves consistent infrastructure deployment at scale without increasing management complexity, as the same specification logic applies universally.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS20250077254A1Methods and systems that manage cloud-computing infrastructure by idempotent application of data specifications

Publication Date: 2025.03.06 VMWARE INC

AI summary

The current document is directed to a cloud-infrastructure-management service that allows users and upstream management systems to define and deploy infrastructure, such as virtual networks, virtual machines, load balancers, and connection topologies, within cloud-computing systems. The cloud-infrastructure-management service includes a describe state module that includes a describe function that generates a configuration file that specifies the current state of a target server running a server-side cloud-infrastructure-management service.