Template-Driven Infrastructure for Virtualized Server Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data center operators face challenges in providing cost-effective cloud computing services while optimizing resource utilization in virtualized server systems, as existing methods require detailed knowledge of hardware resources and configurations, leading to inefficiencies and potential misalignment with user requirements.

Innovation Solution

The implementation of template-driven infrastructure in virtualized server systems, where a template manager provisions resources using predefined templates that include instructions and tags, allowing users to select configurations for workload domains without needing in-depth knowledge of underlying hardware, and dynamically adjusts resources based on user requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If detailed knowledge of hardware resources and configurations is required for provisioning, then resource allocation precision is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveresource allocation precisionVSAvoidease of provisioning
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent introduces templates as an intermediary layer between users and hardware resources. These templates pre-define resource configurations, allowing users to provision services by selecting templates rather than manually configuring hardware details. This mediator approach maintains allocation precision while dramatically improving ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies preliminary action by pre-configuring resource templates with all necessary hardware specifications and configurations before users need them. These pre-defined templates contain detailed resource allocation settings, so when users select a template, the detailed configuration work has already been completed in advance, eliminating the need for users to have deep hardware knowledge.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If manual configuration of virtualized resources is required, then adaptability to specific user needs is improved, but productivity deteriorates

Engineering Contradiction:
Improveadaptability to user needsVSAvoidprovisioning speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent pre-configures multiple templates covering different service scenarios and user needs. Each template contains pre-defined resource allocations, configurations, and parameters. When users need provisioning, they simply select from these pre-prepared templates, which dramatically accelerates productivity while maintaining adaptability through the variety of available templates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates universal templates that can serve multiple purposes and different user scenarios. Each template is designed to be adaptable through parameters and variables, allowing a single template framework to handle diverse provisioning needs across different services, departments, and use cases, thus maintaining versatility while improving speed.

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

3Ease of operation

If standardized resource provisioning is used, then ease of operation is improved, but adaptability to specific configurations deteriorates

Engineering Contradiction:
Improveease of provisioningVSAvoidconfiguration flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by allowing templates to have both standardized structure and customizable local parameters. Each template provides a standardized framework for ease of operation, while simultaneously allowing users to modify specific local configurations, parameters, and settings to adapt to particular needs. This enables standardization at the template level while maintaining flexibility at the instantiation level.

Inventive Principle:
Principle #3Local quality

4Productivity

If comprehensive hardware knowledge is required for resource management, then resource utilization optimization is improved, but device complexity deteriorates

Engineering Contradiction:
Improveresource utilizationVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces templates as an intermediary that encapsulates complex hardware resource knowledge and configuration details. The templates serve as a buffer between the complex underlying hardware infrastructure and the users, providing simplified interfaces while maintaining optimized resource allocation strategies within the template definitions. This hides system complexity while preserving resource utilization optimization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10855537B2Methods and apparatus for template driven infrastructure in virtualized server systems
Publication Date: 2020.12.01 VMWARE INC
  • US10855537B2 patent drawing
  • US10855537B2 patent drawing
  • US10855537B2 patent drawing

AI summary

Methods, apparatus, and articles of manufacture are disclosed for template driven infrastructure in virtualized server systems. An example apparatus includes a catalog mapper to map a requirement and system information associated with a cloud computing environment including a virtual controller to a first tag including instructions to deploy a first virtual resource corresponding to physical hardware and identify a template including the first tag based on the mapping, a plan generator to generate a plan corresponding to the template including an order of execution of tags including the first tag to deploy virtual resources including the first virtual resource to the cloud computing environment, and a controller invoker to deploy a workload domain to the cloud computing environment to execute an application by executing the instructions associated with the first tag included in the template in response to determining that the virtual controller can execute the plan.