Virtualization Software Update Management via Desired State Model

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtualization computing systems, the lifecycle management of virtualization software is cumbersome and error-prone due to inter-dependencies among software installation bundles, making it difficult to make piecemeal changes and track the current state of the software configuration across hosts in a cluster.

Innovation Solution

A desired state model is introduced where virtualization software components are grouped into release units, allowing developers to create and ship software independently, with a hierarchical structure that includes a base image, add-ons, firmware, and user-selected solutions, enabling users to define and achieve a desired software state across hosts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If new versions or updates of SIBs are released independently, then software update flexibility is improved, but system reliability deteriorates due to inter-dependencies among SIBs

Engineering Contradiction:
Improvesoftware update flexibilityVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the virtualization software into Software Installation Bundles (SIBs), which are the smallest unit of software that can be shipped and installed. Each SIB is a self-contained module that can be independently managed, updated, and tracked. This segmentation allows flexible updates while maintaining system reliability by ensuring that each SIB's dependencies are properly managed through the desired state model.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a desired state model that continuously compares the current state of software in hosts against the desired state. This feedback mechanism tracks the current state of each SIB and its dependencies, ensuring that updates maintain system reliability by verifying compatibility and dependency satisfaction before and after updates.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If piecemeal changes are made to virtualization software, then ease of operation is improved, but difficulty of detecting and measuring worsens due to layered changes over time

Engineering Contradiction:
Improveease of making changesVSAvoiddifficulty of tracking software state
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent establishes a desired state model in advance that defines the target configuration of software components. Before making piecemeal changes, the system compares the current state against this predefined desired state, allowing operators to easily initiate changes while the system automatically tracks and measures the resulting state transitions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors and tracks the current state of virtualization software, providing feedback that shows how piecemeal changes affect the overall configuration. This feedback mechanism maintains ease of operation by automatically managing the complexity of tracking layered changes, presenting a clear view of the current state versus desired state.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If multiple types of releases are created, then adaptability is improved, but device complexity worsens due to lack of clear rules for creation

Engineering Contradiction:
Improverelease type varietyVSAvoidcomplexity of release management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal desired state model that can represent multiple types of releases (GA releases, rollups, patches, updates, extensions) through a single unified framework. This universal model handles different release types with consistent rules and processes, reducing the complexity of release management while maintaining the ability to handle diverse update scenarios.

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

Data Source

PatentUS11762651B2Software and firmware updates in a combined single pane of glass interface
Publication Date: 2023.09.19 VMWARE INC
  • US11762651B2 patent drawing
  • US11762651B2 patent drawing
  • US11762651B2 patent drawing

AI summary

An image of a virtualization software and firmware in a plurality of hosts are upgraded by performing the steps of: in response to a user input, generating a software specification that specifies a desired state of the virtualization software and a desired state of the firmware; based on the software specification, preparing a desired image of the virtualization software that includes software components of a desired version of the firmware; and coordinating an upgrade to the desired image of the virtualization software and the desired version of the firmware in the hosts. The upgrade includes an upgrade in each of the hosts to the desired version of the firmware, and an upgrade in each of the hosts to the desired image of the virtualization software that includes the software components of the desired version of the base image and the software components of the desired version of the firmware.