Virtual Infrastructure Deployment via Hardware BOM Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In a bring-your-own-hardware (BYOH) model for software-defined data centers, software providers face challenges in deploying virtual infrastructure across diverse hardware devices with varying capabilities, requiring frequent updates to hardcoded deployment services, which is unscalable and inefficient.

Innovation Solution

The method involves retrieving hardware bills of materials (BOMs) for each hardware device, determining deployment policies based on these details, and deploying virtual infrastructure accordingly, allowing for centralized storage and management of certified hardware models without modifying microservices, thus supporting multiple hardware devices and configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If deployment service uses hardcoded logic for each certified hardware device model, then deployment can be performed on multiple hardware devices, but frequent updates are required as more hardware models are certified, making the system unscalable

Engineering Contradiction:
Improvesupport for multiple hardware device modelsVSAvoiddeployment service complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the deployment service into separate microservices, where each microservice is responsible for a specific hardware device model. This allows independent deployment, management, and updating of each hardware model's deployment logic without affecting others, resolving the scalability issue while maintaining support for multiple hardware models.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hardware abstraction layer that acts as an intermediary between the deployment service and physical hardware devices. This abstraction layer standardizes hardware-specific operations, allowing the deployment service to work with diverse hardware models through unified interfaces without requiring hardcoded logic for each model.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If software provider procures only a small variety of hardware device models, then deployment software can be simpler, but customer flexibility and choice are limited

Engineering Contradiction:
Improvedeployment software simplicityVSAvoidcustomer hardware choice
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal deployment service architecture that can handle multiple hardware device models through standardized interfaces and abstraction layers. This allows the same deployment software to work across diverse hardware models, providing customer flexibility while maintaining operational simplicity through unified management.

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

3Adaptability or versatility

If deployment service is updated frequently to support new hardware models, then hardware certification is supported, but maintenance overhead and deployment time increase

Engineering Contradiction:
Improvehardware model certificationVSAvoiddeployment service update time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring deployment microservices for each hardware model with all necessary logic and parameters beforehand. When new hardware models need to be supported, new microservices can be deployed independently without affecting existing ones, significantly reducing update time and maintenance overhead.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent makes the deployment service dynamic by allowing microservices to be added, removed, or updated independently based on hardware certification needs. This dynamic architecture enables the system to adapt to new hardware models without requiring comprehensive updates to the entire deployment service, reducing maintenance time.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20240394090A1Bill-of-materials-driven virtual infrastructure deployment
Publication Date: 2024.11.28 VMWARE INC
  • US20240394090A1 patent drawing
  • US20240394090A1 patent drawing
  • US20240394090A1 patent drawing

AI summary

A method of deploying virtual infrastructure on hardware infrastructure to support execution of software on the virtual infrastructure, includes the steps of: retrieving a hardware bill of materials (BOM) separately for each of a plurality of hardware devices of a group of hardware devices by using identifying information of each of the plurality of hardware devices, wherein the retrieved hardware BOMs include details about hardware components of different hardware device models corresponding to the plurality of hardware devices; determining, based on the details from the retrieved hardware BOMs, policies to apply to a deployment of the virtual infrastructure on the plurality of hardware devices; and deploying the virtual infrastructure on the plurality of hardware devices according to the determined policies.