PXE-based operating system installation method, device, equipment and storage medium

Abstract

The application discloses a PXE-based operating system installation method and device, equipment and a storage medium, and relates to the technical field of network management. In the method, the adaptation of an image group is performed in advance for each machine type. For a target machine group, the adapted image group identifier can be acquired based on each machine type, and then the PXE image group file is acquired and encapsulated into a machine installation platform software package together with a cloud platform installation tool. When an operating system is installed for the machine group, the corresponding PXE executable file can be generated for each physical machine according to the machine type of the physical machine, so that each physical machine downloads the PXE image group file according to the indication of the PXE executable file of the physical machine and then installs the corresponding operating system. Since the PXE image group file of each physical machine is adapted to the machine type of the physical machine, the installation failure caused by the mismatch between the machine type and the PXE image group is avoided, the probability of successful installation of the physical machine is improved, and the installation efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and provides a method, apparatus, device and storage medium for installing a PXE-based operating system. Background Technology

[0002] A Preboot Execution Environment (PXE) is a mechanism that allows a computer to boot without relying on local data storage devices. This is achieved through network protocols such as Dynamic Host Configuration Protocol (DHCP) and Trivial File Transfer Protocol (TFTP), as well as concepts like globally unique identifiers, generic network driver interfaces, and universally unique identifiers. It also utilizes pre-defined application programming interfaces (APIs) that extend the physical machine firmware. When installing an operating system on a computer using the PXE boot process, a PXE image group is typically used. A PXE image group includes an operating system kernel and a diskless image initrd. Installation will only succeed if the computer model to be installed is compatible with the PXE image group used during installation.

[0003] Currently, when management devices use the PXE boot process to uniformly install customized operating system master disks on various computers within their jurisdiction, a certain kernel and initrd group is usually pre-specified as the default PXE image group. Correspondingly, each computer will uniformly use the default PXE image group to attempt installation. However, each computer may contain multiple different models. If the default PXE image is not suitable for the current model, the installation will fail. Furthermore, it is necessary to select other versions of the PXE image group for the computers that failed to install and reinstall, making the installation process cumbersome and extremely inefficient. Summary of the Invention

[0004] This application provides a PXE-based operating system installation method, apparatus, device, and storage medium to improve operating system installation efficiency.

[0005] On the one hand, a method for installing an operating system based on a preboot execution environment (PXE) is provided, the method comprising:

[0006] For each target model included in the target cluster, based on the mapping relationship between each model that has passed the adaptation verification and each image group identifier, the target image group identifier corresponding to each target model is determined respectively;

[0007] Based on the obtained target image group identifiers, the corresponding image group description files are obtained respectively;

[0008] Based on the storage location indicated by the obtained image group description files, the PXE image group files corresponding to each target model are obtained respectively;

[0009] Based on the obtained PXE image group files, a package is formed to obtain the installation platform package, and the installation platform package is sent to the target device so that the target device can install the corresponding operating system for the target cluster based on the installation platform package.

[0010] Optionally, the method further includes:

[0011] Add an adaptation verification record corresponding to each adaptation verification result to the adaptation management information; each adaptation verification record includes a device model, an image group identifier, and the corresponding adaptation verification result.

[0012] On the one hand, a method for installing an operating system based on PXE is provided, the method comprising:

[0013] Obtain the installation platform package for the target cluster and store the PXE image group files included in the installation platform package; wherein, the installation platform package includes PXE image group files adapted to each model in the target cluster;

[0014] Based on the model of each physical machine in the target machine group, generate a PXE executable file corresponding to each physical machine; wherein, the PXE executable file of each physical machine indicates the storage location of its adapted PXE image group file;

[0015] After instructing each physical machine to install the operating system, the corresponding PXE executable file for each physical machine is sent to the respective physical machine based on the download request of each physical machine. This allows each physical machine to download the corresponding PXE image group file and install the corresponding operating system based on the instructions of the obtained PXE executable file.

[0016] On the one hand, a method for installing an operating system based on PXE is provided, the method comprising:

[0017] Obtain the PXE pre-boot file corresponding to this physical machine; wherein, the PXE pre-boot file indicates the PXE executable file required for installing the operating system on this physical machine;

[0018] Execute the PXE pre-boot file to obtain the PXE executable file; wherein, the PXE executable file indicates the PXE image group file adapted for this physical machine;

[0019] Based on the instructions in the PXE executable file, download the corresponding PXE image group file, and install the corresponding operating system based on the PXE image group file.

[0020] On the one hand, a PXE-based operating system installation device is provided, the device comprising:

[0021] The determining unit is used to determine the target image group identifier corresponding to each target model based on the mapping relationship between each target model that has passed the adaptation verification and each image group identifier for each target model included in the target group.

[0022] The acquisition unit is configured to acquire the corresponding image group description file based on the acquired target image group identifier; and to acquire the PXE image group file corresponding to each target model based on the storage location indicated by the acquired image group description file.

[0023] The packaging unit is used to package the obtained PXE image group files to obtain the installation platform package, and send the installation platform package to the target device so that the target device can install the corresponding operating system for the target cluster based on the installation platform package.

[0024] Optionally, the device further includes an adaptation verification unit, used for:

[0025] Obtain at least one device model and at least one image group identifier;

[0026] Each of the at least one model and each of the at least one image group identifiers are combined in pairs to obtain multiple combinations to be adapted, each combination to be adapted includes a model and an image group identifier.

[0027] Each of the multiple combinations to be adapted is subjected to adaptation verification to obtain the adaptation verification result corresponding to each of the multiple combinations to be adapted.

[0028] The mapping relationship is updated based on the obtained multiple adaptation verification results.

[0029] Optionally, the adaptation verification unit is specifically used for:

[0030] For each of the multiple combinations to be adapted, the following operations are performed respectively:

[0031] For a combination to be adapted, the PXE image group file corresponding to the image group identifier included in the combination to be adapted is used to attempt to install on at least one prototype machine corresponding to the model included in the combination to be adapted.

[0032] Based on the installation results of the at least one prototype, the adaptation verification result corresponding to the one combination to be adapted is obtained.

[0033] Optionally, the adaptation verification unit is further configured to:

[0034] Obtain at least one device model and at least one image group identifier;

[0035] For each of the at least one model, perform the following operations:

[0036] For a given model, starting from the base image group identifier corresponding to that model, and arranged in descending order of release time, the PXE image group files corresponding to each image group identifier are used sequentially to attempt installation on at least one prototype of that model.

[0037] Based on the installation results of each PXE image group file, the compatibility verification result corresponding to the aforementioned model is obtained.

[0038] Based on the obtained multiple adaptation verification results, the mapping relationship table is updated.

[0039] Optionally, the adaptation verification unit is specifically used for:

[0040] For each of the multiple adaptation verification results, perform the following operations:

[0041] For a given adaptation verification result, if the adaptation verification result indicates that the adaptation verification has passed, then it is determined whether the mapping relationship already records the corresponding relationship of the first model corresponding to the given adaptation verification result.

[0042] If the correspondence of the first model has been recorded, then the correspondence is updated based on the first image group identifier corresponding to the adaptation verification result;

[0043] If the corresponding relationship of the first model is not recorded, then a corresponding relationship between the first model and the first image group identifier is added to the mapping relationship table.

[0044] Optionally, the adaptation verification unit is specifically used for:

[0045] Determine whether the time difference between the publication time of the first mirror group identifier and the current time is less than the time difference between the publication time of the second mirror group identifier corresponding to the recorded correspondence and the current time.

[0046] If it is less than, then the second mirror group identifier in the correspondence is changed to the first mirror group identifier.

[0047] Optionally, the adaptation verification unit is further configured to:

[0048] If the adaptation verification result indicates that the adaptation verification failed, then it is determined whether the mapping relationship already records the corresponding relationship of the first model;

[0049] If the corresponding relationship of the first model is not recorded, then a corresponding relationship between the first model and the base image group identifier is added to the mapping relationship table.

[0050] On the one hand, a PXE-based operating system installation device is provided, the device comprising:

[0051] A receiving unit is configured to obtain an installation platform package for a target cluster and store the PXE image group files included in the installation platform package; wherein, the installation platform package includes PXE image group files adapted to each model in the target cluster;

[0052] The generation unit is used to generate a PXE executable file corresponding to each physical machine according to the model of each physical machine in the target machine group; wherein, the PXE executable file of each physical machine indicates the PXE image group file that it is adapted to.

[0053] The sending unit is configured to, after instructing each physical machine to install the operating system, send the corresponding PXE pre-boot file to the respective physical machine based on the download request of each physical machine, so that each physical machine can address the storage location indicated by the extension bit of the obtained PXE pre-boot file to obtain the corresponding PXE executable file.

[0054] Optionally, the generation unit is further configured to:

[0055] Store the corresponding PXE executable file for each physical machine to the designated storage location;

[0056] Add the storage location of the corresponding PXE executable file for each physical machine to the extension bit of the corresponding PXE pre-boot file for each physical machine;

[0057] The sending unit is specifically configured to: after instructing each physical machine to install the operating system, send the corresponding PXE pre-boot file of each physical machine to the corresponding physical machine based on the download request of each physical machine, so that each physical machine can address the storage location indicated by the extension bit of the obtained PXE pre-boot file to obtain the corresponding PXE executable file.

