Remote boot method, device, storage medium and computer program product of diskless system

Abstract

The present application relates to a diskless computer system, and discloses a remote startup method for a diskless system, including: the server generates a second startup script for the target host online according to an external startup notification, and the second startup script specifies the path of the second system image; the server broadcasts a Wake‑on‑LAN packet to remotely start the target host; after the network card of the target host receives the Wake‑on‑LAN packet, the target host executes a PXE network startup, loads the second system image through the network and starts it; the server resets the startup script of the target host to a first startup script according to an external release notification, and the path of the first system image is specified in the first startup script; the server sends a shutdown command to the second system image to perform a shutdown operation. Through Wake‑on‑LAN and software shutdown, ordinary consumer-grade hosts can realize remote power on / off without purchasing additional hardware, and by generating a second startup script online, an idle host can be started to other workload images, so that the idle host can use idle time to run other workloads, thereby improving the utilization efficiency of idle hosts.

Description

Technical Field

[0001] The present application relates to a diskless computer system, and in particular to a remote startup technology for a diskless system. Background Art

[0002] This section is intended to provide a background or context for the embodiments of the present application as stated in the claims. The contents in this section are for reference only and do not constitute an admission or confirmation that they are prior art that has been disclosed.

[0003] OpenStack Ironic is a sub-project of the OpenStack project, which aims to provide automated management and deployment of bare metal servers. Bare metal servers are physical servers without pre-installed operating systems or virtualization software. They are usually used for workloads with high performance requirements and direct control of hardware resources, such as high-performance computing and big data processing.

[0004] The main goal of the Ironic project is to provide bare metal server management and deployment capabilities for cloud computing environments, allowing users to manage and deploy bare metal servers as easily as virtual machines, improving the utilization and flexibility of bare metal servers. The following are the main features and functions of the Ironic project:

[0005] Hardware management: Ironic provides a set of flexible APIs and tools for managing the hardware resources of bare metal servers, including CPU, memory, disk, network, etc.

[0006] Deployment operations: Ironic supports automated deployment of operating systems and applications on bare metal servers, including operating system installation, image deployment, network configuration, etc.

[0007] Resource Scheduling: Ironic provides resource scheduling and allocation functions, allowing users to dynamically allocate bare metal servers according to demand to meet different workload requirements.

[0008] Scalability: Ironic is a highly scalable project that supports a variety of hardware and deployment configurations and can be easily integrated into various cloud computing environments.

[0009] Open standards: Ironic follows open standards and is compatible with other OpenStack projects and standards. It can be seamlessly integrated with other OpenStack projects and external systems.

[0010] Openstack Ironic uses IPMI (Intelligent Platform Management Interface, a standard interface for remote management of server hardware) to communicate with bare metal servers to perform operations such as power on, power off, and restart. IPMI is usually integrated on the server motherboard, allowing remote management of the server's power, temperature, fan speed, etc. However, in application scenarios such as Internet cafes or e-sports hotels, game consoles are all ordinary consumer-grade motherboards, without server motherboards, and cannot support IPMI or support IPMI requires additional costs (purchase of hardware such as boot sticks, etc.).

[0011] In application scenarios such as Internet cafes or e-sports hotels, a diskless system solution is usually used. That is, the game console has no hard disk and is started from the network after power-on. The network boot image is loaded from the server in the local area network. All game consoles use the same system image, which is generally started manually and can be shut down remotely.

[0012] When the game console is idle, it is impossible to start the console by remote wake-up (because most Internet cafe machines are turned on manually), so that it can use the idle time to run other workloads (because its images are mostly unified game images) and generate revenue.

[0013] Therefore, there is an urgent need for a technical solution that allows the game console to be remotely started and run a specified workload image in a fully automatic manner when idle, and can be remotely shut down and end work when needed. Moreover, after shutting down and then manually restarting the computer, the original Internet cafe image can still be automatically started without affecting the normal operation of the Internet cafe. Summary of the invention

