CN117591136A - Storage image generation method, device, computer equipment and storage medium - Google Patents

Abstract

The invention relates to the technical field of computers, and discloses a storage mirror image generation method, a storage mirror image generation device, computer equipment and a storage medium. The memory image generation method comprises the following steps: acquiring the system type of a target operating system, target version information of a red cap software package manager file, a compiling configuration file and a software package configuration file; analyzing the compiling configuration file to obtain all component codes; based on the system type and the component code, an executable binary program is obtained; generating a red cap software package manager file based on the target version information, the executable binary program, and the software package configuration file; based on the red cap software package manager file, a target IOS image is generated. According to the scheme provided by the embodiment of the invention, the manufacturing efficiency of the IOS mirror image can be improved, and meanwhile, the manual workload can be reduced.

Description

Storage image generation method, device, computer equipment and storage medium

Technical field

The present invention relates to the field of computer technology, and specifically to storage image generation methods, devices, computer equipment and storage media.

Background technique

Among related technologies, Ceph, as a mainstream open source storage system and an important component of OpenStack, is widely used in the cloud computing business of major enterprises. Among them, ceph is an open source storage software, and OpenStack is an open source cloud computing management platform project. . In recent years, with the overall rise of localization, in addition to the original Intel X86 architecture, ceph has also continued to adapt and support various domestic operating systems and domestic processors. Storage manufacturers regularly provide storage systems in the form of IOS (International Organization for Standardization, IOS image) images. However, due to differences in different hardware architectures and operating systems, R&D personnel often need to manually produce ISOs for different operating systems, resulting in the production of IOS images. The efficiency is lower and the manual workload is larger.

Contents of the invention

In view of this, the present invention provides a storage image generation method, device, computer equipment and storage medium, which can improve the production efficiency of IOS images and reduce manual workload.

In a first aspect, the present invention provides a storage image generation method, which method includes:

Obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, where the compilation configuration file includes the component code of each component corresponding to the distributed file storage system, The software package configuration file is used to make the Red Hat software package manager file;

Parse the compiled configuration file to obtain all component codes;

Based on the system type and the component code, obtain an executable binary program;

Generate the Red Hat software package manager file based on the target version information, the executable binary program and the software package configuration file;

Based on the Red Hat package manager file, the target IOS image is generated.

The storage image generation method provided by the embodiment of the present invention obtains the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, and analyzes the compilation configuration file. , obtain all component codes, obtain an executable binary program based on the system type and the component code, and then generate the The Red Hat software package manager file can automatically generate the target IOS image based on the Red Hat package manager file. Therefore, the production efficiency of the IOS image can be improved and the manual workload can be reduced at the same time.

In some optional implementations, generating the Red Hat software package manager file based on the target version information, the executable binary program and the software package configuration file includes:

Obtain initial version information of the Red Hat software package manager file, where the initial version information is determined based on the operation instruction file of the software package configuration file;

Replace the initial version information with the target version information to obtain a replaced software package configuration file;

The Red Hat software package manager file is generated based on the executable binary program and the replaced software package configuration file.

The storage image generation method provided by the embodiment of the present invention obtains the initial version information of the Red Hat software package manager file and replaces the initial version information with the target version information to obtain the replaced software package configuration file, which can be based on the executable binary program and replaced package configuration files to generate the actual Red Hat Package Manager files to be built.

In some optional implementations, generating a target IOS image based on the Red Hat package manager file includes:

Obtain the base directory corresponding to the target operating system, where the base directory is the input directory for generating the target IOS image;

Copy the Red Hat package manager file to the base directory;

The target IOS image is generated in the base directory.

The storage image generation method provided by the embodiment of the present invention can ensure that the generated target is obtained by obtaining the base directory corresponding to the target operating system, copying the Red Hat software package manager file to the base directory, and generating the target IOS image under the base directory. Accuracy of iOS images.

In some optional implementations, generating the target IOS image under the base directory includes:

Create a subdirectory identified by platform or date under the basic directory;

Generate the target IOS image in the subdirectory.

The storage image generation method provided by the embodiment of the present invention can generate a target IOS image in the subdirectory by creating a subdirectory identified by platform or date in the basic directory.

In some optional implementations, obtaining the basic directory corresponding to the target operating system includes:

Obtain the initial International Organization for Standardization files of the target operating system, where the initial International Organization for Standardization files include installation files, system startup boot files and basic management file packages;