[0058] On the one hand, an operating system installation device based on the Preboot Execution Environment (PXE) is provided, the device comprising:

[0059] The acquisition unit is used to acquire the PXE pre-boot file corresponding to the physical machine; wherein, the PXE pre-boot file indicates the PXE executable file required for installing the operating system on the physical machine;

[0060] An execution unit is used to execute the PXE pre-boot file and obtain the PXE executable file; wherein the PXE executable file indicates the PXE image group file adapted to this physical machine;

[0061] The download and installation unit is used to download the corresponding PXE image group file based on the instructions of the PXE executable file, and to install the corresponding operating system based on the PXE image group file.

[0062] On one hand, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of any of the above methods.

[0063] On the one hand, a computer storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of any of the above methods.

[0064] On one hand, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of any of the methods described above.

[0065] In this embodiment, image group adaptation is performed in advance for each machine model, and the mapping relationship between each machine model that has passed the adaptation verification and each image group identifier is stored. Then, for the target machine group to be installed with the operating system, the target image group identifier can be obtained based on each target machine model it includes, and then the corresponding PXE image group file can be obtained and packaged into a package. The obtained installation platform package is sent to the target device. In this way, when the target device installs the operating system for the target machine group based on the installation platform package, the corresponding PXE executable file can be generated for each physical machine model, and the PXE executable file is indicated in the PXE pre-boot file. Accordingly, each physical machine can obtain the corresponding PXE executable file based on its own PXE pre-boot file, and download the PXE image group file based on the instructions of the PXE executable file and then install the corresponding operating system. Since the PXE image file of each physical machine is adapted to its own model, the installation failure caused by the model and PXE image group incompatibility is avoided, which increases the probability of successful installation on physical machines and thus improves the installation efficiency. Attached Figure Description

[0066] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0067] Figure 1 Application scenario diagrams provided for embodiments of this application;

[0068] Figure 2 This is a schematic diagram of the system architecture provided for an embodiment of this application;

[0069] Figure 3 A schematic flowchart illustrating the PXE-based operating system installation method provided in this application embodiment;

[0070] Figure 4 This is a schematic diagram of a process for adapting a device model to a PXE image group file, provided in an embodiment of this application.

[0071] Figure 5 A schematic diagram of the combination to be adapted provided in the embodiments of this application;

[0072] Figure 6 A flowchart illustrating the adaptation verification process provided in this application embodiment;

[0073] Figure 7 A schematic diagram illustrating the process of updating the mapping relationship table provided in an embodiment of this application;

[0074] Figure 8 This is a schematic diagram illustrating another process for adapting the device model to the PXE image group file, as provided in an embodiment of this application.

[0075] Figure 9 Another flowchart illustrating the adaptation verification process provided in this application embodiment;

[0076] Figure 10 A schematic diagram of a PXE-based operating system installation device provided in an embodiment of this application;

[0077] Figure 11 Another schematic diagram of the structure of the PXE-based operating system installation device provided in the embodiments of this application;

[0078] Figure 12 A schematic diagram of yet another structure of the PXE-based operating system installation device provided in the embodiments of this application;

[0079] Figure 13 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0080] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0081] To facilitate understanding of the technical solutions provided in the embodiments of this application, some key terms used in the embodiments of this application will be explained below:

[0082] PXE image group: This is a collective term for the kernel and initrd used in PXE deployment of operating systems. A PXE image group includes a kernel and a diskless image initrd.

[0083] Kernel: A real-time operating system that ensures specific functions are completed within a certain time limit. Typically, in PXE boot, the kernel and initrd are used to start the memory system, thereby installing the operating system.

[0084] initrd: Mounts RAM as a disk, then finds and executes the init function in RAM. It is mounted to an initial root file system in the system before the actual root file system is available, and is loaded together with the kernel as part of the PXE boot process.

[0085] PXE preboot files, also known as preboot executables, are executable files used for PXE booting in the preboot execution environment, such as bootx64.efi and pxelinux.0.

[0086] Extended PXE preboot files: Extended PXE preboot files have addressable features, which can be used to boot and obtain certain information, such as iPXE or grubx64.efi.

[0087] Model: The model number of the physical machine. The model number is assigned based on the hardware configuration of the physical machine. For example, the model number will be different based on the different models and capacities of hardware such as CPU, RAID card, network card or memory. Each model number uniquely identifies the configuration of a physical machine.

[0088] Private Cloud: A private cloud is typically an enterprise-grade cloud platform that supports private deployment and features high availability, unified management, and industry compliance. Generally, a private cloud can be a cloud platform deployed on top of a public cloud, targeting a specific private cloud user and only accessible to that user.

[0089] The design concept of the embodiments of this application will be briefly introduced below.

[0090] Currently, many enterprises have deployed dedicated cloud platforms. The physical machine clusters of different enterprises deploying dedicated clouds often purchase physical machines from different manufacturers and models. Physical machines from different manufacturers and models often require different hardware drivers. The kernel and diskless image initrd in different PXE image group files may contain different hardware drivers, suitable for different machine models. When managing devices to uniformly install a customized operating system master disk, a certain set of kernel and initrd is usually pre-specified as the default PXE image group file. Accordingly, each computer will uniformly use the default PXE image group file to attempt installation. However, each computer may contain multiple different machine models. If the default PXE image group file is not suitable for the current machine model, the installation will fail. For example, machine model 1 may need PXE image group file A, and machine model 2 may need PXE image group file B. However, the default PXE image group file can only be one set, which means that using PXE image group file A cannot install machine model 1 and machine model 2 at the same time. Furthermore, if the installation fails, it is necessary to select a different version of the PXE image file for the computer where the installation failed and try to install it again, making the installation process cumbersome and extremely inefficient.

[0091] Therefore, in private clouds, recording the machine model and the adapted PXE image group files for automated installation of physical machine operating systems is a necessary requirement. Automated installation of physical machine operating systems requires using different PXE image group files for different physical machine models. Maintaining the mapping between physical machine models and PXE image group files, and thus outputting the corresponding PXE image group files for different private cloud users, becomes a common requirement. Considering that the current PXE boot process can only uniformly specify a default PXE image group for all machine models because it is unclear which PXE image groups each model can use, configuring image groups for each physical machine can avoid the problem of incompatibility between machine model and PXE image group.

[0092] In view of this, this application provides a PXE-based operating system installation method. In this method, image groups are pre-adapted for each machine model, and the mapping relationship between each adapted machine model and each image group identifier is stored. Then, for a target machine group to be installed with the operating system, the target image group identifier can be obtained based on the included target machine models. The corresponding PXE image group file is then obtained and packaged into a package. The obtained installation platform package is sent to the target device. Thus, when the target device installs the operating system for the target machine group based on the installation platform package, it can... For each physical machine model, a corresponding PXE executable file is generated, and the PXE executable file information is indicated in the PXE pre-boot file. Accordingly, each physical machine can obtain the corresponding PXE executable file based on its own PXE pre-boot file, and then download the PXE image group file according to the instructions of the PXE executable file to install the corresponding operating system. Since the PXE image file of each physical machine is compatible with its own model, the installation failure caused by the incompatibility between the model and the PXE image group is avoided, which increases the probability of successful installation on physical machines and thus improves the installation efficiency.

[0093] In this embodiment, the adaptation results of PXE image group files of various versions were performed for each model, and the adaptation records of each model were recorded in the adaptation management information, i.e. whether the adaptation verification passed. This facilitates unified management of model and PXE image group identifiers, and establishes a mapping relationship between each model and each version of PXE image group. In the mapping relationship, the highest version of PXE image group adapted to each model can be saved to provide users with a better user experience.

[0094] After introducing the design concept of the embodiments of this application, the following is a brief introduction to the application scenarios to which the technical solutions of the embodiments of this application can be applied. It should be noted that the application scenarios described below are only for illustrating the embodiments of this application and are not intended to limit the scope. In specific implementation, the technical solutions provided by the embodiments of this application can be flexibly applied according to actual needs.

[0095] The solution provided in this application can be applied to most remote operating system installation scenarios, such as PXE-based private cloud deployment scenarios. Figure 1 The diagram shown is an application scenario diagram provided by an embodiment of this application. In this scenario, there are server 101, management device 102 and physical cluster 103.

[0096] Among them, server 101 can be the backend server of a service provider that provides cloud platform services. It can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms, but it is not limited to these.

[0097] Management device 102 is a user-side management device, which can be a single physical machine or a server. Physical machine cluster 103 is a cluster of multiple physical machines on the user side. For example, when an enterprise deploys a private cloud, management device 102 can be the management device within that private cloud, while the physical machines included in physical machine cluster 103 can be managed devices within that private cloud, such as physical machines used by individual members of the enterprise. These physical machines can be owned by the enterprise itself or belong to the cloud platform server service provider, and the enterprise, as a tenant, has the right to use these physical machines.

