Cloud Management Platform Abstraction for Multi-Provider Infrastructure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customers face challenges in managing cloud infrastructures across multiple cloud service providers due to limited support from their primary cloud management platforms, which often cannot accommodate cloud infrastructure tools like Terraform, leading to inefficiencies in deploying and managing cloud resources.

Innovation Solution

The solution involves a cloud management platform that receives a configuration file from cloud infrastructure tools, creates a cloud template, determines necessary cloud resources, maps these resources to native resources, and displays a graphical user interface to manage and visualize the cloud infrastructure, enabling the platform to support and manage cloud resources created by tools like Terraform.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If cloud infrastructure tools like Terraform are used to automate creation and management of cloud infrastructures, then productivity and automation extent are improved, but cloud management platforms cannot support these tools leading to device complexity and ease of operation deterioration

Engineering Contradiction:
Improveautomation of cloud infrastructure creation and managementVSAvoidcloud management platform support for infrastructure tools
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The cloud management platform is enhanced to provide universal support for multiple cloud infrastructure tools (Terraform, CloudFormation, ARM, Bicep) through a unified abstraction layer. The system can ingest configuration files from different tool types, translate them into a common internal representation, and manage resources regardless of the original tool used, making the platform adaptable to various infrastructure-as-code approaches.

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

Solution Approach 2:

An intermediary translation layer is introduced between the cloud infrastructure tools and the cloud management platform. Configuration files from tools like Terraform are converted into an intermediate cloud template format that the platform can understand and manage natively. This mediator enables compatibility without requiring the platform to support each tool's specific syntax and semantics directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If cloud infrastructure tools are integrated into the cloud management platform, then ease of operation is improved, but device complexity increases due to supporting multiple formats and tools

Engineering Contradiction:
Improvemanagement of cloud infrastructuresVSAvoidplatform architecture for supporting multiple tools
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system architecture is segmented into distinct functional layers: a configuration ingestion layer that handles various tool-specific formats, a translation layer that converts to internal representation, and a resource management layer that operates on the unified model. This segmentation isolates complexity to specific modules while maintaining simplicity in the user-facing management interface.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of implementing native support for each cloud infrastructure tool's complex syntax and semantics, the system creates simplified copies or abstractions of resource definitions in a unified internal format. Configuration files from external tools are copied and transformed into this standardized representation, allowing the platform to manage resources through a consistent, simplified interface without directly handling the diversity of external tool formats.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If multiple cloud service providers are supported, then adaptability is improved, but time required for creating and managing infrastructures increases

Engineering Contradiction:
Improvesupport for multiple cloud service providersVSAvoidtime to create and manage cloud infrastructures
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The cloud management platform provides universal multi-provider support through a single unified interface. Users can define cloud infrastructures that span multiple cloud service providers (AWS, Azure, Google Cloud, etc.) using the same configuration approach, and the platform automatically manages the provider-specific details, eliminating the need for separate management processes for each provider.

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

Solution Approach 2:

The system merges the management of multiple cloud providers into a single unified workflow. Configuration files can define resources across different providers simultaneously, and the platform combines the provisioning, monitoring, and management operations into one coordinated process, reducing the total time required compared to managing each provider separately.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11431563B1Intelligent management of cloud infrastructures using a cloud management platform
Publication Date: 2022.08.30 VMWARE INC
  • US11431563B1 patent drawing
  • US11431563B1 patent drawing
  • US11431563B1 patent drawing

AI summary

This relates generally to create and manage a cloud infrastructure using a cloud infrastructure tool. An example method includes, at a server associated with a cloud management platform, receiving a configuration file associated with a cloud infrastructure tool describing a desired state of a cloud infrastructure; creating a cloud template based on the configuration file; determining cloud resources for achieving the desired state of the cloud infrastructure based on the cloud template; for each of the cloud resources: determining a type of the cloud resource; identifying a native resource associated with the cloud management platform based on the type of the resource; mapping an identification of the native resource to the cloud resource; and storing the mapping between the cloud resource and the native resource in a non-native format; and displaying a graphical user interface configured to display a topology for the cloud resources and the cloud infrastructure tool.