Containerized Application Extensions in Distributed Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy techniques for managing containerized application extensions in distributed virtualization systems are inefficient, leading to delayed availability of application extensions and limited user experience due to the need for manual feature requests and system upgrades.

Innovation Solution

Implementing a system and method for managing containerized application extensions through an interaction protocol in a distributed virtualization environment, allowing users to browse, download, and integrate extensions directly into the virtualized processing environment using APIs, enabling quick extension of functionality and user experience without requiring system upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If legacy techniques are used to extend application functionality through manual feature requests and system upgrades, then application functionality can be extended, but the availability of extensions is delayed and user experience is degraded

Engineering Contradiction:
Improveapplication functionality extensionVSAvoidextension availability delay
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables self-service extension installation where users can independently browse, select, and install application extensions from a repository without requiring vendor intervention or system administrator approval. The virtualization environment automatically manages the installation and integration of extensions, eliminating the need for manual feature requests and scheduled system upgrades.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Application extensions are pre-packaged in containerized formats with all dependencies and configurations prepared in advance. The extension repository pre-approves and stages extensions before they become available for installation, so that when users need functionality extensions, they are immediately available without waiting for vendor development cycles or system upgrade schedules.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If legacy techniques are used with explicit vendor-provided extensions only, then system stability is maintained, but user experience is limited to explicitly requested extensions

Engineering Contradiction:
Improvesystem stabilityVSAvoidextension availability scope
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

A containerized application extension repository acts as an intermediary between extension developers and the virtualization environment. The repository validates, approves, and hosts extensions, ensuring they meet system requirements before making them available. This intermediary layer maintains system stability while enabling access to a broader range of extensions beyond those explicitly requested from vendors.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The extension repository serves multiple functions: it validates extension compatibility, manages installation workflows, provides user access to extensions, and maintains system integrity. This universal platform enables diverse extension sources (vendor-provided, community-contributed, user-created) to be integrated through a single standardized interface, expanding availability scope while maintaining reliability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If manual feature requests and system upgrades are used to add functionality, then system control is maintained, but productivity is reduced due to delayed extension availability

Engineering Contradiction:
Improveextension deployment speedVSAvoidextension installation complexity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

Users can independently browse the extension repository, search for desired functionality, select extensions, and install them directly into their virtualization environments without requiring system administrator intervention or complex manual processes. The system automatically handles installation, configuration, and integration, dramatically improving productivity while maintaining ease of operation through automated workflows.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The manual mechanical process of feature requests, vendor development, system upgrade scheduling, and administrator-mediated installation is replaced by an automated electronic system. Users interact with a digital repository through standardized interfaces, and the system automatically manages the deployment pipeline, replacing multi-step manual procedures with streamlined automated operations that improve both productivity and ease of operation.

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

Data Source

PatentUS10649679B2Containerized application extensions in distributed storage systems
Publication Date: 2020.05.12 NUTANIX INC
  • US10649679B2 patent drawing
  • US10649679B2 patent drawing
  • US10649679B2 patent drawing

AI summary

Systems for distributed data storage. A user accesses a user interface in a distributed virtualization system comprising computing nodes that support virtualized controllers that include preconfigured APIs to receive application extension modules. The system receives a user command from a user interface at the virtualized controller, the user command corresponding to a download request for at least one application extension. A successful download and integration event causes integration of the containerized application extension into the system. The additional functionality of the containerized application extension is offered to the user. The user can address additional functionality of the containerized application extension through a user interface.