Pre-Upgrade Component Detection in Virtual Hosts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current virtualization systems lack a reliable method for pre-validating upgrades in virtual environments, leading to inefficiencies and downtime, as they do not provide mechanisms for detecting and validating upgradeable components before the upgrade process, and existing APIs are insufficient for comprehensive validation checks.

Innovation Solution

The implementation of an upgrade orchestrator that performs pre-upgrade component detection and validation, using a component detection subsystem to identify upgradeable components and a validation subsystem to ensure compatibility, allowing for parallel processing across multiple hosts and coordinating upgrades even when VMs are powered off.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If upgrade validation is performed manually after upgrade, then system reliability is maintained, but downtime increases and efficiency decreases

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs upgrade validation before the actual upgrade process by detecting upgradeable components and simulating compatibility checks in advance. This preliminary validation ensures system reliability is maintained while avoiding post-upgrade downtime, as the validation occurs during the pre-upgrade phase when the system is still operational.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation mechanism that acts as a mediator between the upgrade process and the system operation. This intermediary performs compatibility testing and component detection without requiring system shutdown, thus maintaining reliability while minimizing downtime by allowing parallel validation operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive validation checks are performed, then upgrade reliability is improved, but system complexity increases

Engineering Contradiction:
Improveupgrade reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the validation process into distinct modular components: component detection subsystem, compatibility validation subsystem, and upgrade execution subsystem. Each subsystem performs a specific function independently, which improves upgrade reliability through comprehensive checks while managing system complexity by organizing validation tasks into separate, manageable modules with defined interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary validation layer that coordinates between the upgrade manager and the underlying system components. This intermediary handles the complexity of comprehensive validation checks by providing a standardized interface, thus improving upgrade reliability without exposing the full complexity to the user or system administrators.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If upgrade validation is performed on each host sequentially, then validation thoroughness is maintained, but productivity decreases

Engineering Contradiction:
Improvevalidation thoroughnessVSAvoidupgrade speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary component detection and validation setup on multiple hosts before initiating the actual upgrade process. By preparing validation environments in advance on each host, the system can then execute comprehensive validation checks in parallel during the upgrade phase, maintaining thoroughness while improving overall productivity through coordinated parallel processing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic parallel processing where the validation process adapts to the state of each host. When one host is ready for validation, it proceeds independently while other hosts prepare or complete different stages. This dynamic approach maintains validation thoroughness for each host while maximizing productivity by utilizing all available hosts simultaneously rather than strictly sequentially.

Inventive Principle:
Principle #15Dynamics

4Reliability

If VM is powered off for upgrade, then component compatibility is validated, but availability decreases

Engineering Contradiction:
Improvecomponent compatibilityVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs component compatibility validation in advance while the VM is still powered on and operational. By detecting upgradeable components and performing validation checks before the VM shutdown required for actual upgrades, the system ensures component compatibility is verified without sacrificing system availability during the validation phase.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation mechanism that operates between the VM runtime environment and the upgrade process. This intermediary enables compatibility checking while the VM remains active, using virtualization interfaces to perform validation without requiring VM shutdown, thus maintaining availability while ensuring component compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10949190B2Upgradeable component detection and validation
Publication Date: 2021.03.16 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10949190B2 patent drawing
  • US10949190B2 patent drawing
  • US10949190B2 patent drawing

AI summary

The disclosure provides for systems and methods for performing upgrades in virtual environments. Some implementations are directed to using an upgrade service to provide pre-upgrade component detection and validation on host(s). A software package may be submitted to an existing software upgrade procedure of a host. The software package may include an upgrade executable that, when launched, provides a new software service, including initializing one or more new public-facing APIs to provide pre-upgrade host component detection and validation. Some implementations are directed to coordinating the upgrade of a first host using an upgrade service launched on another networked machine or second host. While running an upgrade service, the first host may make a request to the second host to coordinate the upgrade of components of the first host while the first host or a VM of the first host running the upgrade service is shut down.