Orchestration Engine Blueprint Transformation for Hybrid Cloud

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current orchestration engines in cloud computing environments face difficulties in translating requirements into hardware and software properties, making it challenging to determine operating system, memory, and processing requirements, and manually selecting blueprints from catalogs is time-consuming and complex.

Innovation Solution

A system comprising a blueprint component and a blueprint transformation component that determines abstract resource types for an abstract blueprint, transforming them into executable resources for an orchestration engine, allowing for efficient determination of computing resource requirements and improving performance by generating executable blueprints that can be executed on a cloud-based platform.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual selection of blueprints from catalogs is used, then users can choose computing resources, but the process is time-consuming and complex

Engineering Contradiction:
Improveease of blueprint selectionVSAvoidtime for manual selection
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs automatic blueprint selection and resource configuration without requiring manual user input. The orchestration engine autonomously translates high-level requirements into executable blueprints, selecting appropriate computing resources based on predefined criteria and constraints, thereby eliminating time-consuming manual selection processes

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

An automated translation layer acts as an intermediary between user requirements and the blueprint catalog. This intermediate orchestration engine converts high-level computing requirements into specific blueprint selections, bridging the gap between user intent and resource allocation without requiring direct user interaction with the catalog

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If orchestration engines translate requirements into hardware and software properties, then resource configuration is determined, but the process is complex and challenging

Engineering Contradiction:
Improveefficiency of resource determinationVSAvoidcomplexity of translation process
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The translation process is divided into distinct modular stages: requirement parsing, resource type identification, blueprint matching, and configuration generation. Each stage handles a specific aspect of the translation, reducing overall complexity by breaking down the monolithic translation process into manageable, independent components

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transforms requirements from high-level abstract parameters to specific hardware and software configuration parameters through automated translation. By systematically mapping parameter types and transformations, the complex translation process becomes manageable through standardized parameter conversion rules

Inventive Principle:
Principle #35Parameter changes

3Extent of automation

If abstract resource types are transformed into executable resources, then blueprints become executable by orchestration engine, but transformation complexity increases

Engineering Contradiction:
Improveautomation of blueprint executionVSAvoidcomplexity of transformation process
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system pre-defines transformation rules and mappings between abstract resource types and executable resources before runtime. By establishing these transformation relationships in advance through blueprint templates and resource type definitions, the actual transformation during execution becomes a straightforward substitution process rather than a complex computation

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11487590B2Orchestration engine resources and blueprint definitions for hybrid cloud composition
Publication Date: 2022.11.01 KYNDRYL INC
  • US11487590B2 patent drawing
  • US11487590B2 patent drawing
  • US11487590B2 patent drawing

AI summary

Techniques that facilitate orchestration engine resources and/or blueprint definitions for hybrid cloud composition are provided. In one example, a system includes a blueprint component and a blueprint transformation component. The blueprint component determines one or more abstract resource types for an abstract blueprint associated with a computing platform. The one or more abstract resource types are indicative of information associated with one or more computing resources for the computing platform. The blueprint transformation component transforms the one or more abstract resource types for the abstract blueprint into one or more executable resources for an executable blueprint that is executable by an orchestration engine.