Automated Update Propagation for Virtual Appliances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing platforms require significant manual input and expertise to configure and manage, making it complex for users to take advantage of their capabilities, and existing methods for updating virtual appliances in distributed systems are tedious and error-prone due to the need for manual user actions across multiple nodes.

Innovation Solution

The implementation of an automated system that uses a cloud manager and application director to manage virtual machine resources, provision, and deploy applications, along with an update mechanism that allows a master virtual appliance to trigger updates on replica nodes using a local update repository, reducing manual intervention and enabling parallel updates across multiple nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual user input and configuration is used to install and deploy components, then flexibility and control are improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improveease of configurationVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system performs self-service through automated configuration management. The configuration management module automatically discovers new nodes, retrieves their configuration data, and pushes configurations without manual intervention. This eliminates the need for users to manually configure each component while maintaining system control through automated processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Configuration data is prepared in advance and stored in a centralized configuration data store before nodes are added to the system. When new nodes join, they automatically receive pre-prepared configuration data, eliminating the need for real-time manual configuration and reducing operational complexity.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If manual update methods are used across multiple nodes, then update control is improved, but productivity and loss of time worsen

Engineering Contradiction:
Improveupdate speedVSAvoidupdate time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

Update packages are prepared in advance and stored in a centralized update data store. When updates are needed, the system automatically distributes these pre-prepared packages to all nodes simultaneously, eliminating the time-consuming sequential manual update process and significantly improving productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The update process is segmented into independent parallel operations: each node receives and installs updates independently from the centralized update server. This segmentation allows multiple nodes to be updated simultaneously rather than sequentially, dramatically reducing total update time while maintaining control over each individual node's update process.

Inventive Principle:
Principle #1Segmentation

3Productivity

If automated update propagation is implemented, then productivity is improved, but reliability may worsen due to potential propagation errors

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidupdate reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback mechanisms where nodes report their configuration and update status back to the configuration management module. This allows the system to verify successful propagation and configuration application, enabling automatic retry or error correction while maintaining high productivity through automated monitoring and validation.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs validation checks before propagating configurations and updates to ensure their correctness and compatibility. Configuration data and update packages are verified against defined schemas and requirements prior to distribution, preventing erroneous data from being propagated and thereby maintaining reliability while enabling automated high-speed deployment.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS10721125B2Systems and methods for update propagation between nodes in a distributed system
Publication Date: 2020.07.21 VMWARE INC
  • US10721125B2 patent drawing
  • US10721125B2 patent drawing
  • US10721125B2 patent drawing

AI summary

Methods and apparatus to propagate an update between nodes in a distributed environment are disclosed. An example apparatus includes a first virtual appliance configured to install an update using an update file from a first update repository, the first update repository located apart from the first virtual appliance, the first virtual appliance configured to form a second update repository at the first virtual appliance, the second update repository to include a copy of the update file from the first update repository. The example apparatus also includes a second virtual appliance, the second virtual appliance formed as a replica of the first virtual appliance, the second virtual appliance to install the update using the copy of the update file from the second update repository.