Golden Configuration Replication for Blade Storage Subsystems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data storage subsystems in blade configurations face challenges in maintaining consistency across multiple locations, as existing methods require manual configuration and boot-up sequences, which can be time-consuming and prone to errors.
Innovation Solution
A "golden" configuration file is created and used to logically configure server blades in a data storage subsystem, mapping World Wide Names (WWNs) to slots, enabling consistent storage access across multiple locations by employing a management module to collect and transfer WWN-to-slot information, and allocating logical volumes accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual configuration and boot-up sequences are used at each blade system, then storage subsystem configurations can be customized for particular circumstances, but consistency across multiple locations cannot be maintained and the process is time-consuming and error-prone
Solution Approach 1:
A 'golden' configuration file is created in advance that contains the desired storage subsystem configuration. This pre-prepared configuration file is then automatically applied to multiple blade systems, eliminating the need for manual configuration at each location and ensuring consistency across all systems.
Solution Approach 2:
The configuration from one blade system (the 'golden' configuration) is copied and applied to other blade systems. The system automatically replicates the storage subsystem configuration, logical volume assignments, and server blade mappings across multiple locations, ensuring identical configurations without manual intervention.
2Reliability
If manual configuration is performed at each blade system, then local customization is possible, but the process is prone to errors and difficult to maintain
Solution Approach 1:
The blade systems automatically perform configuration tasks using the golden configuration file. The management module autonomously collects WWN to slot information, transfers it to the storage system, and applies the configuration without requiring manual intervention at each location, reducing human error and simplifying management.
Solution Approach 2:
The management module collects WWN to slot information from server blades and uses this feedback to automatically adjust and apply the correct configuration. This closed-loop approach ensures that the configuration accurately reflects the actual hardware state while maintaining consistency across multiple systems.
3Ease of operation
If normal boot-up sequence is followed, then system startup is straightforward, but storage system and files cannot be manually configured with respect to servers
Solution Approach 1:
The boot-up process and configuration application are merged into a single automated sequence. The golden configuration file is applied during the boot-up process itself, combining the simplicity of automatic startup with the capability of proper storage-to-server configuration without requiring separate manual steps.
Data Source
AI summary
Consistency for replicating data storage subsystem configurations in accordance with a “golden” configuration file. A data storage subsystem comprises a blade system with a plurality of slots, the blade system configured to support a plurality of blades and a storage system, each arranged in a predetermined slot of the blade system. The storage system arranges a logical configuration of the server blades in accordance with a “golden” configuration file. The server blade slot versus WWN information is collected and provided to the storage system. The storage system converts the “golden” configuration file slot information to WWNs. The server blades are enabled for access to said storage system as they log on with WWNs in accordance with the “golden” configuration file.