Server deployment methods, systems, devices, apparatuses, and media

Abstract

The application discloses a server deployment method, system, device, apparatus and medium, and relates to the technical field of server deployment. The highly personalized and adaptive system configuration is realized through twice booting. The first boot is to deploy a first operating system which is simplified and retains the basic functions of the server, so as to automatically generate a configuration table based on a management node providing a PXE service. The configuration table is compared with configuration files in the subsequent boot of an actual second operating system (official operating system) to generate a personalized deployment file composed of the installation configuration of each server to be installed. The deployment file corresponds to different execution conditions of each server to be installed, and the personalized server deployment is realized. The problem that the single configuration information cannot be distinguished and even time-consuming error problems occur due to the fixed configuration file in the PXE configuration process is avoided, the installation efficiency and accuracy are improved, and the intelligent and personalized server operating system installation process is realized.

Description

Technical Field

[0001] This invention relates to the field of server deployment technology, and in particular to a server deployment method, system, device, apparatus, and medium. Background Technology

[0002] A Preboot Execution Environment (PXE) is a technology that allows a computer to boot an operating system over a network without local storage. It is integrated into the computer's Basic Input / Output System (BIOS) or Unified Extensible Firmware Interface (UEFI), allowing the computer to download and boot an operating system or other software from a network server.

[0003] During the PXE phase, due to the different types of servers, their corresponding deployment configuration information varies greatly. However, the configuration file is fixed during the PXE configuration process, and automatically installing the same configuration file will result in the same installation result. The individual configuration information of each server cannot be distinguished, and the configuration process is time-consuming and prone to errors, reducing configuration efficiency.

[0004] Therefore, how to achieve personalized configuration of each server to improve configuration quality is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this invention is to provide a server deployment method, system, device, apparatus, and medium to solve the problem that the configuration process is time-consuming and error-prone because each server has the same configuration file and cannot distinguish individual configuration information.

[0006] To address the aforementioned technical problems, this invention provides a server deployment method, comprising:

[0007] A first operating system is pre-deployed on each server to be installed; wherein, the first operating system includes the function of collecting hardware information of the server to which it belongs;

[0008] A configuration table is generated based on the configuration information returned by each of the servers to be installed;

[0009] Restart each of the servers to be installed, and perform a pre-boot execution environment installation on the second operating system of each of the servers to be installed to generate an installation configuration file;

[0010] The installation configuration file and the configuration table are compared to obtain the deployment file corresponding to each server to be installed, so as to deploy and install each server to be installed.

[0011] On the one hand, after generating the configuration table but before restarting each of the servers to be installed, the process also includes:

[0012] Obtain the initial configuration information corresponding to each of the servers to be installed;

[0013] Compare the configuration information in the configuration table with the initial configuration information;

[0014] If the configuration information in the configuration table is the same as the initial configuration information, then proceed to the step of restarting each of the servers to be installed.

[0015] On the other hand, after generating the configuration table, the following is also included:

[0016] The first configuration information is obtained by running the first operating system based on the hardware information of each of the servers to be installed;

[0017] Compare the configuration information in the configuration table with the first configuration information;

[0018] If the configuration information in the configuration table is different from the first configuration information, the configuration information in the different configuration table will be marked; and it will be determined that the marked configuration information corresponds to a hardware information failure in the server to be installed.

[0019] Determine whether the hardware information of the server to be installed corresponding to the fault is the key hardware information of the business scenario corresponding to the server to be installed;

[0020] If it is critical hardware information, then the server to be installed will be marked as a faulty server.

[0021] If it is not critical hardware information, then the critical hardware information is identified, and the process proceeds to restart each of the servers to be installed, without comparing the configuration information of the critical hardware information corresponding to the generated installation configuration file.

[0022] On the other hand, after generating the configuration table but before restarting each of the servers to be installed, the process also includes:

[0023] The first operating system is deleted from the memory of each of the servers to be installed, in order to proceed to the step of restarting each of the servers to be installed.

[0024] On the other hand, the step of comparing the installation configuration file and the configuration table to obtain the deployment file corresponding to each of the servers to be installed includes:

[0025] The configuration information corresponding to the installation configuration file and the configuration table is pre-classified to obtain a first general type and a second personalized type; wherein, the configuration information of the first general type is the basic configuration information of all servers to be installed; and the configuration information of the second personalized type is the personalized configuration information corresponding to each of the servers to be installed.

[0026] Determine whether the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table are the same;

[0027] If the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table is the same, then determine whether the configuration information of the second personalized type of the installation configuration file and the second personalized type of the configuration table is the same;

[0028] If the configuration information of the second personality type of the installation configuration file is the same as the configuration information of the second personality type of the configuration table, then the configuration information of the second personality type of the installation configuration file is determined as the deployment file of the current server to be installed;

