Live Kernel Update via Cloned Root Volume Group

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for updating or patching an operating system kernel require rebooting, resulting in downtime and limitations, such as restricted modifications to kernel and kernel extensions, and network blackout during data transfer, which disrupts active systems and user workloads.

Innovation Solution

The solution involves creating a cloned root volume group, migrating application instances to a new logical partition using network tunnels, and applying updates to the cloned partition, allowing seamless live updates without downtime by maintaining network connectivity and minimizing disruption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If kernel update is applied by rebooting the computing system, then the update is successfully installed and executed, but the system experiences downtime and network blackout

Engineering Contradiction:
Improvekernel update reliabilityVSAvoidsystem downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a cloned root volume group and applies the kernel update to the clone before the original system needs updating. This preliminary action allows the updated kernel to be ready and waiting in the cloned partition, so that when the switch occurs, the updated kernel is already in place and can be activated immediately without rebooting the original system.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a cloned root volume group that is a copy of the original root volume group. This clone contains the updated kernel and can be boot-loaded independently. The copying approach allows the system to maintain the original running kernel while having an updated kernel ready in the clone, enabling seamless transitions without system downtime.

Inventive Principle:
Principle #26Copying

2Reliability

If kernel update is applied by rebooting the computing system, then the update takes effect, but network connectivity is lost during the update process

Engineering Contradiction:
Improvekernel update effectivenessVSAvoidnetwork blackout
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a cloned root volume group as an intermediary that holds the updated kernel. Instead of directly updating the running kernel (which would cause network blackout), the update is applied to the clone first. The clone acts as a buffer that allows network operations to continue on the original system while the updated kernel is prepared separately and can be switched to when ready.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If traditional kernel update method is used requiring system reboot, then kernel fixes are applied, but applications must be restarted and workloads are disrupted

Engineering Contradiction:
Improvekernel fix applicationVSAvoidapplication continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the kernel update process from the application execution. By creating a cloned root volume group that contains the updated kernel, the system can load and execute the new kernel without forcing applications to restart. The segmentation allows the kernel layer to be updated independently while the application layer continues running, maintaining productivity and avoiding workload disruption.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10503492B2Live kernel updating using progressive checkpointing and network tunnels
Publication Date: 2019.12.10 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10503492B2 patent drawing
  • US10503492B2 patent drawing
  • US10503492B2 patent drawing

AI summary

Technical solutions are described for performing a live update of an operating system. An example method includes cloning an original root volume group associated with an operating system instance executing in a first logical partition to generate a cloned root volume group for booting a second logical partition. The method further includes applying the update to the cloned root volume group, and booting the second logical partition. The method further includes migrating an application instance, from the original root volume group to the second logical partition. The migration includes creating a network tunnel between the first and second logical partitions, and restarting the application instance on the second logical partition. The migration further includes forwarding data directed to the application instance on the first logical partition to the application instance on the second logical partition, and assigning a network address of the first logical partition to the second logical partition.