Automatic operating system deployment method, device and system

By writing PN information into BIOS-DMI information and using DHCP and TFTP protocols, the automated operating system installation between the PXE server and the target computer is realized, solving the problems of complex configuration management and insufficient automation in traditional deployment methods, and improving the Deployment efficiency and accuracy.

CN119248296APending Publication Date: 2025-01-03ZIGUANG COMPUTER TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411314906.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-20
Publication Date
2025-01-03

AI Technical Summary

Technical Problem

Traditional PXE deployment methods face the problems of complex configuration management and insufficient automation in batch deployment of domestic operating systems.

Method used

By writing PN information into the BIOS-DMI information of the target computer, using DHCP and TFTP protocols to communicate with the PXE server, obtaining and transmitting installation requirements information, thereby automating the installation process of the operating system.

Benefits of technology

It simplifies the operation process, improves installation accuracy and efficiency, reduces human errors, saves time and labor costs, and reduces the time cost of building installation images, providing support for large-scale deployment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119248296A_ABST
    Figure CN119248296A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of system deployment, in particular to an automatic operating system deployment method, device and system.The method comprises the steps that in the computer production process, PN information is written into BIOS-DMI information, and then a configuration file corresponding to the PN information is configured in a PXE server; and during connection, the PXE server allocates an IP address to the computer through the DHCP service, and sends the target temporary boot file through the TFTP service. And the computer reads PN information in the BIOS-DMI information by using the target temporary boot file, and transmits the PN information to the PXE server. And the PXE server sends a corresponding configuration file to the computer according to the received PN information, so that the installation process of the operating system is started and automatically completed. According to the scheme, the operation process is simplified, the installation accuracy and efficiency are improved, and the possibility of human errors is reduced through automatic processing.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of system deployment, and in particular to an automated operating system deployment method, device and system. Background Art

[0002] Preboot Execution Environment (PXE) is a system that allows a computer to boot from a network. In the absence of a local hard drive, PXE boots the computer by downloading an operating system and applications over the network.

[0003] In the installation of domestic operating systems, the advantages of PXE are particularly obvious, which can significantly simplify the batch deployment and management of a large number of devices. In the traditional PXE deployment process, PXE uses network protocols such as Dynamic Host Configuration Protocol (DHCP) and Trivial File Transfer Protocol (TFTP) to provide the necessary boot program and configuration information to the client, thereby achieving the installation of the operating system.

[0004] However, as the demand for domestic operating systems increases, the complexity of batch deployment also increases accordingly. Traditional PXE deployment methods face problems such as complex configuration management and insufficient automation. Summary of the invention

[0005] In view of this, the present invention provides an automated operating system deployment method, device and system to solve the problems faced by traditional PXE deployment methods such as complex configuration management and insufficient automation as the demand for domestic operating systems increases.

[0006] In a first aspect, the present invention provides an automated operating system deployment method, the method being applied to a target computer, the target computer being connected to a PXE server, the method comprising:

[0007] Writing PN information into the BIOS-DMI information of the target computer; the PN information includes installation requirement information;

[0008] Obtain an IP address from the PXE server through a DHCP service, and obtain a target temporary boot file from the PXE server through a TFTP service;

[0009] The PN information written into the BIOS-DMI information is read through the target temporary boot file, and the PN information is sent to the PXE server; the PXE server includes a configuration file corresponding to each PN information;

[0010] The configuration file returned by the PXE server based on the PN information is obtained, and an automatic installation process of the operating system is performed based on the configuration file.

[0011] The above solution not only simplifies the operation process, but also improves the accuracy and efficiency of installation. Through automated processing, it reduces the possibility of human error and saves time and labor costs. In addition, the reusability of the configuration file of PN information further reduces the time cost of building the installation image, providing strong support for the large-scale deployment of domestic operating systems.

[0012] In an optional implementation manner, writing the PN information into the BIOS-DMI information of the target computer includes:

[0013] During the production process of the target computer, the PN information is written into the BIOS-DMI information of the target computer; the BIOS-DMI information is information stored in a designated data area in the BIOS system of the target computer; the installation requirement information includes the operating system information, driver information and software configuration information that need to be installed on the target computer; and the configuration file corresponding to each PN information includes an operating system image, a driver package and a software configuration package.

[0014] In an optional implementation, the obtaining an IP address from the PXE server through a DHCP service, and obtaining a target temporary boot file from the PXE server through a TFTP service, includes:

[0015] When the target computer starts, sending a DHCP request to the PXE server to obtain the IP address assigned by the PXE server to the target computer;

[0016] Based on the IP address, a TFTP protocol request is sent to the PXE server to obtain the target temporary boot file.

[0017] In an optional implementation, the process of obtaining a configuration file returned by the PXE server based on the PN information and performing an automatic installation process of the operating system based on the configuration file includes:

[0018] Obtaining a configuration file returned by the PXE server based on the PN information, and starting to boot the operating system;

[0019] Based on the configuration file, the installation process of the operating system, driver and software configuration is automatically performed.

[0020] In a second aspect, the present invention provides an automated operating system deployment method, the method being applied to a PXE server, the PXE server being connected to a target computer, the method comprising:

[0021] Allocate an IP address to the target computer through a DHCP service, and send a target temporary boot file to the target computer through a TFTP service, so that the target computer reads the PN information pre-written in the BIOS-DMI information area of ​​the target computer through the target temporary boot file;

[0022] The PN information sent by the target computer is obtained, and a configuration file corresponding to the PN information is sent to the target computer, so that the target computer performs an automatic installation process of the operating system based on the configuration file.

[0023] In a third aspect, the present invention provides an automated operating system deployment device, the device is applied to a target computer, the target computer is connected to a PXE server, and the device comprises:

[0024] A PN information writing module, used to write PN information into the BIOS-DMI information of the target computer; the PN information includes installation requirement information;

[0025] A temporary boot file acquisition module, used to obtain an IP address from the PXE server through a DHCP service, and to obtain a target temporary boot file from the PXE server through a TFTP service;

[0026] A PN information reading module, used for reading the PN information written into the BIOS-DMI information through the target temporary boot file, and sending the PN information to the PXE server; the PXE server includes a configuration file corresponding to each PN information;

[0027] The automatic installation module is used to obtain the configuration file returned by the PXE server based on the PN information, and perform an automatic installation process of the operating system based on the configuration file.

[0028] In a fourth aspect, the present invention provides an automated operating system deployment device, the device is applied to a PXE server, the PXE server is connected to a target computer, and the device comprises:

[0029] a temporary boot file sending module, used for allocating an IP address to the target computer through a DHCP service, and sending a target temporary boot file to the target computer through a TFTP service, so that the target computer reads the PN information pre-written in the BIOS-DMI information area of ​​the target computer through the target temporary boot file;

[0030] The configuration file sending module is used to obtain the PN information sent by the target computer, and send the configuration file corresponding to the PN information to the target computer, so that the target computer performs an automatic installation process of the operating system based on the configuration file.

[0031] In a fifth aspect, the present invention provides an automated operating system deployment system, the system comprising: a target computer and a PXE server connected to each other;

[0032] The target computer is used to write PN information into the BIOS-DMI information of the target computer; the PN information includes installation requirement information;

[0033] The PXE server is used to assign an IP address to the target computer through a DHCP service, and to send a target temporary boot file to the target computer through a TFTP service;

[0034] The target computer is further configured to read the PN information written into the BIOS-DMI information through the target temporary boot file, and send the PN information to the PXE server; the PXE server includes a configuration file corresponding to each PN information;

[0035] The PXE server is further used to send the configuration file corresponding to the PN information to the target computer;

[0036] The target computer is also used to perform an automatic installation process of the operating system based on the configuration file.

[0037] In a sixth aspect, the present invention provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to thereby execute an automated operating system deployment method of the first aspect or any corresponding embodiment thereof.

