Operation system installation method, cluster system, server and medium

Abstract

The invention discloses an installation method of an operating system, a cluster system, a server and a medium, and relates to the technical field of computers. And determining a server type and a target operating system corresponding to each client according to the identification information corresponding to the target demand, and configuring a startup mirror image corresponding to each server type. The server model is automatically identified through the identification information, so that the target operating systems of different platforms can be installed subsequently, the operating systems of specific types of platforms can be installed, and the operating systems of different platforms meeting target requirements can be installed subsequently in batches. According to the embodiment of the invention, each update object of the starting environment corresponding to the target operating system is packaged in a modular manner, and the whole operating system does not need to be manually deleted for updating during subsequent update iteration, so that the starting environment to be updated is determined in the modular manner; and running the to-be-updated starting environment to perform installation processing on the starting mirror image by using the packaged module information, thereby realizing version updating iteration operation, and improving the deployment efficiency of batch deployment and installation of the operating systems by the server.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an operating system installation method, a cluster system, a server and a medium. Background Art

[0002] In a cluster system, a single-platform operating system is installed on multiple servers. In response to user-specific requirements, such as installing operating systems of different platforms on multiple servers, manual installation operation tabs are required. At the same time, when the various drivers, patches, and other update objects of the operating system are updated, the entire operating system needs to be deleted and reinstalled with the updated version of the operating system, which prolongs the deployment and installation time and reduces deployment efficiency.

[0003] Therefore, how to improve the deployment and installation efficiency of cluster servers is an urgent problem that those skilled in the art need to solve. Summary of the Invention

[0004] The purpose of the present invention is to provide an operating system installation method, cluster system, server and medium to solve the problem of low deployment efficiency caused by the manual installation and update of conventional operating systems, which results in prolonged installation time.

[0005] To solve the above technical problems, the present invention provides an operating system installation method, which is applied to a main server, comprising:

[0006] Obtain identification information corresponding to the target requirements for installing the operating system;

[0007] Determining the server model and target operating system corresponding to each client according to the identification information, so as to configure a startup image corresponding to each server model;

[0008] Modularly encapsulating each update object of the target operating system corresponding to the startup environment to determine the startup environment to be updated;

[0009] The startup environment to be updated is run, and the startup image corresponding to the server transmission of each client is installed.

[0010] First, obtain identification information corresponding to the target requirements for installing the operating system, including:

[0011] Obtaining the requirement information for installing the operating system stored in the database; wherein the database stores a first mapping relationship between the requirement information corresponding to each project, the supported operating system, the client, and the server model;

[0012] Determine identification information corresponding to the target demand based on the demand information.

[0013] On the other hand, identification information corresponding to the target requirements for installing the operating system is obtained, including:

[0014] Pre-establishing a topology structure between the server corresponding to the client and the server corresponding to the main server;

[0015] The identification information corresponding to the target requirement of installing the operating system of each client is obtained through the topology structure.

[0016] On the other hand, determining the server model and target operating system corresponding to each client according to the identification information to configure the startup image corresponding to each server model includes:

[0017] When the identification information is motherboard configuration information, pre-establishing a second mapping relationship between the motherboard configuration information, the server model, and the operating system;

[0018] Identify and process the motherboard configuration information of each client according to the second mapping relationship to obtain the server model and target operating system of the client, wherein the number of the target operating system on each client is at least one;

[0019] When there are multiple target operating systems in the server model of each client, the target operating systems are imported into the startup environments corresponding to the multiple target operating systems to configure startup images corresponding to the multiple target operating systems.

[0020] On the other hand, the update object includes at least driver information, application software information, and patch information; modularizing and packaging the update objects corresponding to the startup environment of the target operating system to determine the startup environment to be updated, including:

[0021] Obtaining the script file and corresponding version information of each update object;

[0022] Each of the script files is packaged according to each version information to obtain corresponding module information; wherein one module information corresponds to one version of an update object;

[0023] The module information is used as the startup environment to be updated.

[0024] On the other hand, the startup environment to be updated is run, and the startup image corresponding to the server transmission of each client is installed, including:

[0025] Deploy the basic operating environment of the main server;

[0026] In the basic operating environment, the corresponding distribution network is determined by the switch between the main server and each client;

[0027] identifying a corresponding basic startup environment based on a server for configuring a protocol and the distribution network;

[0028] Identify the hard disk specification information of the client to which the server model of the boot image transmitted by the server of each client belongs; and perform system partition operation on the hard disk in the server of the client according to the hard disk specification information;

[0029] Obtaining a clean system version of the target operating system;