The base directory is generated based on the initial International Organization for Standardization file.

The storage image generation method provided by the embodiment of the present invention can generate the target IOS image of the corresponding target operating system based on the basic directory by obtaining the initial ISO file of the target operating system and generating a basic directory based on the initial ISO file.

In some optional implementations, the executable binary program is obtained based on the system type and the component code, including:

Determine target compilation instructions based on the system type and the component code;

The component code is compiled based on the target compilation instruction to obtain an executable binary program.

The storage image generation method provided by the embodiment of the present invention determines the target compilation instruction through the system type and component code, and can compile the component code based on the target compilation instruction to obtain an executable binary program, so that it can be subsequently generated based on the executable binary program. Accurate Red Hat Package Manager documentation.

In some optional implementations, before obtaining the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, the process includes:

Extract the initial IOS image of the target operating system;

Generate the first verification file of the initial IOS image;

Store the first verification file;

The method of obtaining the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file includes:

Generate a second verification file of the target IOS image;

Compare the first verification file and the second verification file to obtain a comparison result;

If the comparison result indicates that the first verification file and the second verification file are inconsistent, re-obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software Package configuration file.

The storage image generation method provided by the embodiment of the present invention generates a first verification file for the initial IOS image and a second verification file for the target IOS image, and compares the first verification file and the second verification file. Able to check the consistency of the target IOS image. If the comparison result indicates that the first verification file and the second verification file are inconsistent, the system type of the target operating system, the target version information of the Red Hat package manager file, and the compilation are re-obtained. Configuration files and software package configuration files to improve the accuracy of the generated target IOS image.

In a second aspect, the present invention provides a storage image generation device, including:

The acquisition module is used to obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, wherein the compilation configuration file includes each corresponding file of the distributed file storage system. The component code of the component, the software package configuration file is used to make the Red Hat software package manager file;

The parsing module is used to parse the compilation configuration file and obtain all component codes;

A program generation module, used to obtain an executable binary program based on the system type and the component code;

A first file generation module, configured to generate the Red Hat software package manager file based on the target version information, the executable binary program and the software package configuration file;

The storage image generation module is used to generate the target IOS image based on the Red Hat package manager file.

In some optional implementations, the first file generation module specifically includes:

The first acquisition sub-module is used to acquire the initial version information of the Red Hat software package manager file, where the initial version information is determined based on the operation instruction file of the software package configuration file;

Replacement submodule, used to replace the initial version information with the target version information to obtain the replaced software package configuration file;

The first file generation submodule is used to generate the Red Hat software package manager file based on the executable binary program and the replaced software package configuration file.

In some optional implementations, the storage image generation module specifically includes:

The second acquisition sub-module is used to acquire the basic directory corresponding to the target operating system, where the basic directory is the input directory for generating the target IOS image;

The copy submodule is used to copy the Red Hat software package manager file to the base directory;

The storage image generation submodule is used to generate the target IOS image in the base directory.

In some optional implementations, the storage image generation submodule specifically includes:

A subdirectory generation unit, used to create a subdirectory identified by platform or date under the basic directory;

A storage image generation unit is configured to generate the target IOS image in the subdirectory.

In some optional implementations, the second acquisition sub-module specifically includes:

An acquisition unit, configured to acquire the initial ISO files of the target operating system, where the initial ISO files include installation files, system startup boot files and basic management file packages;

A basic directory generating unit, configured to generate the basic directory based on the initial International Organization for Standardization file.

In some optional implementations, the program generation module specifically includes:

Instruction determination submodule, used to determine target compilation instructions according to the system type and the component code;

A program generation submodule is used to compile the component code based on the target compilation instruction to obtain an executable binary program.

In some optional implementations, the storage image generation device further includes:

An extraction module, used to extract the initial IOS image of the target operating system;

The second file generation module is used to generate the first verification file of the initial IOS image;

A storage module used to store the first verification file;

The acquisition modules specifically include:

The second file generation submodule is used to generate the second verification file of the target IOS image;

A comparison submodule, used to compare the first verification file and the second verification file to obtain a comparison result;

The third acquisition sub-module is used to re-acquire the system type of the target operating system and the target of the Red Hat software package manager file if the comparison result indicates that the first verification file and the second verification file are inconsistent. Version information, compilation configuration files and package configuration files.