[0038] In a seventh aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute an automated operating system deployment method according to the first aspect or any corresponding embodiment thereof.

[0039] In an eighth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute an automated operating system deployment method according to the first aspect or any corresponding embodiment thereof.

[0040] The technical solution provided by the present invention may include the following beneficial effects:

[0041] In the process of computer production, the present invention writes PN information containing information such as the operating system, driver, and software to be installed into the BIOS-DMI information, and then configures the operating system, driver, and software information corresponding to the PN on the PXE server. When the computer is connected to the PXE server, the PXE server assigns an IP address to the computer through the DHCP service and sends a target temporary boot file through the TFTP service. The computer uses the target temporary boot file to read the PN information in the BIOS-DMI information and transmits it to the PXE server. The PXE server sends the corresponding operating system, driver, and software to the computer based on the received PN information, thereby starting and automatically completing the installation process of the operating system.

[0042] The above solution not only simplifies the operation process, but also improves the accuracy and efficiency of installation. Through automated processing, it reduces the possibility of human error and saves time and labor costs. In addition, the reusability of the configuration file of PN information further reduces the time cost of building the installation image, providing strong support for the large-scale deployment of domestic operating systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 is a schematic diagram of the structure of an automated operating system deployment system according to an embodiment of the present invention;

[0045] Figure 2 is a flow chart of an automated operating system deployment method according to an embodiment of the present invention;

[0046] Figure 3 is a flow chart of another automated operating system deployment method according to an embodiment of the present invention;

[0047] Figure 4 is a flowchart of another automated operating system deployment method according to an embodiment of the present invention;

[0048] Figure 5 is a structural block diagram of an automated operating system deployment device according to an embodiment of the present invention;

[0049] Figure 6 is a structural block diagram of another automated operating system deployment device according to an embodiment of the present invention;

[0050] Figure 7 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0052] In this embodiment, an automated operating system deployment system is provided. Figure 1 is a schematic diagram of the structure of an automated operating system deployment system according to an embodiment of the present invention. Figure 1 As shown, the system includes: a target computer 110 and a PXE server 120 connected to each other;

[0053] The target computer 110 is used to write PN information into the BIOS-DMI information of the target computer 110; the PN information includes installation requirement information;

[0054] The PXE server 120 is used to assign an IP address to the target computer 110 through a DHCP service, and to send a target temporary boot file to the target computer 110 through a TFTP service;

[0055] The target computer 110 is further used to read the PN information written into the BIOS-DMI information through the target temporary boot file, and send the PN information to the PXE server 120; the PXE server 120 includes a configuration file corresponding to each PN information;

[0056] The PXE server 120 is further used to send the configuration file corresponding to the PN information to the target computer 110;

[0057] The target computer 110 is also used to perform an automatic installation process of the operating system based on the configuration file.

[0058] Furthermore, in this embodiment, the target computer 110 refers to a computer that needs to be installed with an operating system, configured with a driver, and deployed with software. The target computer 110 will have its specific PN information written into its BIOS-DMI (Desktop Management Interface) information during the production process. The PN information contains all the key information required by the computer during the installation process, such as the operating system (OS) to be installed, the corresponding driver (Driver), and specific software (Software).

[0059] Further, in this embodiment, the PXE server 120 is one of the core components of the automated deployment system, and is responsible for providing network boot services, IP address allocation, boot file transmission, and distribution of installation files for the target computer 110. The PXE server 120 communicates with the target computer 110 through the DHCP protocol and the TFTP protocol, and provides corresponding installation resources according to the needs of the target computer 110. The target computer 110 and the PXE server 120 cooperate with each other in the PXE automated deployment system based on BIOS-DMI, and jointly realize the automated installation and configuration of the operating system. The above deployment method not only simplifies the installation process, but also greatly improves the installation efficiency and accuracy.