[0029] If the configuration information of the second personality type of the installation configuration file is different from the configuration information of the second personality type of the configuration table, then it is determined whether it is the key configuration information of the current server to be installed based on the existence of different second personality types of configuration information;

[0030] If it is not the critical configuration information of the server to be installed, then the configuration information of the second personality type of the installation configuration file will be used as the deployment file of the server to be installed.

[0031] On the other hand, before performing a pre-boot execution environment installation on the second operating system of each of the aforementioned servers to be installed to generate the installation configuration file, the process also includes:

[0032] The host configuration protocol service, file transfer protocol service, and file service deployed with the startup execution environment are pre-centralized on a single deployment server;

[0033] Add the mainstream open-source driver files and image files to the deployment server.

[0034] To address the aforementioned technical problems, the present invention also provides a cluster system, including a deployment server and servers to be installed;

[0035] The deployment server is used to pre-deploy a first operating system on each server to be installed; wherein the first operating system includes the function of collecting hardware information of the server; generating a configuration table based on the configuration information returned by each server to be installed; restarting each server to be installed, and performing a pre-boot execution environment installation on the second operating system of each server to be installed to generate an installation configuration file; comparing the installation configuration file and the configuration table to obtain the deployment file corresponding to each server to be installed, so as to deploy and install each server to be installed;

[0036] The server to be installed is used to receive deployment and installation instructions and perform deployment and installation according to the corresponding deployment files.

[0037] To address the aforementioned technical problems, the present invention also provides a server deployment device, comprising:

[0038] The first deployment module is used to pre-deploy a first operating system on each server to be installed; wherein the first operating system includes the function of collecting hardware information of the server to which it belongs;

[0039] The generation module is used to generate a configuration table based on the configuration information returned by each of the servers to be installed;

[0040] The restart module is used to restart each of the servers to be installed and to perform a pre-boot execution environment installation on the second operating system of each of the servers to be installed in order to generate an installation configuration file;

[0041] The second deployment module is used to compare the installation configuration file and the configuration table to obtain the deployment file corresponding to each of the servers to be installed, so as to deploy and install each of the servers to be installed.

[0042] To address the aforementioned technical problems, the present invention also provides a server deployment apparatus, comprising:

[0043] Memory, used to store computer programs;

[0044] A processor for implementing the steps of the server deployment method as described above when executing the computer program.

[0045] To address the aforementioned technical problems, this invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the server deployment method described above. This invention provides a server deployment method that pre-deploys a first operating system on each server to be installed; wherein the first operating system includes the function of collecting hardware information of its respective server; generating a configuration table based on configuration information returned by each server to be installed; restarting each server to be installed and performing a pre-boot execution environment installation on a second operating system for each server to be installed to generate an installation configuration file; comparing the installation configuration file and the configuration table to obtain a deployment file corresponding to each server to be installed, thereby deploying and installing each server to be installed.

[0046] The beneficial effects of this invention lie in achieving a high degree of personalization and adaptability in system configuration through two boot processes. The first boot deploys a streamlined first operating system that retains the basic functions of the server. A configuration table is automatically generated based on the configuration files returned from the management node providing PXE services. This configuration table is then compared with the configuration files under the actual second operating system (the production operating system) in the subsequent boot process to generate a personalized deployment file consisting of the installation configuration for each server to be installed. This deployment file corresponds to different execution conditions for each server, achieving personalized server deployment. This avoids the problems of indistinguishable individual configuration information or time-consuming errors caused by fixed configuration files during the PXE configuration process, improving installation efficiency and accuracy, and realizing an intelligent and personalized server operating system installation process.

[0047] Secondly, the configuration information in the configuration table is compared with the initial configuration information. This first comparison, performed before restarting each server to be installed, verifies the accuracy of the current configuration information generated by the first operating system, thus improving accuracy during subsequent comparisons with the installation and deployment files under the production operating system. The initial configuration information generated after the first operating system starts is compared with the configuration information in the configuration table generated during the first operating system's runtime, ensuring the accuracy of the current configuration information and improving its overall accuracy. The configuration information in the installation configuration file and configuration table is divided into a first general type and a second personalized type. If the configuration information of the first general type is the same, the key configuration information of the second personalized type is compared. This clarifies the accuracy of the comparison for the servers to be installed and improves the precision of personalized configurations. These three types of services are integrated into a single deployment server, improving the simplification and automation of configuration, while also increasing the efficiency of configuration and installation.

[0048] In addition, the present invention also provides a cluster system, server deployment equipment, apparatus and medium, which have the same beneficial effects as the server deployment method described above. Attached Figure Description

[0049] To more clearly illustrate the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 A flowchart illustrating a server deployment method provided in an embodiment of the present invention;

[0051] Figure 2 An architecture diagram of a cluster system provided in an embodiment of the present invention;

