Automated Patching for Virtualization Servers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual application of patches to virtualization servers, such as VMware ESX Server, is time-consuming and requires multiple reboots, making it inefficient and prone to errors.

Innovation Solution

Automating the patch application process using scripts that download, decompress, and install software patches in the correct order, with a single reboot after all patches are installed, eliminating the need for individual reboots with each patch.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual patch application is performed one patch at a time with reboot after each patch, then each patch can be applied individually with verification, but the total time required for patching increases significantly and system downtime multiplies

Engineering Contradiction:
Improvepatch application reliabilityVSAvoidtotal patching time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent combines multiple individual patch applications into a single batch operation. Instead of applying patches one by one with separate reboots, the system collects multiple patches, applies them in sequence within a single maintenance window, and performs only one reboot at the end. This merging of operations reduces total downtime from hours to minutes while maintaining reliability through automated verification.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary actions by pre-collecting and validating multiple patches before application. The automated script prepares the patch bundle, verifies compatibility, and plans the application sequence in advance. This preliminary preparation ensures that when patches are applied, they can be installed efficiently in a single operation without intermediate interruptions.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual patch application process is used, then administrators can verify each patch individually, but the process becomes prone to human errors and requires significant user intervention

Engineering Contradiction:
Improvepatch verification accuracyVSAvoidpatching process simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patch application system performs self-service through automated scripting. The system automatically downloads patches, validates their integrity, determines the correct application sequence, applies them in the proper order, and verifies successful installation. This eliminates human error in the verification process while maintaining thorough checking, and reduces administrator intervention to simply initiating and monitoring the automated process.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The automated system implements continuous feedback loops during patch application. Each patch is applied and its success is immediately verified by the system through automated checks. If a patch fails, the system receives feedback and can rollback or alert administrators. This automated feedback mechanism maintains verification accuracy while simplifying operation compared to manual processes.

Inventive Principle:
Principle #23Feedback

3Reliability

If multiple reboots are performed during patching, then each patch can be activated properly, but system availability decreases and productivity is reduced

Engineering Contradiction:
Improvepatch activation completenessVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system merges multiple reboot operations into a single reboot event. By applying all necessary patches in sequence before the final reboot, the system ensures that each patch is properly activated while minimizing the total time the system is unavailable. This single consolidated reboot maintains patch activation completeness while maximizing system availability compared to multiple separate reboots.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patch application process maintains continuity of useful action by keeping the system in a controlled state throughout the patching sequence. Rather than interrupting service multiple times with separate reboots, the system continuously applies patches in a coordinated manner and performs one final activation reboot. This continuous approach minimizes productivity loss while ensuring all patches are properly activated.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS11550564B1Automating application of software patches to a server having a virtualization layer
Publication Date: 2023.01.10 GOOGLE LLC
  • US11550564B1 patent drawing
  • US11550564B1 patent drawing
  • US11550564B1 patent drawing

AI summary

A method and system for automating application of software patches to a server system having a virtualization layer. A plurality of software patches are downloaded to a computer system having a first operating system. The software patches to apply to a server console operating system are then determined. The software patches are automatically copied to the server system by executing a first script file. The copied software patches are automatically decompressed by executing a second script file. The decompressed software patches are installed in a specified order by executing the second script file. The console operating system is rebooted only after all software patches are installed.