[0098] In one possible implementation, a private cloud user can apply for bulk installation services on a service provider's cloud platform. For example, the cloud platform can provide external web pages or clients, allowing the enterprise to submit its application and provide its installation requirements, such as operating system requirements and included machine models. The service provider's server 101 can then generate a customized installation platform package for the private cloud user based on the application and using the method provided in this application, and send it to the enterprise's management device 102.

[0099] Specifically, this application embodiment addresses the operating system installation needs of dedicated cloud users deploying dedicated clouds by initiating projects and managing these projects to record project information for each dedicated cloud user, such as a list of machine models corresponding to each dedicated cloud user. When a dedicated cloud user needs to deploy the installation platform package required for installing the system through the PXE boot process, the information of the dedicated cloud user is obtained from the managed project information. Combined with the pre-adapted and verified mapping relationship between each machine model and the PXE image group identifier, the PXE image group identifiers corresponding to each machine model of the dedicated cloud user are obtained. Then, based on the PXE image group files corresponding to these PXE image group identifiers and the installation tools of the cloud platform, the installation platform package required for the dedicated cloud user's installation is generated and provided to the dedicated cloud user. Correspondingly, after the private cloud user obtains the installation platform package, since the installation platform package contains the PXE image group files required for each model of the private cloud user's physical cluster 103, the enterprise's management device 102 can then install the installation tool based on the installation platform package and install the operating system for the physical cluster 103 using the installation tool. This allows for the configuration of the corresponding PXE image group file for each physical machine, thus avoiding the problem of incompatibility between the machine model and the PXE image group file.

[0100] The server 101, management device 102, and physical cluster 103 can communicate directly or indirectly through one or more networks. This network can be a wired network or a wireless network; for example, a wireless network can be a mobile cellular network or a Wireless-Fidelity (WIFI) network, or any other possible network. This application embodiment does not limit the scope of such networks.

[0101] Optionally, the management device 102 and the physical cluster 103, or the individual physical machines, can be connected via a local area network to form an enterprise's own cloud.

[0102] See Figure 2 The diagram shown is a schematic representation of the system architecture of an embodiment of this application. This system architecture can include two parts, namely... Figure 2 The system side and the private cloud user side are shown. The system side mainly implements the management functions of machine models and PXE image groups, as well as the function of generating installation packages for the installation platform for users. The private cloud user side generally refers to the project site. A project is an installation project for a physical cluster, that is, it implements the function of installing the operating system for a specific physical cluster.

[0103] The system side may include the following parts:

[0104] (1) PXE installation tools

[0105] A PXE installation tool is a tool that automates the installation of an operating system on a physical machine through the PXE boot process. The PXE installation tool in this embodiment may include, for example: Figure 2 Both PXE installation tools shown require PXE installation during the compatibility verification phase. Since the compatibility verification process is essentially a simulation of installing an operating system on a physical machine via PXE boot, it also needs to be performed using a PXE installation tool. Figure 2 The PXE installation tool (adapter) shown refers to the tool used in the R&D environment to participate in the adaptation and verification process for various machine models. Figure 2 The PXE installation tool (project) shown refers to the PXE installation tool used by enterprise customers when actually installing operating systems on their physical machine clusters.

[0106] (2) PXE Image Adaptation Management Module

[0107] The PXE image group adaptation management module is used to manage PXE image group files, such as the description file of the PXE image group file and the corresponding image file, and provides the source information of the PXE image group file for the adaptation verification between the model and the PXE image group file.

[0108] (3) Adaptation to record management module

[0109] The compatibility record management module manages the compatibility verification results between device models and PXE image group files. It includes results for successful and failed compatibility verification. Specifically, after each device model and each PXE image group file undergoes compatibility verification, the module records the result. For example, for device model 1 and PXE image group files (group A), if the PXE image group file is successfully installed on the prototype device corresponding to device model 1, the module adds a compatibility verification record for device model 1 and PXE image group files (group A), indicating a successful compatibility verification. Conversely, if the PXE image group file fails to install on the prototype device corresponding to device model 1, or is unusable after installation, the module also adds a record for compatibility verification of device model 1 and PXE image group files (group A), indicating a failed compatibility verification.

[0110] (4) Mapping Relationship Management Module

[0111] The mapping relationship management module is used to manage the mapping relationship between each machine model that has passed the adaptation verification and the PXE image group identifier. Generally speaking, for each machine model, the mapping relationship management module can save the PXE image group identifier of the latest version of the PXE image group file that has passed the adaptation verification for that machine model. In this way, when the installation package of the installation platform is finally generated for the private cloud user, the PXE image group file of each machine model is of a higher version. Usually, the higher version has more functions and is more optimized, thus the user experience of the private cloud user is better.

[0112] (5) Project Management Module

[0113] The project management module is used to manage project information for each private cloud user. When it is necessary to deploy the PXE installation tool for a private cloud user, the list of machine models for that private cloud user is obtained from the project management module.

[0114] (6) Installation Platform Installation Package Release Module

[0115] The installation package publishing module of the installation platform is used for installation projects for specific private cloud users. It obtains the list of machine models for the private cloud user from the project management module, obtains the PXE image group identifier corresponding to each machine model in the machine model list from the mapping relationship management module, and packages the grouping information and image files related to each PXE image group identifier from the PXE image group file management module, and publishes them to the private cloud user together with the PXE installation tool.

[0116] The private cloud user side may include a physical machine configuration generation module. When the private cloud user performs the actual operating system installation, this module uses the PXE installation tool (project) to generate a PXE executable file for the physical machine's PXE pre-boot file based on the mapping relationship between the model of each physical machine in its physical machine cluster and the PXE image group identifier, which is used for the normal PXE installation process.

[0117] The methods and steps performed by each of the above modules will be described in detail in subsequent embodiments, so they will not be elaborated on here.

[0118] In one possible application scenario, this application embodiment recommends that various related data be stored using cloud storage technology. Cloud storage is a new concept that extends and develops from the concept of cloud computing. A distributed cloud storage system refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to aggregate a large number of storage devices (or storage nodes) of various types in the network through application software or application interfaces to work together and jointly provide data storage and business access functions to the outside world.

[0119] In one possible application scenario, to reduce communication latency, servers 101 can be deployed in various regions. Alternatively, for load balancing, different servers 101 can serve the regions corresponding to the devices of various private cloud users. Multiple servers 101 can share data through blockchain, forming a data-sharing system. For example, if a private cloud user's device is located at location a, and its corresponding server 101 is the first server 101, then the first server 101 provides services to private cloud users at location a. If a private cloud user's device is located at location b, and its corresponding server 101 is the second server 101, then the second server 101 provides services to private cloud users at location b.

[0120] Each server 101 in the data sharing system has a corresponding node identifier. Each server 101 can also store node identifiers of other servers 101 in the data sharing system, so that generated blocks can be broadcast to other servers 101 in the data sharing system based on their node identifiers. Each server 101 can maintain a node identifier list as shown in the table below, storing the server 101 name and node identifier in this list. The node identifier can be an Internet Protocol (IP) address or any other information that can be used to identify the node.

[0121] Of course, the methods provided in the embodiments of this application are not limited to... Figure 1 or Figure 2 The application scenarios shown can also be used in other possible scenarios, and this application embodiment does not impose any limitations. Figure 1 or Figure 2 The functions that each device or module in the application scenario shown can achieve will be described in the subsequent method embodiments, and will not be elaborated on here.

[0122] Please see Figure 3 The following is a flowchart illustrating the PXE-based operating system installation method provided in this application embodiment.

[0123] Step 301: For each target machine model included in the target machine cluster, the server determines the target image group identifier corresponding to each target machine model based on the mapping relationship between each machine model that has passed the adaptation verification and each image group identifier.

[0124] In the embodiments of the present application, the target cluster refers to the cluster specified in the installation project applied by the target private cloud user. When the target private cloud user needs to install the operating system in batches, the information of the target cluster to be installed, such as the list of models included, can be submitted. Then, for each target model included in the model list, based on the mapping relationship between each model that passes the adaptation verification and each mirror group identifier, the target mirror group identifier corresponding to each target model is determined respectively.

[0125] Step 302: The server obtains the storage locations of the PXE mirror group files corresponding to each target mirror group identifier from the mirror group description file based on the obtained target mirror group identifiers.

[0126] Among them, the mirror group identifier can uniquely identify a group of PXE mirror group files. When storing the relevant content of the PXE mirror group files, the mirror group identifier can be used as the identifier for storage, and the corresponding mirror group description file can be obtained according to the mirror group identifier.

[0127] The mirror group description file can include the detailed information of the PXE mirror group files, that is, the detailed information of the kernel and initrd. For example, it can include ID, name, version, architecture, storage path, md5 checksum, etc. When storing the detailed information, it can be stored in json format or key-value (KV) format. Of course, other possible formats can also be used for storage. The content of the mirror group description file can be saved in a file or a database.

[0128] Exemplarily, the mirror group description file can be stored in the following format:

[0129] {"ID": <id value>, "version": <version number>, "build": <generation date>, "arch": <architecture>, "kernel": {"name": <name>, "store_url": <storage path>, "md5sum": <MD5 value>}, "initrd": {"name": <name>, "store_url": <storage path>, "md5sum": <MD5 value>}}