[0052] Figure 3 This invention provides a schematic diagram illustrating the interaction between a deployment server and a server to be installed, as provided in an embodiment of the invention.

[0053] Figure 4 A structural diagram of a server deployment device provided in an embodiment of the present invention;

[0054] Figure 5 This is a structural diagram of a server deployment device provided in an embodiment of the present invention. Detailed Implementation

[0055] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of the present invention.

[0056] The core of this invention is to provide a server deployment method, system, device, apparatus, and medium to solve the problem that the configuration process is time-consuming and error-prone because each server has the same configuration file and cannot distinguish individual configuration information.

[0057] To enable those skilled in the art to better understand the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0058] PXE is an important remote boot protocol that allows administrators to remotely boot servers and install and configure operating systems over a network. PXE improves deployment efficiency, reduces human error, saves time and costs, and greatly simplifies server deployment and maintenance processes. With the rapid development of cloud computing and data centers, automated installation technology has become crucial for improving efficiency.

[0059] In a server cluster system, there is a PXE deployment server and other servers to be installed. The number of PXE deployment servers is not limited; there can be one or more. Furthermore, the servers to be installed are usually not of a single type; they may include management nodes, compute nodes, storage nodes, etc. Compute nodes can be central processing units (CPUs) or graphics processing units (GPUs), etc. The hardware of each node can vary significantly, leading to substantial differences in their final uses. Therefore, the same configuration file cannot be used to complete the installation.

[0060] When multiple servers simultaneously enter the PXE deployment workflow, they share the same automatic installation configuration file, resulting in identical installation outcomes. This makes it difficult to differentiate between the installed servers, necessitating individual configuration for each server when forming a cluster. This additional configuration process is time-consuming and prone to errors. The server deployment method provided by this invention solves these technical problems.

[0061] Figure 1 A flowchart of a server deployment method provided in an embodiment of the present invention is shown below. Figure 1 As shown, the method includes:

[0062] S11: Pre-deploy the first operating system on each server to be installed;

[0063] The first operating system includes the function of collecting hardware information of the server it belongs to;

[0064] S12: Generate a configuration table based on the configuration information returned by each server to be installed;

[0065] S13: Restart each server to be installed, and perform a pre-boot execution environment installation on the second operating system of each server to generate the installation configuration file;

[0066] S14: Compare the installation configuration file and configuration table to obtain the deployment file corresponding to each server to be installed, so as to deploy and install each server to be installed.

[0067] Specifically, the first operating system differs from the second operating system. The first operating system is a temporary operating system, while the second is a built-in operating system. Compared to the server's built-in operating system (the official operating system), the temporary operating system is more streamlined, retaining only basic functions. It can be used to collect information about the server's hardware system, such as the motherboard serial number, CPU, GPU, network card models, and storage. The first operating system typically refers to an operating system set up to meet certain short-term needs; it can be a physical server or a virtual server. This type of system does not require long-term operation and management and is typically used for development and testing, temporary projects, handling unexpected events, or network load balancing. There are several methods for creating a first operating system, including using cloud service providers, physical servers, or virtualization technology. The process of setting up a temporary server typically includes determining requirements, selecting a suitable cloud service provider or virtualization software, creating a server instance or virtual machine, configuring network and security settings, installing and configuring software, testing server functionality, and using and maintaining the server. A first operating system can also be quickly deployed using certain tools and services; its selection and management need to consider the server's purpose, configuration requirements, storage capacity, etc.

[0068] A first operating system is pre-deployed on each server to be installed. The purpose is to quickly start a temporary, disposable computing environment to facilitate the acquisition of the configuration table. Hardware information is transmitted back to the management node providing PXE services, i.e., the deployment server. Based on the transmitted configuration information, a configuration table is automatically generated using the first operating system. This configuration table includes automatically installed configurations such as serial numbers, hostnames, user passwords, network information (e.g., Internet Protocol (IP), Domain Name System (DNS), etc.), storage allocation information, and necessary driver information (e.g., GPU, InfiniBand (IB) cards, etc.).

[0069] Step S13 involves restarting each server to be installed. PXE installation is then performed on the secondary operating system of each server to generate an installation configuration file. By comparing and filtering this installation configuration file with the configuration table, the corresponding personalized configuration deployment file for each server can be determined, facilitating precise and personalized installation. The process for corresponding installation configuration files is the same as the regular configuration installation process and is not specified here.

[0070] Traditional PXE deployments typically follow this workflow:

[0071] 1. When the server to be installed boots from bare metal, it will automatically enter network installation mode, or it can be controlled to enter network installation mode through the BIOS, Baseboard Management Controller (BMC), etc. At this time, the PXE-enabled network card will send a DHCP request to the Dynamic Host Configuration Protocol Service (DHCP) server in the network (usually the PXE deployment server) to obtain an IP address and other network configuration information.

[0072] 2. After receiving the request, the DHCP server will send a DHCP response to the server to be installed. This response includes network configuration information such as IP address, subnet mask, and gateway, as well as the IP address of the PXE deployment server and the boot file name (e.g., bootx64.efi).

[0073] 3. After receiving the DHCP response, the server to be installed will send a TFTP request to the PXE deployment server to download the boot file. The boot file requested for download is usually the PXE bootloader. The PXE bootloader is a specific software, usually located on the PXE server, used to help the computer complete the boot process in a network environment.

[0074] 4. The PXE deployment server will respond to the Trivial File Transfer Protocol Service (TFTP) request from the server to be installed and transfer the boot file to the server to be installed.

[0075] 5. After the server to be installed successfully downloads the boot file, it will load the file and execute the program within it, thereby initiating the process of remotely booting the operating system. During the boot process, the server to be installed will download the installation image and configuration files from the PXE deployment server. The configuration files are designed to replace the steps that need to be manually entered in the installation interface during manual installation.

[0076] In step S14, the comparison and filtering process stores information about all servers to be installed in a configuration table. Here, the unique installation configuration files of each server are compared with the configuration information in the table to find the corresponding deployment files for each server, facilitating subsequent deployment and installation. This comparison and filtering can be done one by one based on the installation configuration files, or by comparing the basic configuration information of the installation configuration files with the basic configuration information in the configuration table. If a comparison is successful, it means that the basic configuration information of the server is universal for subsequent deployment and installation. Then, the comparison is refined to the individual configuration information of each server (which differs from the configuration information of other servers). If a comparison is successful, the successfully compared configuration information is used as the current deployment file for subsequent deployment and installation on the server.

[0077] This invention provides a server deployment method that pre-deploys a first operating system on each server to be installed. The first operating system includes the function of collecting hardware information of the server. A configuration table is generated based on the configuration information returned by each server. Each server is restarted, and a pre-boot execution environment is installed on a second operating system to generate an installation configuration file. The installation configuration file and the configuration table are compared to obtain the deployment file corresponding to each server, and then the server is deployed and installed. This method achieves a high degree of personalization and adaptability in system configuration through two boot processes. The first boot deploys a streamlined first operating system that retains the basic functions of the server. A configuration table is automatically generated based on the configuration file under the management node providing PXE services. This configuration table is then compared with the configuration file under the actual second operating system (the official operating system) in subsequent boots to generate a personalized deployment file consisting of the installation configuration for each server. This deployment file corresponds to different execution conditions for each server, achieving personalized server deployment. This avoids the problems of indistinguishable individual configuration information or time-consuming errors caused by fixed configuration files during the PXE configuration process, improving installation efficiency and accuracy, and realizing an intelligent and personalized server operating system installation process. In some embodiments, after generating the configuration table and before restarting each server to be installed, the following is also included:

[0078] Obtain the initial configuration information for each server to be installed;

[0079] Compare the configuration information in the configuration table with the initial configuration information;

[0080] If the configuration information in the configuration table is the same as the initial configuration information, then proceed to the step of restarting each server to be installed.

[0081] Specifically, the initial configuration information can be configuration information provided by the manufacturer or configuration information compiled manually. In this embodiment, the configuration information in the configuration table is compared with the initial configuration information. This first comparison is performed before restarting each server to be installed to verify the accuracy of the configuration information in the current configuration table generated by the first operating system, so as to improve the accuracy in the subsequent comparison with the installation and deployment files under the official operating system.

[0082] In some embodiments, after generating the configuration table, the method further includes:

[0083] The first configuration information is obtained by running the first operating system based on the hardware information of each server to be installed.

[0084] Compare the configuration information in the configuration table with the first configuration information;

[0085] If the configuration information in the configuration table is different from the first configuration information, the configuration information in the different configuration table will be marked; and it will be determined that the hardware information of the server to be installed corresponds to the marked configuration information has failed.

[0086] Determine whether the hardware information of the server to be installed corresponding to the fault is the key hardware information of the business scenario corresponding to the server to be installed.

[0087] If it is critical hardware information, the server to be installed will be marked as a faulty server.

[0088] If it is not critical hardware information, then the critical hardware information will be marked, and the process will proceed to restarting the server to be installed. The configuration information of the critical hardware information corresponding to the generated installation configuration file will not be compared.

[0089] Specifically, this embodiment differs from the previous embodiment in that it compares configuration information after the configuration table is generated. In this embodiment, the first configuration information is obtained after running under the first operating system. The configuration information in the configuration table is generated during the deployment and operation of the first operating system by collecting hardware information of the node to be installed, such as during the pre-configuration phase, where configuration parameters are defined before the first operating system starts. When the first operating system starts, it automatically detects and records information such as resource usage, network configuration, and installed software packages. In this embodiment, based on the first configuration information obtained after running under the first operating system, the configuration information in the configuration table is compared with the first configuration information. If they differ, the configuration information in the different configuration table is marked, and it is determined that the hardware information corresponding to the marked configuration information has failed. To ensure that the critical hardware information for the business scenario corresponding to the server to be installed is not the faulty hardware information, if it is, it indicates that the server to be installed has failed and cannot be deployed and installed. If it is not critical hardware information, it needs to be marked, and the configuration information of the critical hardware information does not need to be compared in the subsequent installation configuration file, thus ignoring the configuration information of the critical hardware information.

[0090] In this embodiment, the first configuration information generated after the first operating system runs is compared with the configuration information in the configuration table generated during the first operating system's runtime to ensure the accuracy of the configuration table through a preliminary comparison of the current configuration information.

[0091] In some embodiments, after generating the configuration table and before restarting each server to be installed, the following is also included:

[0092] The first operating system is deleted from the memory of each server to be installed, in order to proceed to the step of restarting each server to be installed.

[0093] To reduce server space usage, the memory of each server to be installed is deleted when the first operating system is not needed, thereby improving the utilization rate of memory in subsequent installations.

[0094] In some embodiments, the installation configuration file and configuration table are compared to obtain the deployment file corresponding to each server to be installed, including:

[0095] The configuration information corresponding to the installation configuration files and configuration tables is pre-categorized into a first general type and a second personalized type. The first general type of configuration information is the basic configuration information of all servers to be installed. The second personalized type of configuration information is the personalized configuration information of each server to be installed.

[0096] Determine whether the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table are the same;

[0097] If the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table is the same, then determine whether the configuration information of the second individual type of the installation configuration file and the second individual type of the configuration table is the same.

[0098] If the configuration information of the second personality type of the installation configuration file is the same as the configuration information of the second personality type of the configuration table, then the configuration information of the second personality type of the installation configuration file will be used as the deployment file of the current server to be installed.

[0099] If the configuration information of the second personality type in the installation configuration file is different from that of the second personality type in the configuration table, then it is determined whether it is the key configuration information of the server to be installed based on the existence of different second personality types.

[0100] If it is not the critical configuration information of the server to be installed, then the configuration information of the second personality type of the installation configuration file will be used as the deployment file of the server to be installed.

[0101] Specifically, in this embodiment, the configuration information corresponding to the installation configuration file and configuration table is divided into two categories: a first general type and a second personalized type. The first general type is used to configure the basic configuration information of all servers to be installed, while the second personalized type is used for the personalized configuration information corresponding to each server to be installed. It should be noted that the configuration information of the first general type is the same and universal across all servers to be installed. The configuration information corresponding to the second personalized type is different for each server to be installed.

[0102] First, compare the configuration information of the first common type in the installation configuration file with the configuration information of the first common type in the configuration table. If they are the same, it means that the configuration information of each server to be installed is compatible and a normal installation can be performed. Next, check if the configuration information of the second common type in the installation configuration file is the same as the configuration information of the second common type in the configuration table corresponding to the server to be installed. If they are the same, it means that the second common type in the installation configuration file and the configuration information of the second common type in the configuration table corresponding to the server to be installed are the same, and subsequent deployment and installation can be triggered. If they are different, it is necessary to check whether the configuration information of the different second common type is critical configuration information of the current server to be installed. If not, it means that the business scenario corresponding to the deployment file of the current server to be installed does not require attention to this critical configuration information, and the difference in this critical configuration information will not affect the deployment and installation of the current server to be installed. If it is, it needs to be temporarily shelved. You can try comparing again or directly report a problem; there are no restrictions here, and you can set it according to the actual situation.

[0103] The configuration information for the installation configuration file and configuration table provided in this embodiment is divided into a first general type and a second personalized type. When the configuration information of the first general type is the same, the key configuration information of the second personalized type is compared. This can clearly show the accuracy of the comparison of the server to be installed and improve the accuracy of personalized configuration.

[0104] In other embodiments, the installation configuration file and configuration table are compared to obtain the deployment file corresponding to each server to be installed, including:

[0105] Retrieve the feature configuration information corresponding to the installation configuration file of the server to be installed;

[0106] The configuration information in the configuration table is filtered based on the feature configuration information to determine the deployment files for the server to be installed.

[0107] It should be noted that the feature configuration information is based on the personalized feature parameters of the server to be installed, distinguishing it from the configuration information of other servers to be installed. By filtering the configuration information in the configuration table based on this feature configuration information, the deployment files for the server to be installed can be determined. This filtering process can be performed using a feature extraction algorithm or by filtering one by one; the specific settings can be chosen based on the actual situation.

[0108] The deployment file obtained by filtering based on feature configuration information provided in this embodiment can accurately determine the personalized deployment file of the server to be installed, thereby simplifying the filtering process and improving the accuracy of the deployment file.

