A Booting Method, Device and Medium for a Diskless Client

Abstract

The present application discloses a method, device and medium for starting a diskless client. After receiving a diskless startup instruction, it is determined whether there is pre-cached information in the local system; wherein, the pre-cached information includes the ID of the boot mode and mirror information; if it exists, the data corresponding to the pre-cached information is downloaded and saved from the server according to the pre-cached information. Compared with the current technology, each time the diskless client starts up, an IO request is generated, and then the corresponding mirror file is obtained from the server. By adopting the technical solution of the present application, the pre-cached information is stored in the local system in advance. When starting up without a disk, the relevant data required is directly booted from the server according to the pre-cached information. The server does not need to search for the relevant data according to the IO request anymore, which improves the processing efficiency of the server, reduces the influence of the network rate on the IO rate, and thus improves the startup speed of the diskless client.

Description

Technical Field

[0001] This application relates to the field of diskless boot technology, and in particular to a method, device, and medium for booting a diskless client. Background Art

[0002] A diskless system is a network transmission technology used in Internet cafes, karaoke bars, and offices. A computer using a diskless system will not use the local hard disk to obtain the boot system, but will obtain the mirror file of the boot system from a designated server on the network and download it back to the local machine for machine startup.

[0003] During the diskless boot process, the diskless client will virtualize a system disk during the startup phase of the extended version "IPXE" of the Preboot eXecution Environment (PXE) or the startup phase of the Unified Extensible Firmware Interface (UEFI). All read and write operations on this virtual disk will be redirected to the system image file on the server through the network. The IPXE or UEFI startup phase will load and run the boot program of the system disk. The boot program needs to read the required file resources from the virtual system disk during the boot process, and these IO requests will ultimately be redirected to the system image file on the server through the network. It can be seen that in the current technology, the system startup speed depends on the virtual disk IO rate, and the virtual disk IO rate is affected by the network rate.

[0004] Therefore, how to reduce the impact of the network rate on the IO rate and improve the startup speed of the diskless client is an urgent problem to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a method, device, and medium for booting a diskless client, which is used to reduce the impact of the network rate on the IO rate and improve the startup speed of the diskless client.

[0006] To solve the above technical problems, this application provides a method for booting a diskless client, and the method includes:

[0007] After receiving the diskless boot instruction, determine whether there is pre-cache information in the local system; wherein, the pre-cache information includes the boot mode and the ID of the mirror information;

[0008] If it exists, download and save the data corresponding to the pre-cache information from the server according to the pre-cache information.

[0009] Preferably, if the pre-cache information does not exist in the local system, it further includes:

[0010] Send a request message to the server to obtain the pre-cached information;

[0011] If the pre-cached information is obtained, enter the step of downloading and saving the data corresponding to the pre-cached information from the server according to the pre-cached information.

[0012] Preferably, if the pre-cached information is not obtained, it further includes:

[0013] Obtain the IDs of the boot mode and the mirror information;

[0014] Record each of the IO request messages generated when booting the mirror information according to the IDs of the boot mode and the mirror information; the IO request message includes the address and length of the starting sector of each IO request;

[0015] Download and save the corresponding data from the server according to the IO request message.

[0016] Preferably, it further includes:

[0017] Generate and save the pre-cached information composed of the IDs of the boot mode and the mirror information;

[0018] Send the pre-cached information and the IO request message to the server for saving.

[0019] Preferably, before the step of sending the pre-cached information and the IO request message to the server for saving, it further includes:

[0020] Allocate each of the IO request messages according to the size of a pre-set block;

[0021] Generate index information for each of the blocks;

[0022] Further, the step of sending the pre-cached information and the IO request message to the server for saving includes: sending the pre-cached information and the index information to the server for saving.

[0023] Preferably, it further includes:

[0024] Delete duplicate IO request messages.

[0025] Preferably, it further includes:

[0026] Merge the IO requests whose lengths meet the preset conditions and whose starting sectors are adjacent.

[0027] To solve the above technical problems, the present application further provides a startup device for a diskless client, and the device includes:

[0028] A judgment module, configured to judge whether there is pre-cached information in the local system after receiving a diskless startup instruction; wherein, the pre-cached information includes a boot mode and an ID of image information.

