Asset Weight and Priority Migration for Cloud Resource Balance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud computing environments, existing asset management systems face challenges in efficiently managing resource distribution across compute nodes, leading to issues such as processor, memory, and bandwidth utilization imbalances, which can result in suboptimal performance and increased error events due to unpredictable virtual machine migrations.
Innovation Solution
The system identifies and utilizes asset weight values and priority values to determine which virtual machines to migrate across compute nodes, balancing resource utilization and priority to optimize resource allocation and reduce error impacts, employing live migrations and automated decision-making processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If virtual machines are migrated without considering asset weight and priority values, then resource distribution may be simplified, but resource utilization balance deteriorates and error events increase
Solution Approach 1:
The patent introduces asset weight values and priority values as parameters to characterize assets, enabling differentiated migration decisions. By changing the parameter set used for migration decisions (from simple to multi-dimensional), the system achieves better resource balance and reliability without excessive complexity
Solution Approach 2:
The system continuously monitors resource utilization and uses asset weight/priority values to make informed migration decisions. This feedback mechanism ensures that migrations are performed when they will improve resource balance, reducing error events while maintaining manageable complexity
2Productivity
If asset migrations are performed frequently to balance resources, then resource utilization balance improves, but system stability deteriorates due to unpredictable migrations
Solution Approach 1:
By introducing asset priority values as an additional parameter, the system can distinguish between critical and non-critical assets. This allows migrations to be performed selectively based on both resource balance needs and asset importance, improving efficiency while maintaining stability through predictable migration patterns
Solution Approach 2:
The system pre-calculates asset weight and priority values before migrations occur. This preliminary characterization of assets enables the system to plan migrations that balance resources while maintaining stability, rather than performing reactive and unpredictable migrations
3Manufacturing precision
If asset weight values are used to determine migration, then resource allocation precision improves, but computational complexity increases
Solution Approach 1:
The patent uses asset weight values as a simplified parameter to represent resource allocation needs. By changing from complex multi-factor analysis to weight-based calculation, the system achieves precise resource allocation with manageable computational complexity
Solution Approach 2:
The system calculates asset weight values for all assets but uses them selectively in migration decisions. This partial application of the complexity (calculating weights but not necessarily re-balancing all assets simultaneously) achieves precision while controlling computational burden
Data Source
AI summary
Asset management for a shared pool of configurable computing resources is disclosed. For a set of assets which share a resource on a first compute node, a set of asset weight values is identified. The set of asset weight values indicates a set of utilization shares of the resource by the set of assets. A set of asset priority values is identified with respect to the set of assets on the first compute node. The set of asset priority values indicates a relative status arrangement for the set of assets. Using the set of asset weight values and the set of asset priority values, a determination is made to migrate a first asset of the set of assets from the first compute node to a second compute node. Accordingly, the first asset of the set of assets is migrated from the first compute node to the second compute node.