A software product installation method, device, equipment and medium

Abstract

The application discloses a software product installation method and device, equipment and medium, including: obtaining the installation package of a software product; determining the dependency package information of the dependency package required by the software product based on the installation package; obtaining the architecture information of the current server; downloading the corresponding target dependency package from the local docker warehouse based on the dependency package information and the architecture information; wherein, the local docker warehouse includes dependency packages corresponding to various server architectures; and installing the software product based on the target dependency package. In this way, the dependency packages corresponding to various server architectures are stored in the local docker warehouse, and when the software product is installed, the dependency package suitable for the current server architecture is downloaded from the local docker warehouse, different installation packages corresponding to different server architectures are not needed, a unified installation package is used to adapt to servers with different architectures, the installation difficulty is reduced, the installation efficiency is improved, and the management difficulty is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software installation, and particularly relates to a software product installation method and device, equipment and a medium. BACKGROUND

[0002] At present, many users will select different types of servers as the servers of software products, and different server architectures have different dependent packages in the software product installation process. In order to adapt to different server architectures, installation packages for different architectures need to be made, so that the existing server architectures need to be well known to the on-site personnel, and the requirements for the on-site personnel are high; and the installation packages of various architectures need to be managed by the operation and maintenance personnel, and the management difficulty is great. SUMMARY

[0003] Therefore, the present application aims to provide a software product installation method, device, equipment and medium, which can adapt to servers of different architectures through unified installation packages, reduce installation difficulty, improve installation efficiency and reduce management difficulty. The specific scheme is as follows:

[0004] In a first aspect, the present application discloses a software product installation method, comprising:

[0005] obtaining an installation package of a software product;

[0006] determining dependent package information of dependent packages required for installing the software product based on the installation package;

[0007] obtaining architecture information of a current server;

[0008] downloading a target dependent package corresponding to the dependent package information and the architecture information from a local docker warehouse; wherein the local docker warehouse comprises dependent packages corresponding to various server architectures;

[0009] installing the software product based on the target dependent package.

[0010] Optionally, the step of determining the dependent package information of the dependent packages required for installing the software product based on the installation package comprises:

[0011] obtaining pre-created dependent package information from the installation package to obtain the dependent package information of the dependent packages required for installing the software product.

[0012] Optionally, after the step of downloading the target dependent package corresponding to the dependent package information and the architecture information from the local docker warehouse, the method further comprises:

[0013] placing the target dependent package in a specified directory;

[0014] Correspondingly, the installing the software product based on the target dependency package comprises:

[0015] reading the target dependency package from the specified directory, and installing the software product based on the target dependency package.

[0016] Optionally, the obtaining the architecture information of the current server comprises:

[0017] obtaining the architecture information of the current server through a linux script.

[0018] Optionally, the installing the software product based on the target dependency package comprises:

[0019] installing the software product based on the target dependency package and using a preset installation script.

[0020] Optionally, before the downloading the corresponding target dependency package from the local docker repository based on the dependency package information and the architecture information, the method further comprises:

[0021] replacing a download source corresponding to the docker repository to deploy the local docker repository.

[0022] Optionally, after the installing the software product based on the target dependency package, the method further comprises:

[0023] returning an installation result of the software product.

[0024] In a second aspect, the present application provides a software product installation device, comprising:

[0025] an installation package obtaining module configured to obtain an installation package of a software product;

[0026] a dependency package information determining module configured to determine, based on the installation package, dependency package information of a dependency package required for installing the software product;

[0027] a server architecture information obtaining module configured to obtain architecture information of a current server;

[0028] a target dependency package downloading module configured to download, based on the dependency package information and the architecture information, a corresponding target dependency package from a local docker repository; wherein the local docker repository comprises dependency packages corresponding to various server architectures;

[0029] a software product installing module configured to install the software product based on the target dependency package.

[0030] In a third aspect, the present application discloses an electronic device, comprising:

[0031] a memory for storing the computer program;

[0032] a processor for executing the computer program to implement the software product installation method.

[0033] In a fourth aspect, the present application discloses a computer readable storage medium for storing a computer program, which, when executed by a processor, implements the software product installation method.

