CN117891472A - Bare metal mirror image deployment method, device and medium - Google Patents

Abstract

The application relates to the technical field of mirror image deployment, and discloses a bare metal mirror image deployment method, a device and a medium, which are applied to a bare metal service node, wherein the method comprises the following steps: receiving a first mirror image in a first format sent by a bare metal control node; converting the first image into a second image in a second format; the storage space occupation amount of the first mirror image is smaller than that of the second mirror image; and deploying the second mirror image to the local hard disk. Therefore, the technical scheme provided by the application finishes the format conversion and deployment of the mirror image at the bare metal service node, avoids the situation that more network resources are occupied due to the fact that the bare metal control node converts the first mirror image with smaller storage space occupation into the second mirror image with larger storage space occupation, delays the format conversion and deployment of the mirror image to the bare metal service node, can reduce the network bandwidth occupation, reduces the mirror image transmission time length, and further improves the deployment efficiency of the bare metal mirror image.

Description

A method, device and medium for bare metal image deployment

Technical Field

The present application relates to the technical field of image deployment, and in particular to a method, device and medium for bare metal image deployment.

Background technique

With the continuous development of server virtualization technology, traditional data center services are gradually migrating to the cloud. However, some heavy-load services, such as databases, still need to be deployed on bare metal infrastructure to meet the high performance and low latency requirements of heavy-load services. Bare metal refers to computer hardware without an operating system.

In bare metal system deployment, the operating system image to be deployed is usually installed and produced in advance, and uploaded to the image warehouse in a streamlined qcow2 format. During deployment, the operating system image is first downloaded from the image warehouse to the bare metal server, converted into raw format and released to its local hard disk, thereby completing rapid deployment.

Specifically, there are two implementation methods for bare metal system deployment based on the Openstack Ironic framework. One feasible implementation method is to mount the local disk on the bare metal server to the Ironic control node using the iSCSI protocol, and the Ironic control node downloads the operating system image in qcow2 format from the image repository, converts the operating system image in qcow2 format to raw format, and then copies it to the mounted remote bare metal server hard disk to complete the deployment.

Another feasible implementation method is different from the above-mentioned iSCSI protocol-based operating system image transmission. After the Ironic control node converts the qcow2 format operating system image into the raw format, a proxy service httpserver is started, and the raw format operating system image is remotely requested to be downloaded through the client request tool http client on the bare metal server, and copied to the local hard disk of the bare metal server to complete the deployment.

In the above two implementation methods, during the bare metal system deployment process, the operating system image in qcow2 format needs to be converted into raw format on the Ironic control node before being transferred to the bare metal server. However, the raw operating system image is often large in size, which will occupy a lot of network bandwidth resources during the transmission process, and the transmission time is long, resulting in low deployment efficiency.

It can be seen that how to reduce the network bandwidth resource usage during bare metal deployment and improve deployment efficiency is a technical problem that technical personnel in this field need to solve urgently.

Summary of the invention

In view of this, one aspect of the present application provides a bare metal image deployment method, which is applied to a bare metal service node, and the method includes:

Receiving a first image in a first format sent by a bare metal control node;

Converting the first image into a second image in a second format; wherein the storage space occupied by the first image is less than the storage space occupied by the second image;

Deploy the second image on the local hard disk.

Another aspect of the present application provides a bare metal image deployment method, which is applied to a bare metal control node, and the method includes:

The first image in the first format is sent to the bare metal service node, so that the bare metal service node converts the first image into a second image in the second format and deploys the second image on the local hard disk; wherein the storage space occupied by the first image is less than the storage space occupied by the second image.

Another aspect of the present application provides a bare metal image deployment device, which is applied to a bare metal service node, and the device includes:

A receiving module, configured to receive a first image in a first format sent by a bare metal control node;

A conversion module, used to convert the first image into a second image in a second format; wherein the storage space occupied by the first image is less than the storage space occupied by the second image;

A deployment module is used to deploy the second image on a local hard disk.

Another aspect of the present application provides a bare metal image deployment device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the bare metal image deployment method when executing the program.

Another aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the program is executed by a processor, the steps of the bare metal image deployment method are implemented.