[0030] On the basis of the pure system version installation, the packaged module information is installed according to the preset installation order, and the corresponding startup image is transmitted to the server of each client to complete the installation of the target operating system;

[0031] The packaged module information is installed according to a preset installation sequence, including:

[0032] Using the patch information as a first system update sequence;

[0033] Using the driving information as a second system update sequence;

[0034] using the application software information as a third system update sequence;

[0035] Screen the version information of the module information corresponding to each system update sequence to determine the module information corresponding to the target version information;

[0036] The module information corresponding to the respective target version information is installed in the order of the first system update sequence, the second system update sequence, and the third system update sequence.

[0037] On the other hand, if there is an installation error during the boot image installation process, the method further includes:

[0038] If there are any installation errors during the installation process, the error information will be output in the log format;

[0039] The installation operation corresponding to the error message is marked for easy maintenance.

[0040] To solve the above technical problems, the present invention further provides a cluster system, comprising a main server and a client; the connection between the main server and the client presents a topological structure;

[0041] The main server is used to execute the steps of the above-mentioned operating system installation method.

[0042] To solve the above technical problems, the present invention further provides a server, comprising:

[0043] memory for storing computer programs;

[0044] A processor is used to implement the steps of the operating system installation method when executing the computer program.

[0045] To solve the above technical problems, the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the operating system installation method as described above are implemented.

[0046] The beneficial effects of the present invention are that, on the one hand, the server model and target operating system corresponding to each client are determined according to the identification information corresponding to the target requirements, so as to configure the startup image corresponding to each server model. The server model is automatically identified by the identification information to facilitate the subsequent installation of target operating systems of different platforms, thereby realizing the installation of operating systems of specific categories of platforms, and the subsequent batch installation of operating systems of different platforms with target requirements. Compared with manual installation, the present invention determines the corresponding server model and target operating system based on the different target requirements of the user, so as to configure the corresponding startup image. On the other hand, the various update objects of the startup environment corresponding to the target operating system are encapsulated in a modular manner, so that there is no need to manually delete the entire operating system for subsequent updates during iterations. Instead, the startup environment to be updated is determined in a modular manner, and the startup environment to be updated is run to install the startup image with the encapsulated module information, thereby realizing version update iteration operations and improving the deployment efficiency of batch deployment and installation of operating systems on servers.

[0047] Secondly, identification information based on database-stored requirements is directly obtained from the primary server, increasing the diversity and flexibility of acquisition methods. Identification information based on client-side target requirements is obtained from the client's server, requiring the pre-established topology between the client and the primary server, thus increasing the diversity of acquisition methods. Server models and target operating systems are identified based on motherboard configuration information, enabling a single platform to install different operating systems across multiple platforms. For cross-platform operating systems, boot images corresponding to multiple operating systems are configured to facilitate subsequent batch deployment and installation. The modular packaging process for each update object improves modular drivers and facilitates the management of system version updates. The configured boot image and the boot environment to be updated are installed. Specifically, after basic service deployment, the customized driver environment and configured boot image are installed. This improves batch installation of systems with different requirements across multiple platforms, simplifies the deployment process, and allows installation of different required operating systems from a single primary server, eliminating the need for multiple devices. Installation error information is logged to facilitate error analysis and troubleshooting, improving installation efficiency.

[0048] In addition, the present invention also provides a cluster system, a server, and a medium, which have the same beneficial effects as the above-mentioned operating system installation method. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the embodiments of the present invention, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0050] Figure 1 A flowchart of a method for installing an operating system provided by an embodiment of the present invention;

[0051] Figure 2 A schematic diagram of the installation and deployment of an operating system provided by an embodiment of the present invention;

[0052] Figure 3 A flowchart of a method for installing and deploying a master server of a system according to an embodiment of the present invention;

[0053] Figure 4 A structural diagram of an installation device for an operating system provided by an embodiment of the present invention;

[0054] Figure 5 A structural diagram of a server provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0055] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0056] The core of the present invention is to provide an operating system installation method, cluster system, server and medium to solve the problem of low deployment efficiency caused by the manual installation and update of conventional operating systems, which results in prolonged installation time.

[0057] In order 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 implementation methods.

[0058] In computers, the operating system is the most fundamental and important foundational system software. From a computer user's perspective, the operating system embodies the various services it provides; from a programmer's perspective, it primarily refers to the user login interface; and from a designer's perspective, it defines the connections between various modules and units. Indeed, the key to designing and improving a new operating system lies in its architecture. Over decades of development, computer operating systems have evolved from simple control loops to more complex distributed operating systems. Coupled with the increasingly diverse needs of computer users, operating systems have become both complex and extensive computer software systems. Depending on the operating environment, operating systems can be categorized as desktop, mobile, server, and embedded. An operating system (OS) is a built-in program that coordinates with a computer's various hardware components to interact with the user. Common operating systems include Windows and the open-source Linux.