[0034] It can be seen that the present application first acquires an installation package of a software product, then determines dependency package information of a dependency package required for installing the software product based on the installation package, acquires architecture information of a current server, then downloads a target dependency package corresponding to the target dependency package from a local docker warehouse based on the dependency package information and the architecture information, the local docker warehouse including dependency packages corresponding to various server architectures, and finally installs the software product based on the target dependency package. That is, the present application stores dependency packages corresponding to various server architectures in a local docker warehouse, acquires dependency package information of a dependency package required for installing a software product and architecture information of a current server based on an installation package when installing the software product, then downloads a corresponding dependency package from the local docker warehouse to install the software product. In this way, different installation packages corresponding to different server architectures do not need to be made, different architectures of servers can be adapted through a unified installation package, installation difficulty is reduced, installation efficiency is improved, and management difficulty is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor on the basis of the provided drawings.

[0036] Figure 1 A software product installation method flow chart disclosed by the present application;

[0037] Figure 2 A specific software product installation method flow chart disclosed by the present application;

[0038] Figure 3 A software product installation device structure schematic diagram disclosed by the present application;

[0039] Figure 4 A structure diagram of an electronic device disclosed by the present application. DETAILED DESCRIPTION

[0040] With reference to the drawings of the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments of the present application, all the other embodiments obtained by a person of ordinary skill in the art without creative work are within the scope of protection of the present application.

[0041] At present, many users will select different types of servers as the servers of software products, and different server architectures have different dependent packages in the software product installation process. In order to adapt to different server architectures, installation packages for different architectures need to be made. Therefore, the on-site personnel need to be familiar with the existing server architectures, and the requirements for on-site personnel are high; for the operation and maintenance personnel, various architecture installation packages need to be managed, and the management difficulty is great. Therefore, the present application provides a software product installation scheme, which can adapt to servers of different architectures through a unified installation package, reduce the installation difficulty, improve the installation efficiency and reduce the management difficulty.

[0042] Referring to Figure 1 The embodiments of the present application disclose a software product installation method, comprising:

[0043] Step S11: obtaining an installation package of a software product.

[0044] Step S12: determining dependent package information of dependent packages required for installing the software product based on the installation package.

[0045] In a specific implementation manner, the dependent package information of the dependent packages required for installing the software product can be obtained from the installation package.

[0046] That is, the installation package in the embodiments of the present application can include the pre-created dependent package information, and the dependent package information of the dependent packages required for the software product can be written into the installation package in advance. The dependent package information can be the dependent package name, such as JDK.

[0047] In addition, the pre-created dependent package information of the dependent packages required for installing the software product can be obtained from the installation package based on the script in the installation package.

[0048] Step S13: obtaining architecture information of a current server.

[0049] In a specific implementation manner, the architecture information of the current server can be obtained through a linux script. That is, the architecture type of the current server is identified.

[0050] In a specific implementation manner, the architecture information of the current server can be obtained through the linux script in the installation package. In a specific implementation manner, the architecture information of the current server can be obtained through the linux script in the installation package.

[0051] That is, the installation package in the embodiment of the application includes dependency package information for obtaining a dependency package required for installing the software product and a script for obtaining architecture information of a current server.

[0052] Step S14: downloading a corresponding target dependency package from a local docker repository based on the dependency package information and the architecture information; wherein the local docker repository includes dependency packages corresponding to various server architectures.

[0053] That is, the embodiment of the application can pre-produce a docker repository and store dependency packages of the software product under various server architectures in the docker repository. When installing the software product, the corresponding download source of the docker repository can be replaced to deploy the local docker repository.

[0054] Further, after the dependency package information and the architecture information, a dependency package matching the dependency package information and the architecture information is searched from the local docker repository to obtain a target dependency package, and then the target dependency package is downloaded. For example, the repository includes JDK packages corresponding to various server architectures, and a JDK package adapted to the current server is determined based on the current server architecture information.

[0055] Further, in a specific implementation, the produced docker repository can be added to the installation package, and the local deployment is performed by the script in the installation package during installation. The produced docker repository can also be a repository independent of the installation. Compared with the installation package, the produced docker repository is added to the installation package, and the operation is more convenient.

[0056] Step S15: installing the software product based on the target dependency package.

[0057] In a specific implementation, the target dependency package can be placed in a specified directory, and the target dependency package is read from the specified directory, and the software product is installed based on the target dependency package.

