Automated Container Boot Sequence Configuration for Disaster Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current disaster recovery processes for cloud native container-based environments are complex and error-prone, as they require manual configuration of boot sequences, which is insufficient for dynamic environments and does not account for cross-dependencies between containerized applications.

Innovation Solution

An automated system that uses a recommendation engine to determine the optimal boot sequence and priority of containers based on parameters such as container type, network configuration, manual restarts, and system configuration, providing a graphical interface for administrators to review and modify the recommendations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration of boot sequences is used in traditional IT systems, then administrators can control the boot order of virtual machines, but the process becomes complex, tedious, and error-prone when applied to container systems with dynamic environments and cross-dependencies

Engineering Contradiction:
Improveboot sequence configurationVSAvoiddisaster recovery process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system enables self-service automation by having the disaster recovery system automatically determine and configure boot sequences based on container dependencies, eliminating the need for manual administrator intervention in complex boot order configuration while maintaining control and accuracy

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system dynamically adjusts boot sequence parameters based on real-time analysis of container dependencies, network configurations, and system state, transforming the static manual configuration approach into a dynamic automated process that adapts to changing environmental conditions

Inventive Principle:
Principle #35Parameter changes

2Extent of automation

If semi-automatic recovery operations using scripts are performed, then some automation is achieved, but the approach remains insufficient for dynamic container environments and does not adequately handle cross-dependencies between containerized applications

Engineering Contradiction:
Improverecovery operationsVSAvoiddisaster recovery process
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The system performs preliminary analysis of container dependencies, network configurations, and application relationships before executing recovery operations, establishing an accurate boot sequence in advance that accounts for all cross-dependencies, thereby ensuring reliable recovery without requiring complex runtime adjustments

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system incorporates feedback mechanisms that continuously monitor container state, dependency satisfaction, and recovery progress, automatically adjusting the boot sequence execution based on real-time conditions to maintain high reliability in dynamic environments

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11416342B2Automatically configuring boot sequence of container systems for disaster recovery
Publication Date: 2022.08.16 EMC IP HLDG CO LLC
  • US11416342B2 patent drawing
  • US11416342B2 patent drawing
  • US11416342B2 patent drawing

AI summary

Embodiments for systems and methods of providing a boot order for containers in a cloud native application environment by collecting container environment data from a first container site; determining dependencies and connections between the containers and applications executed within the containers based on a number of system parameters; calculating a recommended order for booting or rebooting the containers during a disaster recovery process; and communicating the recommended order to a system administrator through a graphical user interface (GUI) for acceptance or modification by the system administrator.