In a third aspect, the present invention provides a computer device, including: a memory and a processor. The memory and the processor are communicatively connected to each other. Computer instructions are stored in the memory, and the processor executes the computer instructions to execute the first aspect. Or the storage image generation method of any corresponding embodiment.

In a fourth aspect, the present invention provides a computer-readable storage medium. Computer instructions are stored on the computer-readable storage medium. The computer instructions are used to cause the computer to execute the storage image of the above-mentioned first aspect or any of its corresponding embodiments. Generate method.

Description of drawings

In order to more clearly explain the specific embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings that need to be used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description The drawings illustrate some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting any creative effort.

Figure 1 is a schematic diagram of an optional implementation environment provided by the embodiment of the present application;

Figure 2 is a flow chart of a storage image generation method according to an embodiment of the present invention;

Figure 3 is a flow chart of another storage image generation method according to an embodiment of the present invention;

Figure 4 is a flow chart of yet another storage image generation method according to an embodiment of the present invention;

Figure 5 is a schematic diagram of a storage image generation device provided by an embodiment of the present application;

Figure 6 is a schematic structural diagram of an optional computer device provided by an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments These are some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts fall within the scope of protection of the present invention.

Referring to Figure 1, Figure 1 is a schematic diagram of an optional implementation environment provided by an embodiment of the present application. The implementation environment includes a server 101.

For example, the server 101 can obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file, and the software package configuration file, where the compilation configuration file includes various configuration files corresponding to the distributed file storage system. The component code and package configuration file of the component are used to make the Red Hat package manager file. Then the compiled configuration file is parsed to obtain all component codes. Based on the system type and component code, an executable binary program is obtained, and then based on The target version information, executable binary program and software package configuration file are used to generate the Red Hat package manager file. Finally, the target IOS image is generated based on the Red Hat package manager file.

The server 101 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or it can provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, Cloud servers for middleware services, domain name services, security services, CDN (Content Delivery Network, content distribution network), and basic cloud computing services such as big data and artificial intelligence platforms. In addition, the server 101 can also be a node server in the blockchain network.

It is worth noting that with the rapid development of information technology, data in all walks of life have experienced explosive growth. As a mainstream open source storage system and an important component of OpenStack, Ceph is widely used in major enterprises. In the cloud computing business, ceph is an open source storage software, and OpenStack is an open source cloud computing management platform project. In recent years, with the overall rise of localization, in addition to the original Intel X86 architecture, ceph has also continued to adapt and support various domestic operating systems and domestic processors. Storage manufacturers regularly provide storage systems in the form of ISOs. However, due to differences in different hardware architectures and operating systems, developers often need to manually compile the corresponding ceph-related codes and software packages for different operating systems and produce ISOs, which leads to the production of IOS images. The efficiency is lower and the manual workload is larger.

Based on this, embodiments of the present invention provide a storage image generation method, device, computer equipment and storage medium, which can improve the production efficiency of IOS images and reduce manual workload.

According to an embodiment of the present invention, an embodiment of a storage image generation method is provided. It should be noted that the steps shown in the flow chart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although A logical order is shown in the flowcharts, but in some cases, the steps shown or described may be performed in a different order than herein.

This embodiment provides a storage image generation method, which can be used in the above-mentioned server. Figure 2 is a flow chart of a storage image generation method according to an embodiment of the present invention. As shown in Figure 2, the process includes the following steps:

Step S201: Obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file, and the software package configuration file.

The target version information refers to the version number of the storage-related Red Hat package manager file contained in the generated target IOS image, such as V2.2.1, where the version number of the target IOS image is related to the storage-related Red Hat software it contains. The version numbers of the package manager files are the same. Therefore, only the target version information of the Red Hat package manager file can be obtained, or the version number of the generated target IOS image can also be obtained. There are no specific restrictions here.

The system type refers to the type of the target operating system used to generate the target IOS image, such as ARM, X86, or Kylin.

For example, the system type of the target operating system and the target version information of the Red Hat package manager file can be passed to the storage image creation program through command line parameters. That is to say, the storage image creation program uses the command line program's In the form of presentation, when you need to create a storage image corresponding to the operating system, run it through the command line program, and pass the system type and target version information to the program through command line parameters. For example, assume that the parameters passed on the command line are create_iso 2.2. 6X86, indicating that you want to create a storage image under the X86 operating system, and its version number is 2.2.6.