[0029] A processing module, configured to, if there is pre-cached information, download and save data corresponding to the pre-cached information from a server according to the pre-cached information.

[0030] To solve the above technical problems, the present application further provides a startup device for a diskless client, which device includes a memory for storing a computer program;

[0031] A processor, configured to implement the steps of the startup method of the diskless client as described above when executing the computer program.

[0032] To solve the above technical problems, the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the startup method of the diskless client as described above are implemented.

[0033] The startup method of the diskless client provided by the present application includes: after receiving a diskless startup instruction, judging whether there is pre-cached information in the local system; wherein, the pre-cached information includes a boot mode and an ID of image information; if there is, downloading and saving data corresponding to the pre-cached information from a server according to the pre-cached information. Compared with the current technology, each time the diskless client starts up, an IO request is generated, and then the corresponding image file is obtained from the server. With the technical solution of the present application, the pre-cached information is stored in the local system in advance, and when starting up disklessly, the relevant data required is directly booted from the server according to the pre-cached information, and the server does not need to search for the relevant data according to the IO request anymore, improving the processing efficiency of the server and reducing the influence of the network rate on the IO rate, thereby improving the startup speed of the diskless client.

[0034] In addition, the startup device and medium of the diskless client provided by the present application correspond to the above startup method of the diskless client, and the effects are the same. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] To more clearly illustrate the embodiments of the present application, the following will briefly introduce the drawings required in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0036] Figure 1 It is a flowchart of a startup method of a diskless client provided by an embodiment of the present application;

[0037] Figure 2 Application effect comparison table of a startup method for a diskless client provided by an embodiment of the present application;

[0038] Figure 3 Structural diagram of a startup device for a diskless client provided by an embodiment of the present application;

[0039] Figure 4 Structural diagram of another startup device for a diskless client provided by an embodiment of the present application. Detailed implementation manners

[0040] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0041] The diskless startup technology generally refers to a computer that downloads a system image through the network and starts up. The diskless client itself does not have a hard disk, that is, there is no system image locally, and the system image is stored on the server. The diskless client uses the startup code in its own network card to obtain an IP address using the Dynamic Host Configuration Protocol (DHCP), and uses the Trivial File Transfer Protocol (TFTP) to download the image or boot file, and constructs a running environment for the image or boot file, so that the diskless client starts up through the image on the server.

[0042] During the diskless startup process, a virtual system disk is virtualized in the IPXE / UEFI stage. All read and write operations on this virtual disk will be redirected to the system image file on the server through the network. The IPXE / UEFI loads and runs the boot program of the system disk. The boot program needs to read the required file resources from the virtual system disk during the boot process. These IO operations will ultimately be redirected to the system image file on the server through the network.

[0043] It can be seen that the startup speed of the diskless client depends on the virtual disk IO rate, and the virtual disk IO rate is most affected by the network rate. In a general gigabit local area network, the network latency is less than 1 ms, and the impact on the startup speed is small; however, in a metropolitan area network, some diskless workstations are far from the computer room where the server is located, the network latency is high, and packet loss may occur, which has a greater impact on the startup speed. It is actually measured that when the network latency is 1 ms - 2 ms, the WIN10 boot stage takes about 10 s longer, and when the network latency is 4 ms, the WIN10 boot stage takes about 34 s longer.

[0044] The core of this application is to provide a startup method, device, and medium for a diskless client, which is used to reduce the impact of network speed on IO speed and improve the startup speed of the diskless client.

[0045] In order to enable those skilled in the art to better understand the solution of this application, the following further detailed description of this application will be given in conjunction with the accompanying drawings and specific implementation manners.

[0046] Figure 1 It is a flowchart of a startup method for a diskless client provided by an embodiment of this application. As Figure 1 shown, this method includes:

[0047] S10: Receive a diskless startup instruction.

[0048] S11: Determine whether there is pre-cached information in the local system; where the pre-cached information includes the ID of the boot mode and image information. If it exists, proceed to step S12.

