Hypervisor Cloning via Virtualization Manager

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manually installing and configuring hypervisors on multiple host systems in a data center is cumbersome, error-prone, and inefficient, requiring repetitive processes that consume significant resources and increase the likelihood of errors.

Innovation Solution

A method and system for automatically cloning a successfully installed and configured hypervisor across multiple host systems using a virtualization manager, which extracts and stores configuration parameters, validates them, and transmits cloning commands to install and configure cloned hypervisors, ensuring only operating hypervisors are selected for cloning and allowing bulk validation and installation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hypervisors are manually installed and configured on multiple host systems, then each hypervisor can be customized and installed, but the process is cumbersome, error-prone, and consumes significant time and resources

Engineering Contradiction:
Improveinstallation correctnessVSAvoidinstallation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a template hypervisor configuration that can be copied and applied to multiple host systems. The template captures the successfully installed and configured hypervisor's settings, software packages, and parameters, allowing rapid deployment across numerous hosts without manual reconfiguration, thereby reducing installation time while maintaining reliability through consistent validated configurations

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary validation of configuration parameters and software packages before deployment by testing them on a single host first. This preliminary action ensures the configuration works correctly before scaling to multiple hosts, preventing errors from propagating across the entire deployment while establishing a proven template for rapid replication

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If hypervisors are manually configured on each host system, then specific software applications and network configurations can be applied, but the process is repetitive and increases the likelihood of errors

Engineering Contradiction:
Improveconfiguration easeVSAvoidconfiguration accuracy
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent copies the validated configuration from a template hypervisor to multiple target hosts. This ensures configuration accuracy by using a proven working configuration as the source, eliminating manual entry errors while maintaining ease of deployment through automated template application across multiple systems

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system implements feedback mechanisms where the virtualization manager validates configuration parameters and monitors installation status on each host. This feedback loop ensures configurations are applied correctly and allows for error detection and correction, maintaining both ease of automated deployment and high configuration accuracy

Inventive Principle:
Principle #23Feedback

3Productivity

If administrators manually install hypervisors on multiple hosts, then each system can be set up according to specifications, but resources are consumed significantly and efficiency is reduced

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidcomputational resources
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple individual installation processes into a single automated deployment operation. By combining the configuration validation, template creation, and bulk deployment into one integrated process managed by the virtualization manager, the system achieves high productivity through parallel processing while optimizing resource utilization by avoiding redundant manual operations across hosts

Inventive Principle:
Principle #5Merging (Combining)

4Extent of automation

If cloned hypervisors are deployed across multiple hosts, then the creation process is simplified and resource consumption is reduced, but validation of configuration parameters is required to ensure correct installation

Engineering Contradiction:
Improvecloning automationVSAvoidvalidation process complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system performs preliminary validation of configuration parameters before the actual cloning and deployment process. The virtualization manager checks all configuration settings, software packages, and host compatibility in advance, creating a validated template that can be automatically cloned across multiple hosts. This preliminary validation reduces the complexity during deployment while ensuring correctness through pre-verified configurations

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10613708B2Cloning a hypervisor
Publication Date: 2020.04.07 RED HAT ISRAEL
  • US10613708B2 patent drawing
  • US10613708B2 patent drawing
  • US10613708B2 patent drawing

AI summary

Systems and methods for hypervisor cloning. An example method may comprise: receiving a request to install and configure cloned hypervisors on host systems, wherein, for each of the cloned hypervisors, the request comprises identification information for each of the cloned hypervisors; identifying, via the virtualization manager, an existing hypervisor installed on another host system, the existing hypervisor operating in a satisfactory state and having a set of configuration parameters; and transmitting one or more clone commands to the host systems in view of the identification information for each of the cloned hypervisors, wherein each of the clone commands causes a respective host system to install and configure one of the cloned hypervisors according to the set of configuration parameters of the existing hypervisor.