Virtual Machine Placement via Device Profile Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual machine placement methods in clusters fail to ensure compatibility with device profiles, leading to downtime during migrations or failovers, as they do not correctly identify suitable host computing systems that support the required virtual devices and configurations.
Innovation Solution
A device profile manager maintains a list of device profiles, mapping them to host computing systems, ensuring that virtual machines are placed on hosts that support the necessary virtual devices and configurations, using mechanisms like load balancing and high availability to maintain compatibility during initial placement, migration, and failover.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If virtual machines are placed on host computing systems without device profile compliance checking, then placement speed is improved, but device compatibility and reliability deteriorate
Solution Approach 1:
The system performs preliminary action by maintaining a pre-established mapping between device profiles and host computing systems before VM placement occurs. This mapping is built in advance based on device compatibility information, allowing the placement decision to be made quickly without performing complex compatibility checks at placement time, thus resolving the contradiction between speed and reliability.
Solution Approach 2:
The device profile mapping acts as an intermediary mechanism between the VM placement decision and the actual host selection. Instead of directly checking compatibility between VM device profiles and host systems during placement, the system uses the pre-built mapping as an intermediary to quickly determine suitable hosts, thereby achieving both fast placement and reliable compatibility.
2Reliability
If device profile compliance is enforced during VM placement, then device compatibility is improved, but placement time and system complexity increase
Solution Approach 1:
The system performs the compatibility mapping action in advance during system initialization or host registration, rather than during VM placement. This preliminary action creates a ready-to-use reference guide that eliminates the need for time-consuming compatibility checks at placement time, thus resolving the contradiction between ensuring compatibility and minimizing placement time.
Solution Approach 2:
The system changes the parameter of how compatibility information is stored and accessed. Instead of storing detailed compatibility matrices that require complex queries during placement, the system transforms the data into a simplified mapping structure that provides compatibility information as a direct lookup, thereby reducing placement time while maintaining reliability.
3Adaptability or versatility
If hardware upgrades are performed without migration planning, then system adaptability is improved, but VM downtime increases
Solution Approach 1:
The system performs preliminary action by pre-mapping device profiles to suitable host systems before hardware upgrades occur. When an upgrade is needed, the system can quickly identify compatible hosts from the pre-established mapping and migrate VMs in advance or during low-impact windows, thereby achieving adaptability while minimizing downtime.
Solution Approach 2:
The system applies beforehand cushioning by maintaining a buffer of pre-identified compatible host systems in the device profile mapping. This cushion allows the system to absorb the disruption of hardware upgrades without causing VM downtime, as alternative compatible hosts are already prepared and waiting to receive migrated VMs.
Data Source
AI summary
Techniques for placing virtual machines based on compliance of device profiles are disclosed. In one embodiment, a list of device profiles may be maintained, each device profile including details of at least one virtual device and associated capabilities. Further, a first device profile from the list of device profiles may be assigned to a virtual machine. Furthermore, the virtual machine may be placed on a host computing system based on compliance of the first device profile.