Version Management System for DevOps Restoration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional system development methods struggle to maintain reliable system configurations in fast-paced DevOps environments where systems are updated frequently, leading to potential function fallbacks during restoration from issues.

Innovation Solution

A version management system that generates and filters system configuration patterns based on version histories, excluding those with high function fallback rates and identifying configurations with sufficient similarity to past operational records for restoration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system is restored to past versions with successful operational track records, then system availability is maintained, but function fallback occurs in high-frequency update environments

Engineering Contradiction:
Improvesystem availabilityVSAvoidfunction provision
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent changes the selection parameters from simple operational track record duration to a comprehensive evaluation including function fallback rate calculation. Instead of merely selecting versions based on how long they operated successfully, the system now evaluates candidate versions by calculating their function fallback rates against predefined necessary functions, thereby adapting the restoration process to high-frequency update environments where functional compatibility is critical

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent performs preliminary analysis of candidate restoration versions by pre-calculating their function fallback rates before actual restoration occurs. The system generates a list of candidate versions, evaluates each against necessary functions to determine their fallback rates, and only selects versions that meet the function provision threshold. This preliminary evaluation prevents function loss before restoration is executed

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If conventional restoration methods are used in DevOps environments, then operational simplicity is maintained, but function fallback rate increases

Engineering Contradiction:
Improverestoration process simplicityVSAvoidfunction provision
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements an automated restoration selection system that performs self-evaluation of candidate versions. The system automatically generates candidate version lists, calculates function fallback rates for each candidate against predefined necessary functions, and selects the appropriate restoration target without manual intervention. This self-service approach maintains operational simplicity while ensuring functional reliability through automated evaluation

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces feedback mechanisms where the system evaluates candidate restoration versions by calculating their function fallback rates based on predefined necessary functions. This feedback loop provides information about which candidate versions will maintain required functions, enabling the system to make informed restoration decisions that balance simplicity with reliability

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10747529B2Version management system and version management method
Publication Date: 2020.08.18 HITACHI LTD
  • US10747529B2 patent drawing
  • US10747529B2 patent drawing
  • US10747529B2 patent drawing

AI summary

A version management system includes a storage device that retains information on version histories of services each providing a predetermined function in a predetermined system, and an arithmetic device that executes a process of generating, based on the information on the version histories, a list of combination patterns of versions of the respective services as system configurations of the system, a process of excluding, from the patterns in the list, the pattern having a function fallback rate equal to or above a predetermined level, the function fallback rate being based on predefined necessary functions, and a process of identifying, in the patterns remaining in the list after the exclusion, the pattern with the highest similarity to a system configuration having a predetermined past operational track record, as a system configuration to which the system is to be restored upon occurrence of a problem.