Virtual Machine Image Deployment System for Enterprise Data Centers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software deployment in modern networked systems, particularly in complex distributed networks like data centers and test labs, is time-consuming and inefficient, affecting overall performance and requiring significant customization and support for both physical and virtual machines, with inconsistencies in deployment across multiple geographic facilities.

Innovation Solution

A globally-scalable imaging/reimaging system providing a centrally hosted virtualization environment with extensible managed development platforms and virtualization APIs for rapid deployment, activation, and preparation of virtual and physical machine images, enabling scalable and customizable software distribution across mixed environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional software reimaging methods are used, then software can be deployed to computing devices, but the deployment process takes considerable time and reduces overall system efficiency

Engineering Contradiction:
Improvesoftware deployment speedVSAvoiddeployment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent creates a master image once and copies it to multiple target machines simultaneously. The imaging system captures a reference machine's configuration and replicates it across numerous devices, reducing deployment time from hours per machine to minutes for the entire fleet.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by preparing the master image in advance and pre-configuring deployment parameters before actual deployment begins. The reference machine is imaged and validated beforehand, so that when deployment starts, the process executes rapidly without preparation delays.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If manual software deployment methods are used, then individual devices can be updated, but the process is inefficient for large-scale enterprise systems with multiple facilities

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The imaging server provides universal deployment capabilities that work across diverse device types, operating systems, and geographic locations through a single unified platform. It handles everything from reference image creation to distributed deployment to multiple facilities through one system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The imaging server acts as an intermediary between the reference machine and target machines. It captures the reference image, processes it into a deployable format, manages the distribution network, and coordinates deployment to multiple targets, simplifying the complex multi-facility deployment process.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If standardized software images are deployed, then deployment process is simplified, but customization needs of different users cannot be met

Engineering Contradiction:
Improvedeployment process simplicityVSAvoidsoftware customization capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The deployment system is dynamic and adaptable. While the core deployment process remains standardized and simple, the system allows dynamic customization through configuration files, deployment parameters, and post-deployment scripting that can be applied selectively to different user groups or individual machines.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system applies local quality by allowing different customization levels for different targets. Standardized images provide uniform baseline deployment, while location-specific or user-specific modifications can be applied to particular machine groups or individuals, achieving both simplicity and adaptability.

Inventive Principle:
Principle #3Local quality

4Reliability

If physical hardware is maintained for test labs and build labs, then physical computing resources are available, but hardware costs and maintenance requirements increase

Engineering Contradiction:
Improvehardware availabilityVSAvoidphysical hardware quantity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Instead of maintaining numerous physical test and build machines, the system creates virtual copies of computing environments through imaging. Multiple virtual machines can run simultaneously on shared physical infrastructure, providing the same functionality as physical hardware without the associated costs and maintenance burden.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent merges multiple physical hardware requirements into a consolidated virtualized infrastructure. By combining test labs, build labs, and production environments on shared physical hardware with rapid imaging capabilities, the system reduces total hardware quantity while maintaining reliability through virtualization.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8544007B2Customization, deployment and management of virtual and physical machine images in an enterprise system
Publication Date: 2013.09.24 ZHIGU HLDG
  • US8544007B2 patent drawing
  • US8544007B2 patent drawing
  • US8544007B2 patent drawing

AI summary

A web page behavior enhancement (WPBE) control element is provided on a rendered web page enabling a user to perform actions on at least a portion of the web page content such as customizing, editing, analyzing, forwarding, and/or annotating the content. The processed content may be presented on the original web page, on a locally stored version of the web page, or archived for subsequent use, where any changes to the original web page content may be tracked and the user notified about the changes. The WPBE control element(s) may be embedded into the web page at the source web application or at the local browser based on factors like web application capabilities, browser capabilities, user preferences, usage pattern, and comparable ones.