Cloud Subscription Pooling for Automated VM Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current VM deployment in public cloud systems requires significant manual effort and access to multiple subscriptions, making it cumbersome for enterprises with many users and subscriptions to efficiently manage resources.

Innovation Solution

A method of managing public cloud resources by grouping subscriptions into reservations with constraints, allocating these reservations among principals, and generating a deployment plan based on workload metadata to automatically select the appropriate subscription for provisioning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual subscription selection is used for VM deployment, then users can access specific subscriptions, but significant manual effort is required and deployment efficiency decreases

Engineering Contradiction:
ImproveVM deployment operationVSAvoiddeployment time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system pre-groups multiple subscriptions into reservations before deployment is needed. Administrators configure reservations in advance that define constraints and allocate subscriptions to principals, so when a user requests VM deployment, the system can immediately select from pre-configured options without manual intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Reservations act as an intermediary layer between users and subscriptions. Instead of users directly selecting from multiple subscriptions, they request deployment through the reservation system, which automatically matches workload constraints with appropriate reservations and selects suitable subscriptions, eliminating manual subscription selection.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If users need access to multiple subscriptions for deployment, then resource flexibility is improved, but system complexity and access management difficulty increase

Engineering Contradiction:
Improveresource access flexibilityVSAvoidsubscription management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the complex subscription management task into distinct components: reservations (which group subscriptions), principals (which receive allocations), and workload constraints (which guide selection). This segmentation allows users to interact with simplified reservation objects rather than managing individual subscriptions directly.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Reservations serve multiple functions simultaneously: they group subscriptions, allocate resources to principals, enforce constraints, and enable automated selection. This multi-functionality reduces the need for separate mechanisms for each management task, simplifying the overall system despite supporting multiple subscriptions.

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

3Productivity

If automated deployment planning is implemented, then manual effort is reduced, but system complexity in managing reservations and constraints increases

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidreservation management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The deployment planning system operates autonomously by automatically matching workload constraints with reservation constraints, selecting appropriate subscriptions, and generating deployment plans without human intervention. The system serves itself by making intelligent decisions based on pre-configured reservation rules and current resource availability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system manages complexity by working with configurable parameters and constraints that can be adjusted without changing the underlying system architecture. Reservation constraints, workload metadata, and allocation rules are all parameterized, allowing flexible management through configuration rather than structural modification.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11070492B2Pooling public cloud resources from different subscriptions using reservations
Publication Date: 2021.07.20 VMWARE INC
  • US11070492B2 patent drawing
  • US11070492B2 patent drawing
  • US11070492B2 patent drawing

AI summary

An example method of managing virtualized computing resources provided by a public cloud includes: grouping subscriptions in the public cloud into reservations, each of the reservations including constraints on virtualized computing resources provided by at least one of the subscriptions; allocating the reservations among a plurality of principals; receiving a request to provision a workload from a user associated with a first principal of the plurality of principals, wherein the workload includes metadata describing constraints of the workload; generating a deployment plan for the workload based on the metadata therein and at least one of the reservations allocated to the first principal, the deployment plan specifying a first subscription of the subscriptions; and transmitting a deployment.