[0130] For example, "ID": <id value>, which represents the specific value of the mirror group identifier of this group of PXE mirror group files. For example, "ID": <231> means the mirror group identifier is 231.

[0131] In this embodiment, a single image group description file can store detailed information about multiple PXE image group files. The storage location of the corresponding PXE image group file can then be obtained by searching within the image group description file based on the image group identifier. Alternatively, a single image group description file can store detailed information about one PXE image group file. The corresponding image group description file can then be obtained based on the image group identifier, and the storage location of the PXE image group file corresponding to each target image group identifier can be obtained from the obtained image group description files.

[0132] Step 303: Based on the obtained storage locations, the server retrieves the PXE image group file corresponding to each target image group identifier.

[0133] As shown in the format above, the image group description file indicates the corresponding "store_url":<storage path> for both the kernel and initrd. Therefore, based on the image group description file, the storage location of the kernel image file and initrd image file corresponding to each image group identifier can be obtained, and the corresponding kernel image file and initrd image file can be retrieved from the corresponding storage location. Similarly, for the image group identifiers corresponding to each model in the target cluster, the PXE image group file corresponding to each target image group identifier can be obtained based on the storage location indicated by the image group description file.

[0134] Step 304: The server packages the obtained PXE image group files to obtain the installation platform installation package.

[0135] Specifically, since cloud users first need to install the PXE installation tool on the management device when performing PXE boot installation, the various PXE image group files and the cloud platform's installation tool can be packaged together during the packaging process and sent to the cloud user. The cloud platform's installation tool serves to build a private cloud platform for the user, enabling the installation of the operating system on each physical machine based on this platform.

[0136] Step 305: The server sends the installation platform package to the target device, and the target device obtains the installation platform package for the target cluster.

[0137] In this embodiment of the application, after obtaining each PXE image group file, it can be packaged and the packaged installation platform package can be sent to the target device so that the target device can install the corresponding operating system for the target cluster based on the installation platform package.

[0138] Among them, the target device can be, for example, the management device of the private cloud user, which can be the server of the private cloud user or any terminal device owned by the user.

[0139] Specifically, when performing package encapsulation, all the PXE image group files corresponding to the models of the target cluster can be encapsulated into an installation package, and the description information of the installation package can be generated; or, package encapsulation can also be performed separately according to different models. For example, each model can be encapsulated into an installation package, and the description information corresponding to each installation package can be generated.

[0140] Exemplarily, the description information of the installation package can include the following content:

[0141] {"model": <unique model identifier>, "PXE image group": <PXE image group name>, "version": <version number>, "build": <generation date>, "arch": <architecture>, "kernel": {"name": <name>, "store_url": <storage path>, "md5sum": <MD5 value>}, "initrd": {"name": <name>, "store_url": <storage path>, "md5sum": <MD5 value>}}

[0142] Step 306: The target device installs the installation platform software package and stores the PXE image group files included in the installation platform installation package.

[0143] After obtaining the installation platform installation package required for the PXE boot process from the service provider, the private cloud user can install the operating system through the installation platform installation package.

[0144] Specifically, the target device can be the management device in the enterprise. After receiving the installation platform installation package for the target cluster of the enterprise, the target device can store the PXE image group files included in the installation platform installation package at a specified storage location, which is a location accessible to all physical machines. For example, it can be the local of the target device, or the cloud server of the enterprise's private cloud, or the enterprise's own server.

[0145] In the embodiments of the present application, generally speaking, in addition to the above-mentioned PXE image group files and corresponding description information, the installation platform installation package can also include the PXE installation tool required for installing the operating system. Therefore, after obtaining the installation platform installation package, the PXE installation tool can be installed, and the information of each physical machine of the target cluster to which the operating system is to be installed can be entered into the PXE installation tool. For example, it can be entered manually, or after installing the installation platform installation package, the PXE installation tool can sense the physical machines it owns through the local area network, so as to automatically enter the physical machine information.

[0146] Step 307: The target device initiates a PXE installation operation instruction to each physical machine.

[0147] Specifically, when it is necessary to install an operating system on each physical machine, the PXE installation tool on the target device can display the physical machines that can be booted by PXE. Then, select the physical machines to be installed and send PXE installation operation instructions to them to instruct the selected physical machines to install the operating system.

[0148] Step 308: The target device generates a PXE executable file for each physical machine in the target cluster, based on the machine model of each physical machine.

[0149] In this embodiment of the application, when installing the operating system on each physical machine, the configuration information required for the installation of the physical machine needs to be indicated in the PXE executable file. For example, as mentioned above, the PXE image group file that it is adapted to is indicated in the PXE executable file of each physical machine. This can be indicated by the image group identifier or the storage location. In this way, when the physical machine performs the actual installation process, it can obtain the PXE image group file that it is adapted to based on the indicated storage location.

[0150] In one implementation, each PXE executable file (PXE pre-boot file) can carry the corresponding PXE executable file content, so that the physical machine can obtain the relevant configuration information after obtaining the PXE pre-boot file.

[0151] In another implementation, leveraging the addressable nature of the extended PXE preboot file, only the PXE executable files corresponding to each physical machine are stored in designated storage locations. Then, the storage location of the corresponding PXE executable file for each physical machine is added to the extension bits of the respective PXE preboot file. This allows each physical machine to address the storage location indicated by the extension bits of the obtained PXE preboot file to retrieve its own corresponding PXE executable file. In practical applications, the extended PXE preboot file can be, for example, iPXE or grubx64.efi. Thus, by utilizing the addressable nature of the extended preboot executable file, a customized PXE executable file based on the PXE preboot file is generated for each physical machine.

[0152] For example, taking physical machine 1 as an example, when generating the PXE executable file for the PXE pre-boot file for physical machine 1, the PXE image group identifier corresponding to the model of physical machine 1 can be found. Then, the corresponding PXE image group is specified in the PXE executable file of the PXE pre-boot file of physical machine 1, that is, the kernel and initrd are specified. The PXE executable file of the PXE pre-boot file is stored in a TFTP path that can be addressed by the extended version of the PXE pre-boot file, such as the CentOS 7 example:

[0153] kernel${TFTP} / CentOS7 / isolinux / vmlinuz ks=${TFTP} / ks.cfg / CentOS-ks.cfginitrd${TFTP} / CentOS7 / isolinux / initrd.img

[0154] boot||goto failed

[0155] Step 309: Based on the PXE installation operation instructions, each physical machine downloads the corresponding PXE pre-boot file.

[0156] Specifically, the physical machine's network card can interact with the DHCP Server deployed by the installation tool to download the PXE pre-boot files required for installing the operating system on the physical machine.

[0157] Step 310: Execute the PXE pre-boot file on each physical machine to obtain the PXE executable file.

[0158] For example, when using an extended version of the preboot executable, each physical machine can address the storage location indicated by the extension bits of the obtained PXE preboot file to obtain its own corresponding PXE executable.

[0159] Step 311: Each physical machine downloads the corresponding PXE image group file to its memory based on the instructions in the PXE executable file.

[0160] Step 312: Each physical machine runs the PXE image group file in memory and begins the operating system installation process.

[0161] Specifically, when the target device distributes the PXE pre-boot file to each physical machine, and the physical machine initiates the PXE deployment of the operating system, the deployment network card of the physical machine can obtain the PXE pre-boot file configured for itself, and then obtain the corresponding PXE executable file based on the obtained PXE pre-boot file. After downloading the PXE image group file from the storage location indicated by the PXE executable file, it runs the PXE image group file in memory to start the automatic installation process of the operating system, thereby installing the corresponding operating system.

[0162] Using the example of physical machine 1 above, once the network card deployed on physical machine 1 obtains and runs the PXE pre-boot file, it can download the PXE executable file of the PXE pre-boot file from the TFTP directory according to the file addressing method. Physical machine 1 reads the PXE executable file and obtains the download path of the PXE image group, namely kernel and initrd. It then downloads the kernel and initrd image files from this path and installs the operating system based on the downloaded files. Since the kernel and initrd specified in the PXE executable file have been adapted and verified for this model's prototype, the installation failure caused by incompatibility between the model and the PXE image group files can be avoided, thereby improving the success rate of operating system installation and correspondingly improving installation efficiency.

[0163] Below, we will combine Figure 2 The system architecture shown illustrates the PXE-based operating system installation method of this application embodiment. In this application embodiment, before practical application, it is necessary to perform compatibility verification between different machine models and PXE image group files to establish a mapping relationship. Figure 2 The PXE image adaptation management module shown is used to manage all PXE image group files and machine models, which will be introduced below.

[0164] (1) Management of PXE image group files

[0165] The management of PXE image group files can include management functions such as creating, updating and deleting PXE image groups. As mentioned earlier, a PXE image group includes the description file, kernel and initrd of the PXE image group. The description file includes detailed management of the kernel and initrd, such as image group identifier, name, version, architecture, storage path and MD5 checksum.

[0166] In one implementation, a new PXE image group can be created. When creating a new PXE image group, the administrator can submit a creation request on the PXE image group management page, which will then upload the kernel and initrd image files of the PXE image group to the storage. After the upload, the PXE image adaptation management module will generate a corresponding description file based on the uploaded kernel and initrd, and save the description file in the PXE image group's file or database.

