Mirror file construction method and mirror file construction apparatus
By acquiring device configuration information and partition data, the target image file in the server is constructed, solving the problems of high storage space and time costs for device image files, and achieving faster and more efficient image file construction.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- HUBEI CENTURY NETWORK TECHNOLOGY CO LTD
- Filing Date
- 2022-09-21
- Publication Date
- 2026-07-21
AI Technical Summary
In existing technologies, device image files occupy a relatively large amount of storage space and have a high time cost in building them.
By obtaining device configuration information, the target image file that can be configured in the server is determined. The device image file is constructed using the device partition format and partition data. Only the target partition data is uploaded to avoid copying the entire disk and reduce the amount of data transferred.
It saves storage space and time costs in building device image files, avoids wasting storage resources, and improves the efficiency of the build process.
Smart Images
Figure CN115543354B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer application technology, and more specifically, to a method for constructing an image file, an apparatus for constructing an image file, and a computer system. Background Technology
[0002] Device image files created for computer devices typically require storage space equivalent to the entire disk capacity of the computer device. Furthermore, the creation process of a device image file requires copying all the data of the computer device into the storage space occupied by the device image file, which is equivalent to the entire disk capacity. This results in high storage space costs and high time costs for creating device image files.
[0003] It is evident that how to save storage space occupied by device image files and the time cost required to build device image files have become technical problems that need to be solved in the existing technology. Summary of the Invention
[0004] In view of this, this application aims to save the storage space occupied by device image files and the time cost required to build device image files.
[0005] One embodiment of this application provides a method for constructing an image file, including:
[0006] Obtain pre-defined device configuration information, wherein the device configuration information includes the total device storage capacity, device partition format, and device partition data, and the device partition data is used to store in a target partition selected among all device partitions set with the device partition format;
[0007] Based on the total storage capacity of the device, a target image file is determined among the configurable image files stored on the server. The storage space occupied by the configurable image file on the server is the same as the actual data volume of the configurable image file. Furthermore, the target image file is any one of the configurable image files whose upper limit of data capacity is adapted to the total storage capacity of the device.
[0008] Using the device partition format and the device partition data, the target image file configured in the server is constructed into a device image file that can be invoked by computer devices.
[0009] Optionally, in some examples, selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device includes: sending an image request carrying the total storage capacity of the device to the server to obtain an image file link provided by the server based on the total storage capacity of the device; and determining the configurable image file corresponding to the image file link as the target image file.
[0010] In some examples, optionally, selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device further includes: if obtaining the image file link from the server fails, sending an image file creation request carrying the total storage capacity of the device to the server; wherein the image file creation request is used to prompt the server to create the configurable image file matching the total storage capacity of the device, and to provide the corresponding image file link after successful creation.
[0011] In some examples, optionally, selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device includes: sending an image request to the server to obtain a list of image file links for configurable image files; selecting an image file link from the list of image file links based on the total storage capacity of the device; and determining the configurable image file corresponding to the selected image file link from the list of image file links as the target image file.
[0012] Optionally, in some examples, selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device further includes: if obtaining the image file link list from the server fails, or if all configurable image files corresponding to the image file links in the obtained image file link list fail to match the total storage capacity of the device, then sending an image file creation request carrying the total storage capacity of the device to the server; wherein, the image file creation request is used to prompt the server to create the configurable image file that matches the total storage capacity of the device, and after successful creation, provide the corresponding image file link.
[0013] Optionally, in some examples, constructing the target image file in the server into a device image file for use by a computer device using the device partition format and the device partition data includes: formatting the target image file according to the device partition format, the formatting being used to match the partition format of the target image file with the device partition format; and copying the device partition data to the mirror partition of the target partition in the target image file.
[0014] Another embodiment of this application provides an image file building apparatus, including a processor, wherein the processor is configured to perform the image file building method as described in the foregoing embodiments.
[0015] Another embodiment of this application provides a non-transitory computer-readable storage medium that stores instructions, which, when executed by a processor, are used to cause the processor to execute the image file construction method as described in the foregoing embodiments.
[0016] Another embodiment of this application provides a computer system including a client and a server, and at least one computer device, wherein the client is configured to execute the image file construction method as described in the foregoing embodiments, and the device image file is invoked by any of the computer devices.
[0017] In some examples, the operating environment of the computer device is optionally configured as a unified extensible firmware interface environment.
[0018] In the embodiments of this application, the server can store configurable image files. Since the storage space occupied by the configurable image file on the server is the same as its actual data volume, even if a device image file is constructed using a configurable image file whose data capacity upper limit matches the total storage capacity of the device, the storage space occupied by the device image file on the server will dynamically fluctuate based on the actual data volume of the device partition data, rather than being a fixed value equal to the total disk capacity represented by the total storage capacity of the device. This avoids the waste of storage resources caused by storage space equal to the total disk capacity. Moreover, the embodiments of this application only need to upload the device partition data in the target partition to the server. Compared with the whole disk data copying method, the embodiments of this application can reduce the amount of data transmission when constructing the device image file, thereby making the process of constructing the device image file faster. Attached Figure Description
[0019] The following figures are for illustrative purposes only and do not limit the scope of this application:
[0020] Figure 1 This is an exemplary flowchart of a method for constructing an image file in one embodiment of this application;
[0021] Figure 2 This is an exemplary structural diagram of a computer system according to another embodiment of this application. Detailed Implementation
[0022] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided with reference to the accompanying drawings and embodiments.
[0023] In the accompanying drawings, the thickness, size, and shape of the objects have been slightly exaggerated for ease of illustration. The drawings are for illustrative purposes only and are not drawn to scale.
[0024] It should also be understood that the terms "comprising," "including," "having," "containing," and / or "comprising," when used in this specification, indicate the presence of the stated features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or combinations thereof. Furthermore, when expressions such as "at least one of..." appear after a list of listed features, they modify the entire listed feature, not individual elements in the list. Additionally, when describing embodiments of this application, the word "may" is used to mean "one or more embodiments of this application." And the term "exemplary" is intended to refer to an example or illustration.
[0025] As used herein, the terms “basically,” “approximately,” and similar terms are used as terms of approximation rather than terms of degree, and are intended to describe inherent biases in measured or calculated values that will be recognized by those skilled in the art.
[0026] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms (e.g., those defined in common dictionaries) shall be interpreted as having the meaning consistent with their meaning in the context of the relevant art and shall not be interpreted in an idealized or overly formal sense unless expressly so specified herein.
[0027] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.
[0028] Figure 1 This is an exemplary flowchart illustrating a method for constructing an image file, as described in one embodiment of this application. Please refer to... Figure 1 In one embodiment of this application, the image file construction method may include:
[0029] S1, obtain the pre-set device configuration information, which includes the total storage capacity of the device, the device partition format, and the device partition data. The device partition data is used to store the device partition data in the target partition set according to the device partition format.
[0030] For example, the device configuration information can be set based on the device attributes of the computer devices in the selected target device set. That is, the total storage capacity, device partition format, and device partition data contained in the device configuration information can be applied to any computer device in the target device set. Furthermore, each computer device in the target device set can be an intranet device deployed in the same local area network or an intranet device deployed in at least two specified local area networks.
[0031] For example, the device partition format in the device configuration information can at least represent the device partition information, such as the number of partitions of the device, the partition format of each partition, the partition capacity of each partition, and which partition among all partitions is selected as the target partition. Furthermore, the total storage capacity of the device contained in the device configuration information can refer to the sum of the partition capacities of all partitions.
[0032] S2, based on the total storage capacity of the device in the device configuration information, determine the target image file among the configurable image files stored on the server. The storage space occupied by the configurable image file on the server is the same as the actual data volume of the configurable image file. Furthermore, the target image file is any configurable image file whose upper limit of data capacity matches the total storage capacity of the device in the device configuration information.
[0033] For example, each configurable image file can be stored on the server in a sparse format. Thus, the storage space occupied by each configurable image file on the server is the same as the actual data volume of the configurable image file. That is, the storage space occupied by each configurable image file on the server changes dynamically in response to changes in its actual data volume, rather than each configurable image file permanently occupying a fixed storage space equal to its data capacity limit.
[0034] Furthermore, for any configurable image file in the server, if its maximum data size matches the total storage capacity of the device in the device configuration information, then the configurable image file can be selected as the target image file.
[0035] For example, the matching described in this application embodiment can be considered as the upper limit of the data capacity of the configurable image file selected as the target image file being greater than the total storage capacity of the device in the device configuration information. That is, the server can store configurable image files with different data capacities, and the upper limit of the data capacity of the configurable image file determined as the target image file should be greater than the total storage capacity of the device in the device configuration information. If there are multiple optional configurable image files with an upper limit of data capacity greater than the total storage capacity of the device in the device configuration information, then one of the multiple optional configurable image files that has an upper limit of data capacity greater than and closest to the total storage capacity of the device in the device configuration information can be selected as the target image file.
[0036] S3 uses the device partition format and device partition data in the device configuration information to configure the target image file in the server, so as to build the target image file in the server into a device image file that can be called by computer devices.
[0037] For example, after the device image file is built, any computer device in the target device set can initiate a communication connection with the server through a broadcast message. The server can respond to the received broadcast message by assigning an IP address to the computer device, so that the computer device can use the assigned IP address to establish a communication connection with the server. Furthermore, the server can associate the IP address assigned to the computer device with the target image file, so that the communication connection between the computer device and the server can be used for the computer device to access the target image file in the server.
[0038] Based on the above process, the server can store configurable image files. Since the storage space occupied by the configurable image file on the server is the same as its actual data volume, even if a device image file is built using a configurable image file whose data capacity upper limit matches the total storage capacity of the device, the storage space occupied by this device image file on the server will dynamically fluctuate based on the actual data volume of the device partition data, rather than being a fixed value equal to the total disk capacity represented by the total storage capacity of the device. This avoids the waste of storage resources caused by storage space equal to the total disk capacity. Moreover, the embodiments of this application only need to upload device partition data to the server. Compared with the method of copying the entire disk data, the embodiments of this application can reduce the amount of data transfer when building the device image file, thereby making the process of building the device image file faster.
[0039] Furthermore, the device image file obtained by the image file construction method described above in this application embodiment can be used as a boot image file or a data image file.
[0040] When a device image file is used as a boot image file, the target partition can be a boot disk partition. The device partition data in the target partition can contain operating system files for booting the computer device. For example, the operating system files can include runtime and boot files for an operating system such as Windows. Furthermore, device image files used as boot image files are applicable to both cases where the computer device is configured as a diskless device and cases where the computer device is configured as a physical disk device, wherein:
[0041] When a computer device is configured as a diskless device with a PXE (Preboot eXecute Environment) network card, the computer device can access the device image file on the server to use the operating system files in the device image file to achieve remote diskless boot.
[0042] For a computer device configured as a physical disk device with a PXE network card and a physical disk, where the target partition on the physical disk is empty or the operating system files in the target partition are waiting to be updated (i.e., the physical disk device has an operating system deployment requirement), the computer device can first access the device image file on the server and use the operating system files in the device image file to boot remotely in a diskless manner. Then, the operating system files in the device image file are copied and downloaded to the target partition of the local disk configured as the boot disk, so that the local operating system files can be used to boot the next time.
[0043] When a device image file is used as a data image file, the target partition can be any partition other than the boot partition of a disk, and the device partition data in the target partition can contain data files of any type. Furthermore, device image files used as data image files are applicable to both diskless devices configured with a PXE network card and physical disk devices configured with a PXE network card and a physical disk, wherein:
[0044] When a computer device is configured as a diskless device with a PXE network card, the computer device can remotely access the file data in the device image file by accessing the device image file on the server.
[0045] When a computer device is configured as a physical disk device with a PXE network card and a physical disk, the computer device can choose to remotely access the file data in the device image file by accessing the server, or it can download the file data in the device image file used as the data image file from the server to the local disk and then perform local access operations.
[0046] Regardless of whether the computer device that calls the device image file is configured as a diskless device with a PXE network card or a physical disk device with a PXE network card and a physical disk, the boot environment of the computer device can be a BIOS (Basic Input Output System), a UEFI (Unified Extensible Firmware Interface) environment, or a boot environment that supports a mixture of the two boot environments (BIOS and UEFI). The specific application to the different systems and boot environments mentioned above can be determined according to the actual situation, and this article will not impose any restrictions on this.
[0047] For different boot environments, the form of partition information represented by the device partition format in the device configuration information obtained in step S1 will also be different.
[0048] For example, booting a UEFI environment requires a separate boot partition in FAT (File Allocation Table) format. In this case, the device partition format in the device configuration information obtained in step S1 includes at least the partition information of the separate boot partition and the partition information of at least one other partition besides the boot partition.
[0049] For example, the startup of the BIOS environment requires obtaining the master boot record located in the first disk sector of the computer device to obtain partition information. In this case, the device partition format in the device configuration information obtained in step S1 may include at least the master boot record of the first sector and the partition information of at least one partition contained in the master boot record.
[0050] For hybrid partition formats that support both BIOS and UEFI boot methods, the device partition format in the device configuration information obtained in step S1 can include both types of partition information.
[0051] In embodiments of this application, the server may pre-create one or more configurable image files with varying maximum data capacities. Alternatively, the configurable image files may be created on the fly in response to a build request for a device image file. It is understood that a configurable image file created on the fly in response to a build request, even if it is subsequently discarded after being built as a device image file (i.e., released after being accessed by a computer device due to disconnection from the server), can still remain on the server. Therefore, for subsequent build requests, the configurable image file previously built as a device image file can also be considered a pre-created configurable image file.
[0052] Regardless of whether the configurable image file in the server is created before the build requirement or created on the spot in response to the build requirement, the process of selecting the target image file in step S2 of the configurable image file can be achieved by sending an image request to the server and obtaining the image file link provided by the server.
[0053] If one or more configurable image files with different upper limits of data capacity are pre-created in the server, the image request can enable the server to provide a link to a pre-created configurable image file. Thus, through step S2, a link to a configurable image file whose upper limit of data capacity matches the total storage capacity of the device in the device configuration information can be obtained, and the configurable image file corresponding to the link can be identified as the target image file.
[0054] For example, a mirroring request can be generated based on device configuration information. That is, the mirroring request can carry at least the total storage capacity of the device as shown in the device configuration information. Accordingly, the mirroring file link provided by the server in response to the mirroring request can be a mirroring file link of a configurable mirroring file selected based on the total storage capacity of the device as shown in the device configuration information. That is, a mirroring file link of any pre-created configurable mirroring file whose data capacity limit matches (e.g., is higher than) the total storage capacity of the device as shown in the device configuration information.
[0055] If obtaining the image file link from the server fails (for example, the failure may be due to the fact that none of the pre-created configurable image files on the server match the total storage capacity of the device in the device configuration information, or because no configurable image files have been created on the server at this time), then step S2 can determine that there is currently no configurable image file on the server that can be used as the target image file. In this case, step S2 may further include:
[0056] Send an image file creation request to the server. This request prompts the server to create a configurable image file that matches the total storage capacity of the device in the device configuration information (i.e., the upper limit of data volume is adapted to the total storage capacity of the device in the device configuration information), and provides a link to the corresponding image file after the configurable image file is successfully created.
[0057] For example, the image file creation request may carry at least the total storage capacity of the device as shown in the device configuration information. Accordingly, the upper limit of the data capacity of the configurable image file created by the server in response to the image file creation request matches (e.g., is higher than) the total storage capacity of the device as shown in the device configuration information.
[0058] Therefore, even if obtaining the image file link fails after sending the image request, step S2 can still obtain the image file link of the configurable image file that matches the total storage capacity of the device in the device configuration information after sending the image file creation request, and the configurable image file corresponding to the image file link is determined as the target image file.
[0059] In a feasible alternative, step S2 can send a mirror request to the server to prompt the server to provide a list of mirror file links for all existing configurable mirror files, so that step S2 can:
[0060] Get a list of image file links for all existing configurable image files on the server;
[0061] Based on the total storage capacity of the device in the device configuration information, select an image file link from the image file link list;
[0062] The configurable image file corresponding to the selected image file link in the image file link list is determined as the target image file that matches the total storage capacity of the device in the device configuration information (e.g., the data volume limit is higher than the total storage capacity of the device in the device configuration information).
[0063] For example, the image file link list can further include the upper limit of the data volume of the configurable image file corresponding to each image file link. Thus, step S2 can select an image file link from the image file link list by comparing the total storage volume of the device in the device configuration information with the upper limit of the data volume of the configurable image file corresponding to each image file link in the image file link list.
[0064] If retrieving the image file link list from the server fails (for example, the failure may be due to the server not having created any configurable image files at this time), or if all configurable image files corresponding to the image file links in the image file link list obtained from the server fail to match the total storage capacity of the device in the device configuration information, then step S2 can determine that there may not be any configurable image files on the server that can be identified as target image files. In this case, step S2 may further include:
[0065] The server sends the aforementioned image file creation request to the server. This request prompts the server to create a configurable image file that matches the total storage capacity of the device in the device configuration information (i.e., the maximum data size is higher than the total storage capacity in the device configuration information), and provides a link to the corresponding image file after the configurable image file is successfully created. For example, the image file creation request may include at least the total storage capacity of the device in the device configuration information. Accordingly, the configurable image file created by the server in response to the image file creation request has a maximum data size that matches (e.g., is higher than) the total storage capacity of the device in the device configuration information.
[0066] Therefore, based on the image file link obtained from the server in step S2, step S3 may further include: establishing an access connection to the target image file, which is used to configure the target image file on the server in step S3, so as to build a device image file that can be called by a computer device on the server. Wherein, such as Figure 1 The execution entity of the image file construction method shown can establish a communication connection with the server before step S2. For example, this communication connection can be any network connection based on communication protocols such as TCP (Transmission Control Protocol) or UDP (User Datagram Protocol). Furthermore, the access connection established in step S3 using the image file link obtained from the server in step S2 can be carried on a network such as... Figure 1 The execution body of the image file construction method shown establishes a communication connection with the server before step S2.
[0067] Specifically, step S3 may include the following steps performed based on the access connection to the target image file:
[0068] The target image file is formatted according to the device partition format in the device configuration information. This formatting process is used to match the partition format of the target image file with the device partition format in the device configuration information, that is, to make the target image file contain the image partitions corresponding to all device partitions set with the device partition format.
[0069] Copy the device partition data that was stored in the target partition to the mirror partition of the target partition in the target image file.
[0070] Furthermore, after completing step S3 to build the device image file, a refresh of all image files stored on the server (including the device image file built in the above embodiment, and other configurable image files stored on the server) can be triggered. Afterwards, as... Figure 1The execution entity of the image file building method shown can disconnect the access connection with the target image file (which has now been built into a device image file), and the communication connection between the execution entity and the server can be maintained or disconnected.
[0071] Accordingly, as mentioned above, any computer device that calls the device image file can also establish a communication connection with the server. For example, this communication connection can be any network connection based on communication protocols such as TCP or UDP, and this communication connection between the computer device and the server can be independent of, for example, Figure 1 The illustrated image file construction method involves a communication connection between the execution entity and the server. Alternatively, the computer device's access to the device image file can also be achieved through an access connection established between the computer device and the device image file by the server. Furthermore, the access connection used by the computer device to access the device image file can be carried within the communication connection between the computer device and the server.
[0072] In the embodiments of this application, the execution entity of the above-described image file building method may be a client, which may include a processor, wherein the processor is configured to execute the image file building method as described in the foregoing embodiments.
[0073] Furthermore, the client may also include a non-transitory computer-readable storage medium that stores instructions that, when executed by a processor, are used to trigger the processor to execute the image file construction method as described in the foregoing embodiments.
[0074] Figure 2 This is an exemplary structural diagram of a computer system according to another embodiment of this application. (Reference) Figure 2 In another embodiment of this application, a computer system may include a client and a server, and at least one computer device with a PXE network card. The client may be configured to execute the image file building method as described in the foregoing embodiments. Furthermore, any one of the at least one computer devices with a PXE network card (e.g., a diskless device or a physical disk device) may invoke the device image file built on the server through an access connection established with the device image file on the server.
[0075] In summary, the server can store configurable image files. Since the storage space occupied by the configurable image file on the server is the same as its actual data volume, even when a device image file is built using a configurable image file whose data capacity upper limit matches the total storage capacity of the device, the storage space occupied by this device image file on the server will dynamically fluctuate based on the actual data volume of the device partition, rather than being a fixed value equal to the total disk capacity represented by the total device storage capacity. This avoids the waste of storage resources caused by storage space equal to the total disk capacity. Moreover, the embodiments of this application only need to upload the partition data in the target partition to the server. Compared with the whole disk data copying method, the embodiments of this application can reduce the amount of data transfer when building the device image file, thereby making the process of building the device image file faster.
[0076] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A method for constructing an image file, characterized in that, include: Obtain pre-defined device configuration information, wherein the device configuration information includes the total device storage capacity, device partition format, and device partition data, and the device partition data is used to store in a target partition selected among all device partitions set with the device partition format; Based on the total storage capacity of the device, a target image file is determined among the configurable image files stored on the server. The storage space occupied by the configurable image file on the server is the same as the actual data volume of the configurable image file. Furthermore, the target image file is any one of the configurable image files whose upper limit of data capacity is adapted to the total storage capacity of the device. Using the device partition format and the device partition data, the target image file configured in the server is constructed into a device image file that can be called by computer devices; The step of determining the target image file in the configurable image files stored on the server based on the total storage capacity of the device includes: Each configurable image file is stored in a sparse format on the server; the storage space occupied by each configurable image file on the server changes dynamically in response to changes in its actual data volume; the server can store configurable image files with different data capacities, and the upper limit of the data capacity of the configurable image file selected as the target image file should be greater than the total storage capacity of the device in the device configuration information; if there are multiple optional configurable image files with an upper limit of data capacity greater than the total storage capacity of the device in the device configuration information, then from the multiple optional configurable image files, the configurable image file with an upper limit of data capacity greater than and closest to the total storage capacity of the device in the device configuration information is selected as the target image file.
2. The image file construction method according to claim 1, characterized in that, The step of selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device includes: Send an image request carrying the total storage capacity of the device to the server to obtain an image file link provided by the server based on the total storage capacity of the device; The configurable image file corresponding to the image file link is determined as the target image file.
3. The image file construction method according to claim 2, characterized in that, The step of selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device further includes: If obtaining the image file link from the server fails, then send an image file creation request carrying the total storage capacity of the device to the server; The image file creation request is used to prompt the server to create a configurable image file that matches the total storage capacity of the device, and to provide a corresponding image file link after successful creation.
4. The image file construction method according to claim 1, characterized in that, The step of selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device includes: Send an image request to the server to obtain a list of image file links that can be configured with image files; Based on the total storage capacity of the device, select an image file link from the image file link list; The configurable image file corresponding to the selected image file link in the image file link list is determined as the target image file.
5. The image file construction method according to claim 4, characterized in that, The step of selecting a target image file from the configurable image files stored on the server based on the total storage capacity of the device further includes: If obtaining the image file link list from the server fails, or if all configurable image files corresponding to the image file links in the obtained image file link list fail to match the total storage capacity of the device, then an image file creation request carrying the total storage capacity of the device is sent to the server. The image file creation request is used to prompt the server to create a configurable image file that matches the total storage capacity of the device, and to provide a corresponding image file link after successful creation.
6. The image file construction method according to claim 1, characterized in that, The step of using the device partition format and the device partition data to construct the target image file in the server into a device image file for use by a computer device includes: The target image file is formatted according to the device partition format, and the formatting process is used to match the partition format of the target image file with the device partition format. The device partition data is copied to the target partition in the target image file.
7. An apparatus for constructing an image file, characterized in that, Includes a processor, wherein the processor is configured to perform the image file construction method as described in any one of claims 1 to 6.
8. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium stores instructions, which, when executed by a processor, are used to cause the processor to perform the image file construction method as described in any one of claims 1 to 6.
9. A computer system, characterized in that, The device includes a client and a server, and at least one computer device, wherein the client is configured to perform the image file construction method as described in any one of claims 1 to 6, and the device image file is invoked by any one of the computer devices.
10. The computer system according to claim 9, characterized in that, The operating environment of the computer device is configured as a unified and scalable firmware interface environment.