[0014] The purpose of the present application is to provide a remote startup method, device, storage medium and computer program product for a diskless system. Through Wake-on-LAN and software shutdown, ordinary consumer-grade hosts can be remotely turned on / off without purchasing additional hardware, and by generating a second startup script online, idle hosts can be started to other workload images, so that idle hosts can use idle time to run other workloads, thereby improving the utilization efficiency of idle hosts.

[0015] To solve the above technical problems, the embodiment of the present application discloses a remote boot method for a diskless system, wherein the diskless system includes at least one target host, the target host has no hard disk, and is booted through the network after being turned on. The network boot image is loaded from a server in a local area network. The method includes the following steps:

[0016] The server generates a second startup script online for the target host according to the external startup notification, wherein the second startup script specifies a path of the second system image;

[0017] The server broadcasts a Wake-on-LAN packet to remotely power on the target host;

[0018] After the network card of the target host receives the Wake-on-LAN packet, the target host performs PXE network startup, loads the second system image through the network, and starts;

[0019] The server resets the startup script of the target host to a first startup script according to the external release notification, wherein the path of the first system image is specified in the first startup script;

[0020] The server sends a shutdown command to the second system image to execute a shutdown operation.

[0021] In a preferred example, the target host performs PXE network booting, and the step of loading the second system image through the network and booting includes the following sub-steps:

[0022] The target host first loads and runs the level 0 boot firmware located in the network card ROM, then loads and runs the level 1 boot firmware located in the server, and finally runs the second boot script, loads and runs the second system image.

[0023] In a preferred example, the target host first loads and runs the level 0 boot firmware located in the network card ROM, then loads and runs the level 1 boot firmware located in the server, and finally runs the second boot script and loads and runs the second system image, including the following sub-steps:

[0024] The target host first loads and runs the level 0 boot firmware located in the network card ROM, and the level 0 boot firmware requests the level 1 boot firmware from the TFTP service located in the server, and the TFTP service returns the level 1 boot firmware;

[0025] The target host loads and runs the first-level startup firmware, and requests the second startup script from the server, and the server returns the second startup script via the HTTP / S protocol;

[0026] The target host runs the second startup script, loads and runs the second system image.

[0027] In a preferred embodiment, before the step of broadcasting a Wake-on-LAN packet to remotely power on the target host, the server further includes the following steps:

[0028] The first-level boot firmware located on the server is replaced with the first-level boot firmware specified by the second system image.

[0029] In a preferred example, a power management service is prefabricated in the second system image; the server sends a shutdown command to the power management service of the second system image to execute a shutdown operation.

[0030] In a preferred example, the server generates a second startup script for the target host online according to the external startup notification, and the step of specifying the path of the second system image in the second startup script further includes the following sub-steps:

[0031] The server provides an ISCSI storage service for the second system image.

[0032] In a preferred example, the target host is a game host located in an Internet cafe or an e-sports hotel, the first system image is a game image, and the second system image is a workload image, and the workload image includes but is not limited to: a high-performance computing image and a big data processing image.

[0033] The embodiment of the present application further discloses a remote boot device for a diskless system, including:

[0034] a memory for storing computer executable instructions; and,

[0035] A processor, coupled to the memory, is configured to implement the steps in the above method when executing the computer executable instructions.

[0036] The embodiments of the present application further disclose a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions implement the steps in the above method when executed by a processor.

[0037] The embodiments of the present application further disclose a computer program product, including computer executable instructions, which implement the steps in the above method when executed by a processor.

[0038] Compared with the prior art, the main differences and effects of the embodiments of the present application are:

[0039] The implementation mode of the present application can realize remote power on / off of ordinary consumer-grade hosts through Wake-on-LAN and software shutdown without purchasing additional hardware, and can enable idle hosts to boot into other workload images by generating a second startup script online, so that idle hosts can use idle time to run other workloads, thereby improving the utilization efficiency of idle hosts.

