Storage Subsystem Automatic Component Configuration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing storage subsystems require extensive user interactions for expanding storage capacity, particularly when adding new disk drives, as users must manually configure RAID types and create storage volumes, which is inefficient.

Innovation Solution

A daemon within the RAID controller automatically determines whether a new component is a host computer or a disk drive and allocates it based on predefined policy rules, minimizing user intervention by managing storage device allocation and expansion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual configuration of new disk drives is performed by user, then storage capacity can be expanded, but extensive user interactions are required which reduces efficiency

Engineering Contradiction:

Improvestorage capacity expansion efficiencyVSAvoiduser interaction complexity

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The storage subsystem automatically detects new disk drives and performs configuration operations without requiring user intervention. The system self-services by autonomously creating storage pools, configuring RAID types, and allocating storage volumes when new components are added, thereby eliminating the need for extensive manual user interactions while maintaining storage capacity expansion capability

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system pre-configures policy rules that automatically determine how new storage devices should be allocated and configured. By establishing these allocation policies in advance, the system can immediately and automatically configure new disk drives upon their addition, eliminating the need for manual step-by-step configuration and significantly improving expansion efficiency

Inventive Principle:

Principle #10Preliminary action

2Extent of automation

If automatic configuration is implemented, then user interaction is minimized, but system complexity increases due to automated detection and allocation mechanisms

Engineering Contradiction:

Improveconfiguration automation levelVSAvoidautomated configuration system complexity

Core Design Contradiction:

Extent of automationVSDevice complexity

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

A daemon process acts as an intermediary between the storage subsystem and new disk drives. This intermediary automatically detects added drives, determines their type (host computer or disk drive), and coordinates the configuration process according to predefined policies, thereby managing system complexity through a dedicated coordination layer

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If storage devices are allocated based on policy rules, then storage resources are optimized, but determination of new component type adds processing steps

Engineering Contradiction:

Improvestorage allocation flexibilityVSAvoidcomponent detection process complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies different allocation policies based on the local characteristics and requirements of different storage devices. By determining the type of each new component (host computer or disk drive) and applying appropriate allocation strategies specific to that component type, the system achieves flexible and optimized storage resource allocation while managing detection complexity through type-specific handling

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS7689797B2Method for automatically configuring additional component to a storage subsystem

Publication Date: 2010.03.30 X CORP

AI summary

A method for automatically configuring a newly added component to a storage subsystem is disclosed. In response to a new component being connected to a storage subsystem, a determination is made whether or not the new component is a host computer or a disk drive. If the new component is a host computer, the new component is added to the storage subsystem as a host computer when the number of computer systems that can be supported by the storage subsystem has not yet been exceeded. If the new component is a disk drive, the new component is allocated to a pool of storage devices within the storage subsystem, wherein some of the pool of storage devices are held in reserve while some of the pool of storage devices are allocated to a host computer based on policy rules.