Redundant Software Stack in Multipath I/O Systems

Solution Overview

Problem

Existing multipath input/output (I/O) systems provide redundant physical paths but lack redundancy in the software stack, leading to potential failures and performance issues when software stack issues occur, rendering physical path redundancy ineffective.

Innovation Solution

Creating a redundant software stack by identifying a container with a valid multipath configuration and duplicating its software stack within a secondary container, establishing a separate path that bypasses the primary software stack, ensuring high availability and load balancing through identical software operations in both paths.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single software stack is used in multipath I/O systems, then device complexity is reduced, but reliability deteriorates because software stack failures cannot be mitigated by physical path redundancy

Engineering Contradiction:

Improvesoftware stack reliabilityVSAvoidsoftware stack complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a duplicate software stack in a second container that mirrors the first software stack in the first container. This copy provides redundancy at the software level, allowing failover if the primary software stack fails, thereby resolving the reliability issue without requiring complete system duplication

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent segments the software stack into separate containerized instances (first container and second container), each with its own isolated software stack. This segmentation allows independent operation and failure isolation, enabling the system to maintain reliability through distributed software instances rather than a single monolithic stack

Inventive Principle:

Principle #1Segmentation

2Reliability

If redundant physical paths are provided, then fault tolerance is improved, but the system remains vulnerable to software stack failures that affect all paths

Engineering Contradiction:

Improvefault toleranceVSAvoidsoftware failure resistance

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a duplicate software stack in a second container that mirrors the first software stack in the first container. This copy provides redundancy at the software level, allowing failover if the primary software stack fails, thereby resolving the reliability issue without requiring complete system duplication

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent extends redundancy from the physical path dimension to the software stack dimension by creating a second container with its own software stack. This adds a new dimension of redundancy, ensuring that failures in one software stack do not compromise the entire system even when physical paths are redundant

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

3Reliability

If a second container with redundant software stack is created, then reliability is improved, but device complexity increases

Engineering Contradiction:

Improvesystem availabilityVSAvoidcontainer configuration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a second container with the same software stack configuration as the first container, making the containers universal and interchangeable. This universality allows the system to maintain reliability through redundancy while managing complexity by using identical, standardized container configurations rather than custom setups

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent creates a duplicate software stack in a second container that mirrors the first software stack in the first container. This copy provides redundancy at the software level, allowing failover if the primary software stack fails, thereby resolving the reliability issue without requiring complete system duplication

Inventive Principle:

Principle #26Copying

Data Source

PatentUS10169120B2Redundant software stack

Publication Date: 2019.01.01 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

The method includes identifying, by one or more computer processors, a first container with first software stack and a valid multipath configuration, wherein the first software stack is a first path of the valid multipath configuration. The method further includes creating, by one or more computer processors, a second container, wherein the second container has the same rules as the first container. The method further includes creating, by one or more computer processes, a second software stack in the second container, wherein the software stack is a redundant software stack of the first software stack. The method further includes creating, by one or more computer processors, a second path from the first container to the second software stack, wherein the second path bypasses the first software stack.