Dynamic Scaling of Virtual Center Management Infrastructure

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current virtualization management systems face bottlenecks due to statically-sized management layers, which become inefficient when handling large numbers of virtual machines or sudden workload bursts, and lack dynamic scalability and resource utilization.

Innovation Solution

Implement a dynamic management infrastructure where Virtual Centers (VCs) are created or deleted based on demand, utilizing management virtual machines that can be spawned or suspended to handle varying workloads, with a global database for shared management tasks and resources, allowing for auto-scaling and efficient resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a statically-sized management layer is used, then system simplicity is maintained, but scalability and performance under varying workloads deteriorate

Engineering Contradiction:

Improvemanagement infrastructure structureVSAvoidworkload handling capacity

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic management infrastructure by allowing Virtual Centers to be created and deleted based on real-time workload conditions. The system monitors task queue depths and automatically provisions or deprovisions management resources, transforming the static management layer into a dynamic one that adapts to varying workload demands without manual intervention.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the operational parameters of the management infrastructure by adjusting the number of active Virtual Centers based on workload metrics. When task queues exceed thresholds, new Virtual Centers are instantiated; when queues are empty for extended periods, Virtual Centers are deleted. This parameter adjustment resolves the contradiction between structural simplicity and adaptive capacity.

Inventive Principle:

Principle #35Parameter changes

2Productivity

If more management servers are provisioned, then task processing capacity increases, but resource waste occurs during idle periods

Engineering Contradiction:

Improvetask processing throughputVSAvoidcomputational resource waste

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The patent implements a discard-and-recover mechanism where Virtual Centers are discarded (deleted) during idle periods when task queues are empty for longer than a predetermined threshold. When workload increases and queues exceed thresholds, these resources are recovered by creating new Virtual Centers. This cycle eliminates continuous resource consumption while maintaining processing capacity availability.

Inventive Principle:

Principle #34Discarding and recovering

Solution Approach 2:

The system employs periodic monitoring of task queue depths and implements periodic provisioning/deprovisioning actions based on threshold comparisons. This periodic action pattern ensures resources are allocated during high-demand periods and released during low-demand periods, optimizing the balance between productivity and resource efficiency.

Inventive Principle:

Principle #19Periodic action

3Device complexity

If a centralized management architecture is used, then coordination is simplified, but performance bottlenecks occur under high workload

Engineering Contradiction:

Improvemanagement architecture structureVSAvoidtask processing speed

Core Design Contradiction:

Device complexityVSSpeed

Solution Approach 1:

The patent segments the centralized management function into multiple Virtual Centers that can operate in parallel. Each Virtual Center handles a portion of the management tasks, distributing the processing load across multiple instances. This segmentation maintains the simplicity of the centralized model while eliminating the performance bottleneck by enabling concurrent task processing across multiple Virtual Centers.

Inventive Principle:

Principle #1Segmentation

4Reliability

If Virtual Centers use separate private databases, then data isolation is achieved, but collaboration and task sharing between VCs are hindered

Engineering Contradiction:

Improvedata integrity and isolationVSAvoidinter-VC collaboration capability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent merges the previously isolated private databases of Virtual Centers into a shared database infrastructure. This merging enables Virtual Centers to access common data resources and collaborate on management tasks while maintaining appropriate access controls. The shared database eliminates the collaboration barriers while preserving data integrity through centralized management and permission-based access.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS9977689B2Dynamic scaling of management infrastructure in virtual environments

Publication Date: 2018.05.22 VMWARE INC

AI summary

Methods, systems, and computer programs for performing management tasks in a virtual infrastructure are presented. The method includes detecting a change, beyond a predetermined threshold, in a number of tasks waiting to be processed by a plurality of management modules executing as execution environments in the virtual infrastructure, each of the plurality of management modules being a management execution environments for the managed objects. If the detected change is a decrease, the method includes selecting one or more of the management modules to be removed and distributing managed objects handled by the selected management modules to one or more non-selected management modules. If the detected change is an increase, the method includes spawning one or more additional management modules executing as execution environments and distributing selected managed objects from the existing management modules to the additional management modules.