[0040] Each technical feature disclosed in the above invention content, each technical feature disclosed in each implementation mode and example below, and each technical feature disclosed in the accompanying drawings can be freely combined with each other to form various new technical solutions (these technical solutions should be deemed to have been recorded in this specification), unless such combination of technical features is technically infeasible. For example, in one example, feature A+B+C is disclosed, and in another example, feature A+B+D+E is disclosed, and features C and D are equivalent technical means that play the same role. Technically, only one of them can be used, and it is impossible to use them at the same time. Feature E can be combined with feature C technically. Then, the solution of A+B+C+D should not be deemed to have been recorded because it is technically infeasible, while the solution of A+B+C+E should be deemed to have been recorded. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a flowchart of a remote startup method of a diskless system according to the first implementation mode of the present application;

[0042] Figure 2 It is a schematic diagram of the overall server architecture of a diskless system according to a preferred embodiment of the first implementation mode of the present application;

[0043] Figure 3 It is a schematic diagram of the workflow of a remote startup method of a diskless system in a preferred embodiment according to the first implementation mode of the present application. DETAILED DESCRIPTION

[0044] In the following description, many technical details are provided to help readers better understand the present application. However, those skilled in the art can understand that the technical solution claimed in the present application can be implemented even without these technical details and various changes and modifications based on the following embodiments.

[0045] Description of some concepts:

[0046] Server: refers to a computer system that can provide services to other devices in the network. The objects served by the server are usually called terminals or clients. The server and the terminal can communicate with each other through wired or wireless means. There are many ways to implement a server. It can be a single computer device or a combination of multiple computer devices (such as cluster servers, cloud servers, etc.). In some application scenarios, the server can also be called a server, cloud, etc.

[0047] Diskless system: refers to a computer system that does not require a local hard drive and usually uses network storage or cloud storage to store and manage data instead of relying on a local hard drive.

[0048] Wake-on-LAN: is a technology for remotely waking up computers. It allows administrators to send specific wake-up signals over the network to wake up the computer when it is turned off or in sleep mode.

[0049] PXE (Preboot Execution Environment) network boot: is a technology used to boot a computer over a network, which allows the computer to load an operating system image and start over the network without the need for a local storage device.

[0050] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0051] A first embodiment of the present application relates to a remote boot method for a diskless system.

[0052] First, it should be noted that the diskless system includes at least one target host, which has no hard disk and is started through the network after being powered on, and the network-started image is loaded from a server in the local area network. In other words, the diskless system includes a server in the local area network and at least one target host.

[0053] Figure 1 It is a flowchart of the remote startup method of the diskless system.

[0054] Specifically, if Figure 1 As shown, the remote boot method of the diskless system includes the following steps:

[0055] In step 101, the server generates a second startup script online for the target host according to an external startup notification, wherein the second startup script specifies a path of a second system image.

[0056] It should be noted that the system image described in this application refers to the abbreviation of the operating system image file, wherein the second system image refers to the operating system image file of other workloads running on the target host during idle time, and the other workloads may include but are not limited to: high-performance computing, big data processing, etc.

[0057] After receiving an external notification through the external interface layer and learning that the target host is available for running services (ie, other workloads), the server first prepares a second startup script required for startup for the target host, wherein the path of the second system image is specified in the second startup script.

[0058] The server generates a second startup script for the target host online. At this time, the second system image (i.e., other workload image) is stored in the server. When the target host is turned on, the second startup script will directly start this image on the target host, so that the target host can start from the network to other workload images and start the "part-time work" of the target host.

[0059] Furthermore, preferably, the above step 101 may also include the following sub-steps:

[0060] The server provides an ISCSI storage service for the second system image, that is, the server has a startup image storage function.

[0061] Then, the process proceeds to step 102, where the server broadcasts a Wake-on-LAN packet to remotely power on the target host.

[0062] In this application, the target host is an ordinary consumer-grade host, which is only equipped with an ordinary consumer-grade motherboard, no server motherboard, and cannot support IPMI.

[0063] The technical solution of the present application is low-cost, and through Wake-on-LAN and software shutdown, an ordinary consumer-grade host (i.e., the target host) can be remotely turned on / off without purchasing additional hardware.

[0064] Then, the process proceeds to step 103. After the network card of the target host receives the Wake-on-LAN packet, the target host performs PXE network booting, loads the second system image through the network, and boots it.

