API Exception Mechanism for Hyper-Converged Infrastructure Bug Fixes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for fixing bugs in upper management layers, such as vRealize and EVO:RAIL, are ineffective when customer workloads do not properly interface with or invoke the expected lower management layers, leading to failed configuration operations in hyper-converged infrastructure setups.

Innovation Solution

Implementing an API exception mechanism that allows the upper management layer to communicate fixes through the lower management layer by using an input string with a lower management layer identifier, API path, and API configuration, enabling direct configuration of the compute/storage/network configuration layer without requiring new product releases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing bug fix methods are used in upper management layers, then configuration operations can be performed, but they fail when customer workloads do not properly interface with lower management layers

Engineering Contradiction:

Improveconfiguration operation successVSAvoidcompatibility with customer workload interfaces

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an API exception mechanism as an intermediary layer between the upper management layer and the lower management layer. This mediator enables the upper management layer to communicate configuration fixes to the lower management layer even when the customer workload does not properly interface with the expected lower management layer, thereby resolving the contradiction between reliability and adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by pre-defining API exceptions and their corresponding handlers in the upper management layer before configuration operations are needed. This allows the system to prepare and transmit configuration fixes in advance through the API exception mechanism, ensuring that configuration operations succeed even when workload interfaces are atypical.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If new product releases are required for bug fixes, then proper interface handling is ensured, but configuration fixes cannot be applied quickly

Engineering Contradiction:

Improvebug fix deployment speedVSAvoidinterface compatibility assurance

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent applies dynamics by making the interface mechanism flexible and adaptable rather than rigid. The API exception mechanism allows the upper management layer to dynamically transmit configuration fixes to the lower management layer without requiring new product releases, enabling quick deployment while maintaining interface compatibility through the handler-based approach.

Inventive Principle:

Principle #15Dynamics

3Reliability

If configuration fixes are transmitted through the lower management layer, then proper communication is achieved, but the lower management layer must know the transmission source

Engineering Contradiction:

Improvecommunication between management layersVSAvoidlower management layer awareness requirement

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the transmission source awareness requirement from the lower management layer by using API exceptions as carriers. The exception data payload contains the necessary information about the upper management layer, allowing the lower management layer to process configuration fixes without needing to know or care about the transmission source, thereby simplifying the communication architecture while maintaining reliability.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS10019304B2Providing an application interface programming exception in an upper management layer

Publication Date: 2018.07.10 VMWARE INC

AI summary

An input string, which includes exception data payload, is received at the API exception that resides in the upper management layer. The API exception is dedicated to receiving the exception data payloads. The API exception validates the input string. The API exception transmits the exception data payload to a lower management layer without the lower management layer knowing where the exception data payload was transmitted from.