Reverse Kickstart File for Network Restoration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network management platforms lack the ability to effectively manage low-level or high-level restoration processes, particularly in identifying software dependencies between machines and restoring individual machine configurations, which is crucial for crash recovery and security management, and they do not provide integrated tools for restoring entire datacenters or networks.

Innovation Solution

A network management platform that generates a reverse kickstart file by updating the original kickstart file with user-supplied modifications and configuration changes, allowing for the reconstruction of systems to a current state by identifying software dependencies and using a dependency map to reorder software installations and re-initializations, enabling centralized management of restoration operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing network management platforms are used for restoration, then basic network management functions are maintained, but the ability to identify software dependencies and restore machine configurations is lost

Engineering Contradiction:
Improverestoration capabilityVSAvoiddependency management
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by capturing and storing kickstart files during the initial machine provisioning phase. These files are archived in a repository before any potential failure occurs, enabling restoration without requiring real-time dependency analysis during crisis recovery

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates and stores copies of kickstart installation files in a centralized repository. These copied files preserve the complete software dependency information and configuration states, allowing exact reproduction of machine states during restoration without needing to analyze live system dependencies

Inventive Principle:
Principle #26Copying

2Loss of information

If kickstart files are stored locally on individual machines, then installation configuration is preserved, but centralized management and recovery capability are lost

Engineering Contradiction:
Improveconfiguration preservationVSAvoidcentralized management
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system merges the distributed kickstart files from multiple machines into a centralized repository. This consolidation enables single-point management of all installation configurations while preserving the complete configuration information from each machine, eliminating the need for administrators to access individual machines

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The kickstart file repository acts as an intermediary between the provisioning platform and target machines. It stores and manages all installation configuration files centrally, allowing the provisioning platform to retrieve and use these files for restoration operations without direct machine-by-machine access

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of repair

If manual restoration processes are used, then individual machine recovery is possible, but network-wide restoration with dependency ordering is impossible

Engineering Contradiction:
Improveindividual machine recoveryVSAvoidrestoration speed
Core Design Contradiction:
Ease of repairVSProductivity

Solution Approach 1:

The system uses feedback from the dependency map analysis to automatically determine the correct restoration sequence. By analyzing software dependencies between machines and comparing against the archived kickstart files, the system generates an optimized restoration order that ensures prerequisites are restored before dependent services, enabling efficient network-wide recovery

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9940208B2Generating reverse installation file for network restoration
Publication Date: 2018.04.10 RED HAT INC
  • US9940208B2 patent drawing
  • US9940208B2 patent drawing
  • US9940208B2 patent drawing

AI summary

Embodiments relate to systems and methods for generating a reverse installation file for network restoration. A set of managed machines, such as personal computers or servers, can be managed by a network management engine communicating with the machines via a secure channel. The network management engine can scan the managed network for kickstart, or provisioning answer files, that were used to install software to network nodes at a prior time. The network management engine can access the original kickstart file, and update that file to reflect a current state of the associated machine by inserting user-supplied updates, storage configuration updates, security credentials, and/or other data. Upon a crash or other malfunction of the associated machine, the network management platform can access the reverse kickstart file and generate a restoration of that node to a current state from the reverse kickstart data.