CN114756247B - System deployment method, device, equipment and storage medium - Google Patents
System deployment method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114756247B CN114756247B CN202210332899.1A CN202210332899A CN114756247B CN 114756247 B CN114756247 B CN 114756247B CN 202210332899 A CN202210332899 A CN 202210332899A CN 114756247 B CN114756247 B CN 114756247B
- Authority
- CN
- China
- Prior art keywords
- target
- operating system
- historical configuration
- configuration parameters
- matching
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 230000003213 activating effect Effects 0.000 claims abstract description 18
- 238000012795 verification Methods 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 16
- 238000009434 installation Methods 0.000 claims description 13
- 238000012423 maintenance Methods 0.000 claims description 5
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 238000013075 data extraction Methods 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 4
- 230000006978 adaptation Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000004807 localization Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007123 defense Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a system deployment method, a device, equipment and a storage medium, which relate to the field of batch filling of operating systems and comprise the following steps: the method comprises the steps of connecting with a target client, receiving an input target image file, and determining a target architecture corresponding to the target client based on the target image file; matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameter set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients; and when the matching is successful, activating the target historical configuration parameters, and deploying a corresponding operating system on the target client by using the activated target historical configuration parameters. According to the method and the system, the architecture of the target client is automatically identified, the identified architecture information is matched with the historical configuration parameter set, and the operating systems are installed for the clients with different architectures concurrently, so that the deployment efficiency of the operating systems is improved, and the probability of filling accidents is reduced.
Description
Technical Field
The present invention relates to the field of batch filling of operating systems, and in particular, to a system deployment method, apparatus, device, and storage medium.
Background
In the field of operating system batch filling, PXE (Pre-boot Execution Environment ) and KVM (Keyboard Video Mouse, a virtualization solution) boot installation are the more mainstream operating system boot installation modes. The PXE plays a role in greatly improving efficiency in the scenes of mass production, adaptation, deployment and the like. Based on the existing market conditions and technical inertia, the technical scheme of batch deployment in the PXE mode at present is based on single architecture such as X86 (a computer language instruction set executed by a microprocessor).
Today, processors of multiple architectures such as ARM (ADVANCED RISC MACHINE, advanced simplified instruction set machine)/MIPS (Microprocessor without interlocked PIPED STAGES architecture) exist on the market at the same time, and with the development of information technology and the positive advancement of localization, the whole machine industry based on the ARM/MIPS architecture is in the state of being concurrent with the whole machine product of multiple processor architectures, whether in factory production, laboratory adaptation and customer batch deployment, becomes an unavoidable reality. Therefore, the scheme of batch deployment of the operating systems under the existing single architecture cannot ensure the expandability of deployment, and the deployment efficiency and flexibility are greatly reduced.
Disclosure of Invention
In view of the above, the present invention aims to provide a system deployment method, device, equipment and storage medium, which can automatically identify and distinguish architectures in the same environment, and concurrently install operating systems for different architectures according to identified architecture information. The specific scheme is as follows:
in a first aspect, the present application discloses a system deployment method, applied to a pre-boot execution environment server, comprising:
the method comprises the steps of connecting with a target client, receiving an input target image file, and determining a target architecture corresponding to the target client based on the target image file;
matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients;
And when the matching is successful, activating the target historical configuration parameters so as to deploy a corresponding operating system on the target client by using the activated target historical configuration parameters.
Optionally, before the connection with the target client, the method further includes:
installing a preset operating system, and closing a firewall and SELINUX services after the installation of the preset operating system is completed;
setting authority information so as to create files and directories;
And respectively deploying three services of httpd, dhcpd and tftp on the three servers, and carrying out preset configuration operation on the services after deployment is completed.
Optionally, before the matching of the target historical configuration parameters corresponding to the target architecture from the historical configuration parameter set, the method further includes:
Acquiring mirror image files corresponding to files generated by frameworks of different clients when installing corresponding operating systems;
the decompressed copies of the image files are sent to the catalogues corresponding to the architecture for storage;
Extracting target data in the copy of the mirror image file, and executing preset verification operation after being connected with the client;
And when verification is passed, selecting an operating system corresponding to each target data from a preset product catalog and deploying the operating system on the corresponding client so as to obtain a corresponding historical configuration parameter set after the operating system deployment is completed.
Optionally, the extracting the target data in the copy of the image file, and executing a preset verification operation after connecting with the client, includes:
determining a framework corresponding to the copy of the image file, and extracting a bootstrap guide file in the framework corresponding to the copy and a platform identification code of the framework corresponding to the copy;
Copying the bootstrap guide file to a root directory of the target service, and executing preset verification operation after the bootstrap guide file is connected with the client.
Optionally, after the performing the preset verification operation after the connection with the client, the method further includes:
matching and packaging the bootstrap guide file and the corresponding platform identification code to obtain packaged information;
And storing the packaged information into a preset storage area.
Optionally, the matching, from the historical configuration parameter set, the target historical configuration parameter corresponding to the target architecture includes:
determining a corresponding target operating system based on the target architecture;
and matching the target operating system with the operating system corresponding to the historical configuration parameters in the historical configuration parameter set.
Optionally, the matching the target operating system with the operating system corresponding to the historical configuration parameter in the historical configuration parameter set includes:
if the target operating system cannot be matched with the operating system corresponding to the historical configuration parameters, judging that the matching is failed;
If the system consistent with the target operating system is not matched in the operating system corresponding to the historical configuration parameters, judging that the matching is failed;
if the system consistent with the target operating system is matched in the operating system corresponding to the historical configuration parameters, judging that the matching is successful;
when the matching of the target operating system and the operating system corresponding to the historical configuration parameters fails, corresponding alarm information is generated and sent to a corresponding maintenance terminal.
In a second aspect, the present application discloses a system deployment device, applied to a pre-boot execution environment server, comprising:
the framework determining module is used for being connected with the target client, receiving an input target image file and determining a target framework corresponding to the target client based on the target image file;
The parameter matching module is used for matching the target historical configuration parameters corresponding to the target architecture from the historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients;
And the system deployment module is used for activating the target historical configuration parameters when the matching is successful, so that the corresponding operating system is deployed on the target client by using the activated target historical configuration parameters.
In a third aspect, the present application discloses an electronic device, comprising:
A memory for storing a computer program;
A processor for executing the computer program to implement the steps of the system deployment method as previously disclosed.
In a fourth aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements a system deployment method as previously disclosed.
It can be seen that the present application provides a system deployment method, comprising: the method comprises the steps of connecting with a target client, receiving an input target image file, and determining a target architecture corresponding to the target client based on the target image file; matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients; and when the matching is successful, activating the target historical configuration parameters so as to deploy a corresponding operating system on the target client by using the activated target historical configuration parameters. Therefore, after the client is connected with the client, the architecture corresponding to the client is judged through the received image file, then the historical configuration parameters corresponding to the architecture are matched from the historical configuration parameter set, so that the automatic judgment of the client architecture is realized, the matched historical configuration parameters are parameters of an operating system corresponding to the architecture installed on the client, the corresponding operating system is deployed on the target client by activating the historical configuration parameters, the deployment expandability is improved, the deployment efficiency and the flexibility are improved, and the probability of filling accidents is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a system deployment method disclosed by the application;
FIG. 2 is a flowchart of a specific system deployment method disclosed in the present application;
FIG. 3 is a flowchart of a specific system deployment method disclosed in the present application;
FIG. 4 is a flowchart of a specific system deployment method disclosed herein;
FIG. 5 is a flowchart of a specific system deployment method disclosed herein;
FIG. 6 is a schematic diagram of a system deployment device according to the present application;
Fig. 7 is a block diagram of an electronic device according to the present application.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
At present, processors with multiple architectures such as ARM/MIPS exist on the market at the same time under the condition of large development of the processors, and along with the development of information technology and the positive promotion of localization, the whole machine industry based on the ARM/MIPS architecture is in full play, and the current situation that the whole machine products with multiple processor architectures coexist is unavoidable to be realized no matter factory production, laboratory adaptation and client batch deployment. Therefore, the scheme of batch deployment of the operating systems under the existing single architecture cannot ensure the expandability of deployment, and the deployment efficiency and flexibility are greatly reduced. Therefore, the application provides a system deployment method, which can improve the expandability, the deployment efficiency and the flexibility of deployment and reduce the probability of filling accidents.
The embodiment of the invention discloses a system deployment method, which is shown in fig. 1 and is applied to a pre-start execution environment server, and the method comprises the following steps:
Step S11: and the target framework corresponding to the target client is determined based on the target image file.
In this embodiment, the target architecture corresponding to the target client is determined based on the target image file. Before connecting with a target client, PXE and an unattended environment are built so as to have basic conditions of batch filling. And simultaneously constructing the same local area network, and selecting and installing a preset operating system for the pre-starting execution environment server. After the installation of the preset operating system is completed, a firewall and SELINUX (Security-Enhanced Linux, preamble Security Enhanced Linux) services of the pre-boot execution environment server are closed, and corresponding permission information (umask) is set to prevent the permission from being insufficient when files and directories are created. Finally, three services, namely httpd (hypertext transfer Protocol), dhcpd (Dynamic Host Configuration Protocol ) and tftp (TRIVIAL FILE TRANSFER Protocol, simple file transfer Protocol), are deployed on the three servers respectively, and preset configuration operation is carried out on the services after deployment is completed. It can be understood that the httpd, dhcpd and tftp services are deployed on the three servers respectively, so that the three services are not disturbed by each other, for example, when one service goes wrong, the other two services are not affected, and therefore, the security of the data is improved. It should be noted that the pre-boot execution environment server selects a full mount when installing a pre-set operating system, and may use a full set of components when deployed.
Step S12: matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameter set comprises history configuration parameters obtained by the architectures of different clients after corresponding operating systems are installed.
In this embodiment, the target historical configuration parameters corresponding to the target architecture are matched from the historical configuration parameter set. It can be understood that matching the target historical configuration parameters corresponding to the target architecture from the historical configuration parameter set has two results of matching success and matching failure. And when the matching is successful, activating the target historical configuration parameters to complete the deployment of the corresponding operating system. And ending deployment generation and sending alarm information to the corresponding maintenance terminal when the matching fails. It should be noted that each of the historical configuration parameters in the set of historical configuration parameters corresponds to an operating system.
Step S13: and when the matching is successful, activating the target historical configuration parameters so as to deploy a corresponding operating system on the target client by using the activated target historical configuration parameters.
In this embodiment, after the history configuration parameters are matched to the target history configuration parameters corresponding to the target architecture from the history configuration parameter set, the corresponding operating system is deployed on the target client by using the activated target history configuration parameters. It can be understood that, by matching the target historical configuration parameters corresponding to the target architecture from the historical configuration parameter set, whether the historical configuration parameters of the operating system corresponding to the target architecture exist or not is judged, if so, the fact that the operating system corresponding to the architecture is deployed once is indicated, and the operating system corresponding to the architecture can be deployed directly by utilizing the historical configuration parameters obtained after the deployment is completed, that is, the operating system corresponding to the architecture enters a preset installation branch according to the identified architecture, and the batch deployment of the corresponding operating systems is performed.
It can be seen that the present application provides a system deployment method, comprising: the method comprises the steps of connecting with a target client, receiving an input target image file, and determining a target architecture corresponding to the target client based on the target image file; matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients; and when the matching is successful, activating the target historical configuration parameters so as to deploy a corresponding operating system on the target client by using the activated target historical configuration parameters. Therefore, after the client is connected with the client, the architecture corresponding to the client is judged through the received image file, then the historical configuration parameters corresponding to the architecture are matched from the historical configuration parameter set, so that the automatic judgment of the client architecture is realized, the matched historical configuration parameters are parameters of an operating system corresponding to the architecture installed on the client, the corresponding operating system is deployed on the target client by activating the historical configuration parameters, the deployment expandability is improved, the deployment efficiency and the flexibility are improved, and the probability of filling accidents is reduced.
Referring to fig. 2, an embodiment of the present invention discloses a system deployment method, and compared with the previous embodiment, the present embodiment further describes and optimizes a technical solution.
Step S21: and the target framework corresponding to the target client is determined based on the target image file.
Step S22: and acquiring image files corresponding to the files generated by the frameworks of different clients when the corresponding operating systems are installed.
In this embodiment, image files corresponding to files generated by architectures of different clients when installing corresponding operating systems are obtained. It can be understood that the clients with different architectures respectively install and deploy the operating systems corresponding to the architectures, and then acquire the image files corresponding to the files with different architectures so as to analyze the image files to acquire the target data of the corresponding operating systems. It should be noted that the architectures of the different clients include, but are not limited to, X86 architecture, ARM architecture, MIPS architecture, power architecture, alpha architecture, and are equally applicable to other architectures, and the operating system may be any operating system, such as a kylin operating system.
Step S23: and sending the decompressed copy of the image file to a directory corresponding to the architecture for storage.
In this embodiment, after acquiring image files corresponding to files generated by architectures of different clients when installing corresponding operating systems, a pre-boot execution environment server decompresses the image files, and then copies the decompressed image files to obtain copies of the corresponding image files. It can be understood that the mirror image directories corresponding to different architectures are set in the pre-boot execution environment server, and copies of the mirror image files corresponding to different architectures are stored in the mirror image directories of different architectures.
Step S24: and extracting target data in the copy of the mirror image file, and executing preset verification operation after the target data is connected with the client.
In this embodiment, after the decompressed copy of the image file is sent to the directory corresponding to the architecture for saving, the target data in the copy of the image file is extracted, and after the client is connected, a preset verification operation is performed. It can be understood that determining the architecture corresponding to the copy of the image file, and extracting the bootstrap guide file in the architecture corresponding to the copy and the platform identification code of the architecture corresponding to the copy; copying the bootstrap guide file to a root directory of a target service of the pre-start execution environment server, and executing preset verification operation after the bootstrap guide file is connected with a client. For example, platform identification codes corresponding to the X86 architecture, the ARM architecture and the MIPS architecture are A1, A2 and A3, the bootstrap guide file is copied to a root directory of the dhcp service of the pre-boot execution environment server, and corresponding verification operation is performed. For example, as shown in fig. 3, when an image file P0 is received, target data in the image file P0 is extracted, when the image file P0 is in an X86 architecture, a Bootstrap and a platform identification code A1 of the X86 architecture are extracted, when the image file P0 is in an ARM architecture, a Bootstrap and a platform identification code A2 of the ARM architecture are extracted, and when the image file P0 is in a MIPS architecture, a Bootstrap and a platform identification code A3 of the MIPS architecture are extracted, so that corresponding operating systems are deployed in parallel and in batches based on different bootstraps and platform identification codes.
It can be understood that after extracting the bootstrap guide file in the architecture corresponding to the copy and the platform identification code of the architecture corresponding to the copy, matching and packaging the bootstrap guide file and the corresponding platform identification code to form an architecture identification matching module, and storing the obtained packaged information in a preset storage area. It should be noted that, matching and packaging the bootstrap guide file and the corresponding platform identification code, that is, when any one of the bootstrap guide file and the platform identification code is obtained, another item and the corresponding architecture can be determined according to the corresponding relation of matching and packaging. In addition, a call API (Application Program Interface ) interface is reserved for the architecture identification matching module.
Step S25: and when verification is passed, selecting an operating system corresponding to each target data from a preset product catalog and deploying the operating system on the corresponding client so as to obtain a corresponding historical configuration parameter set after the operating system deployment is completed.
In this embodiment, when verification is passed, an operating system corresponding to each target data is selected from a preset product catalog, and the operating system is deployed on the corresponding client, so as to obtain a corresponding historical configuration parameter set after the operating system deployment is completed. It can be understood that firstly, operating system products in a demand library are combed to obtain a preset product catalog, then, corresponding operating systems are installed and deployed on clients of different architectures according to the extracted target data to obtain historical configuration parameters of each architecture after the corresponding operating systems are installed and deployed, so that a historical configuration parameter set of all operating systems installed in the demand library is obtained, and the historical configuration parameter set is stored. In addition, a call API interface is reserved for the historical configuration parameter set. It should be noted that the API interface that calls the historical configuration parameter set is a different interface than the API interface that calls the architecture identification matching module.
Step S26: matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameter set comprises history configuration parameters obtained by the architectures of different clients after corresponding operating systems are installed.
Step S27: and when the matching is successful, activating the target historical configuration parameters so as to deploy a corresponding operating system on the target client by using the activated target historical configuration parameters.
For the specific content of the steps S21, S26, S27, reference may be made to the corresponding content disclosed in the foregoing embodiment, and no further description is given here.
It can be seen that, in the embodiment of the present application, by obtaining image files corresponding to files generated when corresponding operating systems are installed by architectures of different clients, extracting target data in copies of the image files, performing a preset verification operation after connecting with the clients, selecting an operating system corresponding to each target data from a preset product catalog when verification passes, deploying the operating system on the corresponding client, obtaining a corresponding historical configuration parameter set after the operating system deployment is completed, matching a target historical configuration parameter corresponding to the target architecture from the historical configuration parameter set, and activating the target historical configuration parameter to deploy the corresponding operating system on the target client when matching is successful, thereby achieving the purpose of deploying the operating system across processor architectures automatically and concurrently, improving deployment expandability, deployment efficiency and flexibility, and reducing the probability of filling accidents.
Referring to fig. 4, an embodiment of the present invention discloses a system deployment method, and compared with the previous embodiment, the present embodiment further describes and optimizes a technical solution.
Step S31: and the target framework corresponding to the target client is determined based on the target image file.
Step S32: and determining a corresponding target operating system based on the target architecture.
In this embodiment, after determining the target architecture corresponding to the target client, determining a target operating system corresponding to the target architecture according to an actual situation, where the target operating system is an operating system to be installed.
Step S33: and matching the target operating system with the operating system corresponding to the historical configuration parameters in the historical configuration parameter set.
In this embodiment, the target operating system is matched with an operating system corresponding to the historical configuration parameter in the historical configuration parameter set. If the target operating system cannot be matched with the operating system corresponding to the historical configuration parameters, judging that the matching is failed; if the system consistent with the target operating system is not matched in the operating system corresponding to the historical configuration parameters, judging that the matching is failed; when the matching of the target operating system and the operating system corresponding to the historical configuration parameters fails, corresponding alarm information is generated and sent to corresponding maintenance unit related personnel. It can be understood that if the target operating system cannot be matched with the operating system corresponding to the historical configuration parameter, it is required to confirm whether the corresponding operating system exists in a preset product catalog in the requirement library and generate the corresponding historical configuration parameter, and meanwhile, troubleshooting problems such as a response path and file authority are required, if the corresponding historical configuration parameter can be matched after the troubleshooting is finished, the step of activating the target historical configuration parameter is performed, and the activated target historical configuration parameter is utilized to deploy the corresponding operating system on the target client. If the corresponding historical configuration parameters still cannot be matched after the investigation is finished, ending the operating system deployment step. If the system consistent with the target operating system is not matched in the operating system corresponding to the historical configuration parameters, after confirming that the architecture does not have the corresponding input operating system, the installation of the architecture is terminated, and the step is to confirm a defense line at the last time of production and deployment, so as to prevent filling accidents. It should be noted that, since the repository is a dynamically changing operating system image pool, there will always be a situation where the historical configuration parameters of a particular operating system installation are missing, for example, some operating system of the MIPS architecture does not exist.
Step S34: and if the system consistent with the target operating system is matched in the operating system corresponding to the historical configuration parameters, judging that the matching is successful and obtaining the target historical configuration parameters.
In this embodiment, if a system consistent with the target operating system is matched in the operating systems corresponding to the historical configuration parameters, it indicates that a corresponding operating system exists on a preset product catalog in the demand library and generates a corresponding historical configuration parameter, and the matching is determined to be successful, and the matched historical configuration parameter is determined to be the target historical configuration parameter.
Step S35: and when the matching is successful, activating the target historical configuration parameters so as to deploy a corresponding operating system on the target client by using the activated target historical configuration parameters.
In this embodiment, when the matching is successful, the target historical configuration parameter is activated, a predetermined installation branch is entered according to the identified architecture, and the activated target historical configuration parameter is used to concurrently perform batch deployment of the corresponding operating systems on the target client.
Specifically, for example, as shown in fig. 5, a complete machine product of an X86 architecture/ARM architecture/MIPS architecture is accessed to a PXE server, an image file P0 is received, a history configuration parameter set K1 of an operating system and packaged information in an architecture identification module are called by an input control module, a target history configuration parameter of a target architecture corresponding to the image file P0 is matched from the history configuration parameter set, when a target history configuration parameter of the target architecture corresponding to the image file P0 exists in the history configuration parameter set, that is, p0=k, a corresponding operating system is deployed on the target client by using the activated target history configuration parameter, the history configuration parameter of P0 is called to a specific directory of the PXE server from a memory, and the operating system corresponding to the history configuration parameter installation deployment of P0 is activated. When the matching fails, namely P0 is not equal to K, error reporting information is output through an output module, meanwhile, the reason of the matching failure is judged, when the reason of the failure is 1, namely the target operating system cannot be matched with the operating system corresponding to the historical configuration parameters, whether the corresponding operating system exists on a preset product catalog in a demand library or not needs to be confirmed, the corresponding historical configuration parameters are generated, meanwhile, problems of a response path, file authority and the like are checked, if the corresponding historical configuration parameters can be matched after the checking is finished, the target historical configuration parameters are activated, and the step of deploying the corresponding operating system on the target client by utilizing the activated target historical configuration parameters is carried out; when the failure cause is the cause 2, that is, if the operating system corresponding to the historical configuration parameter is not matched with the system consistent with the target operating system, the installation of the architecture is terminated after confirming that the architecture does not have the corresponding input operating system.
For the specific content of the above step S31, reference may be made to the corresponding content disclosed in the foregoing embodiment, and no detailed description is given here.
Therefore, the embodiment of the application can automatically identify and distinguish the whole machine products with different frameworks in the same environment, carries out corresponding logic judgment processing according to the identified information, determines the corresponding target operating system based on the target framework, matches the target operating system with the operating system corresponding to the historical configuration parameters in the historical configuration parameter set, carries out corresponding operation according to failure reasons when the matching fails, activates the target historical configuration parameters when the matching is successful, and utilizes the activated target historical configuration parameters to concurrently install and deploy the corresponding operating systems for the whole machine products with different frameworks, thereby improving the expandability of deployment, the deployment efficiency and the flexibility and reducing the probability of filling accidents.
Referring to fig. 6, the embodiment of the application also correspondingly discloses a system deployment device, which is applied to a pre-start execution environment server and comprises:
the architecture determining module 11 is configured to connect with a target client, receive an input target image file, and determine a target architecture corresponding to the target client based on the target image file;
A parameter matching module 12, configured to match a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients;
And the system deployment module 13 is used for activating the target historical configuration parameters when the matching is successful, so that the corresponding operating system is deployed on the target client by using the activated target historical configuration parameters.
It can be seen that the present application includes: the method comprises the steps of connecting with a target client, receiving an input target image file, and determining a target architecture corresponding to the target client based on the target image file; matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients; and when the matching is successful, activating the target historical configuration parameters so as to deploy a corresponding operating system on the target client by using the activated target historical configuration parameters. Therefore, after the client is connected with the client, the architecture corresponding to the client is judged through the received image file, then the historical configuration parameters corresponding to the architecture are matched from the historical configuration parameter set, so that the automatic judgment of the client architecture is realized, the matched historical configuration parameters are parameters of an operating system corresponding to the architecture installed on the client, the corresponding operating system is deployed on the target client by activating the historical configuration parameters, the deployment expandability is improved, the deployment efficiency and the flexibility are improved, and the probability of filling accidents is reduced.
In some specific embodiments, the architecture determining module 11 specifically includes:
The system installation unit is used for installing a preset operating system and closing a firewall and SELINUX services after the installation of the preset operating system is completed;
A right setting unit for setting right information so as to create files and directories;
the service deployment unit is used for respectively deploying three services of httpd, dhcpd and tftp on the three servers, and carrying out preset configuration operation on the services after deployment is completed;
the connection unit is used for being connected with the target client;
and the target architecture determining unit is used for receiving the input target image file and determining a target architecture corresponding to the target client based on the target image file.
In some embodiments, the parameter matching module 12 specifically includes:
the image file acquisition unit is used for acquiring image files corresponding to files generated by the frameworks of different clients when the corresponding operating systems are installed;
The copy storing unit is used for sending the decompressed copy of the mirror image file to the catalog corresponding to the framework for storing;
The data extraction unit is used for extracting target data in the copy of the mirror image file and executing preset verification operation after being connected with the client;
the system deployment unit is used for selecting an operating system corresponding to each target data from a preset product catalog when verification is passed and deploying the operating system on the corresponding client;
The historical configuration parameter set acquisition unit is used for acquiring a corresponding historical configuration parameter set after the operating system deployment is completed;
A target operating system determining unit, configured to determine a corresponding target operating system based on the target architecture;
And the matching unit is used for matching the target operating system with the operating system corresponding to the historical configuration parameters in the historical configuration parameter set.
In some embodiments, the parameter matching module 12 specifically includes:
a first matching failure judging unit, configured to judge that matching fails if the target operating system cannot be matched with the operating system corresponding to the historical configuration parameter;
A second matching failure judging unit, configured to judge that matching fails if a system consistent with the target operating system is not matched in the operating systems corresponding to the historical configuration parameters;
A successful matching judging unit, configured to judge that the matching is successful if a system consistent with the target operating system is matched in the operating systems corresponding to the historical configuration parameters;
And the alarm information generating unit is used for generating corresponding alarm information and sending the alarm information to a corresponding maintenance terminal when the matching of the target operating system and the operating system corresponding to the historical configuration parameters fails.
Further, the embodiment of the application also provides electronic equipment. Fig. 7 is a block diagram of an electronic device 20, according to an exemplary embodiment, and is not intended to limit the scope of use of the present application in any way.
Fig. 7 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input output interface 25, and a communication bus 26. Wherein the memory 22 is configured to store a computer program that is loaded and executed by the processor 21 to implement the relevant steps in the system deployment method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in the present embodiment may be specifically an electronic computer.
In this embodiment, the power supply 23 is configured to provide an operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 25 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application requirement, which is not limited herein.
The memory 22 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk, or an optical disk, and the resources stored thereon may include an operating system 221, a computer program 222, and the like, and the storage may be temporary storage or permanent storage.
The operating system 221 is used for managing and controlling various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, netware, unix, linux, etc. The computer program 222 may further include a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the system deployment method performed by the electronic device 20 as disclosed in any of the previous embodiments.
Further, the embodiment of the application also discloses a storage medium, wherein the storage medium stores a computer program, and when the computer program is loaded and executed by a processor, the steps of the system deployment method disclosed in any of the previous embodiments are realized.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing has described in detail a system deployment method, apparatus, device and storage medium provided by the present invention, and specific examples have been applied herein to illustrate the principles and embodiments of the present invention, and the above examples are only for aiding in the understanding of the method and core idea of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
Claims (8)
1. A system deployment method, applied to a pre-boot execution environment server, comprising:
the method comprises the steps of connecting with a target client, receiving an input target image file, and determining a target architecture corresponding to the target client based on the target image file;
matching a target historical configuration parameter corresponding to the target architecture from a historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients;
activating the target historical configuration parameters when the matching is successful, so that a corresponding operating system is deployed on the target client by using the activated target historical configuration parameters;
wherein before the matching of the target historical configuration parameters corresponding to the target architecture from the historical configuration parameter set, the method further comprises:
Acquiring mirror image files corresponding to files generated by frameworks of different clients when installing corresponding operating systems; the decompressed copies of the image files are sent to the catalogues corresponding to the architecture for storage; extracting target data in the copy of the mirror image file, and executing preset verification operation after being connected with the client; when verification is passed, selecting an operating system corresponding to each target data from a preset product catalog and deploying the operating system on the corresponding client so as to obtain a corresponding historical configuration parameter set after the operating system deployment is completed;
The extracting the target data in the copy of the image file, and executing a preset verification operation after connecting with the client, includes:
Determining a framework corresponding to the copy of the image file, and extracting a bootstrap guide file in the framework corresponding to the copy and a platform identification code of the framework corresponding to the copy; copying the bootstrap guide file to a root directory of the target service, and executing preset verification operation after the bootstrap guide file is connected with the client.
2. The system deployment method of claim 1, wherein prior to the connecting with the target client, further comprising:
installing a preset operating system, and closing a firewall and SELINUX services after the installation of the preset operating system is completed;
setting authority information so as to create files and directories;
And respectively deploying three services of httpd, dhcpd and tftp on the three servers, and carrying out preset configuration operation on the services after deployment is completed.
3. The system deployment method according to claim 1, wherein after performing a preset verification operation after connecting with the client, further comprising:
matching and packaging the bootstrap guide file and the corresponding platform identification code to obtain packaged information;
And storing the packaged information into a preset storage area.
4. A system deployment method according to any one of claims 1 to 3, wherein said matching a target historical configuration parameter corresponding to the target architecture from a set of historical configuration parameters comprises:
determining a corresponding target operating system based on the target architecture;
and matching the target operating system with the operating system corresponding to the historical configuration parameters in the historical configuration parameter set.
5. The system deployment method of claim 4 wherein said matching the target operating system with the operating system corresponding to the historical configuration parameters in the set of historical configuration parameters comprises:
if the target operating system cannot be matched with the operating system corresponding to the historical configuration parameters, judging that the matching is failed;
If the system consistent with the target operating system is not matched in the operating system corresponding to the historical configuration parameters, judging that the matching is failed;
if the system consistent with the target operating system is matched in the operating system corresponding to the historical configuration parameters, judging that the matching is successful;
when the matching of the target operating system and the operating system corresponding to the historical configuration parameters fails, corresponding alarm information is generated and sent to a corresponding maintenance terminal.
6. A system deployment apparatus for use with a pre-boot execution environment server, comprising:
the framework determining module is used for being connected with the target client, receiving an input target image file and determining a target framework corresponding to the target client based on the target image file;
The parameter matching module is used for matching the target historical configuration parameters corresponding to the target architecture from the historical configuration parameter set; the history configuration parameters set comprises history configuration parameters obtained after corresponding operating systems are installed by the frameworks of different clients;
The system deployment module is used for activating the target historical configuration parameters when the matching is successful, so that a corresponding operating system is deployed on the target client by using the activated target historical configuration parameters;
The parameter matching module specifically comprises:
the image file acquisition unit is used for acquiring image files corresponding to files generated by the frameworks of different clients when the corresponding operating systems are installed;
The copy storing unit is used for sending the decompressed copy of the mirror image file to the catalog corresponding to the framework for storing;
The data extraction unit is used for extracting target data in the copy of the mirror image file and executing preset verification operation after being connected with the client;
the system deployment unit is used for selecting an operating system corresponding to each target data from a preset product catalog when verification is passed and deploying the operating system on the corresponding client;
The historical configuration parameter set acquisition unit is used for acquiring a corresponding historical configuration parameter set after the operating system deployment is completed;
The data extraction unit is specifically configured to:
Determining a framework corresponding to the copy of the image file, and extracting a bootstrap guide file in the framework corresponding to the copy and a platform identification code of the framework corresponding to the copy; copying the bootstrap guide file to a root directory of the target service, and executing preset verification operation after the bootstrap guide file is connected with the client.
7. An electronic device, comprising:
A memory for storing a computer program;
a processor for executing the computer program to implement the steps of the system deployment method according to any one of claims 1 to 5.
8. A computer-readable storage medium storing a computer program; wherein the computer program, when executed by a processor, implements the system deployment method according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210332899.1A CN114756247B (en) | 2022-03-31 | 2022-03-31 | System deployment method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210332899.1A CN114756247B (en) | 2022-03-31 | 2022-03-31 | System deployment method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114756247A CN114756247A (en) | 2022-07-15 |
| CN114756247B true CN114756247B (en) | 2024-06-21 |
Family
ID=82328298
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210332899.1A Active CN114756247B (en) | 2022-03-31 | 2022-03-31 | System deployment method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114756247B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112148375A (en) * | 2020-09-15 | 2020-12-29 | 深圳宝新创科技股份有限公司 | System installation method, server, client and storage medium |
| CN113342365A (en) * | 2021-06-28 | 2021-09-03 | 深圳前海微众银行股份有限公司 | Operating system deployment method, device, equipment and computer-readable storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11288055B2 (en) * | 2020-02-18 | 2022-03-29 | International Business Machines Corporation | Model-based differencing to selectively generate and deploy images in a target computing environment |
| CN114115920A (en) * | 2021-12-02 | 2022-03-01 | 深圳前海微众银行股份有限公司 | Operating system deployment method, system, device and computer-readable storage medium |
-
2022
- 2022-03-31 CN CN202210332899.1A patent/CN114756247B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112148375A (en) * | 2020-09-15 | 2020-12-29 | 深圳宝新创科技股份有限公司 | System installation method, server, client and storage medium |
| CN113342365A (en) * | 2021-06-28 | 2021-09-03 | 深圳前海微众银行股份有限公司 | Operating system deployment method, device, equipment and computer-readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114756247A (en) | 2022-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1142309B1 (en) | Method and apparatus for operating system downloads in a set-top box environment | |
| US8151277B2 (en) | Method and system for dynamic remote injection of in-process agents into virtual machine based applications | |
| CN111090452B (en) | Service environment switching method and computer readable storage medium | |
| CN101770372B (en) | Firmware update system, method and building method of firmware of firmware update system | |
| CN110045991B (en) | RAID configuration method and device of server, computer equipment and storage medium | |
| US20220103555A1 (en) | Service deployment method, device, system, and computer-readable storage medium | |
| CN109308184B (en) | Middleware installation and update method, device and computer readable storage medium | |
| CN112148315A (en) | Software deployment method, device, server and storage medium | |
| CN111143023A (en) | Resource changing method and device, equipment and storage medium | |
| CN107766055A (en) | A kind of client linux system installation method based on GUI module | |
| CN112214227A (en) | Edge server mirror image customization and deployment system and method | |
| CN112099825A (en) | Method, device and equipment for upgrading component and storage medium | |
| CN116820493A (en) | Mirror image file deployment method, system, equipment and storage medium | |
| CN111475175A (en) | Method, device and medium for installing and guiding operation system based on ARM server | |
| CN109032612B (en) | Interface calling method and device of hybrid application and computer readable storage medium | |
| CN115202680A (en) | System and method for automatically upgrading local client on line in remote manner | |
| CN107995033B (en) | ONU configuration file upgrading method and device | |
| CN113821226A (en) | ONIE system installation method, apparatus, device and medium | |
| CN114756247B (en) | System deployment method, device, equipment and storage medium | |
| US20030120827A1 (en) | Method and apparatus for automatically detecting machine states during an operating system installation through a network | |
| CN114721784B (en) | Application running method and device, electronic equipment and readable medium | |
| CN111596964A (en) | Method and device for realizing batch deployment of Windows systems based on wireless network | |
| CN115016801A (en) | Test environment deployment method, system, terminal and storage medium in complex system | |
| CN115599399A (en) | Application program deployment method and device and storage medium | |
| CN114443065A (en) | Platform deployment method, platform deployment device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |