Declarative Configuration for Consistent Computing Infrastructure Fleets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional methods of managing distributed computing infrastructures face challenges in ensuring consistency, reliability, security, and efficient deployment across multiple data centers, leading to issues such as errors, downtime, increased operational costs, and difficulty in monitoring performance and resource utilization.

Innovation Solution

A computer-implemented method utilizing software components like version control, hierarchical configuration, infrastructure orchestration, and metric management to automate and secure the deployment and configuration of computing infrastructures, including features like branching, merging, load balancing, and fault tolerance, with centralized data storage and monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration methods are used to manage computing infrastructures, then operational flexibility is maintained, but consistency and reliability deteriorate due to errors and configuration drift

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces manual mechanical configuration processes with automated software-based configuration management systems. Configuration files are automatically generated, validated, and deployed across infrastructures, eliminating human error and configuration drift while maintaining operational flexibility through version control and automated workflows.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent transforms configuration management from a manual process to an automated one by changing the state of configuration deployment. Configuration parameters are defined in code, automatically validated against templates, and deployed through automated workflows, fundamentally changing how configurations are managed across infrastructures.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If manual deployment processes are used, then operational control is maintained, but deployment efficiency and speed deteriorate

Engineering Contradiction:
Improvedeployment speedVSAvoiddeployment consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent replaces manual deployment processes with automated deployment workflows that use configuration files and orchestration systems. This substitution enables rapid, consistent deployment across multiple infrastructures while maintaining full control through versioned configuration files and automated validation processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent implements preliminary action by pre-defining configuration templates and validation rules before deployment. Configuration files are prepared, validated, and version-controlled in advance, ensuring that deployment operations can proceed rapidly and consistently without manual intervention during the actual deployment process.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If traditional access control methods are used, then implementation simplicity is maintained, but security coverage deteriorates across distributed infrastructures

Engineering Contradiction:
Improvesecurity coverageVSAvoidsecurity management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a centralized configuration management system that provides universal security controls across all distributed infrastructures. The same configuration files and access control policies are applied consistently across multiple environments, ensuring comprehensive security coverage while simplifying management through a single source of truth.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent replaces traditional distributed access control mechanisms with automated, code-based security policies. Access control rules are defined in configuration files, automatically validated, and deployed across all infrastructures, ensuring consistent security coverage while reducing manual security management complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If centralized configuration management is implemented, then consistency is improved, but system complexity increases

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments configuration management into distinct, manageable components: configuration file templates, validation rules, deployment workflows, and orchestration logic. This segmentation allows each component to be developed, validated, and maintained independently, reducing overall system complexity while achieving centralized configuration consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces configuration files and orchestration systems as intermediaries between human operators and infrastructure components. These intermediaries automate the translation of high-level configuration intent into specific deployment actions, simplifying the system architecture by abstracting away complex management details while maintaining centralized control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250335208A1Method and system for managing a fleet of computing infrastructures
Publication Date: 2025.10.30 OVH
  • US20250335208A1 patent drawing
  • US20250335208A1 patent drawing
  • US20250335208A1 patent drawing

AI summary

A computer-implemented method for managing a fleet of computing infrastructures is presented. Each computing infrastructure comprising an orchestration module configured to deploy and manage applications using declarative configuration files defining a state of each application, associated dependencies, and components. The method includes storing a configuration file for each of the computing infrastructures; managing data of the configuration files in a hierarchical manner; monitoring a version control system module for updates to the configuration files, defining the configuration of the computing infrastructures to include interactions between the components, and applying the updated configuration files to the computer infrastructures; and generating a template for the declarative configuration files that defines the configuration and interactions of components and create and store artifacts of the declarative configuration files. Therefore, at predetermined intervals, the configuration module automatically deploys the configurations by accessing the stored artifacts and executing the declarative configuration files of the computing infrastructures.