The compilation configuration file includes the component code of each component corresponding to the distributed file storage system (ceph), which can be input as subsequent compilation code. For example, if each line specifies a component service in line units, then the compiled configuration file can include the component name, the code warehouse address of each component (such as the git code warehouse address) and the code branch name, with " ="separated as follows:

git@192.168.167.103:project/server1.git=master

git@192.168.167.103:project/server2.git=develop

git@192.168.167.103:project/server3.git=develop server3

Among them, the information before "=" is the code warehouse address of the component, and the information after "=" is the code branch name.

The software package configuration file is used to make the Red Hat Package Manager (RPM) file. The software package configuration file can include SPEC files, corresponding component configuration files, and system service configuration files. Among them, the SPEC file includes the information necessary to create an RPM package, including the files belonging to the RPM package and the folder where the RPM package files are installed under the operating system, the operations that will be performed when installing and uninstalling the RPM package, etc. In addition, when making an RPM package, the executable binary program, corresponding component configuration files, system service configuration files, etc. are organized into corresponding structures and packaged into an RPM file based on the definitions in the SPEC file. The configuration file of the corresponding component is the relevant configuration parameters of the corresponding component, which needs to be loaded at runtime. The system service configuration file usually refers to the configuration file of the systemd (system daemon) service. If the storage component needs to be managed in the form of a systemd service, the corresponding systemd service configuration file needs to be provided.

It should be noted that storage-related components and services are generally included in the storage system ISO image in the form of RPM packages, so each storage-related component needs to be made into RPM form. Based on this, the relevant configuration files for making and storing the RPM packages of each component need to be centrally placed to facilitate subsequent processing.

Step S202: parse the compilation configuration file to obtain all component codes.

The storage image creation program parses the compiled configuration file to pull all component codes. This component includes ceph-related components, management software or other components, which are not listed here.

Step S203: Obtain an executable binary program based on the system type and component code.

Specifically, the storage image creation program uses the compilation tools and compilation instructions of the corresponding target operating system to compile the component code according to the passed system type, and generates an executable binary program.

Step S204: Generate a Red Hat software package manager file based on the target version information, executable binary program and software package configuration file.

The storage image creation program uses the target version information to update the directory where the target IOS image is generated, and generates the Red Hat package manager file in this directory based on the executable binary program and the software package configuration file.

Step S205: Generate the target IOS image based on the Red Hat software package manager file.

The storage image creation program is based on the Red Hat package manager file and can generate the target IOS image by calling the mkisofs command.

The storage image generation method provided by the embodiment of the present invention obtains the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, and analyzes the compilation configuration file to obtain All component codes can obtain executable binary programs based on system type and component code, and then generate Red Hat package manager files based on target version information, executable binary programs and software package configuration files, and based on Red Hat software packages The manager file can automatically generate the target IOS image corresponding to the target operating system. Therefore, it can improve the efficiency of IOS image production and reduce manual workload.

This embodiment provides a storage image generation method, which can be used in the above-mentioned server. Figure 3 is a flow chart of a storage image generation method according to an embodiment of the present invention. As shown in Figure 3, the process includes the following steps:

Step S301: Obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file, and the software package configuration file.

Among them, the compiled configuration file includes the component code of each component corresponding to the distributed file storage system, and the software package configuration file is used to make the Red Hat software package manager file.

For details, please refer to step S201 in the embodiment shown in Figure 2, which will not be described again here.

Step S302: parse the compilation configuration file to obtain all component codes.

Please refer to step S202 in the embodiment shown in Figure 2 for details, which will not be described again here.

Step S303: Obtain an executable binary program based on the system type and component code.

Specifically, the above step S303 specifically includes:

Step S3031: Determine the target compilation instruction according to the system type and component code.

For example, assuming the system type is Cross-compilation instructions.

Step S3032: Compile the component code based on the target compilation instructions to obtain an executable binary program.

In the embodiment of this application, the target compilation instructions are determined through the system type and component code, and the component code can be compiled based on the target compilation instructions to obtain an executable binary program, so that accurate Red Hat can be subsequently generated based on the executable binary program. Package manager files.

Step S304: Generate a Red Hat software package manager file based on the target version information, executable binary program and software package configuration file.