The present application provides a method, device and medium for bare metal image deployment, which completes the format conversion and deployment of the image at the bare metal service node, avoids converting the first image with a smaller storage space occupancy into the second image with a larger storage space occupancy at the bare metal control node, resulting in more network resources being occupied, and delays the image format conversion and deployment to the bare metal service node, which can reduce the network bandwidth occupancy and the image transmission time, thereby improving the deployment efficiency of the bare metal image.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a process of deploying a bare metal image according to an embodiment of the present application;

FIG2 is a block diagram of a bare metal image deployment provided by an embodiment of the present application;

FIG3 is a schematic diagram of the structure of a bare metal image deployment device provided in an embodiment of the present application;

FIG4 is a schematic diagram of the structure of a bare metal image deployment device provided in another embodiment of the present application.

The figure numbers are as follows: 1 is the image repository, 2 is the bare metal control node, 3 is the bare metal service node, 40 is the memory, 41 is the processor, 42 is the display screen, 43 is the input and output interface, 44 is the communication interface, 45 is the power supply, 46 is the communication bus, 401 is the computer program, 402 is the operating system, and 403 is the data.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used in this article refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

During the development of automobiles, it is necessary to verify the performance of the vehicle through a Computer Aided Engineering (CAE) simulation platform, for example, to verify the chassis comfort of the vehicle, and to evaluate the strength, stiffness, fatigue durability, and NVH (noise, vibration, and harshness) characteristics of the vehicle structural components (such as the body, frame, and suspension system) under static loads (such as deadweight) and dynamic loads (such as collisions, road impacts, and torsion). Specifically, when verifying the performance of the vehicle through the CAE simulation platform, it is necessary to install the operating system on the physical server, that is, it is necessary to deploy the operating system image on the bare metal (physical server) in order to implement CAE simulation on the physical server.

When deploying bare metal images, how to reduce the amount of network resources occupied during image transmission and improve the efficiency of image deployment is a crucial research direction. In order to solve the above technical problems, the embodiment of the present application provides a bare metal image deployment method, which delays the image format conversion to the bare metal service node, that is, delays it to the physical machine server, thereby saving network resources and improving the efficiency of image deployment.

FIG1 is a flow chart of a method for bare metal image deployment provided in an embodiment of the present application. As shown in FIG1 , the method includes:

S10: receiving a first image in a first format sent by a bare metal control node;

Figure 2 is a principle block diagram of a bare metal image deployment provided in an embodiment of the present application. As shown in Figure 2, in a specific embodiment, the bare metal control node 2 downloads a first image in a first format from the image repository 1 and sends the first image to the bare metal service node 3.

In some optional embodiments, since images in qcow2 format are easy to archive and distribute, the first format of the first image can be qcow2 format, and of course it can also be images in other formats, which is not limited in this application. It should be noted that the bare metal image deployment method provided in this application can simultaneously deploy images on multiple bare metals.

S11: converting the first image into a second image in a second format; wherein the storage space occupied by the first image is smaller than the storage space occupied by the second image;

Furthermore, after the bare metal service node 3 receives the first image in the first format sent by the bare metal control node 2 through step S10, the bare metal service node 3 converts the first image into a second image in the second format. It can be understood that in order to reduce the excessive network resources occupied by the image during the transmission process, the storage space occupied by the first image is less than the storage space occupied by the second image.

In some optional embodiments, the second image is a raw format image, that is, an image in a format required for the normal operation of the bare metal service node 3. It is understandable that the raw format image occupies a large amount of storage space, for example, a first image in qcow2 format occupying 10 gigabytes (GB) of actual storage space may be marked as a second image in raw format of 100GB, that is, the first image in qcow2 format of 10GB can be converted into a second image in raw format of 100GB.

Therefore, if the bare metal control node 2 converts the first image into the second image and then transmits the second image to the bare metal service node 3 for deployment, more network bandwidth resources will be occupied during the transmission process, which will increase the transmission time. Therefore, the conversion of the first image in qcow2 format into the second image in raw format is completed in the bare metal service node 3, thereby saving network resources.

S12: deploy the second image on the local hard disk.

Furthermore, the second image is deployed to the local hard disk of the bare metal service node 3, thereby completing the bare metal image deployment, saving network resources and storage space by streamlining transmission and delaying conversion.

