Blueprint Orchestrator for Heterogeneous Cloud Resource Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions struggle to efficiently compose and manage heterogeneous cloud resources across multiple resource providers, due to complexities in native functionalities and the lack of integrated lifecycle management services.
Innovation Solution
A method and system that utilize a blueprint orchestrator to obtain resource information, generate blueprints, compose resources, and perform lifecycle management operations across multiple resource providers, enabling generic requests and operations across heterogeneous environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If native functionality of each resource provider is invoked to manage resources, then resource-specific operations can be performed, but system complexity increases and lifecycle management becomes difficult
Solution Approach 1:
The patent introduces a lifecycle management (LCM) resource as an intermediary layer between the user and multiple resource providers. This LCM resource composes and coordinates the native functionalities of different resource providers (Azure, AWS, GCP) through a unified interface, enabling heterogeneous resource management without requiring users to directly handle the complexity of each provider's native functionality. The LCM resource acts as a mediator that translates generic LCM operations into provider-specific operations.
2Adaptability or versatility
If multiple resource providers are integrated to provide diverse services, then service versatility improves, but the difficulty of composing and managing resources increases
Solution Approach 1:
The patent implements a universal lifecycle management resource that can manage multiple types of heterogeneous resources from different resource providers through a single unified interface. This LCM resource provides multi-functional capabilities to perform create, read, update, delete, and other lifecycle operations across Azure, AWS, and GCP resources without requiring separate management mechanisms for each provider, thereby simplifying resource composition and management.
3Reliability
If resource providers maintain their own native functionalities, then provider-specific optimization is achieved, but integrated lifecycle management services become complex
Solution Approach 1:
The LCM resource serves as an intermediary that preserves the native functionalities of resource providers while abstracting away the complexity of integrated lifecycle management. It maintains reliable provider-specific operations by invoking native functions when needed, while simultaneously providing unified lifecycle management services that coordinate across multiple providers without exposing the underlying complexity to users.
Data Source
AI summary
Techniques described herein relate to a method for provisioning and managing resources on resource providers. The method may include obtaining, by a blueprint orchestrator, a blueprint generation request associated with resource providers (RPs) from a user; in response to obtaining the blueprint generation request: making a determination that the blueprint generation request is associated with lifecycle management (LCM) services; in response to the determination: obtaining resource information associated with the LCM services and the RPs; generating a blueprint based on the resource information and a software repository associated with the RPs; composing RP resources and LCM resources on the RPs based on a generic composition request using the blueprint; and performing LCM operations on the RP resources using the LCM resources and the blueprint.