[0058] Specifically, the software product is installed based on the target dependency package and by using a preset installation script. The installation package can include the preset installation script.

[0059] Finally, the installation result of the software product is returned to timely inform the installer of the installation result.

[0060] It can be seen that the embodiment of the application first acquires the installation package of the software product, then determines the dependency package information of the dependency package required for installing the software product based on the installation package, acquires the architecture information of the current server, then downloads the corresponding target dependency package from the local docker warehouse based on the dependency package information and the architecture information, the local docker warehouse includes dependency packages corresponding to various server architectures, and finally installs the software product based on the target dependency package. That is, the application stores dependency packages corresponding to various server architectures in the local docker warehouse, first acquires the dependency package information of the dependency package required for installing the software product and the architecture information of the current server based on the installation package when installing the software product, then downloads the corresponding dependency package from the local docker warehouse, and installs the software product. In this way, different installation packages corresponding to different server architectures do not need to be made, different architectures of servers can be adapted through a unified installation package, the installation difficulty is reduced, the installation efficiency is improved, and the management difficulty is reduced.

[0061] Referring to Figure 2 as shown, Figure 2 A specific software product installation method flowchart disclosed by the embodiment of the application is shown. First, a docker local warehouse is made, and each dependency package is stored in the docker local warehouse. When installing, the required dependency package is identified according to the dependency package information in the installation package, the architecture information of the server is identified through a linux script, then the dependency package is matched and downloaded in the local warehouse according to the dependency package information and the architecture information, is stored in a specified directory, and the software product is installed based on the installation script. That is, the embodiment of the application first pushes all dependency packages into the local docker warehouse, then identifies the required dependency package according to the dependency package information in the installation package, identifies the architecture information of the server through a linux script, downloads the dependency package from the docker warehouse according to the dependency package information and the architecture information of the server, then installs the software product according to the script in the installation package, and finally returns the installation result of the software product.

[0062] It can be understood that the embodiment of the application establishes a local docker warehouse, puts the dependency package required by the server of each architecture in the installation process into the local warehouse, automatically detects the required dependency package during the installation process, downloads it, and then installs it according to the installation script. Through the preset installation startup script, one-key installation can be realized in the network and non-network environment. The warehouse is constantly improved and supplemented through the feedback information. When the software is upgraded, only the upgraded part of the installation package needs to be modified, and the other environment can be self-adaptive. In this way, based on the docker warehouse, there is no need to use storage to store the dependency package. Based on the linux script detection installation package and server hardware, it is fast, convenient, and removes the obstruction of server architecture to the software product installation process, and truly realizes one-key installation, which is suitable for non-network environment and solves the problem of smoothly downloading the dependency package in the non-internet environment. The following problems in the prior art are solved: the server architecture is more, the adaptation difficulty is large, different server architectures require different dependency packages, and it is difficult to find the dependency package on the Internet and adapt it, and the adaptation time is long, which affects the project progress. The technical requirements for on-site technical personnel are high, and the on-site technology needs to be familiar with the architecture of the server to determine what kind of installation package is needed. The installation package management is difficult, one installation package is made for one server architecture, the number of installation packages is large, and the installation package is large, which is difficult to manage. If the program is updated, it needs to be updated in each installation package, which is a large amount of work and a waste of time.

[0063] Referring to Figure 3 The embodiment of the application provides a software product installation device, which comprises:

[0064] An installation package acquisition module 11 is configured to acquire an installation package of a software product.

[0065] A dependency package information determination module 12 is configured to determine dependency package information of a dependency package required for installing the software product based on the installation package.

[0066] A server architecture information acquisition module 13 is configured to acquire architecture information of a current server.

[0067] A target dependency package download module 14 is configured to download a corresponding target dependency package from a local docker warehouse based on the dependency package information and the architecture information. The local docker warehouse comprises dependency packages corresponding to various server architectures.

[0068] A software product installation module 15 is configured to install the software product based on the target dependency package.