[0065] Further, specifically, the target host executes PXE network boot, loads the second system image through the network and starts, which may include the following sub-steps:

[0066] The target host first loads and runs the level 0 boot firmware located in the network card ROM, then loads and runs the level 1 boot firmware located in the server, and finally runs the second boot script, loads and runs the second system image.

[0067] Furthermore, specifically, the above steps further include the following sub-steps:

[0068] The target host first loads and runs the level 0 boot firmware located in the network card ROM, and the level 0 boot firmware requests the level 1 boot firmware from the TFTP service located in the server, and the TFTP service returns the level 1 boot firmware;

[0069] The target host loads and runs the first-level startup firmware, and requests the second startup script from the server, and the server returns the second startup script via the HTTP / S protocol;

[0070] The target host runs the second startup script, loads and runs the second system image.

[0071] In this implementation, preferably, before the above step 102, the remote startup method of the diskless system may further include the following steps:

[0072] The first-level boot firmware located on the server is replaced with the first-level boot firmware specified by the second system image.

[0073] That is, before the target host is powered on, the original first-level boot firmware located in the server needs to be replaced with the first-level boot firmware specified by the second system image. It should be noted that this step is the initialization step of the remote boot method of the diskless system, which only needs to be executed once and must be executed before the target host is powered on.

[0074] Then, the process proceeds to step 104 , in which the server resets the startup script of the target host to a first startup script according to the external release notification, wherein the path of the first system image is specified in the first startup script.

[0075] After the server receives external notification through the external interface layer and learns that the target host needs to be released, it needs to restore and reset the original startup script of the target host (i.e., the first startup script) so that the target host can boot from the network to its original workload image (for example, the game image) the next time it is turned on, thereby resuming the "main job" of the target host.

[0076] Here, the release reason may include: other workload services have been completed, or the target host is no longer idle and needs to resume executing its original work tasks, etc.

[0077] Then, the process proceeds to step 105 , where the server sends a shutdown command to the second system image to execute a shutdown operation.

[0078] In this implementation, preferably, a power management service is prefabricated in the second system image; the server sends a shutdown command to the power management service of the second system image to perform a shutdown operation.

[0079] In this embodiment, preferably, the target host is a game host located in an Internet cafe or an e-sports hotel, the first system image is a game image, and the second system image is a workload image. The workload image may include but is not limited to: a high-performance computing image and a big data processing image.

[0080] This process ends thereafter.

[0081] To summarize, the technical solution of the present application can enable ordinary consumer-grade hosts to achieve remote power on / off through Wake-on-LAN and software shutdown without purchasing additional hardware, and by generating a second startup script online, idle hosts can be started to mirror other workloads, allowing idle hosts to use idle time to run other workloads, thereby improving the utilization efficiency of idle hosts.

[0082] In order to better understand the technical solution of the present application, a preferred embodiment is described below. The details listed in the preferred embodiment are mainly for ease of understanding and are not intended to limit the scope of protection of the present application.

[0083] Figure 2 is a schematic diagram of the overall server architecture of a diskless system in the preferred embodiment, Figure 3 It is a schematic diagram of the workflow of a remote startup method for a diskless system in the preferred embodiment.

[0084] In this preferred embodiment, the target host is a game console located in an Internet cafe or an e-sports hotel, and the server is an Internet cafe server.

[0085] 1. Overall server architecture

[0086] Specifically, if Figure 2 As shown, the technical solution of the present application adds a power management module and a startup management module on the basis of the original Internet cafe server function.

[0087] a) Power management module:

[0088] i. Remote power on / off module: remotely power on / off the target host within the LAN.

[0089] ii. Host online / offline detection module: monitors host status and obtains online and offline events.

[0090] b) Start the management module:

[0091] i. Online generation of startup script: Generate startup script online based on external notification.

[0092] ii. Startup script HTTP / S service: Provides a startup script based on the target host request ID.

[0093] iii.ISCSI storage service (standard service): provides boot image storage.

[0094] 2. Workflow

[0095] The complete workflow of this preferred embodiment is as follows Figure 3As shown, the following steps are included:

[0096] (1) After the external interface layer receives an external notification that host A is available for running services, the boot management module first prepares the script required for booting for host A (the path of the system image is specified in the script), and then the power management module broadcasts the wake-on-lan packet. After receiving the packet, the network card of host A starts to boot from the network. The first thing loaded and run is the level 0 boot firmware located in the network card ROM. This firmware will request the level 1 boot firmware from the TFTP service located in the original server of the Internet cafe (it is necessary to replace the level 1 firmware of the original Internet cafe server with the level 1 firmware specified by pcboot in advance). After the level 1 boot firmware is loaded and run, it will request the boot script from the boot management module (via the http / s protocol), and then run this script to load and run the system image. The power management service is pre-made in the system image. This service will establish communication with the power management module through websocket and accept commands.

[0097] (2) After the external interface layer receives an external notification that host A needs to be released, the startup management module first resets the startup script of host A so that the next time it is turned on, it can boot from the image of the Internet cafe server to the game image, and then sends a shutdown command to the power management service in the system image to execute the shutdown.

[0098] This preferred embodiment can achieve the following technical effects:

[0099] 1. Through Wake-on-LAN and software shutdown, ordinary consumer-grade hosts can also achieve remote power on / off without purchasing additional hardware, so the cost is low and ordinary consumer-grade computers with motherboards that support Wake-on-LAN can support it.

[0100] 2. By generating startup scripts online, users can dynamically arrange workloads for idle hosts (non-uniform single images), thereby improving the utilization efficiency of idle hosts.

[0101] The second embodiment of the present application relates to a remote boot device for a diskless system, which includes a memory for storing computer executable instructions, and a processor; the processor is used to implement the steps in the above-mentioned method implementation methods when executing the computer executable instructions in the memory. Among them, the processor can be a central processing unit (Central Processing Unit, referred to as "CPU"), a graphic processing unit (Graphic Processing Unit, referred to as "GPU"), a digital signal processor (Digital Signal Processor, referred to as "DSP"), a microcontroller unit (Microcontroller Unit, referred to as "MCU"), a neural network processor (referred to as "NPU"), an application-specific integrated circuit (Application Specific Integrated Circuit, referred to as "ASIC"), a field programmable gate array (Field Programmable Gate Array, referred to as "FPGA") or other programmable logic devices. The aforementioned memory can be a read-only memory (read-only memory, referred to as "ROM"), a random access memory (random access memory, referred to as "RAM"), a flash memory (Flash), a hard disk or a solid-state hard disk, etc. The steps of the method disclosed in each embodiment of the present invention can be directly embodied as a hardware processor to be executed, or a combination of hardware and software modules in the processor to be executed.

[0102] Accordingly, the embodiments of the present application also provide a computer-readable storage medium, in which computer executable instructions are stored, and when the computer executable instructions are executed by the processor, the various method embodiments of the present application are implemented. Computer-readable storage media include permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be a computer-readable instruction, a data structure, a module of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable storage media does not include temporary computer-readable media (transitory media), such as modulated data signals and carriers.

[0103] In addition, an embodiment of the present application further provides a computer program product, which includes computer executable instructions, and when the computer executable instructions are executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0104] It should be noted that, in the present application, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the term "include", "comprise" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of more restrictions, the elements defined by the sentence "include one" do not exclude the existence of other identical elements in the process, method, article or equipment including the elements. In the present application, if it is mentioned that a certain action is performed according to a certain element, it means at least the meaning of performing the action according to the element, which includes two situations: performing the action only according to the element and performing the action according to the element and other elements. Multiple, multiple, multiple, etc. expressions include 2, 2 times, 2 kinds and more than 2, more than 2 times, more than 2 kinds.

[0105] The serial numbers used in describing the steps of the method do not themselves constitute any limitation on the order of these steps. For example, the step with a larger serial number does not necessarily have to be executed after the step with a smaller serial number. The step with a larger serial number may be executed first and then the step with a smaller serial number. They may also be executed in parallel, as long as this execution order is reasonable for those skilled in the art. For another example, multiple steps with consecutive serial numbers (e.g., step 101, step 102, step 103, etc.) do not limit other steps that can be executed in between. For example, there may be other steps between step 101 and step 102.

