Middleware Template Version Inheritance for Cloud Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud provisioning approaches require significant human intervention and time to update middleware provisioning services, leading to errors and inefficiencies when new versions are deployed, as they need to redefine system resource and security settings for all tenants.

Innovation Solution

Creating a first version of a middleware provisioning service template with system and security definitions, and then creating a second version that inherits these definitions from the first, allowing for streamlined updates and minimizing impact on existing consumers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a new version of middleware provisioning service template is created by redefining all system resource and security settings, then the service can be updated to new versions, but the process requires significant human intervention and time

Engineering Contradiction:
Improveservice update speedVSAvoidtime to redefine system resource and security settings
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by creating a parent template that pre-defines system resource and security settings before version updates are needed. When updating to a new version, the system automatically inherits these pre-defined settings from the parent template, eliminating the need to redefine them manually for each version update.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by allowing child templates to automatically copy system resource and security definitions from a parent template. This copying mechanism enables new versions to inherit all necessary configurations automatically, significantly reducing the time and human intervention required for service updates.

Inventive Principle:
Principle #26Copying

2Reliability

If all system resource and security definitions are redefined for each new version, then the service can be updated, but errors increase due to manual intervention

Engineering Contradiction:
Improveaccuracy of service definitionsVSAvoidcomplexity of version update process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent reduces errors by implementing an automatic copying mechanism where child templates inherit system resource and security definitions from parent templates. This automated copying eliminates manual redefinition and associated errors, while the hierarchical template structure simplifies the overall version update process.

Inventive Principle:
Principle #26Copying

3Productivity

If traditional provisioning methods are used for each tenant, then individual tenant requirements can be met, but the process is inefficient and time-consuming

Engineering Contradiction:
Improveprovisioning efficiencyVSAvoidease of service template updates
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent applies universality by creating parent templates that define universal system resource and security settings that can be inherited by multiple child templates serving different tenants. This multi-functional template hierarchy enables efficient provisioning for multiple tenants while maintaining the ability to customize individual tenant requirements through selective inheritance and modification.

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

Data Source

PatentUS10701182B2Creating new versions of provisioning service templates
Publication Date: 2020.06.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10701182B2 patent drawing
  • US10701182B2 patent drawing
  • US10701182B2 patent drawing

AI summary

A method includes creating a first version of a middleware provisioning service template. The first version includes a plurality of system resource definitions and security definitions. The method also includes publishing the first version. The method further includes creating a second version of the middleware provisioning service template and inheriting from the first version to the second version all of the system resource definitions and security definitions.