Storage Compartment Assignment for Legacy Host Upgrade Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional storage systems face challenges due to mixed operating systems and outdated firmware, leading to interoperability issues that hinder software and firmware upgrades, causing performance and availability problems and increased security risks.

Innovation Solution

Dynamically partition storage systems into compartment constructs, enabling independent upgrades by analyzing host-storage interoperability and assigning storage objects based on risk profiles, using AI techniques to optimize compartment configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If storage systems support mixed operating systems and legacy firmware, then compatibility with diverse applications is maintained, but interoperability issues arise that hinder software and firmware upgrades

Engineering Contradiction:
Improvecompatibility with diverse applicationsVSAvoidinteroperability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The storage system is divided into multiple compartment constructs, each isolated from others. Legacy hosts with outdated firmware are assigned to specific compartments, allowing the overall system to maintain compatibility with diverse applications while preventing interoperability issues from propagating across the entire system. Each compartment operates independently with its own firmware version.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The compartment construct acts as an intermediary layer between hosts and the storage system core. This intermediary structure allows legacy hosts to access storage resources while being isolated from upgrade operations, enabling firmware updates in non-legacy compartments without affecting legacy application compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If storage systems perform software and firmware upgrades, then performance and security are improved, but legacy hosts prevent upgrades due to interoperability conflicts

Engineering Contradiction:
Improveperformance and securityVSAvoidupgrade capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments hosts into legacy and non-legacy groups based on firmware compatibility. Non-legacy hosts form upgradeable compartments that can receive performance and security updates, while legacy hosts are isolated in separate compartments. This segmentation enables partial upgrades without requiring complete system homogeneity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The compartment construct dynamically adapts to mixed firmware environments by allowing different firmware versions to coexist in different compartments. This dynamic structure enables gradual modernization where upgradeable compartments can be updated independently, improving performance and security over time without being blocked by legacy hosts.

Inventive Principle:
Principle #15Dynamics

3Productivity

If legacy hosts are maintained for application compatibility, then existing applications continue to run, but they create bottlenecks that stall overall system modernization

Engineering Contradiction:
Improveapplication continuityVSAvoidmodernization timeline
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The storage system segments legacy and modern hosts into separate compartment constructs. This segmentation allows legacy applications to continue running on their designated compartments without interfering with modernization efforts in other compartments. Application continuity is maintained while parallel modernization paths can proceed independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary classification of hosts into legacy and non-legacy compartments before upgrade operations. This preliminary action identifies which hosts can be upgraded and which must remain isolated, enabling planned modernization that minimizes disruption to application continuity while accelerating the overall modernization timeline.

Inventive Principle:
Principle #10Preliminary action

4Object-affected harmful factors

If all hosts are upgraded to latest firmware, then security risks are reduced, but legacy applications that require older firmware versions become incompatible

Engineering Contradiction:
Improvesecurity risksVSAvoidapplication compatibility
Core Design Contradiction:
Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The storage system segments hosts based on firmware version requirements. Legacy applications are assigned to compartments with older firmware versions that maintain application compatibility, while non-legacy applications are assigned to compartments with latest firmware that provide enhanced security. This segmentation allows security improvements without sacrificing legacy application compatibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different compartments are assigned different firmware quality levels appropriate to their specific application requirements. Legacy application compartments maintain older firmware with proven compatibility, while modern application compartments receive latest firmware with improved security. Each compartment has locally optimized firmware quality matching its application needs.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12511039B2Dynamically assigning storage objects to compartment constructs of a storage system to reduce application risk
Publication Date: 2025.12.30 KYNDRYL INC
  • US12511039B2 patent drawing
  • US12511039B2 patent drawing
  • US12511039B2 patent drawing

AI summary

A computer-implemented method, according to one embodiment, includes mapping hosts in communication with a storage system to compartment constructs that are logical partitions of the storage system, analyzing interoperability of the hosts and the compartment constructs and defining, based on the analysis, risk profiles for applications run on the hosts. Ownership of storage objects to the compartment constructs is assigned based on the risk profiles, where each of the storage objects define a logical partition of one of the hosts and a logical partition of a storage volume of the storage system.