Therefore, the bare metal image deployment method provided in the embodiment of the present application completes the image format conversion and deployment at the bare metal service node 3, avoiding the conversion of the first image with a smaller storage space occupancy into the second image with a larger storage space occupancy at the bare metal control node 2, which results in occupying more network resources, and delays the image format conversion and deployment to the bare metal service node 3, which can reduce the network bandwidth occupancy and the image transmission time, thereby improving the deployment efficiency of the bare metal image.

In an optional embodiment, the first image is an image compressed by a preset method; wherein the preset method includes a zip compression method. Based on the above embodiment, in order to further reduce the network resources occupied by the first image during the transmission process, the first image is compressed, and specifically, the first format is qcow2 format as an example for explanation.

After bare metal control node 2 downloads the first image in qcow2 format from image repository 1, it zips the first image in qcow2 format and transmits the compressed first image to bare metal service node 3. It is worth noting that the first image obtained by bare metal service node 3 is an image in qcow2 format and is a zip-compressed image.

For example, a 10GB first image in qcow2 format is compressed into a 2GB first image in qcow2 format. This can further save network resources occupied by the bare metal control node 2 when transmitting the first image, improve the transmission rate, and thus improve the bare metal image deployment efficiency.

In fact, the present application does not limit the preset compression method of the first image. Since the zip compression method can compress the image to obtain an image that occupies a smaller storage space, it is preferred to compress it using the zip compression method.

Therefore, before the bare metal control node 2 is ready to distribute and transmit the first image to the bare metal service node 3, the simplified qcow2 format is maintained and compressed, and the dual measures are taken to reduce the transmission disk capacity.

It can be understood that, based on the above embodiment, after the compressed first image is transmitted to the bare metal service node 3, the bare metal service node 3 needs to first decompress the first image and then convert the first image into a second image in a second format.

Specifically, taking the first format as qcow2 format and the second format as raw format as an example, the bare metal control node 2 compresses the 10GB first image in qcow2 format into a 2GB first image in qcow2 format, and then transmits it to the bare metal service node 3. The bare metal service node 3 decompresses the 2GB first image in qcow2 format into a 10GB first image in qcow2 format based on the unzip decompression method.

Furthermore, the 10GB first image in qcow2 format is converted into the second image in raw format by using the qemu-img tool. qemu-img is a command line tool that is part of the QEMU (Quick Emulator) virtualization software suite for emulating processors and is used to create, convert, and manage disk image files.

It is worth noting that in some optional embodiments, the bare metal control node 2 may be an Ironic control node. Ironic is a project in the Open Stack architecture launched by the open source community and is used to manage the bare metal service node 3.

Therefore, the bare metal image deployment method provided in the embodiment of the present application compresses the first image and transmits it to the bare metal service node 3 through the bare metal control node 2, and the bare metal service node 3 completes the decompression and format conversion of the first image, and deploys the second image obtained by the format conversion to the local hard disk, thereby realizing the bare metal image deployment, further saving the image in the transmission process. The amount of network resources occupied by the image can be reduced. In addition, the use of compressed storage can reduce the occupation of local storage space.

In an optional embodiment, in order to further improve the bare metal image deployment efficiency and reduce the storage space occupied, the bare metal image deployment method provided in the embodiment of the present application decompresses the first image, converts the first image into a second image in a second format, and deploys the second image on a local hard disk, including:

For the data in the first image and the second image, the data in the first image is decompressed in sequence in a streaming data processing manner, the decompressed data is converted into the data in the second image, and the data in the second image is deployed on the local hard disk.

It is understandable that if the compressed first image is first decompressed and then stored, and then the decompressed first image is converted into a second image for storage, and finally the second image is deployed on the local hard disk, more storage space will be occupied and the efficiency of image deployment will be low.

Therefore, the technical solution provided in the embodiment of the present application is that when the bare metal service node 3 receives the compressed first image, it decompresses the first image in sequence in a non-landing manner, that is, in a streaming data processing manner, converts the decompressed first image into a second image, and deploys the second image on the local hard disk.

That is to say, the first image is not stored after being decompressed, but is directly converted into a second image in a second format. After the second image is obtained, it is not stored either, but is directly deployed on the local hard disk, thereby reducing the storage space occupied by the bare metal service node 3 and improving the bare metal deployment efficiency.

In some optional embodiments, converting the first image into a second image in a second format includes:

Download the virtual memory disk from the bare metal control node through the PXE boot technology;

The proxy service is started in the virtual memory disk so as to convert the first image into the second image through the proxy service.

