Hybrid Cloud Provisioning Template Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mechanisms fail to provide integrated, automated provisioning and deployment of application environments across hybrid cloud platforms, leading to high human error and lack of reusable and interoperable artefacts, making it difficult and time-consuming to manage computing resources across multiple cloud providers.

Innovation Solution

A system and method that generate platform-independent provisioning templates and target platform artefacts, compatible with multiple cloud platforms, allowing for seamless execution and deployment across hybrid cloud environments using a Dynamic Provisioning and Deployment (DPDS) engine.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If provider-specific templates and scripts are used for each cloud provider, then provisioning and deployment can be performed on individual platforms, but the complexity of managing multiple heterogeneous templates increases and reusability decreases

Engineering Contradiction:
Improveplatform compatibilityVSAvoidtemplate management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a universal provisioning template format that can be used across multiple cloud providers (AWS, Azure, GCP, OpenStack). Instead of maintaining separate provider-specific templates, a single template format with provider-agnostic syntax handles provisioning for all platforms, eliminating the need to create and manage multiple heterogeneous templates while maintaining full compatibility with each provider's infrastructure

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

Solution Approach 2:

The patent introduces an intermediary layer consisting of a template compiler and provider-specific adapters. The universal template is compiled into provider-specific deployment scripts through this intermediary layer, which translates the abstract template into concrete provider-specific actions. This mediator handles the complexity of provider differences internally while presenting a unified interface to users

Inventive Principle:
Principle #24Intermediary (Mediator)

2Extent of automation

If manual provisioning processes are used across multiple cloud providers, then flexibility in handling provider-specific requirements is maintained, but human error increases and automation capability decreases

Engineering Contradiction:
Improveprovisioning automationVSAvoidhuman error rate
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The system enables self-service automated provisioning where the template compiler automatically generates provider-specific deployment scripts from universal templates without human intervention. The workflow engine then automatically executes these scripts, and the validation engine automatically verifies deployment success. This end-to-end automation eliminates manual provisioning steps and associated human errors while maintaining the ability to handle provider-specific requirements through the intermediary translation layer

Inventive Principle:
Principle #25Self-service

3Ease of operation

If provider-specific deployment scripts are used for each cloud platform, then deployment can be executed on individual platforms, but interoperability between platforms decreases and reusability of deployment artifacts becomes difficult

Engineering Contradiction:
Improvedeployment executionVSAvoidartifact reusability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal deployment artifact (the provisioning template) that can be executed across multiple cloud platforms. The template uses provider-agnostic syntax and structure that describes deployment intent rather than provider-specific commands. The template compiler automatically adapts this universal artifact into provider-specific execution scripts, enabling the same artifact to be reused across AWS, Azure, GCP, and OpenStack without modification while maintaining ease of execution on each platform

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

4Manufacturing precision

If separate templates are created for each cloud provider, then specific provider requirements can be met, but the time required to provision and manage resources across multiple providers increases

Engineering Contradiction:
Improveprovisioning accuracyVSAvoidprovisioning time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-defining provider-specific adaptation rules and translation mappings in the intermediary layer. When a universal template is submitted, the template compiler already has the necessary provider-specific knowledge embedded to automatically generate correct deployment scripts for any target platform. This preliminary preparation of translation rules eliminates the need to manually create and test separate templates for each provider, significantly reducing provisioning time while maintaining precise adherence to each provider's requirements through the pre-configured adaptation logic

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9935825B2System and method for provisioning and deployment of application environment on hybrid cloud platform
Publication Date: 2018.04.03 WIPRO LTD
  • US9935825B2 patent drawing
  • US9935825B2 patent drawing
  • US9935825B2 patent drawing

AI summary

This disclosure relates generally to computer resource management over multiple cloud platforms, and more particularly to a system and method for provisioning of application environment and deployment of application across hybrid cloud platform. In one embodiment, a method is provided for provisioning an application environment across a hybrid cloud platform. The method comprises generating a platform independent provisioning template based on at least one of a resource specification and a configuration data. The platform independent provisioning template is compatible with multiple cloud platforms. The method further comprises generating a plurality of target platform artifacts compatible with a corresponding plurality of target cloud platforms based on at least one of the resource specification and the configuration data, associating the plurality of target platform artifacts with the platform independent provisioning template, and provisioning the application environment across the hybrid cloud platform by executing the platform independent provisioning template on each of the plurality of target cloud platforms.