[0059] Conventional operating system installation generally corresponds to the operating system of a single platform, for example, multiple clients correspond to the operating system of the same platform. If multiple platforms correspond to different operating systems, multiple operating systems must be manually installed. Furthermore, when the version information of a certain update object in the operating system needs to be updated, the entire operating system must be manually deleted and the operating system containing the updated version information reinstalled, making the entire installation process time-consuming. The operating system installation method provided by the present invention can solve the above technical problems.

[0060] Figure 1 A flowchart of a method for installing an operating system provided by an embodiment of the present invention is shown in FIG. Figure 1 As shown, the method is applied to the main server side and includes:

[0061] S11: Obtain identification information corresponding to the target requirement for installing the operating system;

[0062] S12: Determine the server model and target operating system corresponding to each client according to the identification information, so as to configure a startup image corresponding to each server model;

[0063] S13: modularize and encapsulate the update objects of the target operating system corresponding to the startup environment to determine the startup environment to be updated;

[0064] S14: running the startup environment to be updated, and performing installation processing on the startup image corresponding to the server transmission of each client.

[0065] Specifically, the identification information corresponding to the target requirement for installing the operating system is obtained in step S11. The target requirement here can be identification information set based on the customer's project requirements, such as a project ID, etc. It can also be identification information for the hardware requirements corresponding to the installation of the corresponding operating system, such as motherboard hardware equipment, etc. The identification information here is used to characterize the server model and operating system that will be subsequently installed on the client. The way to obtain the identification information can be to carry out subsequent installation and deployment based on the customer requirements corresponding to the list, or to identify the operating system that needs to be updated or added / deleted based on the original client, or to identify the operating system corresponding to which operating system the server corresponding to the original client is suitable for, etc., which is not limited here.

[0066] In step S12, the server model and target operating system corresponding to each client are determined based on the identification information. It should be noted that the specific identification process is not limited, and subsequent identification can be performed by establishing a mapping relationship, or identification can be performed based on a specific identification method. It should be noted that the target operating system corresponding to a client can be one or multiple, and the multiple target operating systems correspond to cross-platform operating systems. For a cluster system with multiple clients, the target operating systems of the multiple clients can be the same, that is, a conventional single platform, or can correspond to different operating systems, that is, multi-platform, or there can be multiple target operating systems corresponding to one client, that is, cross-platform. The above three scenarios are all applicable and can be set according to actual conditions. The purpose of step S12 is to configure the boot image corresponding to each server model so that a variety of different types of operating systems can enter the pre-boot execution environment (PXE) boot, that is, subsequently enter the boot environment of the corresponding platform through network allocation to enter the system version selection interface, select the corresponding version of the system, and automatically install and deploy the system.

[0067] In step S13, the target operating system's corresponding boot environment's update objects are modularly packaged. These update objects ensure system stability, hardware compatibility, and performance optimization. These update objects can include patches, hardware driver information, software driver information, and application updates. Patch updates can resolve operating system compatibility issues, lay the foundation for subsequent driver and application installation, and ensure seamless integration between the operating system and drivers. Hardware driver information, primarily motherboard drivers, is used to enable the built-in functions and features of the motherboard's various controller hardware and is crucial to the overall performance and stability of the system. After the motherboard drivers, drivers for devices such as graphics cards, sound cards, and network cards need to be installed to ensure proper operation and optimal performance of the hardware. Application updates are considered important because application updates typically involve adding new features, improving the user experience, and adapting to the latest operating system version. Application updates can be performed after both the system and hardware drivers are updated and running stably, reducing the risk of application update failures due to system or driver issues. Conventional update processes for each update object require updating the entire operating system, making the entire update process cumbersome and time-consuming. This embodiment modularizes and encapsulates each update object. When updating, the corresponding encapsulated module information is directly updated. This encapsulated module information serves as the startup environment to be updated. The update process involves editing each startup environment and adding the corresponding update object version for each startup stage, allowing users to select the desired version. Modularizing software and hardware information not only enriches the system scope but also simplifies the tedious operations associated with system updates.

