Live Appliance Proxy File System for Virtual Machine Version Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies for managing and distributing virtual machines lack efficient mechanisms for publishing, subscribing to, and updating live appliances, which are sequences of virtual machine images, leading to difficulties in ensuring users have the latest versions and seamless integration with host systems.

Innovation Solution

The system enables the publishing, distribution, and subscription of live appliances by using a virtual machine image with a data source that includes version descriptions, allowing for automatic detection and updating of virtual machine images, and providing a proxy for users to run the current version of the virtual machine image through a virtual machine monitor, along with a user file system protocol for data binding and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual version management of virtual machine images is used, then users can control updates, but users cannot always run the latest version without manual intervention

Engineering Contradiction:
Improveautomatic version updateVSAvoidmanual version control
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The system enables virtual machine images to automatically check for version updates, subscribe to update feeds, and download new versions without requiring manual user intervention. The publication system automatically manages version distribution and the subscriber system automatically retrieves and activates latest versions.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements a feedback mechanism where the subscriber system continuously checks for version updates by querying the publication system. When updates are detected, the system automatically downloads and activates new versions, creating a closed-loop update management process.

Inventive Principle:
Principle #23Feedback

2Reliability

If a centralized system for publishing and subscribing to virtual machine images is implemented, then version consistency is improved, but system complexity increases

Engineering Contradiction:
Improveversion consistencyVSAvoidsystem architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is divided into distinct functional modules: a publication system for managing and distributing virtual machine images, a subscriber system for retrieving and running images, and a feed system for version notification. This segmentation allows each component to specialize in its function while maintaining overall system reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces intermediate components including a feed reader that subscribes to version feeds and a feed push mechanism that notifies subscribers of updates. These intermediaries manage the complexity of version synchronization by handling update detection and distribution coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If automatic update detection and downloading is implemented, then users always get the latest version, but network bandwidth and system resources are consumed

Engineering Contradiction:
Improvelatest version guaranteeVSAvoidnetwork bandwidth
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The subscriber system implements periodic update checking by subscribing to version feeds and checking for updates at scheduled intervals rather than continuously. This periodic action ensures the system gets the latest version while consuming network bandwidth only when necessary.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs preliminary actions by pre-subscribing to version feeds and proactively checking for updates before users need them. This allows the system to detect and download updates in advance, ensuring latest version availability while managing network usage during off-peak times.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9063814B2Binding user data files
Publication Date: 2015.06.23 RED HAT LLC
  • US9063814B2 patent drawing
  • US9063814B2 patent drawing
  • US9063814B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer program apparatus, implementing techniques for publishing, subscribing to, or playing live appliances. A live appliance includes a current virtual machine image. In publishing, a proxy file of a live appliance file type is provided to the publisher. The type is mapped to a live appliance player; so that when a proxy file is opened, the current virtual machine image is run. The player automatically binds a writeable file system external to the virtual machine image to the image to provide file storage that is accessible from within the virtual machine image and from a host operating system. The player also creates a subscription to the live appliance on the host computer if one does not exist when the proxy file is run. With the subscription, the player runs the then-current virtual machine image whenever the live appliance is run.