[0069] It can be seen that the embodiment of the application first acquires the installation package of the software product, then determines the dependency package information of the dependency package required for installing the software product based on the installation package, acquires the architecture information of the current server, then downloads the corresponding target dependency package from the local docker warehouse based on the dependency package information and the architecture information, the local docker warehouse includes the dependency packages corresponding to various server architectures, and finally installs the software product based on the target dependency package. That is, the application stores the dependency packages corresponding to various server architectures in the local docker warehouse, acquires the dependency package information of the dependency package required for installing the software product and the architecture information of the current server based on the installation package when installing the software product, then downloads the corresponding dependency package from the local docker warehouse, and installs the software product. In this way, different installation packages corresponding to different server architectures do not need to be made, different architectures of servers can be adapted through a unified installation package, the installation difficulty is reduced, the installation efficiency is improved, and the management difficulty is reduced.

[0070] In a specific implementation, the dependency package information determination module 12 is specifically configured to acquire the pre-created dependency package information from the installation package by the target dependency package downloading module, to obtain the dependency package information of the dependency package required for installing the software product.

[0071] The apparatus further includes a target dependency package storage module configured to store the target dependency package in a specified directory after the target dependency package downloading module downloads the corresponding target dependency package from the local docker warehouse based on the dependency package information and the architecture information.

[0072] Correspondingly, the software product installation module 15 is specifically configured to read the target dependency package from the specified directory and install the software product based on the target dependency package.

[0073] The server architecture information acquisition module 13 is specifically configured to acquire the architecture information of the current server through a linux script.

[0074] The software product installation module is specifically configured to install the software product based on the target dependency package and by using a preset installation script.

[0075] Further, the apparatus further includes a warehouse deployment module configured to replace a download source corresponding to the docker warehouse to deploy the local docker warehouse before the target dependency package downloading module downloads the corresponding target dependency package from the local docker warehouse based on the dependency package information and the architecture information.

[0076] In addition, the device further comprises an installation result returning module, configured to return an installation result of the software product after the software product installation module installs the software product based on the target dependent package.

[0077] Referring to Figure 4 As shown in the drawings, the embodiment of the present application discloses an electronic device 20, comprising a processor 21 and a memory 22; wherein the memory 22 is configured to save a computer program; the processor 21 is configured to execute the computer program to realize the following steps:

[0078] An installation package of a software product is acquired; dependent package information of a dependent package required for installing the software product is determined based on the installation package; architecture information of a current server is acquired; a target dependent package corresponding to the dependent package information and the architecture information is downloaded from a local docker warehouse; wherein the local docker warehouse comprises dependent packages corresponding to various server architectures; and the software product is installed based on the target dependent package.

[0079] As can be seen, the embodiment of the present application first acquires an installation package of a software product, then determines dependent package information of a dependent package required for installing the software product based on the installation package, acquires architecture information of a current server, then downloads a target dependent package corresponding to the dependent package information and the architecture information from a local docker warehouse, the local docker warehouse comprises dependent packages corresponding to various server architectures, and finally installs the software product based on the target dependent package. That is, the present application utilizes the local docker warehouse to store dependent packages corresponding to various server architectures, when installing a software product, first acquires dependent package information of a dependent package required for installing the software product and architecture information of a current server based on an installation package, then downloads a corresponding dependent package from the local docker warehouse to install the software product. In this way, different installation packages corresponding to different server architectures are not required, a unified installation package can be used to adapt to servers of different architectures, installation difficulty is reduced, installation efficiency is improved, and management difficulty is reduced.

[0080] In the embodiment, when the processor 21 executes the computer program saved in the memory 22, the following steps can be specifically realized: dependent package information required for installing the software product is obtained from the installation package.

[0081] In the embodiment, when the processor 21 executes the computer program saved in the memory 22, the following steps can be specifically realized: the target dependent package is placed in a specified directory; the target dependent package is read from the specified directory, and the software product is installed based on the target dependent package.

[0082] In this embodiment, the processor 21 executes the computer program stored in the memory 22, and the following steps can be implemented: obtaining the architecture information of the current server through a linux script.

[0083] In this embodiment, the processor 21 executes the computer program stored in the memory 22, and the following steps can be implemented: installing the software product based on the target dependent package and using a preset installation script.

[0084] In this embodiment, the processor 21 executes the computer program stored in the memory 22, and the following steps can be implemented: replacing the download source corresponding to the docker warehouse to deploy a local docker warehouse.

[0085] In this embodiment, the processor 21 executes the computer program stored in the memory 22, and the following steps can be implemented: returning the installation result of the software product.