[0068] In step S14, the boot environment to be updated is run, and the corresponding boot image transmitted by the server to each client is installed. It should be noted that both steps S12 and S13 configure the boot image and edit the boot environment before the actual installation. The installation process in step S14 builds upon the PXE installation process and incorporates version updates for the update objects in the boot environment based on user needs. The conventional PXE installation process first establishes a "installation source," such as File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Trivial File Transfer Protocol (TFTP), or Dynamic Host Configuration Protocol (DHCP). When a host boots, the standard input and output (STO) calls the PXE client into the main server's memory to perform relevant operations and prompt relevant options for selection. The PXE client downloads the boot file over the network and runs it locally. The specific process is that the PXE client sends an Internet Protocol (IP) request to the local area network (LAN) through the network card. The DHCP server then provides it with an IP address and the files required for system installation. The system then uses these files to install the system. The installation process, in turn, requires resources provided by other servers, such as the package manager's software repository (such as the yum repository) and kernel files. Once the host has these resources, the installation can proceed smoothly. The end result is that when any host chooses to boot from the network, it obtains an IP address assigned by the DHCP server. Using this IP address, it communicates with the TFTP server on the LAN to obtain the boot files, and then communicates with FTP or HTTP to obtain the yum source files and kernel files. The installation then begins automatically, without any human intervention.

[0069] It should be noted that PXE installation is not restricted by external devices such as optical drives and CDs, and can be unattended, especially during batch installation, which reduces the workload of operation and maintenance personnel.

[0070] An embodiment of the present invention provides an operating system installation method, which obtains identification information corresponding to the target requirement for installing the operating system; determines the server model and target operating system corresponding to each client based on the identification information to configure the startup image corresponding to each server model; modularly encapsulates each update object of the startup environment corresponding to the target operating system to determine the startup environment to be updated; runs the startup environment to be updated, and performs installation processing on the startup image corresponding to the server transmission of each client. On the one hand, the server model and target operating system corresponding to each client are determined based on the identification information corresponding to the target requirement to configure the startup image corresponding to each server model. The server model is automatically identified through the identification information to facilitate the subsequent installation of target operating systems of different platforms, thereby realizing the installation of operating systems for specific categories of platforms, and the subsequent batch installation of operating systems for different platforms with target requirements. Compared with manual installation, the present invention determines the corresponding server model and target operating system based on the different target requirements of the user to configure the corresponding startup image. On the other hand, the various update objects of the startup environment corresponding to the target operating system are encapsulated in a modular manner, so that there is no need to manually delete the entire operating system for updating during subsequent updates and iterations. Instead, the startup environment to be updated is determined in a modular manner, and the startup environment to be updated is run to install the startup image with the encapsulated module information, thereby realizing version update iterative operations and improving the deployment efficiency of batch deployment and installation of operating systems on servers.

[0071] In some embodiments, obtaining identification information corresponding to a target requirement for installing an operating system includes:

[0072] Obtaining the required information for installing the operating system stored in the database; wherein the database stores a first mapping relationship between the required information corresponding to each project, the supported operating system, the client, and the server model;

[0073] Determine identification information corresponding to the target demand based on the demand information.

[0074] It should be noted that the target requirement can be the requirement information for installing the operating system stored in the database corresponding to the main server. This requirement information can be directly issued by the user, or it can be deployed directly according to the client list of the main server before the overall installation and deployment, or it can be based on the installation and deployment of the original client, and then the version information is replaced or the operating system is added or deleted. The identification information here is determined based on the requirement information in the database, and the database stores the first mapping relationship between the requirement information corresponding to the project, the operating system, the client, and the server model. It can be in the form of table information or list. It plays an identification role corresponding to the project name, project requirements, project identification number (ID), etc.

[0075] The acquisition of identification information based on demand information stored in the database provided in this embodiment is directly acquired through the main server, thereby increasing the diversity and flexibility of acquisition paths.

[0076] In other embodiments, obtaining identification information corresponding to target requirements for installing the operating system includes:

[0077] Pre-establish a topology structure between the server corresponding to the client and the server corresponding to the main server;

[0078] The identification information corresponding to the target requirement of each client for installing the operating system is obtained through the topology structure.

[0079] Specifically, this identification information is obtained by determining the client's target operating system installation requirements based on the topology established between the client and the primary server. The client already knows the operating system it will install, and the primary server determines the appropriate operating system based on the client's server motherboard hardware information.

[0080] The acquisition of identification information based on the target requirements of the client provided in this embodiment is acquired through the server of the client, and requires pre-establishment of a topological structure between the client and the main server, thereby increasing the diversity of acquisition paths.

[0081] In some embodiments, determining the server model and target operating system corresponding to each client according to the identification information to configure the startup image corresponding to each server model includes:

[0082] When the identification information is motherboard configuration information, a second mapping relationship between the motherboard configuration information, the server model, and the operating system is pre-established;