[0167] In another implementation, existing PXE image groups can be updated. When updating an existing PXE image group, administrators can select the PXE image group to be updated on the PXE image group management page and edit it. For example, for a specific PXE image group, the kernel or initrd it contains can be updated, and the kernel or initrd image files contained in the PXE image group can be re-uploaded. Correspondingly, the PXE image adaptation management module will update the description file of the PXE image group accordingly.

[0168] In another implementation, existing PXE image groups can also be deleted. For example, when a PXE image group becomes unusable, such as due to an outdated version, administrators can select the PXE image group to be deleted on the PXE image group management page and perform the deletion operation to remove these PXE image groups and avoid occupying storage space. Accordingly, based on the deletion operation, the PXE image adaptation management module deletes the description files, kernel, and initrd image files of these PXE image groups.

[0169] (2) Model Management

[0170] The PXE image adaptation management module can also manage metadata information for all machine models. Metadata information may include machine model identifier (ID) and hardware information, such as manufacturer name, model number, architecture, CPU model, RAID card model, disk model, and network card model.

[0171] The PXE image adaptation management module can save the metadata information of the device model in JSON format or key-value format. For example, it can save it in the following format:

[0172] {"ID": <model ID>, "date": {"manufacturer": <name>, "model": <factory model>, "arch": <hardware architecture>, "CPU model": <CPU model>, "RAID": <disk array card model>, "DISK": <disk model>, "network card": [{"network card 1": <model>}, …]}}

[0173] In the embodiments of this application, in order to smoothly select the PXE image group files that can be adapted to each model for each project, it is necessary to pre - adapt the models and PXE image group files and establish a mapping relationship. See Figure 4 As shown, it is a schematic flow diagram for adapting models and PXE image group files.

[0174] Step 401: Obtain at least one model and at least one image group identifier.

[0175] Among them, the PXE image adaptation management module is used to manage models and PXE image groups. Therefore, at least one model and at least one image group identifier can be obtained from the PXE image adaptation management module. Among them, when none of the models or PXE image groups managed by the PXE image adaptation management module have been adapted, then all models and the image group identifiers of all PXE image groups can be obtained; or, when specific models or PXE image groups are specified for adaptation, then the specified models and the image group identifiers of the specified PXE image groups can be obtained; or, when there are new models or PXE image groups, then the image group identifiers of the new models or new PXE image groups can be obtained.

[0176] Step 402: Combine each model in at least one model and each image group identifier in at least one image group identifier pairwise to obtain multiple待 - adapted combinations, and each待 - adapted combination includes a model and an image group identifier.

[0177] In the embodiments of this application, the models and image group identifiers can be combined pairwise to obtain multiple待 - adapted combinations, and each待 - adapted combination includes a model and an image group identifier. That is to say, any model is adapted and verified with any PXE image group to determine whether the model and the PXE image group are adapted.

[0178] Exemplarily, see Figure 5 As shown, if the at least one model obtained currently includes models 1 to 5, and the obtained image group identifiers include identifiers A to C, then pairwise combination can obtain 15待 - adapted combinations, and each待 - adapted combination includes a model and an image group identifier. For example, Figure 5 As shown, (model 1, image group identifier A) is a待 - adapted combination, and the other combinations are similar.

[0179] Step 403: Perform adaptation verification on multiple combinations to be adapted, and obtain the adaptation verification results corresponding to each combination.

[0180] In this embodiment of the application, for a combination to be adapted, the PXE image group file corresponding to the image group identifier included in the combination to be adapted is used to attempt to install on at least one prototype machine corresponding to the model included in the combination to be adapted. Then, based on the installation result of at least one prototype machine, the adaptation verification result corresponding to the combination to be adapted is obtained. The adaptation record management module adds the corresponding adaptation verification record to the adaptation management information stored in itself. An adaptation verification record includes a model, an image group identifier and the corresponding adaptation verification result.

[0181] Since the adaptation verification process is similar for each pair of devices to be adapted, this section will only use one pair of devices to be adapted as an example, such as the pair of devices to be adapted mentioned above (model 1, image group identifier A). See also Figure 6 The diagram shown is a flowchart of the adaptation verification process.

[0182] For the device model 1 and image group identifier A to be adapted and verified, the PXE installation tool obtains the information of device model 1 and the PXE image group file corresponding to image group identifier A from the PXE image group adaptation management module. Then, based on the information of device model 1, the PXE installation tool selects a prototype device belonging to device model 1 and attempts to install the operating system using the obtained PXE image group file, thereby obtaining the adaptation verification result between device model 1 and image group identifier A. When the operating system is successfully installed on the prototype device using the PXE image group file corresponding to image group identifier A, the adaptation verification between device model 1 and image group identifier A passes, and the adaptation record management module records a new adaptation success record. If the adaptation verification between device model 1 and image group identifier A fails, the adaptation record management module records a new adaptation failure record.

[0183] Specifically, the adaptation record management module can record the adaptation records of device models and image group identifiers in the form of a mapping table. For example, the mapping table structure between device models and PXE image groups can be defined as follows:

[0184] [{“Model ID”:<Model ID-1>,“Image Group ID”:<Image Group ID1>,“Adaptation Result”:<pass|failed>}, {"Model ID":<Model ID-2>, "Image Group ID":<Image Group ID-2>, "Adaptation Result":<pass|failed>},……{“Model ID”:<Model ID-n>,“Image Group ID”:<Image Group ID-n>,“Adaptation Result”:<pass|failed>}]

[0185] If the compatibility verification between device model 1 and image group identifier A passes, the compatibility record management module will add the following compatibility pass record:

[0186] {“Model ID”:<Model 1>,“Image Group ID”:<Image Group A>,“Adaptation Result”: <pass>}

[0187] If the compatibility verification between device model 1 and image group identifier A fails, the compatibility record management module will add the following compatibility failure record:

[0188] {"Model ID":<Model 1>, "Image Group ID":<Image Group A>, "Adaptation Result":} <failed>}

[0189] Step 404: Update the mapping table based on the obtained multiple adaptation verification results.

[0190] See also Figure 5 As shown, the mapping table stores the PXE image group identifiers that have passed the adaptation verification for each device model. In practical applications, the mapping table can record one type of PXE image group identifier that has passed the adaptation verification for each device model, such as the PXE image group identifier of the highest version among the PXE image groups adapted to each device model. Therefore, after obtaining the adaptation verification results for each combination to be adapted, the mapping table can be updated based on the obtained adaptation verification results.

[0191] See Figure 7 The diagram shows a flowchart of the process for updating the mapping table. The adaptation verification result has two possibilities: one is that the verification passed. For any one of these results, if the verification passes, it can be determined whether the mapping table already records the mapping relationship for the first device model corresponding to that verification result. If it does, the mapping table is updated based on the first image group identifier corresponding to that verification result.

[0192] The mapping table can be updated based on the first image group identifier corresponding to the adaptation verification result by comparing the version of the PXE image group corresponding to the first image group identifier with the version of the PXE image group corresponding to the second image group identifier of the first model recorded in the mapping table. If the version of the PXE image group corresponding to the first image group identifier is higher, that is, the time difference between the release time of the first image group identifier and the current time is less than the time difference between the release time of the second image group identifier and the current time, then the second image group identifier in the mapping relationship of the first model is changed to the first image group identifier.

[0193] For example, for device 1 and PXE image group A, if the compatibility verification between device 1 and PXE image group A passes, it is determined whether the mapping table has recorded the corresponding relationship related to device 1. If it has recorded the corresponding PXE image group B for device 1, then PXE image group A and PXE image group B can be compared. If the version of PXE image group A is updated, then the mapping relationship of device 1 is updated to PXE image group A.

[0194] After determining whether the mapping table already records the corresponding first model for the adaptation verification result, if it is determined that the mapping relationship for the first model is not recorded, then a new mapping relationship between the first model and the first image group identifier is added to the mapping table. For example, for model 1 and PXE image group A, if the mapping table does not record the PXE image group corresponding to model 1, then the mapping relationship between model 1 and PXE image group A is added to the mapping table.

[0195] In this embodiment of the application, another possibility for the adaptation verification result is that the verification failed. If the adaptation verification result indicates that the adaptation verification failed, it can be determined whether the mapping relationship table has recorded the mapping relationship of the first model corresponding to the adaptation verification result. If the mapping relationship of the first model is not recorded, it means that the model has not been set with an adapted PXE image group. In order to ensure that the subsequent release of the installation platform installation package for the model can proceed normally, the PXE image group corresponding to the model can be set as the base PXE image group, thereby adding the mapping relationship between the model and the base PXE image group to the mapping relationship table.

[0196] For example, if the above-mentioned model 1 and PXE image group A fail to adapt, and there is no corresponding mapping relationship for model 1 in the recorded mapping relationship, then a new mapping relationship between model 1 and the base PXE image group can be added.

[0197] The baseline PXE image group refers to the PXE image group initially used when attempting to install on a physical machine. It can generally be set to a PXE image group that is widely applicable based on experience. For example, if a certain version of the PXE image group can be successfully adapted to most machine models, then it can be set as the PXE image group.

