Virtual Server Deployment via Temporary Hypervisor Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional resource management software for virtual servers faces challenges in reducing total processing time due to depletion of shared resources on the hypervisor, leading to increased processing time for multiple deployment requests in large data centers.
Innovation Solution
A method where the management server instructs the virtual server to temporarily execute tasks on a different execution place and then transitions back to the original place, optimizing resource allocation and processing efficiency by utilizing the execution place determining unit to select the shortest processing time path.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple deployment processes are executed simultaneously on the same hypervisor, then resource utilization is improved, but the total processing time increases due to resource depletion
Solution Approach 1:
The patent segments the deployment process into two distinct phases: a resource-intensive preparation phase executed on a temporary hypervisor with abundant resources, and a finalization phase executed on the target hypervisor. This segmentation allows simultaneous execution of multiple deployment processes without resource conflicts, reducing total processing time while maintaining high resource utilization.
Solution Approach 2:
The patent introduces a temporary hypervisor as an intermediary execution environment. This intermediary handles the resource-intensive preparation work, allowing the target hypervisor to remain responsive and avoid resource depletion. The temporary hypervisor acts as a buffer that enables parallel processing without compromising system performance.
2Reliability
If deployment processes are executed sequentially on the target hypervisor, then resource depletion is avoided, but the total processing time increases
Solution Approach 1:
The patent performs preliminary actions (virtual server creation, configuration, and preparation) on a temporary hypervisor before the final deployment to the target hypervisor. This preliminary execution of resource-intensive tasks on the temporary hypervisor allows sequential target hypervisor operations without delays, maintaining resource stability while reducing overall processing time.
Solution Approach 2:
The patent extracts the resource-intensive preparation steps from the target hypervisor and relocates them to a temporary hypervisor. This extraction allows the target hypervisor to execute only lightweight finalization tasks sequentially, avoiding resource depletion while maintaining reliable and stable operations.
3Manufacturing precision
If virtual server preparation is performed on the target hypervisor, then deployment accuracy is improved, but resource depletion occurs leading to increased processing time
Solution Approach 1:
The patent segments the deployment process into preparation (on temporary hypervisor) and finalization (on target hypervisor) phases. This ensures deployment accuracy is maintained during the finalization phase on the target hypervisor, while the preparation phase on the temporary hypervisor handles resource-intensive tasks without affecting target hypervisor throughput.
Solution Approach 2:
The temporary hypervisor serves as an intermediary that handles resource-intensive preparation work, allowing the target hypervisor to focus on precise finalization tasks. This intermediary approach maintains deployment accuracy on the target hypervisor while preventing resource depletion that would reduce processing throughput.
Data Source
AI summary
Each of hypervisors operates on one of physical servers, and a virtual server operates in accordance with a file image on one of data stores. A management server, when being instructed to execute a task that is configured by a series of steps for a hypervisor on the physical server, gives an instruction for changing the execution place of a step to a temporary execution place and executing the task in a case where there is no restriction on the execution place of the step and instructs a default hypervisor to execute the task in a case where there is a restriction on the execution place of the step.