[0049] In specific implementation, when the same diskless client starts up multiple times, the boot image information and boot mode should be the same. Among them, the boot mode includes UEFI or IPXE. IPXE is an open-source diskless startup technology developed on the basis of PXE. It provides a complete PXE implementation and enhances most functions. UEFI is a personal computer system specification used to define the software interface between the operating system and the system firmware. The Extensible Firmware Interface (EFI) is an upgrade solution launched by Intel Corporation to replace the BIOS in future PC-like computer systems. EFI is responsible for power-on self-test, contacting the operating system, and providing an interface to connect the operating system and hardware, and was later renamed UEFI. There are multiple pieces of image information stored in the server to meet different needs. Therefore, the server will configure its own ID for each piece of image information to distinguish each piece of image information.

[0050] After the diskless client starts up for the first time, it will record the ID of the image information and the boot mode of the diskless client during startup and save them in the local system. When the diskless client starts up subsequently and receives a diskless startup instruction, it directly accesses the database of the local system and obtains the pre-cached information from it.

[0051] S12: Download and save the data corresponding to the pre-cached information from the server according to the pre-cached information.

[0052] In step S12, the diskless client downloads and saves the data corresponding to the pre-cache information from the server according to the pre-cache information. It can be understood that since the pre-cache information includes the boot mode and the ID of the image information, the image information that the diskless client needs to boot can be determined through this information. The image information booted by the diskless client is often not all the image information, and only a part of the image information needs to be booted. Therefore, the data corresponding to the pre-cache information in this embodiment is the data required by the diskless client at startup.

[0053] In a specific implementation, since the data exists in the server, after the task of the diskless client ends, the server will recycle the data for subsequent use. After the diskless client finds the image information according to the pre-cache information, it downloads the data corresponding to the pre-cache information. Since the data booted by the diskless client is the same, when the diskless client starts up subsequently, only according to the pre-cache information, the position where the required data is located on the server's disk can be found, and then the data can be downloaded. This position is the position of each IO request. This position includes the address of the sector where each IO request is located and the length of each IO request. It should be noted that the address of the sector where each IO request is located and the length of each IO request have been recorded and stored in the server when the diskless client starts up for the first time, and there is a corresponding relationship with the pre-cache information. When the diskless client downloads data according to the pre-cache information, it finds this position according to the pre-cache information and downloads the data at this position.

[0054] The startup method of the diskless client provided by the embodiment of the present application includes: after receiving the diskless startup instruction, determining whether there is pre-cache information in the local system; where the pre-cache information includes the boot mode and the ID of the image information; if it exists, downloading and saving the data corresponding to the pre-cache information from the server according to the pre-cache information. Compared with the current technology, when the diskless client starts up each time, an IO request is generated, and then the corresponding image file is obtained from the server. Adopting this technical solution, the pre-cache information is stored in the local system in advance. When starting up disklessly, the relevant data required is directly booted from the server according to the pre-cache information. The server does not need to search for the relevant data according to the IO request anymore, which improves the processing efficiency of the server and reduces the influence of the network rate on the IO rate, thereby improving the startup speed of the diskless client.

[0055] It can be understood that the data of the image information booted by diskless clients with the same configuration is the same. After the diskless client starts up for the first time, the pre-cache information will be stored locally and can be directly used in subsequent use. For other diskless clients with the same configuration, there is no pre-cache information in the local system when starting up for the first time, but the server already stores the relevant records of the data required by the diskless client after the first startup when starting up.

[0056] Therefore, based on the above embodiments, in this embodiment, if there is no pre-cached information in the local system, it further includes:

[0057] Sending a request message to the server to obtain pre-cached information;

[0058] If the pre-cached information is obtained, proceed to the step of downloading and saving the data corresponding to the pre-cached information from the server according to the pre-cached information.

[0059] It can be understood that the request message in this embodiment is for obtaining the pre-cached information of a diskless client with the same configuration as this diskless client. In order to accurately obtain the required pre-cached information, the request message should have a certain identification. The request message may include the boot mode of the diskless client and the ID of the required image information.

[0060] For the startup method of the diskless client provided by the embodiments of the present application, since the image information booted by diskless clients with the same configuration is the same, therefore, if there is no pre-cached information in the local system of the diskless client, a request for pre-cached information is sent to the server, and then data is downloaded according to the pre-cached information, improving the startup speed. By adopting this technical solution, the startup speed of diskless clients with the same configuration in different locations can be improved.

[0061] The image information booted by diskless clients with different configurations is different. When a diskless client starts for the first time, there is no pre-cached information in the local system, and moreover, the server has no relevant records.