[0198] Similarly, when a new model is introduced, the default mapping relationship for that model can be recorded in the mapping relationship table so that the subsequent release of the installation platform package for that model can proceed normally. The default mapping relationship may include, for example, the model ID and the baseline PXE image group ID.

[0199] For example, when a new model with ID YD255xx is added, and the base PXE image group is 467, then the following record can be added:

[0200] {"Model ID": YD255xx, "Image Group ID": 467}

[0201] See Figure 8 The diagram shown illustrates another process for adapting a device model to a PXE image group file, as provided in this application embodiment.

[0202] Step 801: Set up a baseline PXE image group and obtain at least one machine model and at least one image group identifier.

[0203] As mentioned above, the baseline PXE image group refers to the PXE image group initially used when attempting to install a system on a physical machine.

[0204] In one implementation, different machine models can be set to the same baseline PXE image group. For example, the installation success rate of each PXE image group can be counted. If the installation success rate of PXE image group A is the highest, then the baseline PXE image group for all machine models can be set to PXE image group A.

[0205] In another implementation, different machine models can be configured with different baseline PXE image groups. For example, machine models can be grouped according to commonalities, and the installation success rate of each PXE image group can be statistically analyzed. If PXE image group A in group 1 has the highest installation success rate, then the baseline PXE image group for all machine models in group 1 can be set as PXE image group A. Alternatively, a baseline PXE image group can be configured for each machine model.

[0206] Step 802: Starting from the base image group identifier corresponding to each model, and in descending order of release time, use the PXE image group file corresponding to each image group identifier to attempt installation on at least one prototype of that model.

[0207] In this embodiment, higher versions of the operating system have better functionality and optimization, so users generally prefer to use higher versions of the operating system. Therefore, when adapting PXE image groups and machine models, different versions of the operating system can be installed gradually in descending order of version. When a certain version of the PXE image group can be successfully adapted, the adaptation process for that machine model can be ended to minimize the number of adaptations.

[0208] See Figure 9 The diagram shows another flowchart of the compatibility verification process. Taking model 1 as an example, when performing compatibility verification on model 1, the operating system is first attempted to be installed on the prototype machine belonging to model 1 using a baseline PXE image group through the PXE installation tool. Compatibility verification is then performed on each version of the PXE image group in a specific order. When the operating system is successfully installed on the prototype machine using the PXE image group file corresponding to a PXE image group identifier, the compatibility verification between model 1 and that PXE image group identifier is passed. The compatibility record management module records a new compatibility pass record. For example, if the compatibility verification between model 1 and that PXE image group identifier is passed, the compatibility record management module records the following new compatibility pass record:

[0209] {"Model ID”: <Model 1>, "Image Group ID”: <PXE Image Group Identifier>, "Adaptation Result”: <pass>}

[0210] If the compatibility verification between model 1 and the PXE image group fails, the compatibility record management module records a new compatibility failure record.

[0211] {"Model ID":<Model 1>, "Image Group ID":} <467> "Adaptation Results": <failed>}

[0212] Furthermore, after the adaptation verification of a PXE image group is completed, if the adaptation verification passes, it will also check whether a PXE image group corresponding to model 1 exists in the mapping relationship table managed by the mapping relationship management module. If it exists, the version of the current PXE image group is compared with the version of the stored PXE image groups. If the version of the current PXE image group is updated, the PXE image group corresponding to model 1 in the mapping relationship table will be updated to the current PXE image group. If no PXE image group corresponding to model 1 is stored, the mapping relationship between model 1 and the current PXE image group will be stored in the mapping relationship table.

[0213] Similarly, if the adaptation verification fails, check whether there is a PXE image group corresponding to model 1 in the stored mapping table. If not, store the mapping relationship between model 1 and the base PXE image group in the mapping table.

[0214] In this embodiment of the application, the above-mentioned adaptation verification process may stop when a compatible PXE image group is obtained, or, in order to have a more comprehensive understanding of the matching situation of each model with different PXE image groups, each model may be tried to be adapted with all PXE image groups to avoid the situation where a version cannot be installed on the project site and a compatible PXE image group cannot be selected in time.

[0215] It should be understood that the order of release time in descending order, that is, the order of version number, is only one possible adaptation order. In actual use, the adaptation order can be set in other ways, and this application embodiment does not limit this.

[0216] Step 803: Based on the installation results of each PXE image group file, obtain the corresponding compatibility verification result for this model.

[0217] Step 804: Update the mapping table based on the obtained multiple adaptation verification results.

[0218] In this embodiment of the application, when updating the mapping relationship table, it can be done after all adaptation verifications for a model have been completed. That is, when a model has finished adaptation and there are successful adaptation results, the PXE image group corresponding to the model is obtained from the mapping relationship table, and the version of the PXE image group is compared with the version of the successfully adapted PXE image group. The mapping relationship table records the mapping relationship between the model and the latest version of the PXE image group. When it is found that an updated PXE image group has been successfully adapted, the PXE image group identifier corresponding to the model in the mapping relationship table is updated.

[0219] In this embodiment, when a private cloud user applies for a batch installation service, the installation package release management module of the installation platform finds the corresponding mapping relationship from the mapping relationship table according to the model used by the private cloud user. Based on the PXE image group identifier in these mapping relationships, it obtains the PXE image group information from the PXE image adaptation management module, and obtains the PXE image group file from the corresponding storage, packages it, and sends it to the private cloud user. The packaging information is divided into multiple entries according to the model, with one entry corresponding to one model. Each entry includes relevant information about the model and the PXE image group.

[0220] Correspondingly, when the dedicated cloud user actually installs the operating system, the PXE installation tool introduces an extended version of the pre-boot execution environment file. Taking advantage of the addressable nature of the extended pre-boot execution file, a customized PXE pre-boot file corresponding to the PXE executable file is generated for each physical machine.

[0221] Specifically, when generating the PXE executable file corresponding to the PXE preboot file, the kernel and initrd information in the corresponding PXE image group are first located based on the physical machine's model. Then, the corresponding kernel and initrd are specified in the PXE executable file corresponding to the physical machine's PXE preboot file. This PXE executable file is placed in a TFTP path that the extended preboot executable file can address. Thus, when the physical machine initiates PXE operating system deployment, the physical machine's deployment network card obtains the corresponding PXE preboot file, runs the file, and downloads the corresponding PXE executable file from the TFTP directory according to the file's addressing method. The physical machine reads this PXE executable file, obtains the download paths for the kernel and initrd, downloads the kernel and initrd, and then installs the operating system.

[0222] In summary, this application provides a method for managing PXE image groups of a private cloud based on physical machine models. By performing compatibility verification between machine models and PXE image groups, recording the results of each verification, and establishing a mapping table between each machine model and the latest version of the PXE image group, for different machine models in a project, the successfully adapted machine models and their corresponding PXE image group files are obtained from the mapping table, packaged, and sent to the private cloud user. The private cloud user's physical machines generate a PXE executable file corresponding to the PXE pre-boot file for a specific physical machine based on the machine model and the corresponding PXE image group, for PXE installation.

[0223] When performing compatibility verification between a device model and a PXE image group, a baseline image group version is provided. If the device model is not adapted, it is mapped to the baseline image group version. The default adaptation result is "pass", and a corresponding mapping relationship is generated. If the device model passes the compatibility verification with a certain PXE image group, the pass record for the device model and the PXE image group is recorded, and a mapping relationship table is generated or updated. If the device model passes the compatibility verification with multiple PXE image groups, only the PXE image group with the latest version is recorded in the mapping relationship table, and the device model and the PXE image group that failed to adapt are not recorded in the mapping relationship table.

[0224] The technical solution of this application addresses the problem in multi-user private clouds where there are over a hundred different physical machine models, and different private cloud users cannot use different PXE image groups despite using different machine models. It enables the use of different PXE image groups based on the actual machine model of the private cloud user. This solves the problem in related technologies where manually modifying to use different PXE image groups results in only one PXE image group being used at a time, leading to installation failures on some machine models. This improves the success rate of installing operating systems on physical machines and is applicable to large-scale physical machine installation scenarios.

[0225] Please see Figure 10 Based on the same inventive concept, this application also provides a PXE-based operating system installation device 100, which includes:

[0226] The determining unit 1001 is used to determine the target image group identifier corresponding to each target model based on the mapping relationship between each target model that has passed the adaptation verification and each image group identifier for each target model included in the target group.

[0227] The acquisition unit 1002 is used to acquire the corresponding image group description file based on the acquired target image group identifier; and to acquire the PXE image group file corresponding to each target model based on the storage location indicated by the acquired image group description file.

[0228] The packaging unit 1003 is used to package the obtained PXE image group files to obtain the installation platform package, and send the installation platform package to the target device so that the target device can install the corresponding operating system for the target cluster based on the installation platform package.

[0229] Among them, the aforementioned determining unit 1001 to packaging unit 1003 correspond, for example, to Figure 2 The installation package release management module of the installation platform shown has the following functions.

[0230] Optionally, the device also includes an adapter verification unit 1004, used for:

[0231] Obtain at least one device model and at least one image group identifier;

