Virtualization Software Lifecycle Management via Metadata Validation
Find Innovative SolutionsGenerate 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 (SIBs), 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 components are grouped into release units, allowing independent creation and shipping with proper naming and versioning, enabling users to manage the lifecycle by layering base images, add-ons, firmware, drivers, and agents in a standardized way, with metadata validation to ensure compatibility and compliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If SIBs are packaged as one or more ISO images for installation, then the virtualization software can be installed across hosts, but lifecycle management becomes cumbersome and error-prone due to inter-dependencies among SIBs
Solution Approach 1:
The patent segments the monolithic ISO image into individual Software Installation Bundles (SIBs), each representing a discrete software component with its own metadata. This segmentation allows lifecycle management operations to target specific SIBs independently, eliminating the complexity of managing entire ISO images and resolving the contradiction between ease of installation and ease of lifecycle management.
Solution Approach 2:
The patent implements a feedback mechanism through metadata that tracks the current state of each SIB and its dependencies. This feedback enables the system to automatically determine valid update paths and prevent erroneous operations, making lifecycle management straightforward despite complex inter-SIB dependencies.
2Productivity
If new versions or updates of SIBs are released independently, then developers can ship updates separately, but releases must be tightly controlled due to dependencies, making piecemeal changes difficult
Solution Approach 1:
The patent performs preliminary actions by pre-defining dependency relationships and compatibility rules in the metadata of each SIB before releases are made. This preliminary structuring allows the system to automatically validate update sequences and control release complexity without slowing down the actual update deployment process.
3Adaptability or versatility
If multiple bulletins are layered over time to implement updates, then new SIBs can be integrated, but the final image content becomes difficult to capture or describe
Solution Approach 1:
The patent creates and maintains a digital copy of the software state through metadata that records which SIBs are present and their versions. This metadata copy provides an accurate, up-to-date description of the final image content without requiring physical inspection of layered bulletins, preventing information loss while maintaining adaptability.
4Reliability
If end users need to know the current state of virtualization software to ensure compliance with desired state, then comprehensive tracking is needed, but no clear method exists to determine compliance or remediation steps
Solution Approach 1:
The patent implements feedback by continuously tracking the current state of SIBs through metadata and comparing it against the desired state. This feedback mechanism automatically identifies compliance gaps and determines remediation steps, ensuring reliability without requiring complex manual tracking processes.
Data Source
AI summary
An image of a virtualization software and firmware in a plurality of hosts are upgraded by: retrieving metadata of a base image based on a first input that specifies a version of the base image, metadata of an add-on image based on a second input that specifies a server of an original equipment manufacturer (OEM) in which the virtualization software is to be installed, and metadata of drivers and agents based on a third input that specifies a firmware package for the server of the OEM; validating a desired image of the virtualization software by extracting dependencies and conflicts defined in metadata of all payloads of the desired image of the virtualization software, and confirming there are no violations of the extracted dependencies and conflicts; and upgrading the current image of the virtualization software to the desired image and upgrading the current version of the firmware to the desired version.