Virtual Machine OS Upgrade via Metadata Registry

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for upgrading a virtual machine's (VM) operating system (OS) are resource-intensive and can lead to system performance degradation and potential failures, especially in environments with numerous VMs, due to the need to delete and recreate VMs, which can cause resource lockups and system outages.

Innovation Solution

A method where metadata of the VM is stored in a resource registry, allowing the new OS version to be loaded onto the existing VM instead of deleting and recreating it, using infrastructure functions to manage the upgrade process and configure the VM with the new OS.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the conventional method of deleting and recreating VMs is used for OS upgrades, then the OS can be updated to a new version, but system resources are significantly consumed and system performance degrades

Engineering Contradiction:
ImproveOS version currencyVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by creating a snapshot of the VM's metadata and configuration state before initiating the OS upgrade process. This snapshot is stored in a resource registry, allowing the system to preserve the original VM state and quickly restore it if needed, thereby enabling resource-efficient upgrades without full VM recreation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a lightweight copy of the VM's metadata and configuration information (而非 the entire VM) and storing it in a resource registry. This metadata copy can be rapidly restored to recreate the VM state if upgrade failures occur, avoiding the need to maintain heavy resource allocations during the upgrade process

Inventive Principle:
Principle #26Copying

2Reliability

If the conventional method of deleting and recreating VMs is used for OS upgrades, then the OS can be updated, but the upgrade process time increases due to VM deletion and recreation

Engineering Contradiction:
ImproveOS version currencyVSAvoidupgrade process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by capturing and storing the VM's metadata snapshot before upgrade initiation. This pre-captured metadata can be rapidly restored during upgrade failures, significantly reducing the time required compared to full VM recreation, while ensuring the OS can still be successfully updated

Inventive Principle:
Principle #10Preliminary action

3Productivity

If VM deletion is delayed due to system maintenance or billing policy, then resources remain locked, but the conventional upgrade process cannot proceed

Engineering Contradiction:
Improveupgrade throughputVSAvoidlocked resources
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent applies segmentation by separating the VM's configuration information into a manageable metadata snapshot that can be independently stored and restored. This segmentation allows the upgrade process to proceed using only the metadata copy, releasing the actual VM resources immediately without waiting for deletion policies, thus improving productivity while reducing locked resources

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates a copy of the VM's metadata and stores it in a resource registry, allowing the upgrade process to operate on this lightweight copy rather than requiring the actual VM to be deleted first. This enables immediate resource release while preserving the ability to restore the original state if needed, resolving the conflict between upgrade throughput and locked resources

Inventive Principle:
Principle #26Copying

4Reliability

If the conventional VM recreation process is used, then OS upgrades can be performed, but system stability is compromised due to potential failures during VM recreation

Engineering Contradiction:
ImproveOS version currencyVSAvoidsystem stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The patent implements preliminary action by creating and storing a snapshot of the VM's metadata before the upgrade process begins. This pre-captured metadata serves as a safety net that can be rapidly restored if upgrade failures occur, significantly enhancing system stability while still allowing OS version updates to proceed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies beforehand cushioning by storing the VM's metadata snapshot in a resource registry before initiating the upgrade. This creates a protective buffer that can absorb potential upgrade failures, allowing the system to restore the original state if needed and thus maintaining stability while enabling OS updates

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS10169027B2Upgrade of an operating system of a virtual machine
Publication Date: 2019.01.01 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10169027B2 patent drawing
  • US10169027B2 patent drawing
  • US10169027B2 patent drawing

AI summary

A method, and associated computer system and computer program product. One or more processors of a computer system receive an upgrade request to upgrade a base operating system (OS) of a virtual machine (VM). In response to receiving the upgrade request, the one or more processors store metadata of the VM into a resource registry. The one or more processors load a new version of the base OS onto the VM. The one or more processors retrieve, from the resource registry, the stored metadata for configuring the VM.