Virtual Machine Image Update Timing Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud providers face challenges in determining the optimal timing and cost-effectiveness of updating virtual machine images versus instances, as updating images is complex and resource-intensive, while updating instances can lead to security vulnerabilities and operational disruptions.

Innovation Solution

A method and system for determining update timing based on costs, using algorithms to assess when it is more cost-effective to update virtual machine images or instances, considering factors like patch frequency, resource usage, and risk of bad patches, with the ability to predict future requests and manage patch schedules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If patches are applied to virtual machine images, then security vulnerabilities and bugs are corrected, but the complexity and effort required increases significantly

Engineering Contradiction:
Improvesecurity vulnerability correctionVSAvoidpatch application complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies patches to virtual machine images before they are instantiated as virtual machine instances. This preliminary action allows the cloud provider to update the base image containing security patches and bug fixes, which then automatically applies to all future instances created from that image, avoiding the complexity of patching each individual instance

Inventive Principle:
Principle #10Preliminary action

2Reliability

If patches are applied to virtual machine instances, then each instance receives updates, but compute resources are consumed during instantiation

Engineering Contradiction:
Improveinstance update coverageVSAvoidcompute resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system updates the virtual machine image in advance before instances are created. When an instance is instantiated from an already-patched image, no additional patching operations are required, eliminating the compute resource consumption that would otherwise be needed to apply patches during or after instance creation

Inventive Principle:
Principle #10Preliminary action

3Reliability

If virtual machine images are updated frequently, then security and functionality are maintained, but the cost of updating increases

Engineering Contradiction:
Improvesecurity maintenanceVSAvoidupdate cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent updates a single virtual machine image that serves as a template for multiple virtual machine instances. One image update propagates to numerous instances, making the update process universal and cost-effective compared to updating each instance individually

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

Solution Approach 2:

By performing updates preliminarily on the image before instantiation, the system avoids repeated update operations across multiple instances, significantly reducing the overall cost and effort of maintaining security and functionality

Inventive Principle:
Principle #10Preliminary action

4Reliability

If virtual machine instances are updated after instantiation, then patches are applied, but customers may receive untested instances

Engineering Contradiction:
Improvepatch applicationVSAvoidinstance testing quality
Core Design Contradiction:
ReliabilityVSManufacturing precision

Solution Approach 1:

The cloud provider applies and tests patches on the virtual machine image before it is instantiated as a customer-facing instance. This preliminary testing ensures that any bugs or issues are caught by the provider before the customer receives the instance, guaranteeing higher quality and reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The virtual machine image acts as an intermediary between the patching process and the final instance deployment. The image serves as a tested, validated template that mediates between provider-side security updates and customer-side instance requirements, ensuring quality control

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11074057B2System and method for determining when cloud virtual machines need to be updated
Publication Date: 2021.07.27 KYNDRYL INC
  • US11074057B2 patent drawing
  • US11074057B2 patent drawing
  • US11074057B2 patent drawing

AI summary

A method of providing a computing infrastructure based on virtual machines. An update is received from a software supplier, the update including one or more patches that at least one of correct bugs, correct security vulnerabilities, or introduce at least one new functionality for virtual machines using software of the software supplier for which the update affects and is applicable. It is determined, using a processor on a computer, whether a virtual machine image, stored in a library and used as a template for instantiating virtual machines and affected by the received update, should be updated immediately in accordance with the received update. The virtual machine image is updated if it is determined that such immediate update should be implemented.