[0232] For each model in at least one model and each image group identifier in at least one image group identifier, pairwise combinations are made to obtain multiple combinations to be adapted. Each combination to be adapted includes a model and an image group identifier.

[0233] Adaptation verification is performed on multiple combinations to be adapted, and the adaptation verification results corresponding to each combination are obtained.

[0234] The mapping relationship is updated based on the obtained multiple adaptation verification results.

[0235] Optionally, the adapter verification unit 1004 is used specifically for:

[0236] For multiple combinations to be adapted, perform the following operations respectively:

[0237] For a combination to be adapted, use the PXE image group file corresponding to the image group identifier included in the combination to be adapted, and attempt to install it on at least one prototype machine corresponding to the model included in the combination to be adapted.

[0238] Based on the installation results of at least one prototype, obtain the adaptation verification result corresponding to a combination to be adapted.

[0239] Optionally, the adapter verification unit 1004 is also used for:

[0240] Obtain at least one device model and at least one image group identifier;

[0241] For each of at least one model type, perform the following operations:

[0242] For a given machine model, starting from the base image group identifier corresponding to that machine model, and arranged in descending order of release time, the PXE image group files corresponding to each image group identifier are used sequentially to attempt installation on at least one prototype machine corresponding to that machine model.

[0243] Based on the installation results of each PXE image group file, a compatibility verification result corresponding to a certain machine model is obtained.

[0244] Based on the obtained multiple adaptation verification results, update the mapping relationship table.

[0245] Optionally, the adapter verification unit 1004 is used specifically for:

[0246] For multiple adaptation verification results, perform the following operations respectively:

[0247] For a given adaptation verification result, if the adaptation verification result indicates that the adaptation verification has passed, then determine whether the mapping relationship already records the corresponding relationship of the first model corresponding to the adaptation verification result;

[0248] If the corresponding relationship for the first model has already been recorded, then the corresponding relationship is updated based on the first image group identifier corresponding to an adaptation verification result;

[0249] If the corresponding relationship for the first model is not recorded, then add a corresponding relationship between the first model and the first image group identifier to the mapping relationship table.

[0250] Optionally, the adapter verification unit 1004 is used specifically for:

[0251] Determine whether the time difference between the publication time of the first mirror group identifier and the current time is less than the time difference between the publication time of the second mirror group identifier corresponding to the recorded correspondence and the current time.

[0252] If it is less than, then the identifier of the second mirror group in the corresponding relationship will be changed to the identifier of the first mirror group.

[0253] Optionally, the adapter verification unit 1004 is also used for:

[0254] If an adaptation verification result indicates that the adaptation verification failed, then determine whether the mapping relationship already records the corresponding relationship of the first model;

[0255] If the corresponding relationship for the first model is not recorded, then add a corresponding relationship between the first model and the base image group identifier to the mapping relationship table.

[0256] Among them, the aforementioned adaptation verification unit 1004 corresponds, for example, to Figure 2 The functions of the PXE installation tool, PXE image adaptation management module, adaptation record management module, and mapping relationship management module are shown.

[0257] This device can be used to execute the system-side methods in the above embodiments. Therefore, the functions that each functional module of this device can achieve can be referred to the descriptions of the above embodiments, and will not be elaborated further.

[0258] Please see Figure 11 Based on the same inventive concept, this application also provides a PXE-based operating system installation device 110, which includes:

[0259] The receiving unit 1101 is used to obtain the installation platform package for the target cluster and store the PXE image group files included in the installation platform package; wherein, the installation platform package includes PXE image group files adapted to each model in the target cluster.

[0260] The generation unit 1102 is used to generate a PXE executable file for each physical machine according to the model of each physical machine in the target machine group; wherein, the PXE executable file of each physical machine indicates the storage location of its adapted PXE image group file.

[0261] The sending unit 1103 is used to send the corresponding PXE pre-boot file of each physical machine to the corresponding physical machine based on the download request of each physical machine after instructing each physical machine to install the operating system, so that each physical machine can access the storage location indicated by the extension bit of the obtained PXE pre-boot file to obtain the corresponding PXE executable file.

[0262] Optionally, the generating unit 1102 is also used for:

[0263] Store the corresponding PXE executable file for each physical machine to the designated storage location;

[0264] Add the storage location of the corresponding PXE executable file for each physical machine to the extension bit of the corresponding PXE pre-boot file for each physical machine;

[0265] The sending unit 1103 is specifically used to: after instructing each physical machine to install the operating system, send the corresponding PXE pre-boot file of each physical machine to the corresponding physical machine based on the download request of each physical machine, so that each physical machine can address the storage location indicated by the extension bit of the obtained PXE pre-boot file to obtain the corresponding PXE executable file.

[0266] This device can be used to execute the methods performed by the management device in the above embodiments. Therefore, the functions that each functional module of this device can achieve can be referred to the descriptions of the above embodiments, and will not be repeated here.

[0267] Please see Figure 12 Based on the same inventive concept, this application also provides a PXE-based operating system installation device 120, which includes:

[0268] The acquisition unit 1201 is used to acquire the PXE pre-boot file corresponding to the physical machine; wherein, the PXE pre-boot file indicates the PXE executable file required for installing the operating system on the physical machine;

[0269] The execution unit 1202 is used to execute the PXE pre-boot file and obtain the PXE executable file; wherein, the PXE executable file indicates the PXE image group file adapted to this physical machine;

[0270] The download and installation unit 1203 is used to download the corresponding PXE image group file based on the instructions of the PXE executable file, and install the corresponding operating system based on the PXE image group file.

[0271] This device can be used to execute the methods performed by the physical machine in the above embodiments. Therefore, the functions that each functional module of this device can achieve can be referred to the descriptions of the above embodiments, and will not be elaborated further.

[0272] Through the aforementioned devices, it is possible to perform compatibility verification between machine models and PXE image groups, record the results of each compatibility verification, and establish a mapping table between each machine model and the latest version of the PXE image group. For different machine models in a project, the successfully adapted machine models and their corresponding PXE image group files are obtained from the mapping table, packaged, and sent to the dedicated cloud user. The dedicated cloud user's physical machines generate PXE executable files corresponding to the PXE pre-boot files for a specific physical machine based on the machine model and the corresponding PXE image group, which are used for PXE installation. This improves the success rate of installing operating systems on physical machines and is suitable for large-scale physical machine installation scenarios.

[0273] Please see Figure 13 Based on the same technical concept, this application also provides a computer device 130, which may include a memory 1301 and a processor 1302.

[0274] The memory 1301 is used to store computer programs executed by the processor 1302. The memory 1301 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function, etc.; the data storage area may store data created based on the use of the computer device, etc. The processor 1302 may be a central processing unit (CPU), or a digital processing unit, etc. This application embodiment does not limit the specific connection medium between the memory 1301 and the processor 1302. This application embodiment... Figure 13 The memory 1301 and the processor 1302 are connected via a bus 1303, and the bus 1303 is in Figure 13 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus 1303 can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 13 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0275] Memory 1301 may be volatile memory, such as random-access memory (RAM); memory 1301 may also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD), or solid-state drive (SSD); or memory 1301 may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 1301 may be a combination of the above-described memories.

[0276] The processor 1302 is used to execute the methods described in the above embodiments when calling the computer program stored in the memory 1301.

[0277] In some possible implementations, various aspects of the methods provided in this application may also be implemented as a program product comprising program code that, when run on a computer device, causes the computer device to perform the steps of the methods according to the various exemplary embodiments of this application described above. For example, the computer device may perform the methods as performed in the above embodiments.

[0278] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0279] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0280] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.< / failed> < / pass> < / failed> < / pass>

Claims

1. An operating system installation method based on a pre-boot execution environment (PXE), characterized in that, The method includes: Obtain at least one device model and at least one image group identifier; Each of the at least one model and each of the at least one image group identifiers are combined in pairs to obtain multiple combinations to be adapted, each combination to be adapted includes a model and an image group identifier. Each of the multiple combinations to be adapted is subjected to adaptation verification to obtain the adaptation verification result corresponding to each of the multiple combinations to be adapted. Based on the obtained multiple adaptation verification results, the mapping relationship is updated. The mapping relationship includes the mapping relationship between each model that has passed the adaptation verification and each image group identifier. For each target model included in the target fleet, based on the mapping relationship, the target image group identifier corresponding to each target model is determined respectively; Based on the obtained target image group identifiers, the storage location of the PXE image group file corresponding to each target image group identifier is obtained from the image group description file; Based on the obtained storage locations, the PXE image group files corresponding to each target image group identifier are obtained respectively; Based on the obtained PXE image group files, a package is formed to obtain the installation platform package, and the installation platform package is sent to the target device so that the target device can install the corresponding operating system for the target cluster based on the installation platform package.

2. The method as described in claim 1, characterized in that, Each of the plurality of combinations to be adapted is subjected to adaptation verification to obtain the adaptation verification result corresponding to each of the plurality of combinations to be adapted, including: For each of the multiple combinations to be adapted, the following operations are performed respectively: For a combination to be adapted, the PXE image group file corresponding to the image group identifier included in the combination to be adapted is used to attempt to install on at least one prototype machine corresponding to the model included in the combination to be adapted. Based on the installation results of the at least one prototype, the adaptation verification result corresponding to the one combination to be adapted is obtained.

