Zero Configuration Management for HCI Node Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large data centers and enterprise networks, manually configuring hyperconverged infrastructure (HCI) nodes for zero configuration settings is impractical, as factory-assigned values do not account for specific deployment characteristics or locations, hindering centralized management.
Innovation Solution
Implementing a zero configuration management service that allows IT administrators to customize zero configuration information for HCI nodes, using multi-case domain name service (mDNS) for communication, and a cluster manager to collect, filter, and store custom settings, enabling selective configuration of nodes based on deployment-specific criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If factory-assigned zero configuration information is used for HCI nodes, then deployment is simplified and automated, but centralized management and customization for specific deployment characteristics become impossible
Solution Approach 1:
The system performs preliminary configuration actions by assigning temporary factory-default zero configuration values (hostnames, IP addresses) to HCI nodes before deployment. These preliminary values enable automated node identification and cluster joining, while allowing subsequent customization through the centralized management interface without requiring manual reconfiguration of each node
Solution Approach 2:
The zero configuration information is made dynamic and changeable rather than fixed. The system allows administrators to modify zero configuration values (hostnames, IP addresses, location information) after initial deployment through centralized management, enabling the system to adapt to specific deployment characteristics while maintaining the benefits of automated initial configuration
2Adaptability or versatility
If manual configuration is performed for each HCI node, then customization for deployment characteristics is achieved, but scalability to large data centers becomes impractical
Solution Approach 1:
A centralized management interface acts as an intermediary between administrators and HCI nodes. This intermediary enables bulk configuration operations where administrators can define custom zero configuration values (hostnames, IP addresses, location information) for multiple nodes simultaneously, which are then automatically distributed and applied across the cluster, achieving both customization and scalability
Solution Approach 2:
The centralized management system provides universal configuration capabilities that work across all HCI nodes in the cluster regardless of their specific deployment characteristics. A single configuration interface can manage diverse nodes with different location requirements, deployment characteristics, and customization needs, eliminating the need for separate manual configuration processes for each node type or location
3Ease of manufacture
If factory zero configuration information is retained without modification, then system deployment is streamlined, but centralized management of specific HCI nodes within a cluster becomes difficult
Solution Approach 1:
The system implements feedback mechanisms where the centralized management interface continuously monitors and discovers nodes using their factory-assigned zero configuration information. This feedback enables the system to identify nodes, retrieve their current configuration state, and present customization options to administrators, allowing management actions to be taken based on real-time node status and deployment characteristics
Data Source
AI summary
A disclosed method includes obtaining, by a cluster manager, first zero configuration information, from one or more unconfigured nodes of an information handling system cluster. A service on the cluster manager may then generate custom zero configuration information for each of the unconfigured nodes and stored the custom zero configuration information in a zero configuration management store. Each unconfigured node may then retrieve its custom zero configuration information from the zero configuration management store and modify one or more zero configuration parameters of the unconfigured node in accordance with the custom zero configuration information. Disclosed methods may determine zero configuration criteria for configuring a node and identify, based on the custom zero configuration information in the zero configuration management store, unconfigured nodes of the cluster matching the zero configuration criteria. A zero touch configuration of the identified nodes may then be performed.