Event Notification Mechanism for HCI Management Network Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Post-deployment reconfiguration of management networks in multi-node hyper-converged infrastructure (HCI) clusters is challenging, especially for edge nodes, where failure to update network configurations can lead to service disruptions.
Innovation Solution
A method is introduced where a central manager, communicatively coupled to each node via a cluster management network, uses an event listening service to detect and respond to management network configuration changes, performing necessary operations such as VLAN changes, IP subnet mask adjustments, and network gateway modifications, with rollback mechanisms to ensure reliability and prevent service disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If management network configuration is changed after HCI node deployment, then network configuration can be updated to meet new requirements, but system stability and service continuity may be compromised
Solution Approach 1:
The system performs preliminary actions by creating a backup of the current management network configuration before applying any changes. This allows the configuration to be updated while maintaining the ability to restore the original state if needed, thus enabling both configuration updates and service continuity.
Solution Approach 2:
The system implements feedback mechanisms by monitoring the health and status of HCI nodes after configuration changes are applied. If service disruptions are detected, the system automatically triggers a rollback to the previous configuration, ensuring service continuity while still allowing for necessary updates.
2Adaptability or versatility
If manual reconfiguration of management network is performed on each HCI node, then configuration changes can be applied, but time consumption and operational complexity increase significantly
Solution Approach 1:
The system merges the configuration management functions into a centralized manager that can push configuration changes to multiple HCI nodes simultaneously. This eliminates the need for manual reconfiguration on each node individually, reducing time consumption while maintaining configuration flexibility through the event listening service.
Solution Approach 2:
HCI nodes are equipped with agents that automatically receive and apply configuration changes pushed by the central manager. The nodes self-configure based on the updated management network parameters without requiring manual intervention, significantly reducing reconfiguration time while maintaining adaptability.
3Adaptability or versatility
If management network configuration is updated on Edge nodes, then network configuration can be synchronized with central manager, but service disruption may occur during the update process
Solution Approach 1:
The system applies beforehand cushioning by creating and storing backup configurations before applying updates to Edge nodes. This protective measure ensures that if service disruption occurs during the update process, the system can quickly restore the previous working configuration, maintaining service availability while enabling configuration synchronization.
Solution Approach 2:
The central manager pushes configuration changes to Edge nodes in a controlled manner, and Edge nodes apply changes during maintenance windows or low-traffic periods. This preliminary planning minimizes service disruption while achieving configuration synchronization across the distributed HCI cluster.
4Adaptability or versatility
If comprehensive management network configuration operations are performed (VLAN, IP subnet mask, gateway changes), then network adaptability is improved, but system complexity and potential for errors increase
Solution Approach 1:
The central manager acts as an intermediary between the administrator and the complex network configuration operations on Edge nodes. It abstracts the complexity of VLAN, IP subnet mask, and gateway changes into a unified configuration push mechanism, reducing the perceived complexity while maintaining comprehensive network configuration capability.
Solution Approach 2:
The event listening service and configuration management system are designed to handle multiple types of network configuration operations (VLAN changes, IP subnet mask adjustments, gateway modifications) through a single unified interface. This multi-functional approach improves network adaptability while reducing configuration management complexity by eliminating the need for separate processes for each configuration type.
Data Source
AI summary
A disclosed method for managing a multi-node, HCI cluster provisions a central manager of the HCI cluster with an event listening service. The service is then registered with an agent in each HCI node. The service, when triggered by a management network configuration event, causes the agent to modify a management network configuration of the node in accordance with the event. Disclosed methods may respond to successfully applying a management network configuration change by sending a success notification to the central manager and awaiting a confirmation from the central manager. If confirmation is not received within a timeout interval, a timeout occurs and the management network configuration is rolled back to a last known good configuration. If the configuration change cannot be successfully applied, a failure notification is sent to the central manager and the configuration of the node is rolled back to a last known good configuration.


