Networking Device Edge Controller for HCI Software Compliance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Hyper-Converged Infrastructure (HCI) systems deployed at network edges face challenges in lifecycle management due to the need for dedicated management servers, which are costly and prone to being a single point of failure, especially where guaranteed connectivity is lacking.
Innovation Solution
A networking-device-based edge controller system that identifies HCI node components, retrieves software inventory information, receives updated software from a master controller via a network, and ensures compliance by providing updates to non-compliant components, eliminating the need for additional management infrastructure and preventing single points of failure through redundant edge controller systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a dedicated management server is provided at each remote business location to manage HCI system component updates, then update operations can be carried out locally without requiring guaranteed network connectivity, but the cost, maintenance burden, and device complexity increase significantly
Solution Approach 1:
The networking device is enhanced to perform multiple functions: it acts as both a standard networking device and as an edge controller capable of managing HCI system component updates. This eliminates the need for separate dedicated management servers at each remote location, reducing device complexity while maintaining local update capability and reliability.
2Ease of operation
If a single management server is provided at the remote business location, then local update operations can be performed, but it becomes a single point of failure for HCI system management
Solution Approach 1:
The management functionality is segmented and distributed across multiple networking devices rather than concentrated in a single management server. Each networking device can independently perform edge controller functions, and if one fails, others can continue to manage HCI system updates, eliminating the single point of failure while maintaining local update capability.
3Ease of manufacture
If conventional HCI systems are deployed at network edges without dedicated management servers, then cost and maintenance issues are reduced, but lifecycle management becomes difficult without local management infrastructure
Solution Approach 1:
The networking device provides self-service edge controller functionality, enabling it to autonomously manage HCI system component updates without requiring external dedicated management servers. The device can retrieve software inventory information, receive updated software from master controllers, and provision updates to HCI node components independently, making lifecycle management easier while maintaining low deployment cost.
Data Source
AI summary
A networking-device-based HCI edge controller system includes a networking device coupled to a master controller system via a network, as well as locally to an HCI node system including HCI node(s). The networking device and the HCI node system are provided at an edge location in a network, and the networking device operates to identify HCI node components that are included in the HCI node(s) in the HCI node system, and retrieve respective software inventory information for each of the HCI node component in the HCI node(s). The networking device receives first updated software from the master controller system via the network, determines that the respective software inventory information for at least one of the HCI node components does not comply with the first updated software for those HCI node components and, in response, provides the first updated software on those HCI node components.