Software package installation method and device and storage medium

Generate associated software package identifiers and total software package identifiers through the software management platform and install them in groups, solving the problem of low software package installation efficiency in distributed clusters and realizing automation and resource conservation.

CN119002946APending Publication Date: 2024-11-22JINAN INSPUR DATA TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410340695.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-03-22
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In distributed clusters, the node operating system and processor architecture are different, resulting in low software package installation efficiency and requires personalized installation for each node, which is relatively low.

Method used

Receive the node's architecture and software configuration information through the software management platform, generate an associated software package identification list and total software package identification, and install it in groups to reduce interaction frequency and resource usage.

Benefits of technology

The software package selection and installation are automated, which reduces the participation of technicians, improves installation efficiency, saves resources, and adapts to the diversity of heterogeneous clusters.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119002946A_ABST
    Figure CN119002946A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of computers, and discloses a software package installation method and device and a storage medium. The method comprises the steps that a client node obtains architecture information and software configuration information corresponding to each node and sends the architecture information and the software configuration information to a software management platform, the software management platform sends the architecture information and the software configuration information corresponding to each node to the software management platform according to the architecture information and the software configuration information corresponding to each node, and a total software package identifier is determined for each node; and sending to the client node. And the client node carries out grouping operation on the nodes according to the total software package identifier of each stage. And the group leader node in the nodes belonging to the same group sends a software package acquisition request to the software management platform. The software management platform can generate a corresponding total software package and send the total software package to the group leader node, and the group leader node synchronizes the total software package to other nodes in the same group. And each node can perform installation operation according to the received total software package. The efficiency of installing the software package can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a software package installation method, device and storage medium. Background Art

[0002] In the field of distributed clusters, the operating systems installed on the nodes in the cluster may be different, and the configured processor architectures may also be different. When installing related software, different operating systems and processor architectures require different software packages.

[0003] For each node in the distributed cluster, the technician needs to select the corresponding software package according to the node's operating system and processor architecture, transfer it to the node, and perform installation operations. Due to the large number of nodes in the distributed cluster, the efficiency of installing the software package through related technologies is low. Summary of the invention

[0004] In view of this, the present invention provides a software package installation method, device, software management platform, client node and storage medium to solve the problem of low efficiency in installing software packages.

[0005] In a first aspect, the present invention provides a method for installing a software package, the method being applied to a software management system, the software management system comprising a software management platform and a heterogeneous cluster, the heterogeneous cluster comprising a plurality of nodes, the method being executed by the software management platform, the method comprising:

[0006] Receive architecture information and software configuration information corresponding to each node sent by the client node;

[0007] Obtain a complete list of software and a list of software compatibility;

[0008] Determine, according to the software configuration information and the architecture information corresponding to each node, the full software list, and the software compatibility list, a list of associated software package identifiers for each node and a total software package identifier corresponding to the list of associated software package identifiers;

[0009] Sending the total software package identifier corresponding to each node to the client node, wherein the client node groups multiple nodes according to the total software package identifier corresponding to each node to obtain at least one node group, and selects a group leader node for each node group;

[0010] Receiving a software package acquisition request sent by a target group leader node, wherein the software package acquisition request includes a target total software package identifier corresponding to the target group leader node, and the target group leader node is any one of the at least one group leader node;

[0011] According to the target general software package identifier, selecting a target associated software package identifier list corresponding to the target general software package identifier from the determined associated software package identifier list of each node, wherein the target associated software package identifier list includes a plurality of associated software package identifiers;

[0012] According to each associated software package identifier in the target associated software package identifier list, acquiring an associated software package corresponding to each associated software package identifier;

[0013] A target master software package is generated according to the obtained multiple associated software packages, and sent to the target group leader node, wherein the target group leader node synchronizes the target master software package to other nodes in the target node group except itself, and all nodes in the target node group install the target software package after receiving the target master software package.

[0014] The software package installation method provided by the present invention has the following advantages:

[0015] First, this solution manages all software related information through the software management platform, and can automatically complete the operations of selecting and installing software packages, reducing the level of technical personnel's involvement and greatly improving the efficiency of installing software packages.

[0016] Second, this solution can select a software package that meets the architectural characteristics of the node through the node's architecture information.

[0017] Third, this solution can select the software package required for the node to install the software through the software configuration information of the node, which can minimize the software package and improve the transmission efficiency.

[0018] Fourth, this solution can classify nodes, and each type of node only needs to obtain the software package once, which can reduce the interaction frequency between heterogeneous clusters and software management platforms and save resources.

[0019] In an optional implementation, the software configuration information includes software information of software to be installed and software information of installed software, and the full software list includes software information of all software and associated software information corresponding to each software;

[0020] The determining, according to the software configuration information and the architecture information corresponding to each node, the full software list, and the software compatibility list, a list of associated software package identifiers for each node and a total software package identifier corresponding to the list of associated software package identifiers includes:

[0021] Determining, in the full software list, first-level associated software information that matches the software information of the software to be installed of each node;

[0022] Compare the first-level associated software information corresponding to each node with the software information of the installed software to obtain the second-level associated software information corresponding to each node;

[0023] Determining, in the software compatibility list, a plurality of associated software package identifiers corresponding to each node according to the second-level associated software information corresponding to each node and the architecture information, wherein the plurality of associated software package identifiers corresponding to each node constitute an associated software package identifier list corresponding to each node;

[0024] According to the multiple associated software package identifiers corresponding to each node, a total software package identifier corresponding to each node is determined.