[0106] This specification includes combinations of the various embodiments described herein. Individual references to embodiments (e.g., "one embodiment" or "some embodiments" or "preferred embodiments"); however, these embodiments are not mutually exclusive unless indicated as mutually exclusive or it is clear to a person skilled in the art that they are mutually exclusive. It should be noted that the word "or" is used in this specification in a non-exclusive sense unless the context clearly indicates or requires otherwise.

[0107] All documents mentioned in this specification are considered to be included in the disclosure of this application as a whole, so that they can be used as a basis for modification when necessary. In addition, it should be understood that the above is only a preferred embodiment of this specification and is not intended to limit the scope of protection of this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of this specification should be included in the scope of protection of one or more embodiments of this specification.

[0108] In some cases, the actions or steps described in the claims may be performed in a different order than in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A remote boot method for a diskless system, wherein the diskless system comprises at least one target host, the target host has no hard disk, and is booted through the network after being turned on, and the network boot image is loaded from a server in a local area network, characterized in that: The method comprises the following steps: The server generates a second startup script online for the target host according to the external startup notification, wherein the second startup script specifies a path of the second system image; The server broadcasts a Wake-on-LAN packet to remotely power on the target host; After the network card of the target host receives the Wake-on-LAN packet, the target host performs PXE network startup, loads the second system image through the network, and starts; The server resets the startup script of the target host to a first startup script according to the external release notification, wherein the path of the first system image is specified in the first startup script; The server sends a shutdown command to the second system image to execute a shutdown operation.

2. The remote boot method of a diskless system as claimed in claim 1, characterized in that: The target host performs PXE network booting, and the step of loading the second system image through the network and booting it includes the following sub-steps: The target host first loads and runs the level 0 boot firmware located in the network card ROM, then loads and runs the level 1 boot firmware located in the server, and finally runs the second boot script, loads and runs the second system image.

3. The remote boot method of a diskless system as claimed in claim 2, characterized in that: The step of the target host first loading and running the level 0 boot firmware located in the network card ROM, then loading and running the level 1 boot firmware located in the server, and finally running the second boot script and loading and running the second system image includes the following sub-steps: The target host first loads and runs the level 0 boot firmware located in the network card ROM, and the level 0 boot firmware requests the level 1 boot firmware from the TFTP service located in the server, and the TFTP service returns the level 1 boot firmware; The target host loads and runs the first-level startup firmware, and requests the second startup script from the server, and the server returns the second startup script via the HTTP / S protocol; The target host runs the second startup script, loads and runs the second system image.

4. The remote boot method of a diskless system as claimed in claim 1, characterized in that: Before the step of the server broadcasting a Wake-on-LAN packet to remotely power on the target host, the server further includes the following steps: The first-level boot firmware located on the server is replaced with the first-level boot firmware specified by the second system image.

5. The remote boot method of a diskless system as claimed in claim 1, characterized in that: A power management service is prefabricated in the second system image; the server sends a shutdown command to the power management service of the second system image to execute a shutdown operation.

6. The remote boot method of a diskless system as claimed in claim 1, characterized in that: The server generates a second startup script for the target host online according to the external startup notification, wherein the step of specifying the path of the second system image in the second startup script further includes the following sub-steps: The server provides an ISCSI storage service for the second system image.

7. The remote boot method of a diskless system as claimed in claim 1, characterized in that: The target host is a game host located in an Internet cafe or an e-sports hotel, the first system image is a game image, and the second system image is a workload image. The workload image includes: a high-performance computing image and a big data processing image.

8. A remote boot device for a diskless system, characterized in that: include: A memory for storing computer executable instructions; as well as, A processor, coupled to the memory, configured to implement the steps of the method according to any one of claims 1 to 7 when executing the computer executable instructions.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps in the method according to any one of claims 1 to 7 are implemented.

10. A computer program product comprising computer executable instructions, characterized in that: When the computer executable instructions are executed by a processor, the steps in the method according to any one of claims 1 to 7 are implemented.

Images