[0062] Therefore, based on the above embodiments, in this embodiment, if the pre-cached information is not obtained, it further includes:

[0063] Obtaining the boot mode and the ID of the image information;

[0064] Recording each IO request message generated when booting the image information according to the boot mode and the ID of the image information; the IO request message includes the address and length of the starting sector of each IO request;

[0065] Downloading and saving the corresponding data from the server according to the IO request message.

[0066] It can be understood that in this embodiment, the IO request message is the position described in the above embodiments. The IO request message includes the address and length of the starting sector of each IO request when booting the image information. The client can find the data required for startup through this IO request message.

[0067] The startup method of the diskless client provided by the embodiments of the present application, as a backup technical solution, can still achieve the startup of the client when no pre-cache information is obtained during the first startup of the diskless client.

[0068] In a specific implementation, when the diskless client is started for the first time, the locations of the data required for startup have been recorded on the server. Therefore, in order to improve the subsequent startup speed of this diskless client or other diskless clients with the same configuration as this diskless client, based on the above embodiments, in this embodiment, it further includes:

[0069] Generating and saving pre-cache information composed of the boot mode and the ID of the image information;

[0070] Sending the pre-cache information and the IO request information to the server for saving.

[0071] It can be understood that, for the convenience of the subsequent startup of this diskless client, the pre-cache information is saved in the local system of this diskless client.

[0072] The startup method of the diskless client provided by the embodiments of the present application saves the boot mode and the ID of the booted image information during the first startup of the diskless client in the local system, and sends the pre-cache information and the IO request information to the server for saving. When this diskless client is started again, the data corresponding to the IO request information on the server can be found according to the pre-cache information in the local system, improving the startup speed. Moreover, other diskless clients with the same configuration can also obtain the pre-cache information from the server during the first startup.

[0073] Since some IO requests overlap when processing IO requests, before the step of sending the pre-cache information and the IO request information to the server for saving, it further includes:

[0074] Allocating each IO request information according to the size of the block set in advance;

[0075] Generating index information for each block;

[0076] Further, sending the pre-cache information and the IO request information to the server for saving includes: sending the pre-cache information and the index information to the server for saving.

[0077] In this embodiment, since the IO requests do not cross blocks, the IO request information is saved in units of blocks according to the size of the block set by the user in advance. In this embodiment, 128 sectors can be merged into one block, that is, 64KB.

[0078] The startup method of the diskless client provided by the embodiment of the present application saves IO request information in units of blocks, indirectly processes overlapping IO requests, and continuous IO requests are also merged for processing, reducing the number of IO requests of the client and alleviating the pressure on the server to process IO requests.

[0079] In specific implementation, some sectors will be read repeatedly, resulting in duplication of IO request information and increasing the processing pressure on the server. Therefore, on the basis of the above embodiment, in this embodiment, it further includes:

[0080] Deleting duplicate IO request information.

[0081] The startup method of the diskless client provided by the embodiment of the present application deletes duplicate IO request information, reduces the number of IO requests, and alleviates the processing pressure on the server.

[0082] In specific implementation, the minimum unit of an IO request is a sector, and the default sector size is 512 bytes. There are many short-length IO requests during the boot process. Excessive numbers of IO requests will reduce the startup speed of the diskless client in a high-latency network environment.

[0083] Therefore, on the basis of the above embodiment, in this embodiment, it further includes:

[0084] Merging IO requests whose lengths meet the preset conditions and whose starting sectors are adjacent.

[0085] The startup method of the diskless client provided by the embodiment of the present application merges IO requests whose lengths meet the preset conditions and whose starting sectors are adjacent. This reduces the number of IO requests and improves the startup speed of the diskless client.

[0086] Figure 2 The following is an application effect comparison table of the startup method of the diskless client provided by the embodiment of the present application. As Figure 2 shown, in a network environment with a latency less than 1ms, using the startup method of the diskless client provided by the present application can improve the startup time by 2s. When the latency is 1ms - 2ms, the startup time can be improved by 8s, and when the latency is 4ms, the startup time can be improved by 16s. It can be seen that using the startup method of the diskless client provided by the present application can effectively reduce the impact of the network rate on the startup speed of the diskless client, and the higher the latency, the more obvious the improvement in the startup speed. Moreover, the number of IO requests is significantly reduced, alleviating the processing pressure on the server.