Specifically, the above step S304 specifically includes:

Step S3041: Obtain the initial version information of the Red Hat software package manager file.

The initial version information is determined based on the operation instruction file of the software package configuration file, which is the SPEC file.

Step S3042: Replace the initial version information with the target version information to obtain the replaced software package configuration file.

Specifically, the storage image creation program replaces the target version information with the initial version information of the Red Hat package manager file in the operation instruction file of the software package configuration file. Among them, the initial version information is the default version information, which is inconsistent with the version information actually used to build the Red Hat package manager file. Therefore, the initial version information in the SPEC file needs to be replaced with the target version information.

Step S3043: Generate a Red Hat software package manager file based on the executable binary program and the replaced software package configuration file.

Specifically, after all components are compiled, the storage image creation program will organize the executable binary program corresponding to the component and the replaced software package configuration file in the form of a directory, and the directory name will be the component name + target version information. logo, and finally package the directory into a tar.gz format file with the same name, and call the rpmbuild command to generate the Red Hat package manager file for the corresponding component.

In the embodiment of this application, by obtaining the initial version information of the Red Hat software package manager file and replacing the initial version information with the target version information, the replaced software package configuration file is obtained, which can be based on the executable binary program and the replaced package configuration file to generate the actual Red Hat Package Manager files to be built.

Step S305: Generate the target IOS image based on the Red Hat software package manager file.

Specifically, the above step S305 specifically includes:

Step S3051: Obtain the basic directory corresponding to the target operating system.

Among them, the base directory is the input directory for generating the target IOS image.

Step S3052: Copy the Red Hat software package manager file to the base directory.

In some optional implementations, after copying the Red Hat package manager files to the base directory, the repodata of the base directory can be updated.

Specifically, after the Red Hat Package Manager file packages for all components are generated, the storage image creation program will automatically copy the generated Red Hat Package Manager files to the specified path of the base directory.

Further, createrepo and repo2module will also be called to create repodata and modularmetadata. Among them, repodata is required for subsequent installation and deployment of the system using the built ISO. Related software packages will be automatically installed during installation. Createrepo is a tool for indexing Red Hat package manager files, for example, under the specified path Red Hat package manager files are retrieved, and the information of each Red Hat package manager file is stored in the specified index file. There are no specific restrictions here.

Step S3053: Generate the target IOS image in the base directory.

Since the Red Hat Package Manager file is part of the software package in the target IOS image, the target IOS image needs to be generated in the base directory containing the Red Hat Package Manager file.

In the embodiment of this application, by obtaining the base directory corresponding to the target operating system, copying the Red Hat package manager file to the base directory, and generating the target IOS image under the base directory, the accuracy of the generated target IOS image can be ensured. sex.

In some optional implementations, step S3051 specifically includes:

Step a1: Obtain the initial ISO file of the target operating system.

The initial ISO files include installation files, system startup boot files, basic management file packages, etc. Among them, the installation file is the ks file. The installation file contains some or all installation options for the operating system, such as setting the time zone, how to partition the drive, or the software packages that should be installed. Customized installation files can facilitate users to install without user intervention, which is especially convenient for application scenarios where a large number of operating systems are deployed at the same time. The system startup boot file is the grub file. The grub file contains the relevant configuration of the system boot menu. For example, information related to the operating system manufacturer can be customized and displayed when booting the system installation. The basic management file package is the basic Red Hat Package Manager file.

Step a2: Generate a basic directory based on the initial ISO file.

Among them, the base directory contains various software packages and related files for installing the minimum environment operating system of the corresponding platform.

It should be noted that the target operating system is generally provided externally in ISO format. For example, the target operating system is a storage system, which is essentially a customized operating system that includes storage-related software. First, the corresponding content needs to be extracted from the initial International Organization for Standardization file corresponding to the target operating system, as the base directory for subsequent generation of the target IOS image of the corresponding target operating system.

Taking the target operating system of Copies the contents of the ISO file to the base directory.

Furthermore, you can use the createrepo command to create updated repodata for generating the target IOS image, and customize the installation file and system startup boot file.

In the embodiment of the present application, by obtaining the initial ISO file of the target operating system and generating a basic directory based on the initial ISO file, the target IOS image of the corresponding target operating system can be generated based on the basic directory.

In some optional implementations, step S3053 specifically includes:

Step b1: Create a subdirectory identified by platform or date in the basic directory.

