Package Manager System for Hyper-Converged Appliance Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional package managers are limited in their ability to interact with external operating environments and access knowledge beyond installed files or packages, making it difficult to manage software dependencies and installations on hyper-converged appliances.

Innovation Solution

A package manager system that includes modules for processing package definitions, determining assertion status, resolving dependencies, and completing assertions by accessing external sources, allowing for the installation of software packages across a network on hyper-converged appliances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional package managers only access knowledge from installed files or previously installed packages, then the package manager structure remains simple, but the ability to manage software dependencies on hyper-converged appliances is insufficient

Engineering Contradiction:
Improveability to manage software dependenciesVSAvoidpackage manager structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary component that bridges the package manager and external knowledge sources. This intermediary translates package manager queries into appropriate external queries and integrates results back into the package management workflow, enabling access to external operating environment information without requiring the package manager itself to be fundamentally redesigned

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The package manager is enhanced to perform multiple functions: traditional package management tasks plus interaction with external operating environments. By making the system multi-functional, it can handle both conventional package installation and the more complex task of managing dependencies across virtualized environments, computer nodes, and external systems

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

2Adaptability or versatility

If the package manager interacts with external operating environments, then the capability to install software across virtualized environments is improved, but the complexity of interaction and information access increases

Engineering Contradiction:
Improveinteraction with external environmentsVSAvoidinteraction complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

An intermediary layer is introduced between the package manager and external operating environments (virtual machines, computer nodes, storage systems). This intermediary handles the complexity of external interactions by providing a standardized interface, translating diverse external system responses into a unified format that the package manager can process, thereby reducing interaction complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where the package manager receives information from external operating environments about available software, dependencies, and system state. This feedback loop enables the package manager to make informed decisions about package installation and configuration while adapting to the actual state of the hyper-converged appliance environment

Inventive Principle:
Principle #23Feedback

3Productivity

If user prompting is required for missing package information, then the package manager remains simple, but the installation process time increases

Engineering Contradiction:
Improveinstallation process speedVSAvoiduser interaction requirement
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by proactively querying external operating environments and knowledge sources before the user needs to install a package. This advance gathering of information about available software, dependencies, and system compatibility eliminates the need for user prompting during the installation process, as the package manager already has the necessary information to proceed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The package manager is enhanced to serve itself by automatically gathering required information from external sources without user intervention. The system independently queries virtual machine configurations, computer node states, and software repositories to obtain missing package information, thereby improving installation speed while maintaining ease of operation

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9916148B2System for managing software package configuration
Publication Date: 2018.03.13 VMWARE INC
  • US9916148B2 patent drawing
  • US9916148B2 patent drawing
  • US9916148B2 patent drawing

AI summary

A method for managing a software package, including: accessing a request to process one or more package definitions in relation to a data repository which retains package definitions, wherein the one or more package definitions is associated with the software package; determining a status of an assertion that indicates either a completed assertion or an incomplete assertion; if the status is determined to be the incomplete assertion, then determining requirements for the software package to be configured for the hyper-converged appliance; attempting to find a match for the assertion in a pool of known resolvable assertions, wherein the match will allow the assertion to be resolved through accessible provisions and thereby fulfill the requirements; if the match is found, then using the accessible provisions to resolve and thereby complete the assertion; and if the assertion is completed, continuing an installation process of the software package.