In a specific embodiment, when converting the first image into a second image in a second format, a virtual memory disk (ramdisk) can be downloaded from the bare metal control node 2 through a preset network boot technology. In some optional embodiments, the preset network boot technology includes but is not limited to the pxe boot technology.

Furthermore, the bare metal service node 3 starts a proxy service (http server) in the virtual memory disk, and converts the first image into the second image through the proxy service using the qemu-img tool.

In some optional embodiments, the proxy service converts the first image into the second image, including:

Divide storage space of preset size in the virtual memory disk;

In a storage space of a preset size, the first image is converted into a second image.

Specifically, the proxy service http server allocates a storage space of a preset size in the virtual memory disk ramdisk so as to convert the first image into the second image in the storage space. Further, the proxy service http server continuously writes the converted second image data in the second format to the local hard disk in an asynchronous manner, thereby completing the bare metal image deployment.

In the above embodiment, a bare metal image deployment method applied to a bare metal service node is described in detail. The embodiment of the present application also provides an embodiment corresponding to a method for bare metal image deployment applied to a bare metal control node, the method comprising:

The first image in the first format is sent to the bare metal service node, so that the bare metal service node converts the first image into a second image in the second format and deploys the second image on the local hard disk; wherein the storage space occupied by the first image is less than the storage space occupied by the second image.

It can be understood that the deployment method on the bare metal control node side provided in the embodiment of the present application corresponds to the deployment method on the bare metal service node side, and therefore the beneficial effects produced are the same and will not be repeated here.

In the above embodiments, the method for bare metal image deployment applied to bare metal service nodes is described in detail, and the present application also provides an embodiment corresponding to a device for bare metal image deployment applied to bare metal service nodes. It should be noted that the present application describes the embodiments of the device part from two perspectives, one is based on the perspective of functional modules, and the other is based on the perspective of hardware structure.

FIG3 is a schematic diagram of the structure of a bare metal image deployment device provided in an embodiment of the present application. The device is applied to a bare metal service node. As shown in FIG3 , the device includes:

A receiving module 30, configured to receive a first image in a first format sent by a bare metal control node;

A conversion module 31, configured to convert the first image into a second image in a second format; wherein the storage space occupied by the first image is smaller than the storage space occupied by the second image;

The deployment module 32 is used to deploy the second image on the local hard disk.

In addition, the bare metal image deployment device provided in the embodiment of the present application also includes:

The decompression module is used to decompress the first image.

The data processing module is used to decompress the data in the first image and the second image in a streaming data processing manner, convert the decompressed data into data in the second image, and deploy the data in the second image on a local hard disk.

Download module, used to download virtual memory disk from bare metal control node through PXE boot technology;

The startup module is used to start the proxy service in the virtual memory disk so as to convert the first image into the second image through the proxy service.

A partitioning module, used to partition storage space of a preset size in the virtual memory disk;

The conversion module is used to convert the first image into the second image in a storage space of a preset size.

In addition, a method for bare metal image deployment applied to a bare metal control node is described in detail. The present application also provides an embodiment corresponding to a device for bare metal image deployment applied to a bare metal control node, the device comprising: a sending module, specifically, the sending module is used to send a first image in a first format to a bare metal service node, so that the bare metal service node converts the first image into a second image in a second format, and deploys the second image on a local hard disk; wherein the storage space occupied by the first image is less than the storage space occupied by the second image.

For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can refer to the partial description of the method embodiments. The device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present application. A person of ordinary skill in the art can understand and implement it without creative work.

FIG4 is a schematic diagram of the structure of a bare metal image deployment device provided by another embodiment of the present application. As shown in FIG4 , the bare metal image deployment device includes: a memory 40 for storing a computer program;

The processor 41 is used to implement the steps of the bare metal image deployment method mentioned in the above embodiment when executing a computer program.

The bare metal image deployment device provided in this embodiment may include but is not limited to a vehicle controller, a laptop computer, or a desktop computer.