[0109] In some embodiments, prior to performing a pre-boot execution environment installation on the second operating system of each server to be installed to generate an installation configuration file, the method further includes:

[0110] The host configuration protocol service, file transfer protocol service, and file service deployed with the startup execution environment are pre-centralized on a single deployment server;

[0111] Add mainstream open-source driver files and image files to the deployment server.

[0112] It should be noted that a PXE deployment server requires a host configuration protocol service (such as Dynamic Host Configuration Protocol (DHCP)), a file transfer protocol service (such as TFTP) and a file service (such as Hypertext Transfer Protocol (HTTP), Network File System (NFS), and File Transfer Protocol (FTP)). These are typically distributed across different deployment servers, requiring separate installation and configuration of the three types of servers. This can easily lead to configuration errors, software incompatibility, or software-system incompatibility. Furthermore, PXE deployment requires multiple files; some need to be downloaded from the internet, while others need to be manually written. Therefore, in this embodiment, all three services reside on a single PXE deployment server. Figure 2 An architecture diagram of a cluster system provided in an embodiment of the present invention, such as Figure 2 As shown, by combining the three services together and adding mainstream open-source image drivers, one-click configuration can be achieved without manually configuring multiple services and downloading additional image drivers. Multiple servers to be installed are represented by 1' to n'.

[0113] The three types of services provided in this embodiment are integrated into one deployment server, which improves the simplification and automation of configuration, and at the same time improves the efficiency of configuration and installation.

[0114] Figure 3 This invention provides a schematic diagram illustrating the interaction between a deployment server and a server to be installed, as shown in the embodiment of the invention. Figure 3 As shown, the deployment server receives a Dynamic Host Configuration Protocol (DHCP) service request from the server to be installed, and responds to this network configuration request to perform subsequent network configuration. The deployment server also receives a Simple File Transfer Protocol (SLTP) service request from the server to be installed to download the boot file, and responds to this request by transferring the boot file. Finally, the deployment server receives a bootloader from the server to be installed and requests to install the necessary files; here, automatic installation and configuration are required based on the deployment file generated from the personalized configuration table.

[0115] Furthermore, the present invention also provides a cluster system, including a deployment server and servers to be installed;

[0116] The deployment server is used to pre-deploy a first operating system on each server to be installed; wherein the first operating system includes the function of collecting hardware information of the server; a configuration table is generated based on the configuration information returned by each server to be installed; each server to be installed is restarted, and a pre-boot execution environment is installed on the second operating system of each server to be installed to generate an installation configuration file; the installation configuration file and the configuration table are compared to obtain the deployment file corresponding to each server to be installed, so as to deploy and install each server to be installed.

[0117] The server to be installed is used to receive deployment and installation instructions and perform deployment and installation according to the corresponding deployment files.

[0118] like Figure 2 As shown, different servers correspond to different functions. In this embodiment, deployment is carried out by deploying servers and each server to be installed.

[0119] For an introduction to the cluster system provided by the present invention, please refer to the above method embodiments. The present invention will not be described in detail here, but it has the same beneficial effects as the above server deployment method.

[0120] The foregoing has described in detail various embodiments corresponding to the server deployment method. Based on this, the present invention also discloses a server deployment device corresponding to the above method. Figure 4 This is a structural diagram of a server deployment device provided in an embodiment of the present invention. Figure 4 As shown, the server deployment equipment includes:

[0121] The first deployment module 11 is used to pre-deploy a first operating system on each server to be installed; wherein, the first operating system includes the function of collecting hardware information of the server to which it belongs;

[0122] The generation module 12 is used to generate a configuration table based on the configuration information returned by each server to be installed.

[0123] Restart module 13 is used to restart each server to be installed and to perform a pre-boot execution environment installation on the second operating system of each server to generate an installation configuration file;

[0124] The second deployment module 14 is used to compare the installation configuration file and the configuration table to obtain the deployment file corresponding to each server to be installed, so as to deploy and install each server to be installed.

[0125] Since the embodiments of the device part correspond to the embodiments described above, please refer to the embodiments of the method part for the description of the device part, and will not be repeated here.

[0126] For an introduction to the server deployment device provided by the present invention, please refer to the above method embodiments. The present invention will not be described in detail here, but it has the same beneficial effects as the above server deployment method.

[0127] Figure 5 A structural diagram of a server deployment device provided in an embodiment of the present invention is shown below. Figure 5 As shown, the device includes:

[0128] Memory 21 is used to store computer programs;

[0129] Processor 22 is used to implement the steps of a server deployment method when executing a computer program.

[0130] The server deployment device provided in this embodiment may include, but is not limited to, smartphones, tablets, laptops, or desktop computers.

[0131] The processor 22 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 22 may be implemented using at least one of the following hardware forms: Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 22 may also include a main processor and a coprocessor. The main processor, also known as the CPU, is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 22 may integrate a GPU, which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 22 may also include an Artificial Intelligence (AI) processor, which is used to handle computational operations related to machine learning.

[0132] The memory 21 may include one or more computer-readable storage media, which may be non-transitory. The memory 21 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 21 is used to store at least the following computer program 211, which, after being loaded and executed by the processor 22, is capable of implementing the relevant steps of the server deployment method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 21 may also include an operating system 212 and data 213, etc., and the storage method may be temporary storage or permanent storage. The operating system 212 may include Windows, Unix, Linux, etc. The data 213 may include, but is not limited to, the data involved in the server deployment method, etc.

[0133] In some embodiments, the server deployment apparatus may further include a display screen 23, an input / output interface 24, a communication interface 25, a power supply 26, and a communication bus 27.

[0134] Those skilled in the field can understand, Figure 5 The structure shown does not constitute a limitation on the server deployment device and may include more or fewer components than illustrated.

[0135] The processor 22 implements the server deployment method provided in any of the above embodiments by calling instructions stored in the memory 21.

[0136] For a description of the server deployment device provided by the present invention, please refer to the above method embodiments. The present invention will not be described in detail here, but it has the same beneficial effects as the above server deployment method.

[0137] Furthermore, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by processor 22, implements the steps of the server deployment method described above.

[0138] It is understood that if the methods in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0139] For an introduction to the computer-readable storage medium provided by the present invention, please refer to the above method embodiments. The present invention will not be described in detail here, but it has the same beneficial effects as the above server deployment method.

[0140] Furthermore, the present invention also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of a server deployment method.

[0141] For an introduction to the computer program product provided by the present invention, please refer to the above method embodiments. The present invention will not be described in detail here, but it has the same beneficial effects as the above server deployment method.

[0142] This invention significantly increases the efficiency of deploying large-scale cluster operating systems. The cluster network can be planned in advance and configured in one step, and additional drivers can be installed along with the operating system. A PXE deployment test was conducted using the technical solution adopted in this invention. The test used a PXE deployment server and 200 bare metal servers to be installed. After the PXE deployment server started its services, the nodes to be installed were started. After 21 minutes and 32 seconds of installation, the 200 servers began to restart. The installation success rate reached 100%. After restarting, the interconnectivity of the 200 servers was tested to verify the correctness of their network configuration. In addition, the system environment of the 200 servers was checked to confirm that their personalized configurations had successfully taken effect. These test results demonstrate that the technical solution of this invention performs excellently in the PXE deployment process, providing a reliable solution for personalized installation of large-scale server operating systems.

[0143] The foregoing has provided a detailed description of a server deployment method, system, device, apparatus, and medium provided by the present invention. The various embodiments in the specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make several improvements and modifications to the present invention without departing from the principles of the invention, and these improvements and modifications also fall within the protection scope of the present invention.

[0144] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

Claims

1. A server deployment method, characterized in that, include: A first operating system is pre-deployed on each server to be installed; wherein, the first operating system includes the function of collecting hardware information of the server to which it belongs; A configuration table is generated based on the configuration information returned by each of the servers to be installed; Restart each of the servers to be installed, and perform a pre-boot execution environment installation on the second operating system of each of the servers to be installed to generate an installation configuration file; The installation configuration file and the configuration table are compared to obtain the deployment file corresponding to each server to be installed, so as to deploy and install each server to be installed; specifically including: The configuration information corresponding to the installation configuration file and the configuration table is pre-classified to obtain a first general type and a second personalized type; wherein, the configuration information of the first general type is the basic configuration information of all servers to be installed; and the configuration information of the second personalized type is the personalized configuration information corresponding to each of the servers to be installed. Determine whether the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table are the same; If the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table is the same, then determine whether the configuration information of the second personalized type of the installation configuration file and the second personalized type of the configuration table is the same; If the configuration information of the second personality type of the installation configuration file is the same as the configuration information of the second personality type of the configuration table, then the configuration information of the second personality type of the installation configuration file is determined as the deployment file of the current server to be installed; If the configuration information of the second personality type of the installation configuration file is different from the configuration information of the second personality type of the configuration table, then it is determined whether it is the key configuration information of the current server to be installed based on the existence of different second personality types of configuration information; If it is not the critical configuration information of the server to be installed, then the configuration information of the second personality type of the installation configuration file will be used as the deployment file of the server to be installed.

2. The server deployment method according to claim 1, characterized in that, After generating the configuration table, and before restarting each of the servers to be installed, the following steps are also included: Obtain the initial configuration information corresponding to each of the servers to be installed; Compare the configuration information in the configuration table with the initial configuration information; If the configuration information in the configuration table is the same as the initial configuration information, then proceed to the step of restarting each of the servers to be installed.

