Virtual Machine Image Patching via Preliminary Action

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtual machine (VM) image updating and patching processes are inefficient, often causing resource waste and risking application breakdowns, as they require frequent and complex updates that may not guarantee successful patching without disrupting VM operations.

Innovation Solution

A system that determines the optimal time to apply patches to VM images by analyzing pending updates, resource availability, and historical request data to minimize resource consumption and risk, allowing for targeted updates before instantiation and quick recovery from potential failures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If VM images are patched frequently to ensure up-to-date security and functionality, then system reliability improves, but resource consumption and operational complexity increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by proactively identifying and preparing patches before they are needed. The patch management system continuously monitors for updates, evaluates their impact, and stages them in advance, so that when a patch is needed, it is already ready and tested for rapid deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamic patch management where patch deployment strategies adapt based on real-time conditions. The system can adjust patching schedules, prioritize critical security patches over optional updates, and modify deployment targets based on current system state and risk assessment.

Inventive Principle:
Principle #15Dynamics

2Loss of time

If patches are applied to VM images before instantiation, then provisioning time is reduced, but risk of breaking configurations increases

Engineering Contradiction:
Improveprovisioning timeVSAvoidconfiguration stability
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system applies patches to VM images in advance during the image preparation phase, before the VMs are instantiated. This preliminary patching ensures that when VMs are created, they already contain the latest security updates and bug fixes, eliminating the need for post-instantiation patching and reducing overall provisioning time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements beforehand cushioning by creating and maintaining multiple versions of VM images with different patch levels. This allows the system to rollback to a previous stable version if a new patch causes issues, providing a safety buffer against configuration breakdowns while still enabling rapid deployment of updated images when they prove stable.

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

3Reliability

If individual VM instances are patched instead of image library VMs, then risk of patch failure is reduced, but resource consumption increases

Engineering Contradiction:
Improvepatch success rateVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system merges the advantages of both approaches by implementing a hybrid strategy. Critical security patches are applied to the image library for all VM instances, while optional or less critical patches are applied selectively to individual VMs based on their specific workloads and requirements. This reduces redundant patching operations while maintaining high security standards.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system segments patch management into different categories: mandatory security patches applied to the base image library, important functional patches applied to specific VM families or workloads, and optional patches applied individually to specific VM instances. This segmentation allows optimized resource usage by avoiding unnecessary patching operations on VMs that don't require them.

Inventive Principle:
Principle #1Segmentation

4Reliability

If VM image updates are applied immediately, then system security is improved, but disruption to VM operations increases

Engineering Contradiction:
Improvesystem securityVSAvoidVM operation continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system implements periodic action by scheduling patch deployments during off-peak hours or maintenance windows. Rather than applying patches immediately when they become available, the system evaluates the patch urgency and schedules deployment during periods of lower VM activity, reducing operational disruption while maintaining security posture.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system dynamically adjusts patch deployment timing based on real-time operational conditions. For critical security vulnerabilities, patches may be deployed more urgently with minimal disruption. For non-critical updates, the system schedules them during maintenance windows or low-activity periods, optimizing the balance between security and operational continuity.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10372435B2System, method and program product for updating virtual machine images
Publication Date: 2019.08.06 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10372435B2 patent drawing
  • US10372435B2 patent drawing
  • US10372435B2 patent drawing

AI summary

A system, method and computer program product for allocating shared resources. Upon receiving requests for resources, the system determines whether there are any pending updates for a VM image for provisioning a virtual machine (VM) for the request. For each image with pending updates the system determines whether to replace the stored image with an updated VM image and provision from the replacement or, update a single instance of the image and provision from the single instance. The system also determines an optimal time to update images with pending updates. After replacing an image, the system provides an alert indicating that an updated said VM was provisioned.