Among them, the processor 41 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 41 can be implemented in at least one hardware form of a digital signal processor (Digital Signal Processor, referred to as DSP), a field programmable gate array (Field-Programmable Gate Array, referred to as FPGA), and a programmable logic array (Programmable Logic Array, referred to as PLA). The processor 41 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a central processing unit (Central Processing Unit, referred to as CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 41 may be integrated with a graphics processing unit (Graphics Processing Unit, referred to as GPU), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 41 may also include an artificial intelligence (Artificial Intelligence, referred to as AI) processor, which is used to process computing operations related to machine learning.

The memory 40 may include one or more computer-readable storage media, which may be non-transitory. The memory 40 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 40 is at least used to store the following computer program 401, wherein, after the computer program is loaded and executed by the processor 41, it can implement the relevant steps of the bare metal image deployment method disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 40 may also include an operating system 402 and data 403, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 402 may include Windows, Unix, Linux, etc. Data 403 may include, but is not limited to, relevant data involved in the bare metal image deployment method, etc.

In some embodiments, the bare metal image deployment device may also include a display screen 42 , an input and output interface 43 , a communication interface 44 , a power supply 45 , and a communication bus 46 .

Those skilled in the art will appreciate that the structure shown in FIG. 4 does not constitute a limitation on the apparatus for bare metal image deployment, and may include more or fewer components than those shown in the figure.

The device for bare metal image deployment provided in an embodiment of the present application includes a memory and a processor. When the processor executes the program stored in the memory, the method for bare metal image deployment in the above embodiment can be implemented.

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 the processor, the steps recorded in the above method embodiment (which may be a method corresponding to a bare metal service node, a method corresponding to a bare metal service node, or a method corresponding to a bare metal service node and a bare metal service node) are implemented.

Although this specification includes many specific implementation details, these should not be interpreted as limiting the scope of any invention or the scope of protection claimed, but are mainly used to describe the features of the specific embodiments of a particular invention. Certain features described in multiple embodiments in this specification may also be implemented in combination in a single embodiment. On the other hand, the various features described in a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although features may work in certain combinations as described above and even initially claimed as such, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may point to a sub-combination or a variation of a sub-combination.

Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the particular order shown or performed sequentially, or requiring that all illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system modules and components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product, or packaged into multiple software products.

Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In some implementations, multitasking and parallel processing may be advantageous.

The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims (10)

1. A bare metal image deployment method, characterized in that it is applied to a bare metal service node, and the method comprises: Receiving a first image in a first format sent by a bare metal control node; Converting the first image into a second image in a second format; wherein the storage space occupied by the first image is less than the storage space occupied by the second image; Deploy the second image on the local hard disk. 2. The method for bare metal image deployment according to claim 1, wherein the first image is an image compressed in a preset manner; wherein the preset manner includes a zip compression manner. 3. The bare metal image deployment method according to claim 2, characterized in that before converting the first image into a second image in a second format, it further comprises: Decompress the first image. 4. The method for deploying a bare metal image according to claim 3, characterized in that the first image is decompressed, the first image is converted into a second image in a second format, and the second image is deployed on a local hard disk, comprising: For the data in the first image and the second image, the data in the first image is decompressed in sequence in a streaming data processing manner, the decompressed data is converted into the data in the second image, and the data in the second image is deployed on the local hard disk. 5. The bare metal image deployment method according to claim 1, wherein converting the first image into a second image in a second format comprises: Downloading a virtual memory disk from the bare metal control node through the pxe boot technology; An agent service is started in the virtual memory disk, so as to convert the first image into the second image through the agent service. 6. The bare metal image deployment method according to claim 5, wherein the proxy service converts the first image into the second image, comprising: Dividing a storage space of a preset size in the virtual memory disk; In the storage space of the preset size, the first image is converted into the second image. 7. A bare metal image deployment method, characterized in that it is applied to a bare metal control node, and the method comprises: The first image in the first format is sent to the bare metal service node, so that the bare metal service node converts the first image into a second image in the second format and deploys the second image on the local hard disk; wherein the storage space occupied by the first image is less than the storage space occupied by the second image. 8. A bare metal image deployment device, characterized in that it is applied to a bare metal service node, and the device comprises: A receiving module, configured to receive a first image in a first format sent by a bare metal control node; A conversion module, used to convert the first image into a second image in a second format; wherein the storage space occupied by the first image is less than the storage space occupied by the second image; A deployment module is used to deploy the second image on a local hard disk. 9. A device for bare metal image deployment, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the bare metal image deployment method described in any one of claims 1 to 7 are implemented. 10. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the steps of the bare metal image deployment method described in any one of claims 1 to 7 are implemented.