[0060] In summary, in the process of computer production, the present invention writes PN information containing the information of the operating system, driver, software, etc. to be installed into the BIOS-DMI information, and then configures the operating system, driver, software, etc. corresponding to the PN on the PXE server. When the computer is connected to the PXE server, the PXE server assigns an IP address to the computer through the DHCP service, and sends the target temporary boot file through the TFTP service. The computer uses this target temporary boot file to read the PN information in the BIOS-DMI information and transmits it to the PXE server. The PXE server sends the corresponding operating system, driver, and software to the computer based on the received PN information, thereby starting and automatically completing the installation process of the operating system.

[0061] The above solution not only simplifies the operation process, but also improves the accuracy and efficiency of installation. Through automated processing, it reduces the possibility of human error and saves time and labor costs. In addition, the reusability of the configuration file of PN information further reduces the time cost of building the installation image, providing strong support for the large-scale deployment of domestic operating systems.

[0062] According to an embodiment of the present invention, an embodiment of an automated operating system deployment method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0063] In this embodiment, an automated operating system deployment method is provided, which is applied to Figure 1 The target computer 110 is connected to the PXE server 120. Figure 2 is a flow chart of an automated operating system deployment method according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0064] Step S201, writing PN information into the BIOS-DMI information of the target computer 110; the PN information includes installation requirement information.

[0065] In some optional implementations, the step S201 includes:

[0066] During the production process of the target computer 110, the PN information is written into the BIOS-DMI information of the target computer 110; the BIOS-DMI information is information stored in a specified data area in the BIOS system of the target computer 110; the installation requirement information includes the operating system information, driver information and software configuration information that need to be installed on the target computer 110; each configuration file corresponding to the PN information includes an operating system image, a driver package and a software configuration package.

[0067] For further information, see Figure 3 A flowchart of another automated operating system deployment method is shown. Figure 3The current computer in the target computer 110 is the target computer 110. In this embodiment, during the production process of the target computer 110 (i.e., when the computer leaves the factory and is configured for the first time), the specified PN information is first written into the BIOS-DMI information. The PN information contains the operating system information OS, driver information, and software configuration information required by the target computer 110 during the installation process, and the operating system information OS, driver information, and software configuration information corresponding to the PN information are configured on the PXE server 120. Among them, the operating system information indicates the operating system version and type that the target computer 110 should install. The driver information lists the specific drivers required for the computer hardware to ensure that the hardware can work correctly. The software configuration information includes the application programs, security software, or other configuration settings that need to be preinstalled. The PN information of this embodiment is written into the BIOS-DMI (Desktop Management Interface) information of the target computer 110. BIOS-DMI is a specified data area stored in the BIOS system for storing and managing system configuration information. The BIOS-DMI information can be read when the computer is started, so that the computer can be configured and identified without an operating system. In the PXE server 120, each PN information has a corresponding configuration file. The configuration file contains the specific files and data required for the actual installation process, such as: operating system image (complete operating system installation file), driver package (compressed package containing all necessary hardware drivers), software configuration package (a collection of pre-installed software and its configuration files).

[0068] In this embodiment, by writing PN information into BIOS-DMI information, the target computer 110 can automatically identify and request the required installation files and configurations when connected to the PXE server 120 without manual intervention; the PN information is directly associated with the specific hardware configuration and requirements, ensuring the accuracy and compatibility of the installation process, and the PN information of this embodiment can be customized according to different target computers 110, which is flexible.

[0069] Step S202: obtaining an IP address from the PXE server 120 through a DHCP service, and obtaining a target temporary boot file from the PXE server 120 through a TFTP service.

[0070] In some optional implementations, step S202 includes:

[0071] When the target computer 110 starts, a DHCP request is sent to the PXE server 120 to obtain the IP address assigned by the PXE server 120 to the target computer 110;

[0072] Based on the IP address, a TFTP protocol request is sent to the PXE server 120 to obtain the target temporary boot file (the target temporary boot file may be a temporary boot file NETBOOT.EFI).