[0025] Specifically, if each node generates a total software package identifier and a total software package, the number of nodes is large, a large amount of storage resources will be occupied, and the transmission efficiency is also low. However, this solution can determine the software package identifier required for each node, that is, the above-mentioned associated software package identifier list, through the software configuration information and architecture information of the node, combined with the full software list and the software compatibility list. Furthermore, the nodes with exactly the same required software package identifiers are assigned the same total software package identifier, that is, for the nodes with exactly the same required software package identifiers, only one total software package needs to be generated, which can save storage resources, network resources, etc., and improve the efficiency of installing software packages.

[0026] In addition, by comparing the first-level associated software information with the software information of the installed software, some software can be filtered out. In this way, repeated acquisition of software packages can be avoided, the size of the installation package can be reduced, and the transmission efficiency and installation efficiency can be improved.

[0027] In an optional implementation, the second-level association information includes at least one sub-association software information, each sub-association information includes the name of the software and the version number of the software, and the architecture information includes the operating system type and the processor architecture type;

[0028] The step of determining, in the software compatibility list according to the second-level associated software information and the architecture information corresponding to each node, a plurality of associated software package identifiers corresponding to each node includes:

[0029] Traversing each piece of sub-associated software information in the target second-level associated software information corresponding to the target node, wherein the target node is any node among the multiple nodes;

[0030] Each time a sub-associated software information is traversed, a target software name and a target software version number are obtained from the traversed sub-associated software information;

[0031] Acquire a target associated software package identifier that matches the target software name, the target software version number, and the operating system class and processor architecture type of the target node in the software compatibility list;

[0032] After traversing all the sub-associated software information in the second-level associated software information corresponding to the target node, a plurality of associated software package identifiers corresponding to the target node are obtained.

[0033] Specifically, this solution can accurately find out the identifier of the software package required by each node, which is in line with the architectural characteristics of the node itself.

[0034] In an optional implementation, the acquiring, according to each associated software package identifier in the target associated software package identifier list, associated software packages corresponding to each associated software package identifier respectively includes:

[0035] According to each associated software package identifier included in the target associated software package identifier list, acquiring a storage path corresponding to each associated software package identifier from the software compatibility list;

[0036] According to the storage path corresponding to each associated software package identifier, the associated software package corresponding to each associated software package identifier is obtained.

[0037] Specifically, by managing the storage paths of various software, when a software package is needed, the corresponding storage path can be obtained according to the identifier of the software package to obtain the software package. In this way, the accuracy and efficiency of finding the software package can be improved without the participation of technical personnel.

[0038] In a second aspect, the present invention provides a method for installing a software package, the method being applied to a software management system, the software management system comprising a software management platform and a heterogeneous cluster, the heterogeneous cluster comprising a plurality of nodes, the method being executed by a client node, wherein the client node is any one of the plurality of nodes, the method comprising:

[0039] Acquire architecture information and software configuration information corresponding to each of the multiple nodes, and send the information to the software management platform, wherein the software management platform generates a total software package identifier corresponding to each node according to the received architecture information and software configuration information corresponding to each node, and sends the total software package identifier to the client node;

[0040] Receiving a total software package identifier corresponding to each node sent by the software management platform;

[0041] Divide the nodes with the same overall software package identifier into a group to obtain at least one node group;

[0042] Selecting a node from a target node group as a target group leader node, wherein the target node group is any node group in at least one node group;

[0043] The target general software package identifier corresponding to the target node group is sent to the target group leader node, wherein the target group leader node sends the target general software package identifier to the software management platform, and after receiving the target general software package identifier, the software management platform obtains the target general software package corresponding to the target general software package identifier and sends it to the target group leader node, and the target group leader node synchronizes the target software package to other nodes in the target node group except itself, and after receiving the target general software package, all nodes in the target node group install the target general software package.

[0044] The software package installation method provided by the present invention has the following advantages:

[0045] First, this solution manages all software related information through the software management platform, and can automatically complete the operations of selecting and installing software packages, reducing the level of technical personnel's involvement and greatly improving the efficiency of installing software packages.

[0046] Second, this solution can select a software package that meets the architectural characteristics of the node through the node's architecture information.

[0047] Third, this solution can select the software package required for the node to install the software through the software configuration information of the node, which can minimize the software package and improve the transmission efficiency.

[0048] Fourth, this solution can classify nodes, and each type of node only needs to obtain the software package once, which can reduce the interaction frequency between heterogeneous clusters and software management platforms and save resources.

[0049] In a third aspect, the present invention provides a software package installation device, the device is applied to a software management system, the software management system includes a software management platform and a heterogeneous cluster, the heterogeneous cluster includes multiple nodes, and the device includes:

[0050] A receiving module, used to receive architecture information and software configuration information corresponding to each node sent by the client node;

[0051] The acquisition module is used to obtain the full software list and software compatibility list;

[0052] a determination module, configured to determine a list of associated software package identifiers of each node and a total software package identifier corresponding to the list of associated software package identifiers according to the software configuration information and the architecture information corresponding to each node, the full software list, and the software compatibility list;

[0053] A sending module, configured to send a total software package identifier corresponding to each node to the client node, wherein the client node groups multiple nodes according to the total software package identifier corresponding to each node to obtain at least one node group, and selects a group leader node for each node group;

[0054] The receiving module is further configured to receive a software package acquisition request sent by a target group leader node, wherein the software package acquisition request includes a target total software package identifier corresponding to the target group leader node, and the target group leader node is any one of the at least one group leader node;

[0055] a selection module, configured to select, according to the target general software package identifier, a target associated software package identifier list corresponding to the target general software package identifier from the determined associated software package identifier list of each node, wherein the target associated software package identifier list includes a plurality of associated software package identifiers;

[0056] The acquisition module is further configured to acquire, according to each associated software package identifier in the target associated software package identifier list, an associated software package corresponding to each associated software package identifier;

