Centralized Management Console UI Caching via Copying

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing multiple underlying systems in a computing environment with different types and versions of management console interfaces poses challenges due to incompatibilities, leading to difficulties in maintaining a centralized management console and potential performance issues.

Innovation Solution

Caching user interfaces for local management nodes at a central management node, allowing the cached copies to be executed as if the user is operating from the local node, and using a gateway to proxy requests to the local nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the central UI includes all required functionality of local node UIs, then the centralized management console can manage all local nodes, but the central UI becomes difficult to maintain and performance decreases due to large number of conditional logic

Engineering Contradiction:
Improveability to manage different local node UI types and versionsVSAvoidcentral UI codebase complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a copy of the local node's management console interface code and executes it within the centralized management console. This allows the central UI to present the exact same interface that the local node would provide, without needing to include all possible local UI variants in its own codebase. The copied interface is instantiated dynamically based on the specific local node being managed.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces an intermediary layer between the centralized management console and local nodes. This intermediary captures the local node's interface code, executes it in a controlled environment, and presents it to users. The intermediary handles the complexity of different UI types and versions, allowing the central console to remain simple while still supporting multiple local node configurations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the central UI includes all required functionality of local node UIs, then the centralized management console can manage all local nodes, but the codebase bloats causing diminished performance and greater latency

Engineering Contradiction:
Improveability to manage different local node UI types and versionsVSAvoiduser interface performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

Instead of including all possible local UI code in the central console's permanent codebase, the system copies only the necessary local UI code dynamically when needed. This on-demand copying approach ensures that the central console loads only the interface code required for the specific local node being managed, avoiding the performance penalty of loading and executing a large number of conditional logic paths for all possible UI types.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the central UI uses extensive conditional logic to handle different local node options, then the centralized management console can adapt to various configurations, but maintenance difficulty increases

Engineering Contradiction:
Improvehandling different local node UI types and versionsVSAvoidcentral UI maintenance ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent eliminates the need for extensive conditional logic in the central UI by copying the actual local node interface code instead. Rather than writing code to handle different UI types through conditional statements, the system simply loads and executes the appropriate local UI code as-is. This approach maintains adaptability while dramatically reducing maintenance complexity, as the central console no longer needs to be updated to accommodate new local UI versions.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Instead of the central UI adapting to local nodes by implementing conditional logic for each local UI type, the patent inverts the approach: the local node's interface code is copied and executed within the central console. This inversion transfers the adaptation responsibility from the central console to the local node's own code, simplifying the central UI's role to merely hosting and presenting the copied interface.

Inventive Principle:
Principle #13The other way round (Inversion)

4Device complexity

If the centralized management console uses a fixed interface version, then the console codebase remains simple, but compatibility issues arise when local nodes use later versions of management code

Engineering Contradiction:
Improvecentral management console codebase simplicityVSAvoidcompatibility with local node UI versions
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent resolves the version compatibility issue by copying the local node's interface code exactly as it exists, regardless of version. The central management console does not need to support multiple versions itself; instead, it copies the specific version required for each local node and executes it. This ensures forward compatibility, as the central console can accommodate any future local node version without requiring updates to its own codebase.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10756985B2Architecture for implementing user interfaces for centralized management of a computing environment
Publication Date: 2020.08.25 NUTANIX INC
  • US10756985B2 patent drawing
  • US10756985B2 patent drawing
  • US10756985B2 patent drawing

AI summary

The present disclosure provides an improved approach to implement a management infrastructure for computing environments. The user interfaces for local management nodes are cached at a central management node. The cached copies of the local node UIs can then be executed as if the user was actually operating from the local node.