Configuration Management Client for Computing Infrastructure

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data center infrastructure management systems face challenges in maintaining customized configurations due to unique hardware and software setups, making it difficult to manage interrelated devices and handle dependencies between resources in a standardized manner.

Innovation Solution

A computing infrastructure management system that uses a configuration management client to translate manifest files into directives based on resource dependencies, ensuring that resources are provisioned in a sequenced and consistent manner across multiple computing devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If customized configurations are implemented to meet unique enterprise resource needs, then adaptability is improved, but device complexity increases

Engineering Contradiction:

Improvecustomization capabilityVSAvoidconfiguration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The configuration management is segmented into discrete resources with explicit dependencies. Each resource (computing device, storage device, network device) is treated as an independent unit that can be individually configured and managed, allowing customization without overwhelming complexity. The manifest file divides the overall configuration into manageable resource units.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system dynamically determines the provisioning sequence based on resource dependencies rather than using a fixed configuration order. The configuration management client automatically analyzes the dependency relationships and adjusts the provisioning sequence accordingly, enabling adaptability to different enterprise needs while maintaining systematic control.

Inventive Principle:

Principle #15Dynamics

2Ease of manufacture

If standardized converged infrastructures are introduced, then ease of manufacture is improved, but adaptability worsens

Engineering Contradiction:

ImprovestandardizationVSAvoidcustomization capability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The manifest file format and configuration management client serve universal purposes across different enterprise configurations. The same standardized tools can manage diverse computing infrastructures by simply changing the manifest content, not the management mechanism. This allows standardized processes to handle customized requirements.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system maintains standardized infrastructure components but allows customization through parameter changes in the manifest file. Enterprise-specific requirements are expressed as configurable parameters (resources and their dependencies) rather than requiring different infrastructure architectures, enabling standardization with adaptability.

Inventive Principle:

Principle #35Parameter changes

3Ease of operation

If manual configuration management is used for each computing device, then ease of operation is maintained, but productivity decreases

Engineering Contradiction:

Improvemanual controlVSAvoidconfiguration speed

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The resource provisioning sequence is determined in advance through automatic dependency analysis before actual provisioning begins. The configuration management client pre-calculates the correct order of operations based on the manifest file, eliminating the need for manual sequencing while ensuring correctness. This preliminary analysis step enables automated execution without sacrificing operational correctness.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The configuration management client acts as an intermediary between the manifest file (configuration specification) and the actual resource provisioning process. It automatically translates the high-level resource dependencies into a detailed provisioning sequence, bridging the gap between simple configuration specification and complex execution without requiring manual intervention.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Productivity

If automated resource provisioning is implemented, then productivity is improved, but difficulty of detecting and measuring increases

Engineering Contradiction:

Improveprovisioning speedVSAvoiddependency analysis complexity

Core Design Contradiction:

ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The system provides feedback mechanisms to track and verify resource provisioning status. The configuration management client monitors the provisioning process and can detect issues in the automated sequence, allowing measurement and verification of the automated process outcomes without manual intervention in the complex dependency analysis.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS10257026B1System and method to manage interrelated devices in a computing infrastructure

Publication Date: 2019.04.09 EMC IP HLDG CO LLC

AI summary

A computing infrastructure management system includes a processing system and a memory for storing a configuration management client, which is executed by the processing system to receive a manifest file associated with a computing infrastructure comprising a plurality of computing devices each having one or more resources. Using the received manifest file, the client translates the manifest file by arranging one or more directives of the manifest file according to one or more dependencies of each resource relative to the resources of the other computing devices, and provisions the resources of each computing device using the translated manifest file.