Cloud-Agnostic Load Balancer Instance Group Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud management systems, such as VMware's vRealize Automation, face challenges in provisioning cloud-agnostic resource instances due to limitations in load balancer models and resource mappings across different cloud providers, leading to inefficiencies and unnecessary resource creation.

Innovation Solution

The introduction of a new custom property, 'useInstanceGroupsFrom,' allows load balancers to share instance groups, reducing redundant resource creation and enabling more efficient provisioning of cloud-agnostic resource instances across multiple cloud providers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If load balancers create separate instance groups for each cloud provider, then cloud provider specificity is maintained, but resource redundancy and provisioning inefficiency increase

Engineering Contradiction:
Improveprovisioning efficiencyVSAvoidresource redundancy
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The load balancer is designed to be cloud-agnostic and can provision resources across multiple cloud providers (AWS, Azure, GCP) using a unified interface. The system creates a single instance group that can serve multiple cloud providers simultaneously, eliminating the need for separate instance groups for each provider and thereby reducing resource redundancy while improving provisioning efficiency

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

Solution Approach 2:

The patent merges the instance group creation process across different cloud providers into a single unified operation. Instead of creating separate instance groups for AWS, Azure, and GCP, the system creates one instance group that can be shared across all three cloud providers, reducing overall resource consumption and simplifying management

Inventive Principle:
Principle #5Merging (Combining)

2Quantity of substance

If a single load balancer provisions resources for multiple cloud providers, then resource sharing is enabled, but cloud provider mapping complexity increases

Engineering Contradiction:
Improveresource sharingVSAvoidcloud provider mapping complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The system introduces a cloud-agnostic load balancer as an intermediary layer between the provisioning system and cloud providers. This intermediary abstracts the cloud provider-specific details away, allowing a single load balancer configuration to map to multiple cloud providers without increasing operational complexity. The intermediary handles the mapping logic internally while presenting a simplified interface externally

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of energy

If instance groups are shared across load balancers, then resource utilization is optimized, but instance group management complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidinstance group management complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The instance group is designed as a universal resource that can be shared across multiple load balancers and cloud providers. This multi-functional design allows a single instance group to serve multiple purposes, optimizing resource utilization. The system manages the complexity of sharing through standardized interfaces and automated provisioning mechanisms

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

Data Source

PatentUS20250130863A1Provisioning cloud-agnostic resource instances by sharing cloud resources
Publication Date: 2025.04.24 VMWARE INC
  • US20250130863A1 patent drawing
  • US20250130863A1 patent drawing
  • US20250130863A1 patent drawing

AI summary

provisioning cloud-agnostic resource instances by sharing cloud resources is described herein. One example method includes creating a blueprint using a development platform, wherein the blueprint includes a definition of a resource, and wherein provisioning the resource includes provisioning a first cloud resource and a second cloud resource provided by a cloud provider, provisioning a first instance of the resource of the blueprint by provisioning a first instance of the first cloud resource and a first instance of the second cloud resource, and provisioning a second instance of the resource of the blueprint, wherein provisioning the second instance of the resource includes provisioning a second instance of the first cloud resource and sharing the first instance of the second cloud resource.