Resource Orchestration Using Object-Oriented Language

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud resource orchestration tools fail to satisfy a complete set of requirements for both deployment time and runtime management, lacking support for runtime operations and integration of object-oriented concepts, resulting in limited application scope and increased learning overhead.

Innovation Solution

Implementing resource orchestration using an object-oriented language, which creates a correspondence relationship between object-oriented language concepts and resource orchestration requirements, enabling the creation of a workflow for orchestration and subsequent implementation that covers all eight specific requirements, including deployment, runtime operations, and lifecycle management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional orchestration languages (Puppet, Chef, Ansible) are used, then deployment automation is achieved, but runtime operations and lifecycle management are not supported

Engineering Contradiction:
Improvedeployment automationVSAvoidruntime operations support
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent applies universality by designing an orchestration language that performs multiple functions: it handles both deployment automation and runtime operations, as well as lifecycle management. This multi-functional approach resolves the contradiction by making a single orchestration system capable of addressing all stages of resource management rather than being limited to deployment only.

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

Solution Approach 2:

The patent implements dynamics by enabling the orchestration language to adapt its behavior based on the operational phase. The language can dynamically switch between deployment-time configurations and runtime operations, allowing the system to be versatile across different phases while maintaining automated orchestration capabilities throughout.

Inventive Principle:
Principle #15Dynamics

2Ease of manufacture

If specialized orchestration languages are used, then deployment capabilities are improved, but learning overhead increases

Engineering Contradiction:
Improvedeployment capabilitiesVSAvoidlearning overhead
Core Design Contradiction:
Ease of manufactureVSEase of operation

Solution Approach 1:

The patent leverages the universality of object-oriented programming concepts (classes, objects, inheritance, polymorphism) that are already widely known to developers. By building the orchestration language on these familiar paradigms rather than creating entirely new syntax and semantics, the system provides enhanced deployment capabilities while minimizing learning overhead for developers already versed in object-oriented programming.

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

3Adaptability or versatility

If comprehensive orchestration requirements are met, then application scope is expanded, but system complexity increases

Engineering Contradiction:
Improveapplication scopeVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the orchestration system into distinct object-oriented components: resource templates as classes, instantiated resources as objects, and separate modules for deployment, runtime operations, and lifecycle management. This modular segmentation allows the system to meet comprehensive orchestration requirements and expand application scope while managing complexity through organized, reusable components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent utilizes parameter changes by leveraging object-oriented language features such as class parameters, object properties, and configuration variables. By systematically managing complexity through parameterized templates and configurable objects, the system can accommodate diverse application scenarios without proportionally increasing overall system complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10564938B2Method and device of resource orchestration using an object-oriented language
Publication Date: 2020.02.18 EMC IP HLDG CO LLC
  • US10564938B2 patent drawing
  • US10564938B2 patent drawing
  • US10564938B2 patent drawing

AI summary

Embodiments of the present disclosure relate to a method and a device of resource orchestration resources using an object-oriented language, and a program. Specifically the present disclosure discloses a method of resource orchestration using an object-oriented language comprising: creating a correspondence relationship from concepts in the object-oriented language to a requirement of resource orchestration; creating a workflow for implementing the resource orchestration and based upon the correspondence relationship; and implementing the resource orchestration based upon the correspondence relationship and the workflow. The present disclosure also discloses a device of resource orchestration using an object-oriented language, and a computer program product for performing steps of a method of resource orchestration using an object-oriented language.