Desired State Model for Virtualization Software Lifecycle

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The lifecycle management of virtualization software in computing systems is cumbersome and error-prone due to inter-dependencies among software installation bundles, making it difficult for end users to understand and maintain the current state of virtualization software across hosts, and to achieve a desired state.

Innovation Solution

A desired state model is introduced where virtualization software components are grouped into release units, allowing independent management and layering, enabling users to specify a base image, add-ons, firmware, and user-selected drivers and agents to create a desired image for hosts, with metadata management and validation processes to ensure compatibility and compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

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

Engineering Contradiction:
Improvedevelopment flexibilityVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the virtualization software into independent Software Installation Bundles (SIBs), each representing a distinct functional component that can be developed, versioned, and released independently. This segmentation allows development teams to work on individual SIBs without affecting others, while the system manages dependencies through a structured framework that ensures reliable integration of updated components.

Inventive Principle:
Principle #1Segmentation

2Reliability

If lifecycle management is performed with tightly controlled releases, then system reliability is improved, but ease of operation deteriorates due to complexity in managing bulletins and ISO images

Engineering Contradiction:
Improvesystem reliabilityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary management framework that sits between the complex SIB dependency structure and the end user. This intermediary automatically handles the complexity of managing multiple SIBs, their dependencies, and versioning through standardized bulletins and ISO images. Users interact with simple, pre-packaged release units rather than individual SIBs, maintaining reliability while dramatically improving ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple types of releases (GA, rollup, patch, update, extension) are supported, then adaptability is improved, but device complexity increases due to lack of clear rules for creation and management

Engineering Contradiction:
Improverelease type adaptabilityVSAvoidlifecycle management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies parameter changes by defining distinct release unit types (GA, rollup, patch, update, extension) with specific parameters and characteristics for each type. Each release unit type has defined rules for creation, content inclusion, and deployment scenarios. This parameter-based approach enables the system to adapt to different release scenarios while maintaining manageable complexity through standardized templates and automated classification.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If changes are layered on top of each other over time, then adaptability is improved, but measurement precision deteriorates making it difficult to capture or describe the current state

Engineering Contradiction:
Improvesoftware evolution capabilityVSAvoidstate tracking precision
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent implements preliminary action by establishing a structured baseline state for the virtualization software before any changes are applied. Each SIB and release unit is registered with its dependencies and version information in advance. When changes are layered through bulletins or ISO images, the system maintains a precise record of the current state by tracking which release units are present and their versions, enabling accurate state measurement and description at any point in time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11269609B2Desired state model for managing lifecycle of virtualization software
Publication Date: 2022.03.08 VMWARE INC
  • US11269609B2 patent drawing
  • US11269609B2 patent drawing
  • US11269609B2 patent drawing

AI summary

An image of a virtualization software in a plurality of hosts is installed or upgraded by performing the steps of: in response to a user input, generating a software specification that specifies a base image and an add-on image; retrieving metadata of the base image and metadata of the add-on image; generating a desired image of the virtualization software based on the metadata of the base image and the metadata of the add-on image; and instructing each of the hosts to install the desired image of the virtualization software or upgrade a current image of the virtualization software to the desired image of the virtualization software.