[0087] In the above embodiments, the startup method of the diskless client is described in detail. The present application also provides corresponding embodiments of the startup device for the diskless client. It should be noted that the embodiments of the device part of the present application are described from two perspectives. One is from the perspective of functional modules, and the other is from the perspective of hardware.

[0088] Figure 3 The following is a structural diagram of a startup device for a diskless client provided by an embodiment of the present application. As Figure 3 shown, the device includes:

[0089] A judgment module 10, configured to judge whether there is pre-cached information in the local system after receiving a diskless startup instruction; wherein, the pre-cached information includes the boot mode and the ID of the image information;

[0090] A processing module 11, configured to, if there is pre-cached information, download and save the data corresponding to the pre-cached information from the server according to the pre-cached information.

[0091] The startup device for a diskless client provided by an embodiment of the present application judges whether there is pre-cached information in the local system after receiving a diskless startup instruction; wherein, the pre-cached information includes the boot mode and the ID of the image information; if there is, it downloads and saves the data corresponding to the pre-cached information from the server according to the pre-cached information. Compared with the current technology, each time a diskless client starts up, an IO request is generated, and then the corresponding image file is obtained from the server. By adopting the technical solution of the present application, the pre-cached information is stored in the local system in advance. When starting up disklessly, the relevant data required is directly booted from the server according to the pre-cached information. The server does not need to search for the relevant data according to the IO request anymore, which improves the processing efficiency of the server, reduces the influence of the network rate on the IO rate, and thus improves the startup speed of the diskless client.

[0092] Since the embodiments of the device part correspond to the embodiments of the method part, for the embodiments of the device part, please refer to the description of the embodiments of the method part, which will not be elaborated here for the time being.

[0093] Figure 4 The following is a structural diagram of another startup device for a diskless client provided by an embodiment of the present application. As Figure 4 shown, the device includes: a memory 20, configured to store a computer program;

[0094] A processor 21, configured to implement the steps of the startup method of the diskless client in the above embodiments when executing the computer program.

[0095] The startup device for a diskless client provided in this embodiment may include but is not limited to a smart phone, a tablet computer, a notebook computer, or a desktop computer, etc.

[0096] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the wake state, also known as the central processing unit (CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 21 may be integrated with a graphics processing unit (GPU), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may further include an artificial intelligence (AI) processor, and the AI processor is used to process computational operations related to machine learning.

[0097] The memory 20 may include one or more computer-readable storage media, and the computer-readable storage media may be non-transitory. The memory 20 may further include high-speed random access memory and non-volatile memory, such as one or more disk storage devices and flash storage devices. In this embodiment, the memory 20 is at least used to store the following computer program 201. After the computer program is loaded and executed by the processor 21, it can implement the relevant steps of the startup method of the diskless client disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may further include an operating system 202 and data 203, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, pre-cache information, request information, index information, etc.

[0098] In some embodiments, the startup device of the diskless client may further include a display screen 22, an input / output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.

[0099] Those skilled in the art can understand that Figure 4 the structure shown in

[0100] The startup device of the diskless client provided by the embodiment of the present application includes a memory and a processor. When the processor executes the program stored in the memory, the following method can be implemented: after receiving a diskless startup instruction, it is determined whether there is pre-cached information in the local system. The pre-cached information includes the boot mode and the ID of the image information. If it exists, the data corresponding to the pre-cached information is downloaded and saved from the server according to the pre-cached information.

[0101] The startup device of the diskless client provided by the embodiment of the present application, after receiving a diskless startup instruction, determines whether there is pre-cached information in the local system; the pre-cached information includes the boot mode and the ID of the image information; if it exists, the data corresponding to the pre-cached information is downloaded and saved from the server according to the pre-cached information. Compared with the current technology, each time the diskless client starts up, an IO request is generated, and then the corresponding image file is obtained from the server. With this technical solution, the pre-cached information is stored in the local system in advance. When starting up without a disk, the relevant data required is directly booted from the server according to the pre-cached information. The server does not need to search for the relevant data according to the IO request anymore, which improves the processing efficiency of the server, reduces the impact of the network rate on the IO rate, and thus improves the startup speed of the diskless client.

[0102] Finally, the present application also provides an embodiment corresponding to a computer-readable storage medium. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps recorded in the above method embodiment are implemented.

[0103] It can be understood that if the method in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0104] The computer-readable storage medium provided by the embodiments of the present application, after receiving a diskless boot instruction, determines whether there is pre-cached information in the local system; wherein, the pre-cached information includes the boot mode and the ID of the image information; if it exists, it downloads and saves the data corresponding to the pre-cached information from the server according to the pre-cached information. Compared with the current technology, each time a diskless client starts, it generates an IO request and then obtains the corresponding image file from the server. With this technical solution, the pre-cached information is stored in the local system in advance. When starting up without a disk, the relevant data required is directly booted from the server according to the pre-cached information. The server no longer needs to find the relevant data according to the IO request, which improves the processing efficiency of the server, reduces the impact of the network rate on the IO rate, and thus improves the startup speed of the diskless client.

