Virtual Machine Template Update Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for updating virtual machine templates in Virtual Desktop Infrastructure (VDI) systems are inefficient, leading to prolonged downtime and resource usage issues due to the lack of effective strategies for managing software updates across multiple virtual machines.

Innovation Solution

A method that determines coefficients for the importance of continuous operation and criticality of updates, using these to decide when to update virtual machine templates, and includes a process for testing and replacing virtual machines with updated templates to minimize downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software updates are installed on virtual machine templates, then software vulnerabilities are eliminated and software is kept up-to-date, but the virtual machines become unavailable for use during the update process

Engineering Contradiction:
Improvesoftware securityVSAvoidvirtual machine downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system creates a test virtual machine from the template before updating, applies the software update to the test machine, and verifies functionality. This preliminary testing action allows the update to be validated before affecting production virtual machines, reducing the risk of downtime and ensuring security updates are applied safely.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a test virtual machine as a copy of the template before applying updates. This copy allows the update process to be tested in isolation without affecting the actual production virtual machines, enabling safe validation of security patches while maintaining operational availability.

Inventive Principle:
Principle #26Copying

2Reliability

If software updates are applied to all virtual machines, then security vulnerabilities are closed, but the time and computing resources required for updates increase significantly

Engineering Contradiction:
Improvevulnerability patchingVSAvoidupdate efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary testing of software updates on a test virtual machine before deploying them to production. This preliminary action validates the update's effectiveness and compatibility, ensuring that security patches are applied correctly without requiring repeated attempts or causing failures across all virtual machines.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system includes a verification step that analyzes critical events from the test virtual machine's operation during the update process. This feedback mechanism determines whether the updated template is suitable for production use, allowing the system to learn from test results and avoid unnecessary update failures in production environments.

Inventive Principle:
Principle #23Feedback

3Extent of automation

If conventional automatic updating methods are used, then software updates are applied automatically, but the problem of selecting an effective update strategy is not solved

Engineering Contradiction:
Improveautomatic update applicationVSAvoidupdate strategy management
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system creates a test virtual machine from the template before applying updates, performing a preliminary action that simplifies the update strategy by isolating the testing process. This preliminary step allows automated updates to be validated in a controlled environment before production deployment, reducing the complexity of managing update strategies across multiple virtual machines.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

By creating a test virtual machine as a copy of the template, the system enables automated updates to be tested in isolation. This copying mechanism simplifies update strategy management by allowing the system to validate updates on a replica before applying them to production, reducing the complexity of coordinating updates across the entire virtual machine fleet.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9182974B1System and methods for updating software of templates of virtual machines
Publication Date: 2015.11.10 AO KASPERSKY LAB
  • US9182974B1 patent drawing
  • US9182974B1 patent drawing
  • US9182974B1 patent drawing

AI summary

Disclosed are systems, methods and computer readable medium for updating software of templates of virtual machines. An example method includes determining a first coefficient indicative of a level of importance of a continuous operation of one or more virtual machines created from a virtual machine template; determining a second coefficient indicative of a level of criticality of software updates on the one or more virtual machines created from the virtual machine template; determining a third coefficient as a function of the first coefficient and the second coefficient; and when the third coefficient exceeds a threshold, updating the software on the virtual machine template to generate an updated virtual machine template.