Specifically, the storage image creation program creates a subdirectory identified by platform/date under the specified path of the base directory. This subdirectory is the default storage path used to store the generated target IOS image. This path can be customized in the program.

Step b2, generate the target IOS image in the subdirectory.

Specifically, the storage image creation program switches to a subdirectory, and in the subdirectory, calls the mkisofs instruction to generate a target IOS image corresponding to the target operating system.

In this embodiment of the present application, by creating a subdirectory identified by platform or date under the base directory, the target IOS image can be generated under the subdirectory.

In some optional implementations, before obtaining the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, the initial IOS image of the target operating system can be extracted and generated. The first verification file of the initial IOS image stores the first verification file.

Then after generating the target IOS image, generate a second verification file of the target IOS image, compare the first verification file and the second verification file, and obtain the comparison result. If the comparison result represents the first verification file It is inconsistent with the second verification file, indicating that an error may have occurred during the process of generating the target IOS image. Therefore, you can re-obtain the system type of the target operating system, the target version information of the Red Hat package manager file, the compilation configuration file and the software package. Configuration file to regenerate a new target IOS image.

Among them, the md5sum command is called to generate the second verification file of the target IOS image. Similarly, you can also call the md5sum command to generate the first verification file of the initial IOS image. Among them, the first verification file and the second verification file are both MD5 verification files.

In this embodiment of the present application, by generating a first verification file for the initial IOS image and a second verification file for the target IOS image, and comparing the first verification file and the second verification file, the target IOS can be verified. The image is checked for consistency. If the comparison result indicates that the first verification file and the second verification file are inconsistent, the system type of the target operating system, the target version information of the Red Hat package manager file, the compilation configuration file and the software are re-obtained. Package configuration file to improve the accuracy of the generated target IOS image.

It should be noted that in each of the above embodiments, after the initial configuration of the basic directory, compilation configuration file and software package configuration file is completed, if there are no subsequent changes, there is no need to configure them again.

In some optional implementations, after the target IOS image is generated, a network file system (such as an nfs shared file system) can be mounted on the server that executes the method of the embodiment of this application and the installation test server, and the method of the embodiment of this application is executed. The server stores the target IOS image in the shared file system, then jumps to the installation test server through a script, and directly uses the target IOS image in the shared file system to perform installation testing on the virtual machine. Staff can use the corresponding management platform Check the test results without waiting for the target IOS image to be generated and test manually, thereby completing the generation and testing of the one-time target IOS image and improving the test time.

In order to explain the storage image generation process more clearly, a specific example is used to illustrate below.

Referring to Figure 4, at the beginning, you can obtain the basic directory corresponding to the target operating system corresponding to each platform architecture, and then set the compilation configuration file. The compilation configuration file includes the component code of each component corresponding to the distributed file storage system. The component code can As input for subsequent compiled code. Then, you can create a Red Hat package manager file production directory, store the Red Hat package manager file in this directory, and then pass the command line parameters to set the system type of the target operating system and the Red Hat package manager The target version information of the server file is passed to the storage image creation program. Then, the corresponding component code is automatically pulled from the compiled configuration file, and an executable binary program is obtained based on the system type and component code. Then, obtain the initial version information of the Red Hat package manager file. The initial version information is determined based on the operation instruction file of the software package configuration file. Replace the initial version information with the target version information to obtain the replaced software package configuration file. Based on the executable binary program and the replaced software package configuration file, generate the Red Hat package manager file, copy the generated Red Hat package manager file to the base directory, and update the repodata in the base directory. Finally, call the mkisofs command to generate the target IOS image, and perform consistency verification on the target IOS image, that is, extract the initial IOS image of the target operating system, and generate the first verification file of the initial IOS image and the second verification file of the target IOS image. , compare the first verification file and the second verification file to obtain the comparison result. If the comparison result indicates that the first verification file and the second verification file are inconsistent, re-obtain the system type and red color of the target operating system. Cap the target version information, compilation configuration file and software package configuration file of the software package manager file. In this way, the embodiment of the present application can automatically generate storage images for multiple platform architectures, greatly improving the efficiency and accuracy of making storage images.

Referring to Figure 5, one embodiment of the present application also provides a storage image generation device, including:

The acquisition module 501 is used to obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, where the compilation configuration file includes various components corresponding to the distributed file storage system The component code and package configuration file are used to make the Red Hat package manager file;

