Blockchain Child Ledger Prevents Configuration Drift

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Configuration drift across multiple environments becomes increasingly difficult to manage as the number of environments and underlying components grow, with existing techniques failing to maintain consistency and manage subsequent changes effectively.

Innovation Solution

Implementing a blockchain-based system that creates a child ledger for each new environment and updates a master ledger when smart contract conditions are met, initiating deployments to all managed environments, thereby ensuring consistency and automating updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional configuration management methods are used across multiple environments, then initial setup is simple, but configuration drift occurs and consistency cannot be maintained as environments and components increase

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

Solution Approach 1:

The system segments configuration management into environment-specific child ledgers (one per environment) and a hierarchical structure that links them to a parent ledger. This segmentation allows each environment to be managed independently while maintaining overall consistency through the hierarchical relationship, preventing configuration drift without requiring complex centralized control of every detail.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system merges individual child ledgers into a parent ledger through cryptographic hashing, creating a unified view of configuration across all environments. This combining approach maintains consistency by ensuring that changes in any child ledger are reflected in the parent ledger, providing a single source of truth while preserving environment-specific autonomy.

Inventive Principle:
Principle #5Merging (Combining)

2Productivity

If manual configuration management is used, then flexibility is high, but time consumption and human error increase

Engineering Contradiction:
Improvedeployment speedVSAvoidtime for configuration management
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service configuration management where the blockchain network automatically validates, propagates, and enforces configuration changes across all environments. Smart contracts automatically execute deployment workflows when configuration changes are approved, eliminating manual intervention and reducing both time consumption and human error while maintaining flexibility through automated decision rules.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements continuous feedback mechanisms where the blockchain network monitors configuration states across all environments and automatically detects drift. When configuration changes are proposed, the system provides feedback through consensus validation and smart contract execution, ensuring that only valid changes are propagated, thereby accelerating deployment while reducing errors.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If centralized configuration control is implemented, then consistency is maintained, but adaptability to environment-specific needs decreases

Engineering Contradiction:
Improveenvironment-specific customizationVSAvoidconfiguration synchronization
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The hierarchical ledger structure segments configuration data into environment-specific child ledgers that can be customized independently while maintaining linkage to a parent ledger. This allows each environment to adapt its configuration to specific needs while the hierarchical relationship ensures that fundamental consistency is maintained through the parent-child linkage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies local quality by allowing each child ledger to have environment-specific configuration details tailored to local requirements, while the parent ledger maintains global configuration standards. This ensures that each environment can be optimized for its specific purpose without losing overall configuration synchronization through the hierarchical structure.

Inventive Principle:
Principle #3Local quality

4Productivity

If configuration changes are propagated manually to each environment, then control is precise, but productivity and scalability are limited

Engineering Contradiction:
Improvedeployment efficiencyVSAvoiddeployment orchestration
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service deployment where the blockchain network automatically propagates configuration changes from the parent ledger to all child ledgers through smart contract execution. This automated propagation mechanism eliminates manual intervention, dramatically improving productivity and scalability while the standardized smart contract framework manages deployment orchestration complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements universal deployment orchestration through smart contracts that can handle multiple environments and configuration types through a single standardized mechanism. This multi-functional approach allows the same deployment framework to serve diverse environments, improving productivity while managing complexity through standardization rather than environment-specific procedures.

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

Data Source

PatentUS10997150B2Configuration drift prevention across multiple systems using blockchain
Publication Date: 2021.05.04 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10997150B2 patent drawing
  • US10997150B2 patent drawing
  • US10997150B2 patent drawing

AI summary

An example operation may include one or more of creating a child ledger for each new environment that is setup, updating a master ledger when a smart contract condition is met, and when the master ledger is updated, initiating deployment of an update to a plurality of managed environments.