[0057] The sending module is further used to generate a target master software package based on the acquired multiple associated software packages, and send it to the target group leader node, wherein the target group leader node synchronizes the target master software package to other nodes in the target node group except itself, and all nodes in the target node group install the target software package after receiving the target master software package.

[0058] In a fourth aspect, the present invention provides a software package installation device, the device is applied to a software management system, the software management system includes a software management platform and a heterogeneous cluster, the heterogeneous cluster includes multiple nodes, and the device includes:

[0059] A receiving module, used to receive a total software package identifier corresponding to each node sent by the software management platform;

[0060] A division module, used for dividing the nodes with the same general software package identifier into a group to obtain at least one node group;

[0061] A selection module, used to select a node from a target node group as a target group leader node, wherein the target node group is any node group in at least one node group;

[0062] A sending module is used to send the target general software package identifier corresponding to the target node group to the target group leader node, wherein the target group leader node sends the target general software package identifier to the software management platform, and after receiving the target general software package identifier, the software management platform obtains the target general software package corresponding to the target general software package identifier and sends it to the target group leader node, and the target group leader node synchronizes the target software package to other nodes in the target node group except itself, and after receiving the target general software package, all nodes in the target node group install the target general software package.

[0063] In a fifth aspect, the present invention provides a software management platform, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the software package installation method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0064] In a sixth aspect, the present invention provides a client node, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the software package installation method of the above-mentioned second aspect or any corresponding embodiment thereof by executing the computer instructions.

[0065] In a seventh aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a software management platform to execute the software package installation method of the first aspect or any corresponding embodiment thereof.

[0066] In an eighth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a software management platform to execute the software package installation method of the second aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0068] Figure 1is a schematic diagram of the architecture of a software management system according to an embodiment of the present invention;

[0069] Figure 2 is a flowchart of a method for installing a software package according to an embodiment of the present invention;

[0070] Figure 3 is a flowchart of another software package installation method according to an embodiment of the present invention;

[0071] Figure 4 is a flowchart of another software package installation method according to an embodiment of the present invention;

[0072] Figure 5 is a structural block diagram of a software package installation device according to an embodiment of the present invention;

[0073] Figure 6 is a structural block diagram of another software package installation device according to an embodiment of the present invention;

[0074] Figure 7 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0075] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0076] The embodiment of the present invention provides a software management system, the structure of which can be as follows: Figure 1 As shown, the software management system includes a software management platform and a heterogeneous cluster. A heterogeneous cluster may include multiple nodes, including a client node among the multiple nodes, which may be pre-specified by a technician. A heterogeneous cluster refers to a cluster in which the architecture information of each node is different.

[0077] The software management platform can be configured with a software dependency management module and a platform interaction module. Among them, the software dependency management module stores a full list of software (for example, Table 1) and a software compatibility list (for example, Table 2). Table 1 can be a soft_full table, and Table 2 can be a soft_compatible table. The full list of software can include software information of all software, as well as associated software information corresponding to each software. The platform interaction module may include a communication interface (for example, an http interface) to perform all relevant processing of the following software management platform. The software management platform can be created based on the FastAPI framework. The http interface can be created based on RESTful rules.

[0078] The client node is used to collect the architecture information and software configuration information of each node in the heterogeneous cluster.

[0079] Table 1

[0080]

[0081] Among them, ID represents the unique identifier of the software, NAME represents the name of the software, VERSION represents the version number of the software, and MOUDLE represents the functional module information of the software. Since some nodes in a heterogeneous cluster may be applied in block scenarios, some nodes may be applied in file scenarios, and some nodes may be applied in object scenarios, when installing distributed software, the nodes in the block scenario need to install the A functional module of the distributed software, the nodes in the file scenario need to install the B functional module of the distributed software, and the nodes in the object scenario need to install the C functional module of the distributed software. Therefore, the functional module information is recorded in Table 1 to facilitate finding the associated software information corresponding to the corresponding functional module. RELETED_PKG represents the associated software information, for example, it may include PKG_NAME and PKG_VERSION, PKG_NAME is the software name of the associated software, and PKG_VERSION is the software version number of the associated software. The format of ID can be an integer, the format of NAME, VERSION, and MOUDLE can be a string, and RELETED_PKG can be a JSON (JavaScript Object Notation) array format.

[0082] Table 2

[0083]

[0084] Among them, COM_PKG_ID represents the unique identifier of the software package, COM_PKG_NAME represents the name of the software package, COM_PKG_VERSION represents the version number of the software package, COM_OS represents the operating system type, COM_ARH represents the processor (Central Processing Unit, CPU) architecture type, and PKG_PATH represents the storage path of the software package.

[0085] The embodiment of the present invention provides a method for installing a software package, which can improve the processing efficiency of installing software packages in a heterogeneous cluster through automatic processing of a software management platform and synchronization of installation packages between nodes in the same group.

[0086] According to an embodiment of the present invention, an embodiment of a method for installing a software package is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0087] In this embodiment, a method for installing a software package is provided, which can be used in the above-mentioned software management system. Figure 2 As shown, the software management platform and the client node interact to complete the installation of the software package. See the following for details, including:

[0088] Step S201: The client node obtains architecture information and software configuration information corresponding to each node, and sends the information to the software management platform.

[0089] The architecture information may include the operating system type and the processor architecture type. The software configuration information may include the software information of the software to be installed and the software information of the installed software. The software information of the software to be installed may include the name, version number and functional module information of the software to be installed. The software information of the installed software may include the name and version number of the installed software.

