Virtual Environment Provisioning via Endpoint Registry

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Provisioning and modifying a virtual computing environment with complex interconnectivity and dependencies between applications and services is a difficult and error-prone task due to the variety of server-specific configurations and deployment topologies.

Innovation Solution

A provisioning service that receives a virtual topology defining virtual nodes and their dependencies, provisions nodes hierarchically, using configuration information and endpoint registries to manage interconnectivity parameters, allowing for automatic provisioning and easy reprovisioning when the topology changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual provisioning is used to configure each node with specific parameters and connectivity information, then customization and control are improved, but complexity and error-proneness increase

Engineering Contradiction:
ImprovecustomizationVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system enables self-service provisioning where the provisioning service automatically configures virtual nodes and their interconnections based on topology definitions. The service autonomously retrieves endpoint information, configures connectivity parameters, and provisions nodes without manual intervention, thereby maintaining customization while reducing complexity and errors.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-defining topology configurations and endpoint information in a centralized registry. Before actual node provisioning, the system prepares connectivity information and dependencies in advance, allowing automated retrieval and configuration during provisioning, which simplifies the process while maintaining adaptability.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If automated provisioning is implemented to reduce manual configuration, then ease of operation is improved, but handling of complex dependencies and interconnectivity may be compromised

Engineering Contradiction:
Improveease of provisioningVSAvoidconnectivity accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the provisioning service continuously monitors node provisioning status and connectivity establishment. When nodes are provisioned, the service verifies interconnections by retrieving endpoint information from the registry and confirming successful communication paths, ensuring reliability while maintaining automated operation.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system introduces an intermediary endpoint registry that mediates between automated provisioning and complex dependencies. The registry stores and manages endpoint information, serving as a centralized authority that the provisioning service queries to ensure accurate connectivity configuration, thereby maintaining both automation and reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If topology changes require reprovisioning of nodes, then adaptability is improved, but time consumption and operational complexity increase

Engineering Contradiction:
ImproveflexibilityVSAvoidreprovisioning time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system uses copying by maintaining topology definitions and endpoint information in a centralized registry that can be rapidly replicated. When topology changes occur, the provisioning service copies updated configuration data from the registry to affected nodes, enabling quick reprovisioning without manual reconfiguration, thus reducing time while maintaining flexibility.

Inventive Principle:
Principle #26Copying

4Manufacturing precision

If detailed configuration information is stored for each node, then provisioning accuracy is improved, but storage requirements and system complexity increase

Engineering Contradiction:
Improveprovisioning accuracyVSAvoiddata storage
Core Design Contradiction:
Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The system applies universality by using a single centralized endpoint registry that serves multiple functions: storing endpoint information, managing topology definitions, supporting node provisioning, and enabling reprovisioning. This consolidates data storage requirements while maintaining provisioning accuracy through centralized management rather than distributed storage.

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

Data Source

PatentUS9256473B1Provision a virtual environment based on topology of virtual nodes, node dependencies and base node configuration information
Publication Date: 2016.02.09 EMC IP HLDG CO LLC
  • US9256473B1 patent drawing
  • US9256473B1 patent drawing
  • US9256473B1 patent drawing

AI summary

A method for automatically provisioning a virtual computing environment comprising a plurality of virtual computing nodes includes provisioning a virtual base node using base configuration information that includes a base endpoint that identifies interconnectivity parameters required to communicate with the virtual base node, and storing the base endpoint in an endpoint registry. The method further includes determining that a virtual first node depends on the virtual base node, and receiving the base endpoint from the endpoint registry. Thereafter, the virtual first node is provisioned using the received base endpoint and first configuration information for the virtual first node.