Cluster Node Change Reversal for Scaling Without Re-Imaging

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing cluster management systems face challenges in efficiently expanding and contracting clusters of information handling systems, often resulting in servers becoming 'configured unhealthy' due to failed expansion procedures, requiring time- and resource-intensive re-imaging or resetting to factory defaults.

Innovation Solution

Implementing a method to record and reverse changes made to nodes during cluster expansion and contraction, allowing nodes to be returned to a usable state without manual re-imaging by storing change records and applying undo changes during removal.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If expansion procedure is performed to add nodes to cluster, then cluster scalability is improved, but nodes may become configured unhealthy requiring re-imaging

Engineering Contradiction:

Improvecluster scalabilityVSAvoidnode usability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by recording all configuration changes made to a node during cluster expansion before they are applied. This change log is stored in advance, enabling the system to revert to the original state if the expansion fails, thus preventing the node from becoming permanently unhealthy.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system prepares compensatory measures in advance by creating a backup of the node's original configuration state. This cushioning mechanism ensures that if the expansion procedure fails or leaves the node in an unhealthy state, the node can be restored to its previous working state without requiring re-imaging.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If re-imaging or factory reset is performed on configured unhealthy nodes, then node state is restored, but time and resources are consumed

Engineering Contradiction:

Improvenode state restorationVSAvoidrecovery time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by recording configuration changes in advance during cluster expansion. This pre-recorded change log enables rapid restoration by simply reversing the recorded changes, eliminating the need for time-consuming re-imaging or factory reset operations.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If nodes are removed from cluster, then cluster flexibility is improved, but nodes require re-imaging for reuse

Engineering Contradiction:

Improvecluster flexibilityVSAvoidnode reuse preparation

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system performs preliminary action by maintaining change logs for all nodes during their cluster membership. When a node is removed, these pre-recorded changes can be reverted to restore the node to its original state, making it ready for reuse in another cluster without requiring re-imaging or factory reset.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system applies the discarding and recovering principle by temporarily storing configuration changes made during cluster membership and then recovering the original node state when the node is removed. This allows the node to be discarded from the cluster while preserving its original configuration for future reuse.

Inventive Principle:

Principle #34Discarding and recovering

4Stability of the object's composition

If firmware and software elements are modified during cluster expansion, then cluster consistency is improved, but nodes become unusable if procedure fails

Engineering Contradiction:

Improvecluster consistencyVSAvoidnode usability

Core Design Contradiction:

Stability of the object's compositionVSReliability

Solution Approach 1:

The system performs preliminary action by recording all firmware and software modification changes before applying them during cluster expansion. This pre-recording enables the system to maintain cluster consistency through coordinated updates while providing a recovery mechanism to restore node usability if the procedure fails.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system prepares compensatory measures by storing backup information of the original firmware and software states before modifications. This cushioning mechanism ensures that if the cluster expansion procedure fails after modifying these elements, the node can be restored to its original state, preventing it from becoming permanently unusable.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS12474942B2Scaling cluster without re-imaging nodes

Publication Date: 2025.11.18 DELL PROD LP

AI summary

An information handling system may include at least one processor and a memory. The information handling system may be configured to: add a node to a cluster of information handling systems; while the node is a member of the cluster, cause a plurality of components of the node to be changed according to a first set of changes; for each change in the first set of changes, store a record of the change; and in response to an indication that the node is to be removed from the cluster, cause the plurality of components of the node to be changed according to a second set of changes, wherein the changes in the second set of changes are configured to undo the changes in the first set of changes.