Pluggable Node Manager for Diverse Interface Compatibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Computing infrastructures with diverse node interfaces face challenges in efficiently performing node management actions due to differences in supported actions, naming conventions, and communication protocols across various vendor implementations.

Innovation Solution

A pluggable node manager is introduced, which maintains configuration data specifying plugins designed to communicate with different node interfaces. This allows client applications to use a common client interface, relieving them of the burden of managing multiple vendor-specific interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor-specific node interfaces are used to communicate with different node interfaces, then compatibility with specific vendor implementations is achieved, but client application complexity increases due to needing to manage multiple vendor-specific interfaces

Engineering Contradiction:

Improvecompatibility with vendor implementationsVSAvoidclient application complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A common client interface acts as an intermediary layer between client applications and vendor-specific node interfaces. This mediator translates generic client requests into vendor-specific commands, allowing clients to work with a unified interface while maintaining compatibility with diverse vendor implementations without increasing client complexity

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The common client interface is designed to work with multiple vendor-specific interfaces through a unified API. This universal interface can adapt to different vendor implementations (IPMI, Redfish, etc.) while presenting a consistent interface to clients, thereby reducing client application complexity while maintaining broad compatibility

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple vendor-specific plugins are maintained to support different node interfaces, then support for diverse interfaces is achieved, but system complexity increases due to managing multiple plugins

Engineering Contradiction:

Improvesupport for diverse interfacesVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments interface-specific functionality into separate vendor-specific plugins while maintaining a unified common client interface. This segmentation allows each plugin to handle only its specific vendor interface (IPMI, Redfish, etc.), reducing the complexity burden on the overall system by isolating vendor-specific complexity into manageable, independent modules

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The common client interface serves as a mediator that manages multiple vendor-specific plugins behind a unified API. This intermediary layer abstracts the complexity of managing multiple plugins from the client, allowing the system to support diverse interfaces while presenting a simplified interface to users

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If vendor-specific interfaces with different naming conventions and protocols are used, then vendor implementation compatibility is achieved, but ease of operation decreases due to differences in supported actions and naming

Engineering Contradiction:

Improvevendor implementation compatibilityVSAvoidease of performing node management actions

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The common client interface acts as a translator between generic operation names and vendor-specific commands. For example, it translates a generic 'power on' command into the appropriate vendor-specific command (e.g., IPMI's 'power on' or Redfish's 'power on'), abstracting away naming convention differences and protocol variations from the user

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The common client interface provides universal support for node management actions across different vendor interfaces through a unified set of operation names and parameters. This allows users to perform the same management actions (boot, shutdown, reset, etc.) using consistent syntax regardless of the underlying vendor implementation

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12284079B2Facilitating performance of node management actions in a computing infrastructure having diverse node interfaces

Publication Date: 2025.04.22 NUTANIX INC

AI summary

An aspect of the present disclosure facilitates performance of node management actions in a computing infrastructure having diverse node interfaces. In one embodiment, a configuration data is maintained, the configuration data specifying plugins designed to communicate with different node interfaces installed on the nodes of a computing infrastructure. The plugins are corresponding implementations of a common client interface. Upon receiving from the client application, via the common client interface, a management action to be performed on a desired node, the configuration data is inspected to identify a specific plugin corresponding to the node interface installed on the desired node. The node management action is then performed on the desired node using the identified specific plugin. Accordingly, the client application can be implemented agnostic to the specific node interfaces installed on a node.