Cluster Scaling Baseline Correction via Configuration Alignment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cluster scaling events in hyper-converged infrastructure (HCI) environments are risky due to potential version mismatches of software and firmware components, especially when new nodes are added, as only certain combinations are rigorously tested and certified, and manual downloads can exacerbate these risks.

Innovation Solution

An information handling system is configured to transmit a request to a remote system for known-good cluster configurations, determine the closest matching configuration, and make necessary changes to align the cluster before initiating a scaling event, ensuring a baseline configuration that has been tested and verified.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If nodes are added to expand cluster capacity, then productivity is improved, but reliability deteriorates due to version mismatches of software and firmware components

Engineering Contradiction:
Improvecluster capacityVSAvoidconfiguration compatibility
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by checking the current cluster configuration against a stored baseline configuration before allowing node addition. This pre-verification ensures that the existing configuration is compatible with the new node, preventing version mismatch issues before they occur

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring and comparing the running cluster configuration with the baseline configuration. When deviations are detected, the system can alert administrators or automatically correct the configuration, ensuring ongoing compatibility as the cluster evolves

Inventive Principle:
Principle #23Feedback

2Ease of operation

If manual software or firmware downloads are performed, then ease of operation is improved, but reliability deteriorates due to unverified component versions

Engineering Contradiction:
Improvemanual component installationVSAvoidcomponent version verification
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system introduces an intermediary mechanism that acts as a gatekeeper between manual component installation and the cluster. This intermediary verifies that downloaded components match the baseline configuration requirements before allowing installation, preventing unverified components from compromising cluster reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces manual verification processes with automated configuration checking. Instead of relying on administrators to manually verify component versions against the baseline, the system automatically performs this verification, reducing human error while maintaining ease of operation

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Speed

If cluster scaling operations are performed without configuration verification, then speed is improved, but reliability deteriorates due to untested component combinations

Engineering Contradiction:
Improvescaling operation speedVSAvoidconfiguration testing
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary configuration verification against the baseline before scaling operations begin. This pre-check ensures that only compatible configurations proceed to scaling, preventing failures from untested component combinations while maintaining operational speed

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11977562B2Knowledge base for correcting baseline for cluster scaling
Publication Date: 2024.05.07 DELL PROD LP
  • US11977562B2 patent drawing
  • US11977562B2 patent drawing

AI summary

An information handling system may include at least one processor and a non-transitory memory coupled to the at least one processor. The information handling system may be configured to: transmit a request to a remote information handling system regarding an upcoming cluster scaling event for an information handling system cluster; receive information from the remote information handling system indicative of a plurality of known-good cluster configurations; determine a closest one of the plurality of known-good cluster configurations; make one or more configuration changes to the information handling system cluster to cause a configuration of the information handling system cluster to match the closest one; and initiate the cluster scaling event.