Cloud Image Deployment via Host-Specific Cache Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud environments, deploying virtual machine images efficiently is challenging due to high IO operations, data duplication, and scalability issues, especially when multiple virtual machines access shared file systems, leading to performance bottlenecks and reduced cache effectiveness.

Innovation Solution

A method for image deployment that selects hosts based on a deployment factor representing the communality relationship between existing base images and new images, using data block communality values to consolidate identical data blocks and reduce IO operations by storing similar images on the same host, thereby optimizing cache usage and improving IO performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple virtual machines access the same shared file system in parallel, then image deployment can be achieved, but IO performance deteriorates due to random access patterns causing disk search overhead

Engineering Contradiction:
Improveimage deployment capabilityVSAvoidIO performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the monolithic shared file system access into host-specific cache layers. Each host maintains its own cache of base image data blocks, transforming the single shared resource into multiple distributed cache segments. This segmentation eliminates the random access bottleneck by allowing each host to serve its own VMs from local cache, while still enabling image deployment across multiple hosts.

Inventive Principle:
Principle #1Segmentation

2Duration of action of stationary object

If large caches are used to consolidate write operations and prevent disk accesses, then flash device lifetime is extended, but cache management complexity increases and heuristic-based caching cannot be customized

Engineering Contradiction:
Improveflash device lifetimeVSAvoidcache management complexity
Core Design Contradiction:
Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-loading base image data blocks into host-specific caches before they are actually needed by virtual machines. The system proactively caches data blocks from base images based on predicted access patterns, so when VMs need this data, it is already available in memory. This eliminates the need for complex real-time heuristic decisions during actual VM operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the caching parameter from heuristic-based (OS-dependent) to image-structure-based (deterministic). Instead of relying on OS heuristics that cannot be customized, the system uses the known structure of base images and VM access patterns to deterministically determine which data blocks to cache. This transforms cache management from a complex adaptive problem to a straightforward predictive process.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If identical data blocks from different base images are stored separately in caches, then each image can be accessed independently, but data duplication increases cache memory consumption

Engineering Contradiction:
Improveimage independenceVSAvoidcache memory consumption
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges identical data blocks from different base images into a single shared cache entry. When the system detects that multiple base images contain identical data blocks (e.g., common OS files), it stores only one copy in the cache and uses reference counting to track which images reference this shared data. This merging dramatically reduces cache memory consumption while preserving image independence through the reference mechanism.

Inventive Principle:
Principle #5Merging (Combining)

4Productivity

If a single host runs multiple virtual machines with similar base images, then resource utilization improves, but IO operations increase due to random access patterns on the same disk

Engineering Contradiction:
Improveresource utilizationVSAvoidIO operations
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The patent introduces an intermediary cache layer between the virtual machines and the physical disk. This cache acts as a mediator that intercepts read requests from multiple VMs and serves identical data from its own memory rather than forwarding requests to the disk. The intermediary cache absorbs the random access pattern generated by multiple VMs, preventing these harmful IO operations from reaching the physical disk while still allowing high resource utilization on the host.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9195489B2Image deployment in a cloud environment
Publication Date: 2015.11.24 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9195489B2 patent drawing
  • US9195489B2 patent drawing
  • US9195489B2 patent drawing

AI summary

The invention relates to a mechanism for image deployment in a cloud environment comprising at least two hosts coupled to at least one disk, and at least one virtual machine created in at least one host of the at least two hosts by deploying an additional image to the at least one disk. The method is characterized in that the at least one host for deploying an additional image is selected according to a deployment factor representing a communality relationship between one or more existing base images in the cloud environment and the additional image.