OS-Based SHAS Configuration Loading for Data-Plane Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for creating a storage high availability solution (SHAS) configuration require communication from a replication manager server, which is not feasible in cloud or multi-tenant environments due to the need for data privacy and independence among customers, necessitating a separation of management and customer data planes.
Innovation Solution
The operating system autonomously discovers and builds the SHAS configuration without external server intervention, utilizing a SHAS Management Address space to validate, maintain, and monitor the configuration, ensuring all device pairs are fully duplicated before enabling the solution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the replication manager server builds and sends the SHAS configuration to operating systems, then the SHAS configuration can be created and loaded, but the management data plane cannot be separated from the customer data plane, compromising customer privacy and independence
Solution Approach 1:
The patent segments the data plane from the management plane by enabling the operating system to independently discover, build, and load SHAS configurations without requiring communication from the replication manager server. This segmentation allows customer data to remain isolated while still receiving high availability protection, resolving the contradiction between configuration reliability and data privacy.
Solution Approach 2:
The operating system performs self-service by autonomously discovering devices, determining device pairs, building the SHAS configuration, and loading it without external intervention from the replication manager server. This self-service capability eliminates the need for management plane communication, thereby protecting customer privacy while ensuring reliable SHAS configuration.
2Ease of operation
If the replication manager server manages the infrastructure for multiple customers in a centralized manner, then infrastructure management is simplified, but customer data privacy and independence are compromised
Solution Approach 1:
The patent divides the system into separate management domains: the replication manager server handles infrastructure-level management, while each operating system independently manages its own customer data and SHAS configurations. This segmentation enables simplified infrastructure management while maintaining strict customer data privacy through architectural isolation.
3Productivity
If the operating system autonomously discovers and builds SHAS configuration without replication manager server intervention, then customer data privacy is protected and system efficiency is enhanced, but the complexity of autonomous device discovery and configuration building increases
Solution Approach 1:
The operating system implements self-service mechanisms for device discovery, configuration building, and loading. By embedding these capabilities directly in the operating system, the patent enhances productivity and data privacy while managing complexity through integrated design rather than external coordination.
Solution Approach 2:
The operating system uses feedback from device discovery processes to dynamically build and update SHAS configurations. This feedback mechanism allows the system to autonomously adapt to changing device states while maintaining configuration accuracy, balancing autonomy with manageable complexity.
Data Source
AI summary
Methods, systems, and products for automatically creating and loading a storage high availability solution configuration includes starting, by an operating system, a storage high availability solution address space; determining, for each device coupled to the operating system, whether the device is part of a device pair as a primary device that has a secondary pair and, if so, adding the device to a list of devices configured for a storage high availability solution, where the list of devices is included in a storage high availability solution configuration; and loading, by the operating system and based on the list of devices including at least one device, the storage high availability solution configuration.