The parsing module 502 is used to parse the compilation configuration file and obtain all component codes;

The program generation module 503 is used to obtain an executable binary program based on the system type and component code;

The first file generation module 504 is used to generate the Red Hat software package manager file based on the target version information, executable binary program and software package configuration file;

The storage image generation module 505 is used to generate a target IOS image based on the Red Hat software package manager file.

In some optional implementations, the first file generation module 504 specifically includes:

The first acquisition submodule is used to obtain the initial version information of the Red Hat software package manager file. The initial version information is determined based on the operation instruction file of the software package configuration file;

The replacement submodule is used to replace the initial version information with the target version information and obtain the replaced software package configuration file;

The first file generation submodule is used to generate Red Hat package manager files based on the executable binary program and the replaced software package configuration file.

In some optional implementations, the storage image generation module 505 specifically includes:

The second acquisition sub-module is used to obtain the basic directory corresponding to the target operating system. The basic directory is the input directory for generating the target IOS image;

Copy submodule, used to copy Red Hat package manager files to the base directory;

The storage image generation submodule is used to generate the target IOS image in the base directory.

In some optional implementations, the storage image generation submodule specifically includes:

The subdirectory generation unit is used to create subdirectories identified by platform or date under the basic directory;

The storage image generation unit is used to generate target IOS images in subdirectories.

In some optional implementations, the second acquisition sub-module specifically includes:

The acquisition unit is used to obtain the initial ISO files of the target operating system. The initial ISO files include installation files, system startup boot files and basic management file packages;

The basic directory generation unit is used to generate the basic directory based on the initial ISO file.

In some optional implementations, the program generation module 503 specifically includes:

Instruction determination submodule, used to determine target compilation instructions based on system type and component code;

The program generation submodule is used to compile the component code based on the target compilation instructions to obtain an executable binary program.

In some optional implementations, the storage image generation device further includes:

Extraction module, used to extract the initial IOS image of the target operating system;

The second file generation module is used to generate the first verification file of the initial IOS image;

A storage module used to store the first verification file;

The acquisition module 501 specifically includes:

The second file generation submodule is used to generate the second verification file of the target IOS image;

The comparison submodule is used to compare the first verification file and the second verification file to obtain the comparison result;

The third acquisition sub-module is used to re-obtain the system type of the target operating system, the target version information of the Red Hat package manager file, and the compilation configuration file if the comparison result indicates that the first verification file and the second verification file are inconsistent. and package configuration files.

The storage image generation device in this embodiment is presented in the form of a functional module. The module here refers to an Application Specific Integrated Circuit (ASIC for short), a processor and a memory that executes one or more software or fixed programs. , and/or other devices that can provide the above functions.

Further functional descriptions of the above-mentioned modules and units are the same as those in the above-mentioned corresponding embodiments, and will not be described again here.

An embodiment of the present invention also provides a computer device having the storage image generating device shown in Figure 5 above.

Please refer to Figure 6. Figure 6 is a schematic structural diagram of a computer device provided by an optional embodiment of the present invention. As shown in Figure 6, the computer device includes: one or more processors 10, a memory 20, and a device for connecting The interfaces of each component include high-speed interfaces and low-speed interfaces. Various components communicate with each other using different buses and can be installed on a common motherboard or in other ways as needed. The processor may process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In some alternative implementations, multiple processors and/or multiple buses may be used with multiple memories and multiple memories, if desired. Likewise, multiple computer devices may be connected, each device providing part of the necessary operation (eg, as a server array, a set of blade servers, or a multi-processor system). Figure 6 takes a processor 10 as an example.

The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include a hardware chip. The above-mentioned hardware chip can be an application-specific integrated circuit, a programmable logic device or a combination thereof. The above-mentioned programmable logic device may be a complex programmable logic device, a field programmable logic gate array, a general array logic or any combination thereof.

The memory 20 stores instructions that can be executed by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

The memory 20 may include a stored program area and a stored data area, wherein the stored program area may store an operating system and an application program required for at least one function; the stored data area may store the use of the computer device according to the presentation of a small program landing page. The data created etc. In addition, the memory 20 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some optional implementations, the memory 20 may optionally include memories remotely located relative to the processor 10 , and these remote memories may be connected to the computer device through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.

The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memories.