[0090] Specifically, all nodes in the heterogeneous cluster can pre-enable the Secure Shell (SSH) protocol. When the client node receives the software upgrade instruction from the user end, it can obtain the operating system types corresponding to all nodes by executing the "uname-a" command, and can obtain the processor architecture types corresponding to all nodes by executing the "lscpu" command. The software information of the installed software of the node can be obtained by executing the software information acquisition command corresponding to the operating system type of each node. For example, for the Linux system, the "dpkg-l" or "rpm-qa" command can be executed to obtain the software information of the installed software. Among them, the software upgrade instruction may include the software information of the software to be installed.

[0091] By executing the above command, the client node can obtain the architecture information and software configuration information corresponding to all nodes. In addition, the client node can also obtain the name and communication address (Internet Protocol, IP) of each node. The client node can generate a first acquisition request based on the name, IP, architecture information and software configuration information of each node, as well as the cluster identifier, and send it to the software management platform.

[0092] Step S202: The software management platform obtains a complete software list and a software compatibility list.

[0093] Specifically, after receiving the first acquisition request, the software management platform can extract the names, IP addresses, architecture information, software configuration information, and cluster identifiers corresponding to all nodes, and obtain the full software list and software compatibility list from the software dependency management module.

[0094] Step S203: the software management platform determines, in the full software list, first-level associated software information that matches the software information of the software to be installed on each node.

[0095] Specifically, for each node, the software management platform can determine the target data that matches the name, version number, and functional module information of the software to be installed at the node in the full software list based on the name, version number, and functional module information of the software to be installed at the node, and determine the associated software information in the target data as the first-level associated software information corresponding to the node.

[0096] For example, the name of the software to be installed corresponding to node Aaa is A, the version number is 1.1.0, and the function module information is a. In Table 1, the target data can be determined to be {0001, A, 1.1.0, a, [(D, 2.3.0), (M, 1.1.0)…]}. Further, the first-level associated software information of node Aaa can be extracted from the target data as [(D, 2.3.0), (M, 1.1.0)…].

[0097] In step S204, the software management platform compares the first-level associated software information corresponding to each node with the software information of the installed software to obtain the second-level associated software information corresponding to each node.

[0098] The second level association information may include at least one piece of sub-association software information, and each piece of sub-association information may include the name and version number of the software.

[0099] Specifically, installing the software to be installed may require multiple software, and the node may have installed some related software. Therefore, a comparison is required to determine the related software that is not installed in the node. For each node, the software management platform can traverse the first-level associated software information, and determine whether there is software information that matches the name and version number of the associated software in the first-level associated software information in the software information of the installed software. If yes, the software information can be removed from the first-level associated software information, and if not, it can be retained. In this way, the second-level associated software information corresponding to the node can be obtained.

[0100] For example, a piece of software information in the software information of the installed software is (D, 2.3.0), and the first-level associated software information is [(D, 2.3.0), (M, 1.1.0) ...], (D, 2.3.0) can be eliminated to obtain the second-level associated software information [(M, 1.1.0) ...]. (M, 1.1.0) is a sub-associated software information in the second section of associated software information.

[0101] Step S205: the software management platform traverses each piece of sub-associated software information in the target second-level associated software information corresponding to the target node.

[0102] The target node may be any node among multiple nodes.

[0103] Specifically, the software management platform may traverse the target second-level associated software information of the target node, and extract the target software name and the target software version number from each sub-associated software information traversed.

[0104] Step S206: The software management platform obtains a target-associated software package identifier that matches the target software name, target software version number, and operating system class and processor architecture type of the target node in the software compatibility list.

[0105] Specifically, the software management platform may determine in the software compatibility list a target associated software package identifier that matches the target software name, target software version number, operating system type and processor architecture type of the target node.

[0106] For example, from the sub-associated software information (M, 1.1.0), it can be extracted that the target software name is M, the target software version number is 1.1.0, the operating system type of the target node is Red Hat, and the processor architecture type is x86. In Table 2, it can be determined that the target associated software package identifier is "0010".

[0107] Step S207: After traversing all the sub-associated software information in the second-level associated software information corresponding to the target node, the software management platform obtains multiple associated software package identifiers corresponding to the target node.

[0108] Specifically, after traversing all sub-associated software information, the associated software package identifier corresponding to each piece of sub-associated software information can be obtained, and these associated software package identifiers constitute the associated software package identifier list of the target node.

[0109] The above steps S205 to S207 can be executed for each node to obtain a list of associated software package identifiers corresponding to each node.

[0110] Step S208: The software management platform determines a total software package identifier corresponding to each node according to a plurality of associated software package identifiers corresponding to each node.

[0111] Specifically, for each node, the software management platform can generate a total software package identifier and a total software package name according to the cluster identifier, the node name, the IP address, and multiple associated software package identifiers corresponding to the node, and record them in the node software package list. The node software package list can be shown in Table 3, which can be a node_zip_pkg table. If there are multiple associated software package identifiers corresponding to multiple nodes that are the same, the same target software package identifier and target software package name can be assigned to the multiple nodes.

[0112] For example, multiple associated software package identifiers of node Aaa include 0010, 0011, and 0012, and multiple associated software package identifiers of node Abb include 0010, 0011, and 0012. The multiple associated software package identifiers corresponding to node Aaa and node Abb are consistent, indicating that the software packages that node 1 and node 2 need to install are completely consistent.

[0113] Table 3

[0114]

[0115] Among them, ZIP_PKG_ID indicates the total software package identifier, ZIP_PKG_NAME indicates the total software package name, and the total software package name can be named in the form of "name of the software to be installed-version number of the software to be installed-functional module information of the software to be installed-operating system type-processor architecture type-number.zip". ZIP_PKG_SOFT_LIST indicates the list of associated software package identifiers, ZIP_PKG_NODE indicates the name of the node, ZIP_PKG_NODE_IP indicates the IP address of the node, and CLUSTER_ID indicates the cluster identifier.