[0105] The above has introduced in detail the startup method, device and medium of the diskless client provided by the present application. Each embodiment in the specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. The same or similar parts among the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple. For the relevant parts, refer to the description of the method part. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

[0106] It should also be noted that in this specification, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including the said element.

Claims

1. A startup method for a diskless client, characterized in that, Including: After receiving the diskless boot instruction, it is determined whether there is pre-cached information in the local system; wherein, the pre-cached information includes the ID of the boot mode and the image information, and the boot mode includes UEFI or IPXE; the pre-cached information is determined according to the boot mode and the ID of the image information corresponding to the first boot of the diskless client; If it exists, the data corresponding to the pre-cached information is downloaded and saved from the server according to the pre-cached information; If the pre-cached information does not exist in the local system, it further includes: sending a request message to the server to obtain the pre-cached information; If the pre-cached information is obtained, it enters the step of downloading and saving the data corresponding to the pre-cached information from the server according to the pre-cached information; If the pre-cached information is not obtained, it further includes: obtaining the ID of the boot mode and the image information; recording each IO request message generated when guiding the image information according to the ID of the boot mode and the image information; the IO request message includes the address and length of the start sector of each IO request; downloading and saving the corresponding data from the server according to the IO request message.

2. The startup method of the diskless client according to claim 1, characterized in that, It also includes: Generating and saving the pre-cached information composed of the ID of the boot mode and the image information; Sending the pre-cached information and the IO request message to the server for saving.

3. The startup method of the diskless client according to claim 2, characterized in that, Before the step of sending the pre-cached information and the IO request message to the server for saving, it further includes: Allocating each of the IO request messages according to the size of a pre-set block; Generating index information for each of the blocks; Further, the sending the pre-cached information and the IO request message to the server for saving includes: sending the pre-cached information and the index information to the server for saving.

4. The startup method of the diskless client according to claim 3, characterized in that, It also includes: Deleting duplicate IO request messages.

5. The startup method of the diskless client according to claim 1, characterized in that, It also includes: Merging the IO request messages whose lengths meet the preset conditions and whose start sectors are adjacent.

6. A startup device for a diskless client, characterized in that, Including: A judgment module, configured to determine whether there is pre-cached information in the local system after receiving the diskless boot instruction; wherein, the pre-cached information includes the ID of the boot mode and the image information, and the boot mode includes UEFI or IPXE; the pre-cached information is determined according to the boot mode and the ID of the image information corresponding to the first boot of the diskless client; A processing module, configured to, if there is pre-cached information, download and save data corresponding to the pre-cached information from a server according to the pre-cached information; if the pre-cached information does not exist in the local system, further include: sending request information to the server to obtain the pre-cached information; if the pre-cached information is obtained, entering the step of downloading and saving data corresponding to the pre-cached information from the server according to the pre-cached information; if the pre-cached information is not obtained, further include: obtaining IDs of the boot mode and the mirror information; recording each IO request information generated when guiding the mirror information according to the IDs of the boot mode and the mirror information; the IO request information includes addresses and lengths of start sectors of each of the IO requests; downloading and saving corresponding data from the server according to the IO request information.

7. A startup device for a diskless client, characterized in that, It includes a memory for storing a computer program; A processor, configured to implement the steps of the method for starting a diskless client according to any one of claims 1 to 6 when executing the computer program.

8. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method for starting a diskless client according to any one of claims 1 to 6 are implemented.

Images