[0073] Further, such as Figure 3 As shown, in this embodiment, the current target computer 110 is connected to the PXE server 120, the PXE server 120 assigns an IP address to the target computer 110 through the DHCP service, and sends a temporary boot file NETBOOT.EFI to the target computer 110 through the TFTP service.

[0074] This embodiment obtains an IP address through a DHCP service, that is, when the target computer 110 is started and set to start from the network (i.e., PXE startup), the target computer 110 will first send a DHCP (Dynamic Host Configuration Protocol) request to the network. After receiving the DHCP request, the PXE server 120 will identify the DHCP request as a PXE startup request, and based on the network configuration and policy, assign a temporary IP address to the target computer 110 (it can also assign a subnet mask, a default gateway, and a DNS server). This information will allow the target computer 110 to communicate in the network. The target computer 110 uses the IP address information provided by the PXE server 120 to configure its network interface so that it can communicate with other devices in the network.

[0075] Afterwards, this embodiment also obtains the target temporary boot file through the TFTP service, that is, after the IP address is configured, the target computer 110 will send a TFTP (Trivial File Transfer Protocol) request to the PXE server 120, requesting to download a target temporary boot file named NETBOOT.EFI. This file is a necessary boot program in the PXE startup process, which is used to enable the target computer 110 to load and start the subsequent installation process. After receiving the TFTP request, the PXE server 120 will search for the NETBOOT.EFI file in the TFTP service root directory configured therein and send it to the target computer 110. Through the TFTP protocol, the NETBOOT.EFI file is transferred from the PXE server 120 to the memory of the target computer 110 as the boot program for the next startup of the target computer 110.

[0076] This embodiment ensures that the target computer 110 can obtain the necessary network configuration information and temporary boot files from the PXE server 120, so that the subsequent operating system installation process can be continued. The IP address is obtained through the DHCP service, so that the target computer 110 can communicate in the network; the temporary boot files are obtained through the TFTP service, which provides necessary support for the further startup and installation process of the target computer 110.

[0077] Step S203, reading the PN information written into the BIOS-DMI information through the target temporary boot file, and sending the PN information to the PXE server 120; the PXE server 120 includes a configuration file corresponding to each PN information.

[0078] Further, the current target computer 110 reads the PN information pre-written in the BIOS-DMI information through the NETBOOT.EFI target temporary boot file, and transmits the PN information to the PXE server 120. That is, in this embodiment, during the startup process, the target computer 110 will execute the target temporary boot file NETBOOT.EFI obtained from the PXE server 120 through the TFTP service. The target temporary boot file has the function of reading the BIOS-DMI information. After reading the BIOS-DMI information, the target temporary boot file will extract the PN information therefrom (the PN information is pre-stored in the BIOS-DMI information in a standard format to ensure that the PXE server 120 can recognize and process it). After extracting the PN information, the target computer 110 sends the PN information to the PXE server 120. The PXE server 120 is configured with a mechanism for receiving and parsing such PN information so as to determine and prepare the corresponding operating system, driver and software according to the PN information.

[0079] Exemplarily, one or more configuration files are maintained in the PXE server 120, and these configuration files correspond to different PN information. Each configuration file contains the download path or location information of the operating system image, driver and software package for a specific PN. When the PXE server 120 receives the PN information sent by the target computer 110, it searches and loads the corresponding configuration file to prepare for the subsequent download and installation process.

[0080] Step S204, obtaining a configuration file returned by the PXE server 120 based on the PN information, and performing an automatic installation process of the operating system based on the configuration file.

[0081] In some optional implementations, step S204 includes:

[0082] Obtain the configuration file returned by the PXE server 120 based on the PN information, and start booting the operating system;

[0083] Based on the configuration file, the installation process of the operating system, driver and software configuration is automatically performed.