[0083] Identifying and processing the motherboard configuration information of each client according to the second mapping relationship to obtain the server model and target operating system of the client, wherein the number of target operating systems on each client is at least one;

[0084] When there are multiple target operating systems in the server model of each client, they are imported into the startup environments corresponding to the multiple target operating systems to configure startup images corresponding to the multiple target operating systems.

[0085] Specifically, when the identification information is motherboard configuration information, a second mapping relationship is pre-established among the motherboard configuration information, the server model, and the operating system. This mapping relationship can be in a table or list format. Based on the second mapping relationship, the motherboard configuration information of each client is identified and processed to obtain the server model and target operating system. This identification processing method can use a one-to-one correspondence for screening, or can also use a specific identification algorithm for identification, which is not limited here.

[0086] It should be noted that the target operating system in a client can be a single type or multiple types, without limitation. Multiple types allow for cross-platform applications. Each client's server model can have multiple target operating systems, so it is necessary to import the corresponding boot environments of multiple target operating systems to configure the boot images for each target operating system.

[0087] This embodiment provides a method for identifying server models and target operating systems based on motherboard configuration information, thereby enabling a single platform to install different operating systems across multiple platforms. When corresponding to a cross-platform operating system, boot images corresponding to multiple operating systems are configured to facilitate subsequent batch deployment and installation.

[0088] In some embodiments, the update object includes at least driver information, application software information, and patch information; modularizing and packaging the update objects corresponding to the startup environment of the target operating system to determine the startup environment to be updated includes:

[0089] Get the script file of each update object and the corresponding version information;

[0090] Each script file is encapsulated according to each version information to obtain corresponding module information; wherein one module information corresponds to one version of an update object;

[0091] Use the module information as the startup environment to be updated.

[0092] Specifically, the update object is at least driver information, application software information and pudding information. The driver information here includes hardware driver information and software driver information. The script file of each update object and the corresponding version information, the version information corresponding to each update object is multiple versions, here the multiple version information can be modularized, or it can be retained and modularized based on the latest version information. Modular encapsulation is based on the packaging of each script file corresponding to each version information to obtain the corresponding module information. The encapsulation process here can be encapsulated according to a conventional encapsulation method, or it can be encapsulated according to a unique encapsulation method based on the current version information script file, which is not limited here. A packaged module information corresponds to a version of an update object. For example, there are 5 version information of update object A, and the corresponding 5 versions are encapsulated into 5 corresponding packaged module information. Each module information is used as the startup environment to be updated.

[0093] The modular encapsulation process corresponding to each update object provided in this embodiment improves modular drive to facilitate the management of system version update iterations.

[0094] In some embodiments, running the boot environment to be updated and installing the boot image corresponding to the server transmission of each client includes:

[0095] Deploy the basic operating environment of the main server;

[0096] In the basic operating environment, the corresponding distribution network is determined by the switch between the main server and each client;

[0097] Identify the corresponding basic startup environment based on the server and allocated network used to configure the protocol;

[0098] Identify the hard disk specification information of the client to which the server model of the boot image transmitted by the server of each client belongs; and perform system partition operation on the hard disk in the server of the client according to the hard disk specification information;

[0099] Get the clean system version of the target operating system;

[0100] On the basis of the pure system version installation, the packaged module information is installed according to the preset installation order, and the corresponding startup image is transmitted to the server of each client to complete the installation of the target operating system;

[0101] The packaged module information is installed according to a preset installation sequence, including:

[0102] Use patch information as the first system update sequence;

[0103] Using the drive information as the second system update sequence;

[0104] Using application software information as a third system update sequence;

[0105] Screen the version information of the module information corresponding to each system update sequence to determine the module information corresponding to the target version information;

[0106] The module information corresponding to the respective target version information is installed in the order of the first system update sequence, the second system update sequence, and the third system update sequence.

[0107] Specifically, the entire installation process requires setting up various services on the master server, configuring the environment, and writing scripts. First, the master server is set up with basic operating system services. This involves configuring various services, such as the web server, database server, and mail server, to set parameters and environments. These configurations ensure that services run as expected and meet specific business requirements. Next, the master server's local security policy is deployed, a static IP address is set, programming language extensions are added for writing clients (such as the PLClient account), Active Directory domain services are installed, the DHCP server and Windows Deployment Server services are installed, Domain Name System (DNS) server configuration is configured, the DHCP manager is configured, the Windows Deployment Services (WDS) server is configured, shared folder settings are set up, firewall settings are configured, and WDS boot authentication is performed. Next, boot images for different platforms are configured to support PXE booting for various systems. Finally, each boot environment is edited, and corresponding versions for each stage are added for user selection.

