Transparent Reboot Interception for Virtualization Host Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based network updates often disrupt virtualized resources due to the need for maintenance, especially when multiple physical servers require updates, causing inconvenience to users and underutilizing network resources.

Innovation Solution

Implementing transparent reboot migration techniques that intercept reboot events to selectively migrate virtualized resources from outdated hosts to updated hosts during maintenance, minimizing user disruption and optimizing resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If physical servers are updated with new software, firmware, or hardware components, then system reliability and security are improved, but virtualized resources hosted on those servers become nonfunctional and inaccessible during the update process

Engineering Contradiction:
Improvesystem reliabilityVSAvoidvirtualized resource availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by detecting reboot events before they occur and proactively initiating virtualized resource migration to target servers. This advance preparation ensures that when the source server undergoes updates, the virtualized resources have already been relocated, preventing service interruption and maintaining continuous availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces a migration management mechanism as an intermediary between the source and target servers. This intermediary coordinates the reboot interception, migration execution, and resource redirection processes, ensuring seamless transition without requiring direct user intervention or causing service disruption.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If virtualized resources are migrated during reboot events, then user disruption is minimized and service continuity is maintained, but system complexity increases due to the need for reboot interception and migration coordination

Engineering Contradiction:
Improveservice continuityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically detecting reboot events and triggering migration workflows without requiring manual user input. The migration process is autonomously managed through event-driven architecture, where the system monitors itself for reboot conditions and executes appropriate countermeasures, reducing operational complexity despite the advanced functionality.

Inventive Principle:
Principle #25Self-service

3Reliability

If maintenance time intervals are scheduled for server updates, then update reliability is ensured, but network resource utilization decreases due to planned downtime and underutilization of being-updated servers

Engineering Contradiction:
Improveupdate reliabilityVSAvoidresource underutilization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system applies dynamics by transitioning from static scheduled maintenance to dynamic event-driven updates. Instead of fixed maintenance windows that cause planned downtime, the system dynamically responds to actual reboot events, migrating virtualized resources in real-time and enabling servers to be updated immediately when reboots occur, thereby maximizing resource utilization and eliminating idle maintenance periods.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11494217B1Transparent reboot interception migration to facilitate virtualization host updates
Publication Date: 2022.11.08 AMAZON TECH INC
  • US11494217B1 patent drawing
  • US11494217B1 patent drawing
  • US11494217B1 patent drawing

AI summary

This disclosure describes systems, devices, and techniques for migrating virtualized resources from outdated hosts during requested reboots of the virtualized resources, in order to update the outdated hosts. In an example method, a pending reboot a virtualized resource occupying a first host can be identified. At least one component of the first host may be determined to be outdated. In response to identifying the pending reboot and determining that the at least one component is outdated, the virtualized resource may be migrated to a second host. The first host may update the at least one component.