Bootstrapping Server Using Internal Configuration Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current clustered storage management systems face challenges in managing configuration data, particularly in bootstrapping and maintaining dynamic configuration data across multiple nodes, which is prone to human error and does not scale well with the number of disk drives, and relies on external administration.
Innovation Solution
The system stores and manages its own configuration data internally, using a cluster-wide locking service and logical-to-physical address mappings to ensure correct and consistent configuration data access, even in the presence of network and storage device failures, allowing nodes to find and update configuration data autonomously.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If manual administration is used to manage storage system configuration data, then the system can be configured and administered, but the process becomes difficult and error-prone as the number of disk drives increases
Solution Approach 1:
The storage management system automatically discovers configuration data on storage devices and populates configuration files without requiring manual administration. The system self-configures by reading configuration data from designated locations on storage devices and using it to populate configuration files during system initialization.
Solution Approach 2:
Configuration data is pre-stored on storage devices at designated locations before the system needs to initialize. This preliminary placement of configuration data allows the system to automatically retrieve and use it during bootstrapping, eliminating the need for manual configuration at system startup.
2Reliability
If configuration data is stored externally to the storage system, then the system can boot with configuration information, but the system relies on external administration and does not scale well
Solution Approach 1:
The system merges the configuration data storage with the storage devices that are already part of the storage system. Instead of using external storage, the configuration data is stored on the same storage devices that the system manages, integrating the configuration storage function into the existing storage infrastructure.
Solution Approach 2:
Storage devices serve dual purposes: they store both user data and system configuration data. The same storage infrastructure that holds operational data is also used to store configuration information, eliminating the need for separate external configuration storage.
3Extent of automation
If the system uses server-managed storage for configuration data, then external administration is reduced, but the system must ensure data consistency during bootstrapping and operations
Solution Approach 1:
The system implements a feedback mechanism where nodes communicate with each other to verify configuration data consistency. During bootstrapping, nodes read configuration data from storage devices and exchange information to ensure all nodes have consistent configuration, allowing the system to detect and correct inconsistencies.
Solution Approach 2:
The system prepares for potential configuration inconsistencies by implementing verification and recovery procedures during the bootstrapping process. Configuration data is validated and cross-checked before being used, and mechanisms are in place to handle cases where configuration data may be inconsistent or corrupted.
Data Source
AI summary
A method and apparatus for booting a clustered management system is provided where the configuration information required to boot the system is stored within the system itself. The techniques cope with several issues including finding the configuration data on the physical disk before the logical disk system is established, coping with replicated copies of configuration data, network partitions and disk drive failures that may prevent a booting node to have perfect knowledge of the state of the entire system, and active nodes modifying or moving configuration data while the booting node is searching for a consistent, correct copy of configuration data.