The computer device also includes a communication interface 30 for the computer device to communicate with other devices or communication networks.

Embodiments of the present invention also provide a computer-readable storage medium. The above-mentioned method according to the embodiment of the present invention can be implemented in hardware or firmware, or can be recorded in a storage medium, or can be implemented as original storage downloaded through the network. Computer code in a remote storage medium or a non-transitory machine-readable storage medium and to be stored in a local storage medium such that the methods described herein may be stored on a computer using a general purpose computer, a special purpose processor, or programmable or special purpose hardware Such software processing on storage media. The storage medium may be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk or a solid state drive, etc.; further, the storage medium may also include a combination of the above types of memories. It can be understood that a computer, processor, microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by the computer, processor or hardware, the above implementations are implemented. The method illustrated.

Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope of the appended rights. within the scope of the requirements.

Claims (10)

1. A storage image generation method, characterized in that the method includes: Obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, where the compilation configuration file includes the component code of each component corresponding to the distributed file storage system, The software package configuration file is used to make the Red Hat software package manager file; Parse the compiled configuration file to obtain all component codes; Based on the system type and the component code, obtain an executable binary program; Generate the Red Hat software package manager file based on the target version information, the executable binary program and the software package configuration file; Based on the Red Hat package manager file, the target IOS image is generated. 2. The method of claim 1, wherein generating the Red Hat software package manager file based on the target version information, the executable binary program and the software package configuration file includes: : Obtain initial version information of the Red Hat software package manager file, where the initial version information is determined based on the operation instruction file of the software package configuration file; Replace the initial version information with the target version information to obtain a replaced software package configuration file; The Red Hat software package manager file is generated based on the executable binary program and the replaced software package configuration file. 3. The method according to claim 1, characterized in that generating a target IOS image based on the Red Hat software package manager file includes: Obtain the base directory corresponding to the target operating system, where the base directory is the input directory for generating the target IOS image; Copy the Red Hat package manager file to the base directory; The target IOS image is generated in the base directory. 4. The method according to claim 3, characterized in that generating the target IOS image under the base directory includes: Create a subdirectory identified by platform or date under the basic directory; Generate the target IOS image in the subdirectory. 5. The method according to claim 3, characterized in that said obtaining the basic directory corresponding to the target operating system includes: Obtain the initial International Organization for Standardization files of the target operating system, where the initial International Organization for Standardization files include installation files, system startup boot files and basic management file packages; The base directory is generated based on the initial International Organization for Standardization file. 6. The method of claim 1, wherein obtaining an executable binary program based on the system type and the component code includes: Determine target compilation instructions based on the system type and the component code; The component code is compiled based on the target compilation instruction to obtain an executable binary program. 7. The method according to claim 1, characterized in that, before obtaining the system type of the target operating system, the target version information of the Red Hat software package manager file, and compiling the configuration file and the software package configuration file, the method includes: Extract the initial IOS image of the target operating system; Generate the first verification file of the initial IOS image; Store the first verification file; The method of obtaining the system type of the target operating system, the target version information of the Red Hat package manager file, the compilation configuration file and the software package configuration file include: Generate a second verification file of the target IOS image; Compare the first verification file and the second verification file to obtain a comparison result; If the comparison result indicates that the first verification file and the second verification file are inconsistent, re-obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, compile the configuration file and software Package configuration file. 8. A storage image generation device, characterized in that it includes: The acquisition module is used to obtain the system type of the target operating system, the target version information of the Red Hat software package manager file, the compilation configuration file and the software package configuration file, wherein the compilation configuration file includes each corresponding file of the distributed file storage system. The component code of the component, the software package configuration file is used to make the Red Hat software package manager file; The parsing module is used to parse the compilation configuration file and obtain all component codes; A program generation module, used to obtain an executable binary program based on the system type and the component code; A first file generation module, configured to generate the Red Hat software package manager file based on the target version information, the executable binary program and the software package configuration file; A storage image generation module is used to generate a target IOS image based on the Red Hat package manager file. 9. A computer device, characterized in that it includes: A memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes any one of claims 1 to 7 by executing the computer instructions. The storage image generation method described. 10. A computer-readable storage medium, characterized in that computer instructions are stored on the computer-readable storage medium, and the computer instructions are used to cause the computer to execute the storage image according to any one of claims 1 to 7 Generate method.