[0108] In the basic operating environment, the corresponding distribution network is determined by the switch between the main server and each client, and the corresponding basic startup environment is identified according to the server used to configure the protocol (such as a DHCP server) and the distribution network. The basic startup environment here takes into account the need to identify the corresponding startup environment during batch installation and connect to deploy the installation system environment. It is the hard disk specification information of the client to which the server model of the startup image transmitted by the server of each client belongs. After the hard disk of the server corresponding to the client to which each hard disk specification information belongs is formatted and partitioned, the hard disk is partitioned. The remote or cloud installation interface can be realized through an automated script, and it can be distinguished by project, date, user, platform, etc. to install and deploy customized or pure system versions.

[0109] Based on the pure system version installation, the packaged module information is installed according to a preset installation sequence. The version number and installation package are automatically packaged into a fixed-mode module and added to the entire automated deployment process. To meet different system requirements and facilitate subsequent system version modifications or additions, the preset installation sequence uses patch information as the first system update sequence, driver information as the second system update sequence, and application software information as the third system update sequence. The version information of the module information corresponding to each system update sequence is filtered to determine the module information corresponding to the target version information. The module information corresponding to the target version information is then installed in the order of the first, second, and third system update sequences. Installing the patch information first ensures operating system compatibility, laying the foundation for subsequent driver and application installation, ensuring seamless integration between the operating system and drivers. Hardware driver information is installed to ensure proper hardware operation. Software driver information installation ensures proper software operation. Application installation is performed only after the system and hardware drivers are updated and running stably, reducing the risk of application update failures due to system or driver issues. In the packaging process here, the version information of the corresponding module information is screened to determine the module information of the target version information, and the module information of the respective target version information is installed based on the order of each update sequence.

[0110] This embodiment provides the installation processing of the configured startup image and the startup environment to be updated. Specifically, after the basic service deployment, the installation processing process is performed corresponding to the customized drive environment and the configured startup image, which improves the batch installation of systems with different needs across platforms, simplifies the deployment process, and allows different required operating systems to be installed through a main server without the need for installation on multiple devices.

[0111] In some embodiments, if there is an installation error during the boot image installation process, the process further includes:

[0112] If there are any installation errors during the installation process, the error information will be output in the log format;

[0113] The installation operations corresponding to the error messages are marked for easy maintenance.

[0114] Specifically, if an installation error occurs, the error information is output via a log file (e.g., a log file) to facilitate troubleshooting of installation errors or compatibility issues between modules. The installation operation corresponding to the error information is marked to facilitate troubleshooting and improve efficiency. This marking can be done via logging or within the corresponding installation operation step; there is no specific limitation here and it can be set based on actual circumstances.

[0115] The log mode provided in this embodiment outputs installation error information, so as to facilitate staff to analyze the log information to troubleshoot and repair errors, thereby improving installation efficiency.

[0116] In some embodiments, during the installation of the operating system, verification processing is performed on each operation step to reduce problems that may occur during the installation process. The verification process includes:

[0117] Obtaining first preset verification information of a configured startup image and a configuration file of the startup image;

[0118] Verifying the configuration file of the startup image using a checksum method to obtain first verification information;

[0119] Compare the first preset verification information with the first verification information and output at least one of the following results:

[0120] Result 1: The configured boot image is complete;

[0121] Result 2: The configured startup image is incomplete;

[0122] In the first result mode, the hardware of the client to which the target operating system belongs is tested according to the hardware diagnostic mechanism to obtain at least one of the following results:

[0123] Result 3: Output information that the hardware test passed;

[0124] Result 4: Output information about hardware test failure;

[0125] In the third result, the original partition of the client hardware to which the target operating system belongs is obtained;

[0126] Delete the original partition and allocate new storage space;

[0127] After the operating system is installed, a compatibility test is performed with the target operating system based on the module information corresponding to the target version information to obtain at least one of the following results:

[0128] Result 5: Outputs information indicating that the verification process of the target operating system has passed.

[0129] Result 6: Outputs information indicating that the verification process of the target operating system has failed.

[0130] Specifically, in this embodiment, the configured boot image, hardware diagnosis, partition test and driver are verified. If any test fails, the subsequent verification test process cannot be performed, so as to improve the efficiency and accuracy of the verification process.

[0131] In results one and two, if the first preset verification information is the same as the first test information, result one is obtained; if they are different, result two is obtained. In results three and four, the hardware is tested according to the hardware diagnostic mechanism. The hardware diagnostic mechanism here is based on a pre-startup system assessment test to determine whether there is a problem with the hardware. If there is a problem, result four is obtained; if not, result three is obtained.