[0116] In some optional implementations, the software management platform may manage multiple heterogeneous clusters. Therefore, the software management platform can first summarize the first node set with the same cluster identifier in the node software package list, and divide the nodes with the same total software package identifier in the first node set into a node group, and then select a leader node from each node group. In addition, for the nodes in the same node group, the software management platform can obtain multiple associated software packages based on the list of associated software package identifiers corresponding to any node in the node group, and generate a total software package corresponding to the node group. Finally, according to the IP of the leader node in the node group, the total software package and the IPs of all nodes in the node group are sent to the leader node of the node group. The leader node can send the total software package to other nodes in the same group so that other nodes can directly perform the operation of installing the software package. In this way, the software management platform performs grouping and determines the leader node, and there is no need to interact between the heterogeneous clusters and the software management platform multiple times, which can improve the efficiency of installing the software package.

[0117] Step S209: the software management platform sends the software package identifier corresponding to each node to the client node.

[0118] Specifically, the software management platform may send the node software package list to the client node, or may only send the software package identifier corresponding to each node to the client.

[0119] Step S210: The client node divides nodes with the same overall software package identifier into a group to obtain at least one node group.

[0120] Specifically, after receiving the node software package list, the client node extracts the total software package identifier corresponding to each node from each piece of data included in the node software package list, and divides the nodes with the same total software package identifier into a group. In this way, multiple nodes of the heterogeneous cluster can be divided into at least one node group.

[0121] Step S211: the client node selects a node from the target node group as a target group leader node.

[0122] The target node group is any node group in the at least one node group. The target group leader node and the client node may be the same node or different nodes.

[0123] Specifically, the client node may select a node in each node group as the leader node of the node group.

[0124] Step S212: the client node sends the target software package identifier corresponding to the target node group to the target group leader node.

[0125] Specifically, the client node may send the software package identifier corresponding to each node group, and the names and IP addresses of all nodes in the node group to the leader node of the node group.

[0126] Step S213: The target group leader node sends a software package acquisition request to the software management platform.

[0127] The software package acquisition request carries the target total software package identifier.

[0128] Specifically, after receiving the general software package identifier corresponding to itself, each group leader node can temporarily store the general software package identifier and send an upgrade confirmation prompt message to the user end. After receiving the upgrade confirmation instruction sent by the user end, it can generate a software package acquisition request based on the general software package identifier and the cluster identifier, and send the software package acquisition request to the software management platform.

[0129] Step S214: the software management platform selects a target associated software package identifier list corresponding to the target software package identifier from the determined associated software package identifier lists of each node.

[0130] The target associated software package identifier list may include multiple associated software package identifiers.

[0131] Specifically, after receiving a software package acquisition request sent by any group leader node, the software management platform can extract the cluster identifier and the total software package identifier to which the node belongs from the software package acquisition request. The software management platform can determine the associated software package identifier list corresponding to both the total software package identifier and the cluster identifier in the node software package list based on the extracted cluster identifier and the total software package identifier.

[0132] For example, according to the software package identifier 10001, the list of associated software package identifiers is determined in Table 3 to be [0010, 0011, 0012].

[0133] Step S215: the software management platform obtains a storage path corresponding to each associated software package identifier from the software compatibility list according to each associated software package identifier included in the target associated software package identifier list.

[0134] Specifically, for each leader node, the software management platform can traverse the list of associated software package identifiers corresponding to the leader node, and each time an associated software package identifier in the list is traversed, the corresponding storage path can be determined in Table 2 according to the associated software package identifier.

[0135] Step S216: the software management platform obtains the associated software package corresponding to each associated software package identifier according to the storage path corresponding to each associated software package identifier.

[0136] Specifically, the software management platform can obtain the corresponding associated software packages according to the determined storage path. In this way, for each group leader node, the software management platform can determine multiple associated software packages corresponding to the group leader node.

[0137] Step S217: the software management platform generates a target general software package according to the acquired multiple associated software packages, and sends it to the target group leader node.

[0138] Specifically, for each group leader node, the software management platform may package multiple associated software packages corresponding to the group leader node into a total software package, and send the total software package to the group leader node after compression.

[0139] Step S218: The target group leader node receives the target general software package, installs the target general software package, and synchronizes the target general software package to other nodes in the target node group to which the target node belongs.

[0140] Specifically, after receiving the total software package, any group leader node can decompress the total software package to obtain multiple associated software packages, and further, the group leader node can install each associated software package. In addition, the group leader node can synchronize the received software package to each node in the node group according to the names and IPs corresponding to all nodes in the node group to which it belongs. After receiving the total software package, these nodes can decompress the total software package to obtain multiple associated software packages, and install each associated software package.

[0141] The software package installation method provided in this embodiment has the following advantages:

[0142] First, this solution manages all software related information through the software management platform, and can automatically complete the operations of selecting and installing software packages, reducing the level of technical personnel's involvement and greatly improving the efficiency of installing software packages.

[0143] Second, this solution can select a software package that meets the architectural characteristics of the node through the node's architecture information.

[0144] Third, this solution can select the software package required for the node to install the software through the software configuration information of the node, which can minimize the software package and improve the transmission efficiency.

[0145] Fourth, this solution can classify nodes, and each type of node only needs to obtain the software package once, which can reduce the interaction frequency between heterogeneous clusters and software management platforms and save resources.

[0146] The above is the overall process of software management platform and client node interacting to complete the installation of software package. Figure 3 shown.

[0147] Figure 3 FIG. 1 is a flowchart of a method for installing a software package provided by an embodiment of the present invention. Figure 3 As shown, the method is applied to a software management system, and the method is executed by a software management platform. The method includes:

[0148] Step S301, receiving architecture information and software configuration information corresponding to each node sent by a client node.

[0149] Step S302, obtaining a complete software list and a software compatibility list.

[0150] The specific processing from step S301 to step S302 can refer to step S202 and will not be repeated here.

[0151] Step S303, according to the software configuration information and architecture information corresponding to each node, the full software list, and the software compatibility list, determine the associated software package identifier list of each node and the total software package identifier corresponding to the associated software package identifier list.

[0152] The specific processing of step S303 can refer to steps S203 to S208, which will not be repeated here.

[0153] Step S304: Send the total software package identifier corresponding to each node to the client node.

[0154] The client node groups multiple nodes according to the total software package identifier corresponding to each node to obtain at least one node group, and selects a group leader node for each node group.

[0155] The specific processing of step S303 can refer to step S209 and will not be repeated here.

[0156] Step S305: receiving a software package acquisition request sent by the target group leader node.

[0157] The software package acquisition request includes a target general software package identifier corresponding to a target group leader node, and the target group leader node is any one of the at least one group leader node.

[0158] Step S306: According to the target general software package identifier, a target associated software package identifier list corresponding to the target general software package identifier is selected from the determined associated software package identifier lists of each node.

[0159] The target associated software package identifier list includes multiple associated software package identifiers.

[0160] The specific processing from step S305 to step S306 can refer to step S214 and will not be repeated here.

[0161] Step S307: acquiring, according to each associated software package identifier in the target associated software package identifier list, an associated software package corresponding to each associated software package identifier.

[0162] The specific processing of step S307 can refer to steps S215 to S216, which will not be repeated here.

[0163] Step S308: Generate a target overall software package according to the acquired multiple associated software packages, and send it to the target group leader node.

[0164] The target group leader node synchronizes the target master software package to other nodes in the target node group except itself, and all nodes in the target node group install the target software package after receiving the target master software package.

[0165] The specific processing of step S308 can refer to step S218 and will not be repeated here.

[0166] The software package installation method provided in this embodiment has the following advantages:

[0167] First, this solution manages all software related information through the software management platform, and can automatically complete the operations of selecting and installing software packages, reducing the level of technical personnel's involvement and greatly improving the efficiency of installing software packages.

[0168] Second, this solution can select a software package that meets the architectural characteristics of the node through the node's architecture information.

[0169] Third, this solution can select the software package required for the node to install the software through the software configuration information of the node, which can minimize the software package and improve the transmission efficiency.

[0170] Fourth, this solution can classify nodes, and each type of node only needs to obtain the software package once, which can reduce the interaction frequency between heterogeneous clusters and software management platforms and save resources.

[0171] Figure 4 FIG. 1 is a flowchart of a method for installing a software package provided by an embodiment of the present invention. Figure 4 As shown, the method is applied to a software management system, the method is executed by a client node, and the method includes:

[0172] Step S401, obtaining architecture information and software configuration information corresponding to each of the multiple nodes, and sending the information to the software management platform.

[0173] The software management platform generates a total software package identifier corresponding to each node based on the received architecture information and software configuration information corresponding to each node, and sends the total software package identifier to the client node.

[0174] The specific processing of step S401 can refer to step S201 and will not be repeated here.

[0175] Step S402: receiving a general software package identifier corresponding to each node sent by a software management platform.

[0176] The specific processing of step S402 can refer to step S209 and will not be repeated here.

[0177] Step S403: divide the nodes with the same overall software package identifier into a group to obtain at least one node group.

[0178] The specific processing of step S403 can refer to step S210 and will not be repeated here.

[0179] Step S404: Select a node from the target node group as the target group leader node.

[0180] The target node group is any node group in at least one node group.

[0181] The specific processing of step S404 can refer to step S211 and will not be repeated here.

[0182] Step S405: Send the target general software package identifier corresponding to the target node group to the target group leader node.

[0183] Among them, the target group leader node sends the target general software package identifier to the software management platform. After receiving the target general software package identifier, the software management platform obtains the target general software package corresponding to the target general software package identifier and sends it to the target group leader node. The target group leader node synchronizes the target software package to other nodes in the target node group except itself. After receiving the target general software package, all nodes in the target node group install the target general software package.

[0184] The specific processing of step S405 can refer to step S212 and will not be repeated here.

[0185] The software package installation method provided in this embodiment has the following advantages:

[0186] First, this solution manages all software related information through the software management platform, and can automatically complete the operations of selecting and installing software packages, reducing the level of technical personnel's involvement and greatly improving the efficiency of installing software packages.

[0187] Second, this solution can select a software package that meets the architectural characteristics of the node through the node's architecture information.

[0188] Third, this solution can select the software package required for the node to install the software through the software configuration information of the node, which can minimize the software package and improve the transmission efficiency.

[0189] Fourth, this solution can classify nodes, and each type of node only needs to obtain the software package once, which can reduce the interaction frequency between heterogeneous clusters and software management platforms and save resources.

[0190] In this embodiment, a software package installation device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made are not repeated here. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0191] This embodiment provides a software package installation device, such as Figure 5 As shown, including:

[0192] The receiving module 501 is used to receive the architecture information and software configuration information corresponding to each node sent by the client node;

[0193] The acquisition module 502 is used to acquire a complete software list and a software compatibility list;

[0194] The determination module 503 is used to determine the associated software package identifier list of each node and the total software package identifier corresponding to the associated software package identifier list according to the software configuration information and architecture information corresponding to each node, the full software list, and the software compatibility list;

[0195] The sending module 504 is used to send the total software package identifier corresponding to each node to the client node, wherein the client node groups multiple nodes according to the total software package identifier corresponding to each node to obtain at least one node group, and selects a group leader node for each node group;

[0196] The receiving module 501 is further configured to receive a software package acquisition request sent by a target leader node, wherein the software package acquisition request includes a target total software package identifier corresponding to the target leader node, and the target leader node is any leader node among the at least one leader node;

[0197] A selection module 505 is used to select a target associated software package identifier list corresponding to the target total software package identifier from the determined associated software package identifier list of each node according to the target total software package identifier, wherein the target associated software package identifier list includes multiple associated software package identifiers;

[0198] The acquisition module 502 is further used to acquire the associated software package corresponding to each associated software package identifier in the target associated software package identifier list;

[0199] The sending module 504 is also used to generate a target master software package based on the multiple associated software packages obtained, and send it to the target group leader node, wherein the target group leader node synchronizes the target master software package to other nodes in the target node group except itself, and all nodes in the target node group install the target software package after receiving the target master software package.

[0200] In some optional implementations, the software configuration information includes software information of the software to be installed and software information of the installed software, and the full software list includes software information of all software and associated software information corresponding to each software; the determination module 503 is used to:

[0201] Determine the first-level associated software information that matches the software information of the software to be installed on each node in the full software list;

[0202] Compare the first-level associated software information corresponding to each node with the software information of the installed software to obtain the second-level associated software information corresponding to each node;

[0203] Determine, in the software compatibility list, a plurality of associated software package identifiers corresponding to each node according to the second-level associated software information and the architecture information corresponding to each node, wherein the plurality of associated software package identifiers corresponding to each node constitute an associated software package identifier list corresponding to each node;

[0204] According to the multiple associated software package identifiers corresponding to each node, a total software package identifier corresponding to each node is determined.

[0205] In some optional implementations, the second-level association information includes at least one sub-association software information, each sub-association information includes the name of the software and the version number of the software, and the architecture information includes the operating system type and the processor architecture type; the determination module 503 is used to:

[0206] Traversing each piece of sub-associated software information in the target second-level associated software information corresponding to the target node, wherein the target node is any node among the multiple nodes;

[0207] Each time a sub-associated software information is traversed, a target software name and a target software version number are obtained from the traversed sub-associated software information;

[0208] Obtaining a target-associated software package identifier that matches the target software name, target software version number, and operating system class and processor architecture type of the target node in the software compatibility list;

[0209] After traversing all the sub-associated software information in the second-level associated software information corresponding to the target node, a plurality of associated software package identifiers corresponding to the target node are obtained.

[0210] In some optional implementations, the acquisition module 502 is used to:

[0211] According to each associated software package identifier included in the target associated software package identifier list, acquiring a storage path corresponding to each associated software package identifier from the software compatibility list;

[0212] According to the storage path corresponding to each associated software package identifier, the associated software package corresponding to each associated software package identifier is obtained.

[0213] This embodiment provides a software package installation device, such as Figure 6 As shown, including:

[0214] The receiving module 601 is used to receive the total software package identifier corresponding to each node sent by the software management platform;

[0215] A division module 602, configured to divide nodes with the same overall software package identifier into a group to obtain at least one node group;

[0216] A selection module 603 is used to select a node from a target node group as a target group leader node, wherein the target node group is any node group in at least one node group;

[0217] The sending module 604 is used to send the target general software package identifier corresponding to the target node group to the target group leader node, wherein the target group leader node sends the target general software package identifier to the software management platform. After receiving the target general software package identifier, the software management platform obtains the target general software package corresponding to the target general software package identifier and sends it to the target group leader node. The target group leader node synchronizes the target software package to other nodes in the target node group except itself. After receiving the target general software package, all nodes in the target node group install the target general software package.

[0218] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0219] The software package installation device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0220] The embodiment of the present invention also provides a computer device having the above Figure 5 or Figure 6 The software package shown is installed by the device.

[0221] See also Figure 7 , Figure 7 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 7 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.

[0222] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0223] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0224] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

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

[0226] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0227] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0228] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for installing a software package, characterized in that: The method is applied to a software management system, the software management system includes a software management platform and a heterogeneous cluster, the heterogeneous cluster includes multiple nodes, the method is executed by the software management platform, and the method includes: Receive architecture information and software configuration information corresponding to each node sent by the client node; Obtain a complete list of software and a list of software compatibility; Determine, according to the software configuration information and the architecture information corresponding to each node, the full software list, and the software compatibility list, a list of associated software package identifiers for each node and a total software package identifier corresponding to the list of associated software package identifiers; Sending the total software package identifier corresponding to each node to the client node, wherein the client node groups multiple nodes according to the total software package identifier corresponding to each node to obtain at least one node group, and selects a group leader node for each node group; Receiving a software package acquisition request sent by a target group leader node, wherein the software package acquisition request includes a target total software package identifier corresponding to the target group leader node, and the target group leader node is any one of the at least one group leader node; According to the target general software package identifier, selecting a target associated software package identifier list corresponding to the target general software package identifier from the determined associated software package identifier list of each node, wherein the target associated software package identifier list includes a plurality of associated software package identifiers; According to each associated software package identifier in the target associated software package identifier list, acquiring an associated software package corresponding to each associated software package identifier; A target master software package is generated according to the obtained multiple associated software packages, and sent to the target group leader node, wherein the target group leader node synchronizes the target master software package to other nodes in the target node group except itself, and all nodes in the target node group install the target software package after receiving the target master software package.

2. The method according to claim 1, characterized in that: The software configuration information includes software information of the software to be installed and software information of the installed software, and the full software list includes software information of all software and associated software information corresponding to each software; The determining, according to the software configuration information and the architecture information corresponding to each node, the full software list, and the software compatibility list, a list of associated software package identifiers for each node and a total software package identifier corresponding to the list of associated software package identifiers includes: Determining, in the full software list, first-level associated software information that matches the software information of the software to be installed of each node; Compare the first-level associated software information corresponding to each node with the software information of the installed software to obtain the second-level associated software information corresponding to each node; Determining, in the software compatibility list, a plurality of associated software package identifiers corresponding to each node according to the second-level associated software information corresponding to each node and the architecture information, wherein the plurality of associated software package identifiers corresponding to each node constitute an associated software package identifier list corresponding to each node; According to the multiple associated software package identifiers corresponding to each node, a total software package identifier corresponding to each node is determined.

3. The method according to claim 2, characterized in that The second-level association information includes at least one sub-association software information, each sub-association information includes the name of the software and the version number of the software, and the architecture information includes the operating system type and the processor architecture type; The step of determining, in the software compatibility list according to the second-level associated software information and the architecture information corresponding to each node, a plurality of associated software package identifiers corresponding to each node includes: Traversing each piece of sub-associated software information in the target second-level associated software information corresponding to the target node, wherein the target node is any node among the multiple nodes; Each time a sub-associated software information is traversed, a target software name and a target software version number are obtained from the traversed sub-associated software information; Acquire a target associated software package identifier that matches the target software name, the target software version number, and the operating system class and processor architecture type of the target node in the software compatibility list; After traversing all the sub-associated software information in the second-level associated software information corresponding to the target node, a plurality of associated software package identifiers corresponding to the target node are obtained.

4. The method according to any one of claims 1 to 3, characterized in that: The acquiring, according to each associated software package identifier in the target associated software package identifier list, associated software packages corresponding to each associated software package identifier respectively comprises: According to each associated software package identifier included in the target associated software package identifier list, acquiring a storage path corresponding to each associated software package identifier from the software compatibility list; According to the storage path corresponding to each associated software package identifier, the associated software package corresponding to each associated software package identifier is obtained.

5. A method for installing a software package, characterized in that: The method is applied to a software management system, the software management system includes a software management platform and a heterogeneous cluster, the heterogeneous cluster includes multiple nodes, the method is executed by a client node, wherein the client node is any node among the multiple nodes, and the method includes: Acquire architecture information and software configuration information corresponding to each of the multiple nodes, and send the information to the software management platform, wherein the software management platform generates a total software package identifier corresponding to each node according to the received architecture information and software configuration information corresponding to each node, and sends the total software package identifier to the client node; Receiving a total software package identifier corresponding to each node sent by the software management platform; Divide the nodes with the same overall software package identifier into a group to obtain at least one node group; Selecting a node from a target node group as a target group leader node, wherein the target node group is any node group in at least one node group; The target general software package identifier corresponding to the target node group is sent to the target group leader node, wherein the target group leader node sends the target general software package identifier to the software management platform, and after receiving the target general software package identifier, the software management platform obtains the target general software package corresponding to the target general software package identifier and sends it to the target group leader node, and the target group leader node synchronizes the target software package to other nodes in the target node group except itself, and after receiving the target general software package, all nodes in the target node group install the target general software package.

6. A software package installation device, characterized in that: The device is applied to a software management system, the software management system includes a software management platform and a heterogeneous cluster, the heterogeneous cluster includes a plurality of nodes, and the device includes: A receiving module, used to receive architecture information and software configuration information corresponding to each node sent by the client node; The acquisition module is used to obtain the full software list and software compatibility list; a determination module, configured to determine a list of associated software package identifiers of each node and a total software package identifier corresponding to the list of associated software package identifiers according to the software configuration information and the architecture information corresponding to each node, the full software list, and the software compatibility list; A sending module, configured to send a total software package identifier corresponding to each node to the client node, wherein the client node groups multiple nodes according to the total software package identifier corresponding to each node to obtain at least one node group, and selects a group leader node for each node group; The receiving module is further configured to receive a software package acquisition request sent by a target group leader node, wherein the software package acquisition request includes a target total software package identifier corresponding to the target group leader node, and the target group leader node is any one of the at least one group leader node; a selection module, configured to select, according to the target general software package identifier, a target associated software package identifier list corresponding to the target general software package identifier from the determined associated software package identifier list of each node, wherein the target associated software package identifier list includes a plurality of associated software package identifiers; The acquisition module is further configured to acquire, according to each associated software package identifier in the target associated software package identifier list, an associated software package corresponding to each associated software package identifier; The sending module is further used to generate a target master software package based on the acquired multiple associated software packages, and send it to the target group leader node, wherein the target group leader node synchronizes the target master software package to other nodes in the target node group except itself, and all nodes in the target node group install the target software package after receiving the target master software package.

7. A software package installation device, characterized in that: The device is applied to a software management system, the software management system includes a software management platform and a heterogeneous cluster, the heterogeneous cluster includes a plurality of nodes, and the device includes: A receiving module, used to receive a total software package identifier corresponding to each node sent by the software management platform; A division module, used for dividing the nodes with the same general software package identifier into a group to obtain at least one node group; A selection module, used to select a node from a target node group as a target group leader node, wherein the target node group is any node group in at least one node group; A sending module is used to send the target general software package identifier corresponding to the target node group to the target group leader node, wherein the target group leader node sends the target general software package identifier to the software management platform, and after receiving the target general software package identifier, the software management platform obtains the target general software package corresponding to the target general software package identifier and sends it to the target group leader node, and the target group leader node synchronizes the target software package to other nodes in the target node group except itself, and after receiving the target general software package, all nodes in the target node group install the target general software package.

8. A software management platform, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the software package installation method according to any one of claims 1 to 4 by executing the computer instructions.

9. A client node, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the software package installation method according to claim 5 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, which are used to enable a software management platform to execute the software package installation method described in any one of claims 1 to 4, or the computer-readable storage medium stores computer instructions, which are used to enable a client node to execute the software package installation method described in claim 5.