Hypervisor-Based Server Deployment and Remote OS Installation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current server deployment methods require specific hardware and software support for remote OS installation, limiting reliability and convenience, especially for cross-operating systems like Linux and Windows, and lack real-time monitoring capabilities.
Innovation Solution
A server deployment method and system in a hypervisor architecture that enables remote OS installation without specific hardware or software support, allowing for automated IP distribution, agent delivery, CPU selection, and monitor screen connection, supporting cross-operating systems like Linux and Windows, and facilitating infrastructure-as-a-service (IaaS) through AMI Composer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If remote OS installation uses KVM switch over IP or remote monitoring software in BMC, then remote installation capability is achieved, but device complexity and deployment complexity increase
Solution Approach 1:
The patent extracts the remote monitoring functionality from traditional hardware devices (KVM switch, BMC) and integrates it into the hypervisor software layer. This allows remote installation capability to be achieved through software rather than additional hardware devices, reducing device complexity while maintaining the ability to remotely monitor and manage server installations.
Solution Approach 2:
The hypervisor is designed to provide multiple functions including remote monitoring, OS installation management, and hardware abstraction. By making the hypervisor multi-functional, the system eliminates the need for separate dedicated devices for each function, thereby reducing overall system complexity while maintaining comprehensive remote installation capabilities.
2Reliability
If remote installation service supports specific OS only (Linux kickstart or Windows RIS), then installation reliability is improved, but adaptability decreases
Solution Approach 1:
The patent introduces the hypervisor as an intermediary layer between the remote installation service and the operating system. This intermediary provides a standardized interface that works across different OS types, allowing the system to maintain reliable installation processes while supporting multiple operating systems including Linux, Windows, and others without requiring OS-specific hardware or software configurations.
Solution Approach 2:
The system segments the installation process into distinct layers: the hypervisor layer handles remote monitoring and coordination, while the OS layer handles specific installation details. This segmentation allows the upper layer to provide universal support for multiple OS types while the lower layer can be customized for each specific operating system, thereby achieving both reliability and adaptability.
3Ease of manufacture
If no remote monitor connection is established, then deployment simplicity is maintained, but installation reliability decreases
Solution Approach 1:
The patent implements automatic monitoring and alerting mechanisms within the hypervisor that self-monitor the installation process without requiring manual intervention. The system automatically detects installation status, monitors for errors, and can trigger alerts or take corrective actions, thereby providing reliable installation monitoring while maintaining deployment simplicity through automation rather than complex manual procedures.
Solution Approach 2:
The hypervisor establishes a feedback loop that continuously monitors the OS installation process and reports status back to the deployment management platform. This automated feedback mechanism provides reliable installation monitoring without requiring complex manual check-in procedures, thereby maintaining deployment simplicity while ensuring installation reliability through continuous automated status reporting.
Data Source
AI summary
A server deployment method and system in a hypervisor architecture are disclosed. The server deployment method, applied between a deployment management platform and at least one deployed server, includes steps of: (a) the deployed server requesting an internet protocol (IP); (b) the deployment management platform distributing the IP; (c) the deployed server requesting an agent; (d) the deployment management platform delivering the agent; (e) the deployed server automatically joining the deployment management platform; (f) the deployment management platform mounting a hard disk shared by the deployed server; (g) the deployment management platform selecting the type of central processing unit (CPU) and installing an operating system to the hard disk shared by the deployed server; and (h) establishing a connection of a monitor screen between the deployment management platform and the deployed server.