Template-Based Provisioning for Distributed Computing Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to provisioning in distributed computing environments are manual, costly, and error-prone, making it difficult to adapt to changes in deployment topologies and accommodate varying numbers of servers, leading to a need for simplified methodologies.

Innovation Solution

An automated method and system for provisioning computing resources that involves obtaining a data structure representing resource dependencies, mapping resources to predefined network templates, and provisioning them across multiple computers to implement applications efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual provisioning approaches are used, then flexibility in handling complex deployment topologies is maintained, but the process becomes costly, time-consuming, and error-prone

Engineering Contradiction:
Improveprovisioning speedVSAvoidprovisioning process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The provisioning process is segmented into distinct phases: topology design phase (defining deployment topologies with templates), mapping phase (mapping application components to topology nodes), and provisioning phase (automated resource allocation). This segmentation allows each phase to be optimized independently, improving overall productivity while managing complexity through structured organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Deployment topologies are designed and templated in advance before actual provisioning occurs. The topology templates define node types, relationships, and configuration parameters beforehand, enabling rapid automated provisioning without manual intervention during deployment. This preliminary action eliminates repetitive manual configuration work.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If fixed infrastructure provisioning is used, then implementation is straightforward, but adaptability to changing deployment topologies and varying server numbers is limited

Engineering Contradiction:
Improvetopology adaptabilityVSAvoidprovisioning implementation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system employs dynamic topology templates that can be instantiated with varying numbers and types of nodes based on实际需求. The mapping mechanism dynamically assigns application components to topology nodes according to resource requirements, enabling the infrastructure to adapt flexibly to different deployment scenarios while maintaining automated provisioning simplicity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The topology templates serve multiple functions: they define deployment structures, specify resource requirements, guide component mapping, and drive automated provisioning. This multi-functionality reduces the need for separate tools and processes, maintaining ease of implementation while achieving high adaptability across different deployment scenarios.

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

3Adaptability or versatility

If deployment topologies are frequently changed to accommodate different requirements, then service flexibility is improved, but the difficulty of changing mappings and adapting to environment changes increases

Engineering Contradiction:
Improveservice flexibilityVSAvoidmapping change complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The mapping between application components and infrastructure resources is segmented into logical layers: application component layer, topology node layer, and physical resource layer. This segmentation allows mapping changes to be made at the topology node level without affecting the entire infrastructure, reducing the complexity of adapting to different service requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Topology templates can be copied and instantiated multiple times with different configurations. When requirements change, existing templates can be replicated with modified parameters rather than creating entirely new mappings from scratch. This copying mechanism simplifies the adaptation process while maintaining service flexibility.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9262143B2Method and apparatus for template-based provisioning in a service delivery environment
Publication Date: 2016.02.16 TAIWAN SEMICONDUCTOR MANUFACTURING CO LTD
  • US9262143B2 patent drawing
  • US9262143B2 patent drawing
  • US9262143B2 patent drawing

AI summary

A method for automated provisioning of computing resources in a distributed computing network includes obtaining a data structure representing a resource dependency characterization of an application to be implemented over the distributed computing network, wherein the data structure indicates a set of resources to be deployed, obtaining a template that represents a predefined network topology for supporting deployment of the set of resources, mapping the set of resources represented in the data structure to the template so as to satisfy a set of component requirements to generate a deployment map, and provisioning the set of resources on a plurality of computers based on the deployment map to implement the application over the distributed computing network.