3. The server deployment method according to claim 2, characterized in that, After generating the configuration table, the following is also included: The first configuration information is obtained by running the first operating system based on the hardware information of each of the servers to be installed; Compare the configuration information in the configuration table with the first configuration information; If the configuration information in the configuration table is different from the first configuration information, the configuration information in the different configuration table will be marked; and it will be determined that the marked configuration information corresponds to a hardware information failure in the server to be installed. Determine whether the hardware information of the server to be installed corresponding to the fault is the key hardware information of the business scenario corresponding to the server to be installed; If it is critical hardware information, then the server to be installed will be marked as a faulty server. If it is not critical hardware information, then the critical hardware information is identified, and the process proceeds to restart each of the servers to be installed, without comparing the configuration information of the critical hardware information corresponding to the generated installation configuration file.

4. The server deployment method according to claim 2, characterized in that, After generating the configuration table, and before restarting each of the servers to be installed, the following steps are also included: The first operating system is deleted from the memory of each of the servers to be installed, in order to proceed to the step of restarting each of the servers to be installed.

5. The server deployment method according to claim 1, characterized in that, Before performing a pre-boot execution environment installation on the second operating system of each of the aforementioned servers to be installed to generate the installation configuration file, the following is also included: The host configuration protocol service, file transfer protocol service, and file service deployed with the startup execution environment are pre-centralized on a single deployment server; Add the mainstream open-source driver files and image files to the deployment server.

6. A cluster system, characterized in that, This includes the deployment server and all servers to be installed; The deployment server is used to pre-deploy a first operating system on each server to be installed; wherein the first operating system includes the function of collecting hardware information of the server; generating a configuration table based on the configuration information returned by each server to be installed; restarting each server to be installed, and performing a pre-boot execution environment installation on the second operating system of each server to be installed to generate an installation configuration file; comparing the installation configuration file and the configuration table to obtain the deployment file corresponding to each server to be installed, so as to deploy and install each server to be installed; specifically including: The configuration information corresponding to the installation configuration file and the configuration table is pre-classified to obtain a first general type and a second personalized type; wherein, the configuration information of the first general type is the basic configuration information of all servers to be installed; and the configuration information of the second personalized type is the personalized configuration information corresponding to each of the servers to be installed. Determine whether the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table are the same; If the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table is the same, then determine whether the configuration information of the second personalized type of the installation configuration file and the second personalized type of the configuration table is the same; If the configuration information of the second personality type of the installation configuration file is the same as the configuration information of the second personality type of the configuration table, then the configuration information of the second personality type of the installation configuration file is determined as the deployment file of the current server to be installed; If the configuration information of the second personality type of the installation configuration file is different from the configuration information of the second personality type of the configuration table, then it is determined whether it is the key configuration information of the current server to be installed based on the existence of different second personality types of configuration information; If it is not the critical configuration information of the server to be installed, then the configuration information of the second personality type of the installation configuration file shall be used as the deployment file of the server to be installed. The server to be installed is used to receive deployment and installation instructions and perform deployment and installation according to the corresponding deployment files.

7. A server deployment device, characterized in that, include: The first deployment module is used to pre-deploy a first operating system on each server to be installed; wherein the first operating system includes the function of collecting hardware information of the server to which it belongs; The generation module is used to generate a configuration table based on the configuration information returned by each of the servers to be installed; The restart module is used to restart each of the servers to be installed and to perform a pre-boot execution environment installation on the second operating system of each of the servers to be installed in order to generate an installation configuration file; The second deployment module is used to compare the installation configuration file and the configuration table to obtain the deployment file corresponding to each of the servers to be installed, so as to deploy and install each of the servers to be installed; specifically, it includes: The configuration information corresponding to the installation configuration file and the configuration table is pre-classified to obtain a first general type and a second personalized type; wherein, the configuration information of the first general type is the basic configuration information of all servers to be installed; and the configuration information of the second personalized type is the personalized configuration information corresponding to each of the servers to be installed. Determine whether the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table are the same; If the configuration information corresponding to the first common type of the installation configuration file and the first common type of the configuration table is the same, then determine whether the configuration information of the second personalized type of the installation configuration file and the second personalized type of the configuration table is the same; If the configuration information of the second personality type of the installation configuration file is the same as the configuration information of the second personality type of the configuration table, then the configuration information of the second personality type of the installation configuration file is determined as the deployment file of the current server to be installed; If the configuration information of the second personality type of the installation configuration file is different from the configuration information of the second personality type of the configuration table, then it is determined whether it is the key configuration information of the current server to be installed based on the existence of different second personality types of configuration information; If it is not the critical configuration information of the server to be installed, then the configuration information of the second personality type of the installation configuration file will be used as the deployment file of the server to be installed.

8. A server deployment apparatus, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the server deployment method as described in any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the server deployment method as described in any one of claims 1 to 5.

Images