[0084] Furthermore, the PXE server 120 sends the specified operating system OS, driver, and software to the current computer according to the configuration file corresponding to the PN information of the current target computer 110, and the current computer starts to start the operating system OS and performs the automatic installation process of the OS. That is, in this embodiment, once the PN information is sent to the PXE server 120, the PXE server 120 will search and return the corresponding configuration file based on the PN information. The configuration file contains detailed information such as the operating system, driver, and software configuration that the target computer 110 needs to install. After obtaining the configuration file, the target computer 110 will start to start the operating system, which means transitioning from the network boot process to the actual operating system loading and initialization stage.

[0085] In the automatic installation process, based on the configuration file obtained, the target computer 110 in this embodiment automatically performs the installation process of the operating system, driver, and software configuration. This automated process greatly reduces manual intervention and improves installation efficiency and accuracy. Exemplarily, the specific installation process includes steps such as decompressing the installation image, configuring system parameters, and installing necessary drivers and applications. The entire process is automatically completed according to the instructions in the configuration file. In this embodiment, BIOS-DMI is combined with PXE so that the PXE server 120 can automatically install more OS according to different BIOS-DMIs. The production process only needs to write the BIOS-DMI information in advance and prepare the configuration file corresponding to the PN information in advance. The entire process can be automatically run without manual participation, thereby improving accuracy in production. Once configured, the configuration file of the PN information can be used permanently, greatly saving the time cost of building the installation image.

[0086] In summary, in the process of computer production, the present invention writes PN information containing the information of the operating system, driver, software, etc. to be installed into the BIOS-DMI information, and then configures the operating system, driver, software, etc. corresponding to the PN on the PXE server. When the computer is connected to the PXE server, the PXE server assigns an IP address to the computer through the DHCP service, and sends the target temporary boot file through the TFTP service. The computer uses this target temporary boot file to read the PN information in the BIOS-DMI information and transmits it to the PXE server. The PXE server sends the corresponding operating system, driver, and software to the computer based on the received PN information, thereby starting and automatically completing the installation process of the operating system.

[0087] The above solution not only simplifies the operation process, but also improves the accuracy and efficiency of installation. Through automated processing, it reduces the possibility of human error and saves time and labor costs. In addition, the reusability of the configuration file of PN information further reduces the time cost of building the installation image, providing strong support for the large-scale deployment of domestic operating systems.

[0088] In this embodiment, an automated operating system deployment method is provided, which is applied to Figure 1 The PXE server 120 is connected to the target computer 110. Figure 4 is a flowchart of another automated operating system deployment method according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0089] Step S401, assigning an IP address to the target computer 110 through the DHCP service, and sending a target temporary boot file to the target computer 110 through the TFTP service, so that the target computer 110 reads the PN information pre-written in the BIOS-DMI information area of ​​the target computer 110 through the target temporary boot file.

[0090] Step S402, obtaining the PN information sent by the target computer 110, and sending a configuration file corresponding to the PN information to the target computer 110, so that the target computer 110 performs an automatic installation process of the operating system based on the configuration file.

[0091] In summary, in the process of computer production, the present invention writes PN information containing the information of the operating system, driver, software, etc. to be installed into the BIOS-DMI information, and then configures the operating system, driver, software, etc. corresponding to the PN on the PXE server. When the computer is connected to the PXE server, the PXE server assigns an IP address to the computer through the DHCP service, and sends the target temporary boot file through the TFTP service. The computer uses this target temporary boot file to read the PN information in the BIOS-DMI information and transmits it to the PXE server. The PXE server sends the corresponding operating system, driver, and software to the computer based on the received PN information, thereby starting and automatically completing the installation process of the operating system.

[0092] The above solution not only simplifies the operation process, but also improves the accuracy and efficiency of installation. Through automated processing, it reduces the possibility of human error and saves time and labor costs. In addition, the reusability of the configuration file of PN information further reduces the time cost of building the installation image, providing strong support for the large-scale deployment of domestic operating systems.

[0093] In this embodiment, an automated operating system deployment device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0094] This embodiment provides an automated operating system deployment device, which is applied to Figure 1 In the target computer 110, the target computer 110 is connected to the PXE server 120, such as Figure 5 As shown, including:

[0095] The PN information writing module 501 is used to write the PN information into the BIOS-DMI information of the target computer 110; the PN information includes installation requirement information;

[0096] A temporary boot file acquisition module 502, configured to acquire an IP address from the PXE server 120 through a DHCP service, and acquire a target temporary boot file from the PXE server 120 through a TFTP service;

[0097] The PN information reading module 503 is used to read the PN information written into the BIOS-DMI information through the target temporary boot file, and send the PN information to the PXE server 120; the PXE server 120 includes a configuration file corresponding to each PN information;

[0098] The automatic installation module 504 is used to obtain the configuration file returned by the PXE server 120 based on the PN information, and perform an automatic installation process of the operating system based on the configuration file.

[0099] In some optional implementations, the PN information writing module 501 is further used to:

[0100] During the production process of the target computer 110, the PN information is written into the BIOS-DMI information of the target computer 110; the BIOS-DMI information is information stored in a designated data area in the BIOS system of the target computer 110; the installation requirement information includes the operating system information, driver information and software configuration information that need to be installed on the target computer 110; and the configuration file corresponding to each PN information includes an operating system image, a driver package and a software configuration package.

[0101] In some optional implementations, the temporary boot file acquisition module 502 is further used to:

[0102] When the target computer 110 starts, a DHCP request is sent to the PXE server 120 to obtain the IP address assigned by the PXE server 120 to the target computer 110;

[0103] Based on the IP address, a TFTP protocol request is sent to the PXE server 120 to obtain the target temporary boot file.

[0104] In some optional implementations, the automatic installation module 504 is further configured to:

[0105] Obtaining a configuration file returned by the PXE server 120 based on the PN information, and starting to boot the operating system;

[0106] Based on the configuration file, the installation process of the operating system, driver and software configuration is automatically performed.

[0107] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0108] This embodiment provides another automatic operating system deployment device, which is applied to Figure 1 In the PXE server 120, the PXE server 120 is connected to the target computer 110, such as Figure 6 As shown, including:

[0109] The temporary boot file sending module 601 is used to assign an IP address to the target computer 110 through the DHCP service, and send a target temporary boot file to the target computer 110 through the TFTP service, so that the target computer 110 reads the PN information pre-written in the BIOS-DMI information area of ​​the target computer 110 through the target temporary boot file;

[0110] The configuration file sending module 602 is used to obtain the PN information sent by the target computer 110, and send the configuration file corresponding to the PN information to the target computer 110, so that the target computer 110 performs an automatic installation process of the operating system based on the configuration file.

[0111] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0112] See also Figure 7 , Figure 7 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 7As shown, the computer device includes: one or more processors 710, memory 720, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 710 is taken as an example.

[0113] The processor 710 may be a central processing unit, a network processor or a combination thereof. The processor 710 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable logic gate array, a general purpose array logic or any combination thereof.

[0114] The memory 720 stores instructions executable by at least one processor 710, so that the at least one processor 710 executes the method shown in the above embodiment.

[0115] The memory 720 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 720 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 720 may optionally include a memory remotely arranged relative to the processor 710, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0116] The memory 720 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 720 may also include a combination of the above types of memory.

[0117] The computer device also includes a communication interface 730, which is used for the computer device to communicate with other devices or a communication network.

[0118] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0119] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0120] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the defined scope.

Claims

1. An automated operating system deployment method, characterized in that: The method is applied to a target computer, the target computer is connected to a PXE server, and the method comprises: Writing PN information into the BIOS-DMI information of the target computer; the PN information includes installation requirement information; Obtain an IP address from the PXE server through a DHCP service, and obtain a target temporary boot file from the PXE server through a TFTP service; The PN information written into the BIOS-DMI information is read through the target temporary boot file, and the PN information is sent to the PXE server; the PXE server includes a configuration file corresponding to each PN information; The configuration file returned by the PXE server based on the PN information is obtained, and an automatic installation process of the operating system is performed based on the configuration file.