3. The method as described in claim 1, characterized in that, The method further includes: Obtain at least one device model and at least one image group identifier; For each of the at least one model, perform the following operations: For a given model, starting from the base image group identifier corresponding to that model, and arranged in descending order of release time, the PXE image group files corresponding to each image group identifier are used sequentially to attempt installation on at least one prototype of that model. Based on the installation results of each PXE image group file, the compatibility verification result corresponding to the aforementioned model is obtained. Based on the obtained multiple adaptation verification results, update the mapping relationship table.

4. The method as described in claim 3, characterized in that, Based on the obtained multiple adaptation verification results, the mapping relationship is updated, including: For each of the multiple adaptation verification results, perform the following operations: For a given adaptation verification result, if the adaptation verification result indicates that the adaptation verification has passed, then it is determined whether the mapping relationship already records the corresponding relationship of the first model corresponding to the adaptation verification result. If the correspondence of the first model has been recorded, then the correspondence is updated based on the first image group identifier corresponding to the adaptation verification result; If the corresponding relationship of the first model is not recorded, then a corresponding relationship between the first model and the first image group identifier is added to the mapping relationship table.

5. The method as described in claim 4, characterized in that, Based on the first mirror group identifier corresponding to the aforementioned adaptation verification result, the correspondence is updated, including: Determine whether the time difference between the publication time of the first mirror group identifier and the current time is less than the time difference between the publication time of the second mirror group identifier corresponding to the recorded correspondence and the current time. If it is less than, then the second mirror group identifier in the correspondence is changed to the first mirror group identifier.

6. The method as described in claim 4, characterized in that, The method further includes: If the adaptation verification result indicates that the adaptation verification failed, then it is determined whether the mapping relationship already records the corresponding relationship of the first model; If the corresponding relationship of the first model is not recorded, then a corresponding relationship between the first model and the base image group identifier is added to the mapping relationship table.

7. A method for installing an operating system based on PXE, characterized in that, The method includes: Obtain the installation platform package for the target cluster and store the PXE image group files included in the installation platform package; wherein, the installation platform package includes PXE image group files adapted to each target model in the target cluster, and the mapping relationship between each target model and the target image group identifier corresponding to the adapted PXE image group file is verified through adaptation. Based on the model of each physical machine in the target machine group, generate a PXE executable file corresponding to each physical machine; wherein, the PXE executable file of each physical machine indicates the PXE image group file that it is adapted to. After instructing each physical machine to install the operating system, the corresponding PXE executable file for each physical machine is sent to the corresponding physical machine based on the download request of each physical machine, so that each physical machine can download the corresponding PXE image group file and install the corresponding operating system based on the instructions of the obtained PXE executable file. The adaptation verification process includes: pairwise combining each model in at least one device model and each image group identifier in at least one image group identifier to obtain multiple adaptation combinations, each of which includes a device model and an image group identifier; performing adaptation verification on each of the multiple adaptation combinations to obtain the adaptation verification result corresponding to each of the multiple adaptation combinations; and updating the mapping relationship based on the obtained multiple adaptation verification results, wherein the mapping relationship includes the mapping relationship between each device model that has passed the adaptation verification and each image group identifier.

8. The method as described in claim 7, characterized in that, After generating a PXE executable file for each physical machine in the target cluster according to the machine type of each physical machine, the method includes: Store the corresponding PXE executable file for each physical machine to the designated storage location; Add the storage location of the corresponding PXE executable file for each physical machine to the extension bit of the corresponding PXE pre-boot file for each physical machine; After instructing each physical machine to install the operating system, based on the download requests of each physical machine, the corresponding PXE executable file for each physical machine is sent to the respective physical machine, including: After instructing each physical machine to install the operating system, based on the download request of each physical machine, the corresponding PXE pre-boot file for each physical machine is sent to the corresponding physical machine, so that each physical machine can access the storage location indicated by the extension bit of the obtained PXE pre-boot file to obtain the corresponding PXE executable file.

9. A method for installing an operating system based on PXE, characterized in that, The method includes: Obtain the PXE pre-boot file corresponding to this physical machine; wherein, the PXE pre-boot file indicates the PXE executable file required for installing the operating system on this physical machine; Execute the PXE pre-boot file to obtain the PXE executable file; wherein, the PXE executable file indicates the PXE image group file adapted to this physical machine, and the mapping relationship between the target machine model to which this physical machine belongs and the target image group identifier corresponding to the PXE image group file has been adapted and verified. Based on the instructions in the PXE executable file, download the corresponding PXE image group file, and install the corresponding operating system based on the PXE image group file; The adaptation verification process includes: pairwise combining each model in at least one device model and each image group identifier in at least one image group identifier to obtain multiple adaptation combinations, each of which includes a device model and an image group identifier; performing adaptation verification on each of the multiple adaptation combinations to obtain the adaptation verification result corresponding to each of the multiple adaptation combinations; and updating the mapping relationship based on the obtained multiple adaptation verification results, wherein the mapping relationship includes the mapping relationship between each device model that has passed the adaptation verification and each image group identifier.

10. A PXE-based operating system installation device, characterized in that, The device includes: An adaptation verification unit is configured to obtain at least one device model and at least one image group identifier; perform pairwise combinations on each of the at least one device model and each of the at least one image group identifier to obtain multiple adaptation combinations, each of which includes one device model and one image group identifier; perform adaptation verification on each of the multiple adaptation combinations to obtain the adaptation verification result corresponding to each of the multiple adaptation combinations; and update the mapping relationship based on the obtained multiple adaptation verification results, wherein the mapping relationship includes the mapping relationship between each device model that has passed the adaptation verification and each image group identifier. The determining unit is used to determine the target image group identifier corresponding to each target model based on the mapping relationship between each target model that has passed the adaptation verification and each image group identifier for each target model included in the target group. The acquisition unit is configured to acquire the corresponding image group description file based on the acquired target image group identifier; and to acquire the PXE image group file corresponding to each target model based on the storage location indicated by the acquired image group description file. The packaging unit is used to package the obtained PXE image group files to obtain the installation platform package, and send the installation platform package to the target device so that the target device can install the corresponding operating system for the target cluster based on the installation platform package.

11. A PXE-based operating system installation device, characterized in that, The device includes: The receiving unit is used to obtain the installation platform package for the target cluster and store the PXE image group files included in the installation platform package; wherein, the installation platform package includes PXE image group files adapted to each target model in the target cluster, and the mapping relationship between each target model and the target image group identifier corresponding to the adapted PXE image group file is verified through adaptation. The generation unit is used to generate a PXE executable file corresponding to each physical machine according to the model of each physical machine in the target machine group; wherein, the PXE executable file of each physical machine indicates the storage location of its adapted PXE image group file. The sending unit is configured to, after instructing each physical machine to install the operating system, send the corresponding PXE pre-boot file to the respective physical machine based on the download request of each physical machine, so that each physical machine can address the storage location indicated by the extension bit of the obtained PXE pre-boot file to obtain the corresponding PXE executable file. The adaptation verification process includes: pairwise combining each model in at least one device model and each image group identifier in at least one image group identifier to obtain multiple adaptation combinations, each of which includes a device model and an image group identifier; performing adaptation verification on each of the multiple adaptation combinations to obtain the adaptation verification result corresponding to each of the multiple adaptation combinations; and updating the mapping relationship based on the obtained multiple adaptation verification results, wherein the mapping relationship includes the mapping relationship between each device model that has passed the adaptation verification and each image group identifier.

12. An operating system installation device based on the Preboot Execution Environment (PXE), characterized in that, The device includes: The acquisition unit is used to acquire the PXE pre-boot file corresponding to the physical machine; wherein, the PXE pre-boot file indicates the PXE executable file required for installing the operating system on the physical machine; An execution unit is used to execute the PXE pre-boot file and obtain the PXE executable file; wherein, the PXE executable file indicates the PXE image group file adapted to this physical machine, and the mapping relationship between the target machine model to which this physical machine belongs and the target image group identifier corresponding to the PXE image group file has been adapted and verified. The download and installation unit is used to download the corresponding PXE image group file based on the instructions of the PXE executable file, and install the corresponding operating system based on the PXE image group file; The adaptation verification process includes: pairwise combining each model in at least one device model and each image group identifier in at least one image group identifier to obtain multiple adaptation combinations, each of which includes a device model and an image group identifier; performing adaptation verification on each of the multiple adaptation combinations to obtain the adaptation verification result corresponding to each of the multiple adaptation combinations; and updating the mapping relationship based on the obtained multiple adaptation verification results, wherein the mapping relationship includes the mapping relationship between each device model that has passed the adaptation verification and each image group identifier.

13. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6, 7 to 8, or 9.

14. A computer storage medium storing computer program instructions thereon, characterized in that, When executed by a processor, the computer program instructions implement the steps of the method described in any one of claims 1 to 6, 7 to 8, or 9.

15. A computer program product comprising computer instructions, characterized in that, When executed by a processor, the computer instructions implement the steps of the method according to any one of claims 1 to 6, 7 to 8, or 9.

Images