[0132] In the third method, obtain the original partitions of the client hardware to which the target operating system belongs and verify the partitions to ensure that the partition operation is correct. For example, during the Windows installation process, if you choose "Custom Installation", you need to delete the old partitions and allocate new storage space, which involves partition verification.

[0133] After the target operating system is installed, the hardware driver needs to be installed. Before installing the driver, check the driver version and compatibility to ensure that it matches the current operating system version. If the compatibility test fails, the output is result 6, and if the compatibility test succeeds, the output is result 5.

[0134] This embodiment provides a verification process for each operation step during the installation process of the target operating system to ensure that the installation process of the target operating system is accurate and improve the installation efficiency.

[0135] Furthermore, the present invention also provides a cluster system, comprising a main server and a client; the connection between the main server and the client presents a topological structure;

[0136] The main server is used to execute the steps of the above-mentioned operating system installation method.

[0137] For an introduction to a cluster system provided by the present invention, please refer to the above method embodiment, which will not be described in detail herein. The method has the same beneficial effects as the above operating system installation method.

[0138] Figure 2 A schematic diagram of an operating system installation and deployment provided by an embodiment of the present invention is shown in FIG. Figure 2 As shown, the main server configures the boot image to automatically identify, calibrate, and automatically deploy the system to the client. The main server edits the network environment corresponding to the boot environment to automatically distribute it to the client.

[0139] Figure 3 This is a flow chart of a method for installing and deploying a main server side of a system according to an embodiment of the present invention, as shown in FIG. Figure 3 As shown, the steps include:

[0140] S21: Set up the main server;

[0141] S22: Automatically identify the identification information of the motherboard hardware and identify the corresponding startup environment;

[0142] S23: Determine whether the calibration is successful in the corresponding startup environment. If successful, proceed to step S24; if unsuccessful, proceed to step S25;

[0143] S24: Automatic deployment system;

[0144] S25: prompt error information;

[0145] S26: Modify or add information to proceed to step S22.

[0146] The above describes in detail various embodiments corresponding to the method for installing an operating system. On this basis, the present invention also discloses an operating system installation device corresponding to the above method. Figure 4 This is a structural diagram of an installation device for an operating system provided by an embodiment of the present invention. Figure 4 As shown, the installation device of the operating system includes:

[0147] An acquisition module 11 is used to acquire identification information corresponding to a target requirement for installing an operating system;

[0148] A configuration module 12 is configured to determine the server model and target operating system corresponding to each client according to the identification information, so as to configure a startup image corresponding to each server model;

[0149] The encapsulation module 13 is used to modularly encapsulate the update objects of the target operating system corresponding to the startup environment to determine the startup environment to be updated;

[0150] The running module 14 is used to run the startup environment to be updated and install the startup image corresponding to the server transmission of each client.

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

[0152] For an introduction to an operating system installation device provided by the present invention, please refer to the above method embodiment, and the present invention will not be repeated here. It has the same beneficial effects as the above operating system installation method.

[0153] Figure 5 A structural diagram of a server provided in an embodiment of the present invention, such as Figure 5 As shown, the server includes:

[0154] Memory 21, for storing computer programs;

[0155] The processor 22 is configured to implement the steps of the operating system installation method when executing a computer program.

[0156] 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 in at least one of the following hardware forms: a digital signal processor (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 22 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a central processing unit (CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 22 may be integrated with a graphics processing unit (GPU), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 22 may also include an artificial intelligence (AI) processor, which is responsible for processing computing operations related to machine learning.

[0157] The memory 21 may include one or more computer-readable storage media, which may be non-transitory. The memory 21 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 21 is at least used to store the following computer program 211, wherein, after the computer program is loaded and executed by the processor 22, it can implement the relevant steps of the operating system installation method disclosed in any of the aforementioned 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. Among them, the operating system 212 may include Windows, Unix, Linux, etc. The data 213 may include but is not limited to data involved in the operating system installation method, etc.

[0158] In some embodiments, the server 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 .

[0159] Those skilled in the art will understand that Figure 5 The structure shown in the figure does not constitute a limitation to the server, and may include more or fewer components than shown in the figure.

[0160] The processor 22 implements the operating system installation method provided by any of the above embodiments by calling the instructions stored in the memory 21.

[0161] For an introduction to a server provided by the present invention, please refer to the above method embodiment, and the present invention will not be repeated here. It has the same beneficial effects as the above operating system installation method.

[0162] Furthermore, the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by the processor 22, the steps of the above-mentioned operating system installation method are implemented.

[0163] It is understood that if the methods in the above embodiments are implemented in the form of 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, or the portion 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 each embodiment of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0164] For an introduction to a computer-readable storage medium provided by the present invention, please refer to the above method embodiment, which will not be described in detail herein. The computer-readable storage medium has the same beneficial effects as the above operating system installation method.

[0165] Furthermore, the present invention also provides a computer program product, comprising a computer program / instruction, which implements the steps of the operating system installation method when executed by a processor.

[0166] For an introduction to a computer program product provided by the present invention, please refer to the above method embodiment, which will not be described in detail herein. It has the same beneficial effects as the above operating system installation method.

[0167] The above is a detailed introduction to the installation method, cluster system, server and medium of an operating system provided by the present invention. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principle of the present invention, the present invention can also be improved and modified in several ways, and these improvements and modifications also fall within the scope of protection of the present invention.

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

Claims

1. A method for installing an operating system, characterized in that: Applied to the main server, including: Obtain identification information corresponding to the target requirement for installing the operating system; Determine the server model and target operating system corresponding to each client according to the identification information, so as to configure the startup image corresponding to each server model; Modularly encapsulating each update object of the target operating system corresponding to the startup environment to determine the startup environment to be updated; The startup environment to be updated is run, and the startup image corresponding to the server transmission of each client is installed.

2. The method for installing an operating system according to claim 1, characterized in that: Obtain identification information corresponding to the target requirements for installing the operating system, including: Obtaining the requirement information for installing the operating system stored in the database; wherein the database stores the first mapping relationship between the requirement information corresponding to each project, the supported operating system, the client, and the server model; Determine identification information corresponding to the target demand according to the demand information.

3. The method for installing an operating system according to claim 1, characterized in that: Obtain identification information corresponding to the target requirements for installing the operating system, including: Pre-establishing a topological structure of a server corresponding to the client and a server corresponding to the main server; The identification information corresponding to the target requirement of installing the operating system on each client is obtained through the topological structure.

4. The method for installing an operating system according to claim 2, characterized in that: Determining the server model and the target operating system corresponding to each client according to the identification information to configure the startup image corresponding to each server model includes: When the identification information is motherboard configuration information, a second mapping relationship corresponding to the motherboard configuration information, the server model and the operating system is pre-established; According to the second mapping relationship, the motherboard configuration information of each client is identified and processed to obtain the server model and target operating system of the client, wherein the number of the target operating system in each client is at least one; When there are multiple target operating systems in the server model of each client, they are imported into the startup environments corresponding to the multiple target operating systems to configure the startup images corresponding to the multiple target operating systems.

5. The method for installing an operating system according to claim 1, characterized in that: The update object includes at least driver information, application software information and patch information; Modularizing and packaging each update object of the target operating system corresponding to the startup environment to determine the startup environment to be updated, including: Obtaining the script file of each update object and the corresponding version information; According to each version information, each script file is packaged to obtain corresponding module information; wherein one module information corresponds to one version of an update object; The module information is used as the startup environment to be updated.

6. The method for installing an operating system according to claim 5, characterized in that: Running the startup environment to be updated, and installing the startup image corresponding to the server transmission of each client, including: Deploy the basic operating environment of the main server; In the basic operating environment, the corresponding distribution network is determined by the switch between the main server and each client; identifying a corresponding basic startup environment according to the server for configuring the protocol and the distribution network; Identify the hard disk specification information of the client to which the server model of the boot image transmitted by the server of each client belongs; and perform system partition operation on the hard disk in the server of the client according to the hard disk specification information; Obtaining a pure system version of the target operating system; On the basis of the installation of the pure system version, the packaged module information is installed according to the preset installation order, and the corresponding startup image is transmitted to the server of each client to complete the installation of the target operating system; The packaged module information is installed according to a preset installation sequence, including: Using the patch information as a first system update sequence; Using the driving information as a second system update sequence; Using the application software information as a third system update sequence; Screening the version information of the module information corresponding to each system update sequence to determine the module information corresponding to the target version information; The module information corresponding to the respective target version information is installed in the order of the first system update sequence, the second system update sequence and the third system update sequence.

7. The method for installing an operating system according to claim 6, characterized in that: If there is an installation error during the boot image installation process, the process further includes: If there is any installation error during the installation process, the error information will be output in the log mode; The installation operation corresponding to the error message is marked for easy maintenance.

8. A cluster system, characterized in that: It includes a main server and a client; the connection between the main server and the client presents a topological structure; The main server is used to execute the steps of the operating system installation method described in any one of claims 1 to 7 above.

9. A server, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the method for installing the operating system as claimed in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for installing the operating system according to any one of claims 1 to 7 are implemented.

Images