Virtualized Software Image Creation via Schema Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The lifecycle management of virtualization software in virtualization computing systems is cumbersome and error-prone due to inter-dependencies among software installation bundles (SIBs), making it difficult to make piecemeal changes or understand the current state of the software configuration, which can lead to compliance issues with desired states.
Innovation Solution
A method to create and update software images for virtualized computing environments by retrieving schemas, determining required software products and features, selecting appropriate versions, and validating that the selected versions provide all necessary features, ensuring compatibility and interoperability.
Engineering Contradictions & Design Principles
Engineering 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
Solution Approach 1:
The patent segments the software update process into independent SIB units, each with its own version identifier and dependency metadata. This allows the system to manage updates at the granular SIB level while maintaining awareness of inter-dependencies through the manifest file that tracks relationships between SIBs.
Solution Approach 2:
The patent implements a feedback mechanism where the system automatically checks dependency relationships before applying updates. The manifest file serves as a feedback structure that records which SIBs depend on which others, enabling the system to validate update compatibility and prevent reliability issues caused by broken dependencies.
2Ease of operation
If piecemeal changes are made to virtualization software, then ease of operation is improved, but manufacturing precision deteriorates due to difficulty in capturing overall content
Solution Approach 1:
The patent performs preliminary actions by generating a comprehensive manifest file before deployment that captures the complete state of all SIBs and their relationships. This manifest serves as a baseline that enables precise tracking of what changes are made and what the resulting configuration should be, maintaining manufacturing precision even as individual piecemeal changes are applied.
Solution Approach 2:
The patent creates a copy of the desired software state in the form of a manifest file that documents all SIB versions, dependencies, and configurations. This manifest copy can be compared against the actual deployed state to verify compliance and track changes, enabling precise configuration management despite frequent piecemeal updates.
3Adaptability or versatility
If multiple bulletins are layered over time, then adaptability is improved, but device complexity increases making it difficult to capture current state
Solution Approach 1:
The patent merges the state information from multiple bulletins into a single unified manifest file that captures the cumulative effect of all updates. Rather than managing separate bulletin files, the system combines dependency relationships, version information, and configuration data from all SIBs into one structured manifest, reducing complexity while maintaining adaptability.
Solution Approach 2:
The patent creates a universal manifest structure that serves multiple functions: it tracks version information, documents dependency relationships, records configuration state, and enables compliance verification. This single multi-functional manifest replaces the need to manage multiple separate bulletin files, reducing device complexity while preserving the ability to evolve software through multiple updates.
4Reliability
If complete releases are packaged as ISO images, then reliability is improved, but productivity deteriorates due to inability to make selective updates
Solution Approach 1:
The patent segments the complete release package into individual SIB units that can be selectively applied. Each SIB is a self-contained unit with its own metadata, allowing the system to maintain the reliability of complete releases while enabling selective deployment of only the specific SIBs needed, improving update deployment efficiency.
Solution Approach 2:
The patent applies partial action by allowing the system to deploy only the specific SIBs required for a particular update scenario rather than forcing deployment of complete release packages. The manifest file enables the system to identify and apply only the necessary SIBs, improving productivity by avoiding unnecessary updates while maintaining reliability through dependency validation.
Data Source
AI summary
A method of creating a software image of a solution to be deployed in a virtualized computing environment includes: retrieving a schema of the solution and determining from the schema software products that are required by the solution and software features that are required by the solution; for each software product, selecting a version of the software product to include in the solution and identifying software features provided by the selected version of the software product; and upon confirming that the selected versions of the software products provide all of the software features that are required, creating the software image of the solution that includes the selected version of each of the software products, and saving the software image in a storage device for deployment in the virtualized computing environment.