2. The method according to claim 1, characterized in that The step of writing the PN information into the BIOS-DMI information of the target computer comprises: During the production process of the target computer, the PN information is written into the BIOS-DMI information of the target computer; the BIOS-DMI information is information stored in a designated data area in the BIOS system of the target computer; the installation requirement information includes the operating system information, driver information and software configuration information that need to be installed on the target computer; and the configuration file corresponding to each PN information includes an operating system image, a driver package and a software configuration package.

3. The method according to claim 1, characterized in that The method of obtaining an IP address from the PXE server through a DHCP service and obtaining a target temporary boot file from the PXE server through a TFTP service includes: When the target computer starts, sending a DHCP request to the PXE server to obtain the IP address assigned by the PXE server to the target computer; Based on the IP address, a TFTP protocol request is sent to the PXE server to obtain the target temporary boot file.

4. The method according to claim 2, characterized in that: The process of obtaining the configuration file returned by the PXE server based on the PN information and automatically installing the operating system based on the configuration file includes: Obtaining a configuration file returned by the PXE server based on the PN information, and starting to boot the operating system; Based on the configuration file, the installation process of the operating system, driver and software configuration is automatically performed.

5. An automated operating system deployment method, characterized in that: The method is applied to a PXE server, the PXE server is connected to a target computer, and the method comprises: Allocating an IP address to the target computer through a DHCP service, and sending a target temporary boot file to the target computer through a TFTP service, so that the target computer reads the PN information pre-written in the BIOS-DMI information area of ​​the target computer through the target temporary boot file; The PN information sent by the target computer is obtained, and a configuration file corresponding to the PN information is sent to the target computer, so that the target computer performs an automatic installation process of the operating system based on the configuration file.

6. An automated operating system deployment device, characterized in that: The device is applied to a target computer, the target computer is connected to a PXE server, and the device comprises: A PN information writing module, used to write PN information into the BIOS-DMI information of the target computer; the PN information includes installation requirement information; A temporary boot file acquisition module, used to obtain an IP address from the PXE server through a DHCP service, and to obtain a target temporary boot file from the PXE server through a TFTP service; A PN information reading module, used for reading the PN information written into the BIOS-DMI information through the target temporary boot file, and sending the PN information to the PXE server; the PXE server includes a configuration file corresponding to each PN information; The automatic installation module is used to obtain the configuration file returned by the PXE server based on the PN information, and perform an automatic installation process of the operating system based on the configuration file.

7. An automated operating system deployment device, characterized in that: The device is applied to a PXE server, the PXE server is connected to a target computer, and the device comprises: A temporary boot file sending module is used to assign an IP address to the target computer through a DHCP service, and to send a target temporary boot file to the target computer through a TFTP service, so that the target computer reads the PN information pre-written in the BIOS-DMI information area of ​​the target computer through the target temporary boot file; The configuration file sending module is used to obtain the PN information sent by the target computer, and send the configuration file corresponding to the PN information to the target computer, so that the target computer performs an automatic installation process of the operating system based on the configuration file.

8. An automated operating system deployment system, characterized in that: The system comprises: a target computer and a PXE server connected to each other; The target computer is used to write PN information into the BIOS-DMI information of the target computer; the PN information includes installation requirement information; The PXE server is used to assign an IP address to the target computer through a DHCP service, and to send a target temporary boot file to the target computer through a TFTP service; The target computer is further configured to read the PN information written into the BIOS-DMI information through the target temporary boot file, and send the PN information to the PXE server; the PXE server includes a configuration file corresponding to each PN information; The PXE server is further used to send the configuration file corresponding to the PN information to the target computer; The target computer is also used to perform an automatic installation process of the operating system based on the configuration file.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes an automated operating system deployment method according to any one of claims 1 to 5 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute an automated operating system deployment method according to any one of claims 1 to 5.

Citation Information

Cited By

  • Server system starting method and device, equipment and medium

    CN120255915A