[0086] In addition, the memory 22 as a carrier for storing resources can be a read-only memory, a random access memory, a magnetic disk or an optical disk, and the storage mode can be temporary storage or permanent storage.

[0087] In addition, the electronic device 20 further includes a power supply 23, a communication interface 24, an input / output interface 25 and a communication bus 26; wherein the power supply 23 is used to provide working 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 the external device, and the communication protocol followed by the communication interface 24 can be any communication protocol applicable to the technical solution of the present application, which will not be limited here; the input / output interface 25 is used to obtain external input data or output data to the outside, and the specific interface type can be selected according to the specific application needs, which will not be limited here.

[0088] Further, the present application further discloses a computer readable storage medium for storing a computer program, wherein the computer program is executed by a processor to implement the software product installation method disclosed in the foregoing embodiments.

[0089] The specific process of the above software product installation method can refer to the corresponding content disclosed in the foregoing embodiments, which will not be repeated here.

[0090] In the present specification, each embodiment is described in a progressive manner, and each embodiment focuses on the difference from other embodiments. The same or similar parts of each embodiment can be referred to each other. For the device disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple, and the related parts can be referred to the method part.

[0091] The steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in random access memory (RAM), flash memory, read-only memory (ROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, hard disk can be used as a storage medium.

[0092] The above provides a kind of software product installation method, device, equipment and medium provided by the present application in detail, the principle and implementation mode of the present application are described in this paper by applying specific example, the above example is only for helping to understand the method of the present application and its core idea;Meanwhile, for the general technical personnel of the prior art, according to the idea of the present application, there will be changes in specific implementation mode and application range, as described above, the content of the specification should not be understood as the limitation of the present application.

Claims

1. A software product installation method characterized by comprising: The method comprises the following steps: obtaining an installation package of a software product; the installation package comprises a docker repository prepared in advance; determining dependency package information of a dependency package required for installing the software product based on the installation package; obtaining architecture information of a current server; downloading a target dependency package corresponding to the dependency package information and the architecture information from a local docker repository; the local docker repository comprises dependency packages corresponding to various server architectures; installing the software product based on the target dependency package. The method further comprises the following steps before the step of downloading the target dependency package from the local docker repository based on the dependency package information and the architecture information: replacing a download source corresponding to the docker repository to deploy the local docker repository.

2. The software product installation method according to claim 1, characterized by, The method further comprises the following steps after the step of downloading the target dependency package from the local docker repository based on the dependency package information and the architecture information: placing the target dependency package in a specified directory. Correspondingly, the step of installing the software product based on the target dependency package comprises the following steps: reading the target dependency package from the specified directory, and installing the software product based on the target dependency package.

3. The software product installation method according to Claim 1, characterized by, The step of obtaining the architecture information of the current server comprises the following step: obtaining the architecture information of the current server through a linux script.

4. The software product installation method according to Claim 1, characterized by, The step of installing the software product based on the target dependency package comprises the following step: installing the software product based on the target dependency package and by using a preset installation script.

5. The software product installation method according to any one of claims 1 to 4, wherein The method further comprises the following step after the step of installing the software product based on the target dependency package: returning an installation result of the software product.

6. A software product installation apparatus characterized by comprising: The method comprises the following steps: an installation package obtaining module is configured to obtain an installation package of a software product; the installation package comprises a docker repository prepared in advance; a dependency package information determining module is configured to determine dependency package information of a dependency package required for installing the software product based on the installation package; a server architecture information obtaining module is configured to obtain architecture information of a current server; a target dependency package downloading module is configured to download a target dependency package corresponding to the dependency package information and the architecture information from a local docker repository; the local docker repository comprises dependency packages corresponding to various server architectures; a software product installing module is configured to install the software product based on the target dependency package. The dependency package information determining module is specifically configured to obtain pre-prepared dependency package information from the installation package, and obtain the dependency package information of the dependency package required for installing the software product. The device further comprises a repository deploying module configured to replace a download source corresponding to the docker repository to deploy the local docker repository before the target dependency package downloading module downloads the target dependency package from the local docker repository based on the dependency package information and the architecture information.

7. An electronic device, comprising: The device comprises the following components: a memory configured to save a computer program; A processor for executing the computer program to implement the software product installation method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, A computer program product for saving a computer program which, when executed by a processor, implements the software product installation method according to any one of claims 1 to 5.

Images