Virtual Appliance Builder with Dependency Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtualization systems lack a simple and repeatable process for creating virtual appliances, requiring developers to possess specific knowledge about repositories and software dependencies, and often fail to manage origin repositories and relationships between software components effectively, leading to barriers in adoption and collaboration among developers.

Innovation Solution

A system and method utilizing a repository metadata server and a dependency resolution service to provide a unified framework for creating, building, and deploying virtual appliances, enabling users to easily manage software components, resolve dependencies, and collaborate through a hosted virtualization environment, with features like caching, real-time analysis, and feedback.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If developers manually manage repositories and software dependencies, then they can have full control over the virtual appliance creation process, but the process becomes complex and requires specific expertise

Engineering Contradiction:
Improveease of creating virtual appliancesVSAvoidcomplexity of managing repositories and dependencies
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a hosted development environment that acts as an intermediary between developers and the complex repository management system. This environment provides automated dependency resolution services and centralized repository management, shielding developers from the underlying complexity while enabling virtual appliance creation without requiring deep expertise in package management or dependency resolution

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If developers work independently on virtual appliance projects, then they maintain autonomy and flexibility, but collaboration and knowledge sharing become difficult

Engineering Contradiction:
Improvecollaboration and knowledge sharingVSAvoidcoordination overhead among developers
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges individual developer workspaces into a unified hosted development environment where multiple developers can access and contribute to the same virtual appliance projects. This consolidation enables automatic synchronization of changes, centralized dependency resolution, and shared access to repository metadata, facilitating collaboration without requiring complex coordination protocols

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If the system caches all repository information locally, then access speed improves, but storage requirements and synchronization complexity increase

Engineering Contradiction:
Improverepository access speedVSAvoidstorage space for cached data
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent implements selective caching where only frequently accessed repository metadata and dependency information are cached locally in the hosted development environment. The system maintains a hierarchical cache structure that stores commonly used package information locally for fast access while keeping the complete repository data available remotely, optimizing the balance between access speed and storage requirements

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8543998B2System and method for building virtual appliances using a repository metadata server and a dependency resolution service
Publication Date: 2013.09.24 ORACLE INT CORP
  • US8543998B2 patent drawing
  • US8543998B2 patent drawing
  • US8543998B2 patent drawing

AI summary

A system and method for building virtual appliances using a repository metadata server and a dependency resolution service is provided. In particular, a hosted web service may provide a collaborative environment for managing origin repositories and software dependencies, whereby remote clients may follow a simple and repeatable process for creating virtual appliances. For example, the repository metadata server may cache and parse metadata associated with an origin repository, download software from the origin repository, and generate resolution data that can be used by the dependency resolution service. The dependency resolution service may then use the resolution data to resolve dependencies for a package selected for an appliance, wherein the dependencies may include packages that are required, recommended, suggested, banned, or otherwise a dependency for the selected package.