CN110099095B - Software deployment method and device, electronic equipment and computer-readable storage medium - Google Patents

Software deployment method and device, electronic equipment and computer-readable storage medium Download PDF

Info

Publication number
CN110099095B
CN110099095B CN201910153067.1A CN201910153067A CN110099095B CN 110099095 B CN110099095 B CN 110099095B CN 201910153067 A CN201910153067 A CN 201910153067A CN 110099095 B CN110099095 B CN 110099095B
Authority
CN
China
Prior art keywords
server
stand
deployment
information
deployment file
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910153067.1A
Other languages
Chinese (zh)
Other versions
CN110099095A (en
Inventor
黎水秀
雷鸣春
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Information Technologies Co Ltd
Original Assignee
New H3C Information Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Information Technologies Co Ltd filed Critical New H3C Information Technologies Co Ltd
Priority to CN201910153067.1A priority Critical patent/CN110099095B/en
Publication of CN110099095A publication Critical patent/CN110099095A/en
Application granted granted Critical
Publication of CN110099095B publication Critical patent/CN110099095B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a software deployment method, a software deployment device, electronic equipment and a computer readable storage medium, and relates to the technical field of stand-alone management, wherein the method comprises the following steps: sending request information for acquiring a deployment file of the stand-alone management software to a server, and receiving deployment file downloading information fed back by the server aiming at the request information; downloading the deployment file of the stand-alone management software from the server based on the received deployment file downloading information; and deploying the stand-alone management software at a local node based on the downloaded deployment file of the stand-alone management software so as to perform local stand-alone management on the local node by using the stand-alone management software. The present disclosure provides a software deployment method, device, electronic device, and computer-readable storage medium, which save the storage space of a local nonvolatile memory and improve the management convenience of local stand-alone management software.

Description

Software deployment method and device, electronic equipment and computer-readable storage medium
Technical Field
The present disclosure relates to the field of local stand-alone management technologies, and in particular, to a software deployment method and apparatus, an electronic device, and a computer-readable storage medium.
Background
At present, a server generally includes a server and at least one node, where each node connected to the server stores local desktop management software in a local non-volatile memory, and when performing local desktop management on a node, reads and deploys the local desktop management software from the local non-volatile memory.
However, the storage space of the local nonvolatile memory of the node is limited, and when the local stand-alone management software is updated, each node connected to the server needs to be updated one by one, which is inconvenient for managing the local stand-alone management software.
Disclosure of Invention
In view of this, an object of the present disclosure is to provide a software deployment method, an apparatus, an electronic device, and a computer-readable storage medium, which save the storage space of a local nonvolatile memory and improve the management convenience of local stand-alone management software.
In a first aspect, an embodiment of the present disclosure provides a software deployment method, applied to a client, including:
sending request information for acquiring a deployment file of the stand-alone management software to a server, and receiving deployment file downloading information fed back by the server aiming at the request information;
downloading the deployment file of the stand-alone management software from the server based on the received deployment file downloading information;
and deploying the stand-alone management software at a local node based on the downloaded deployment file of the stand-alone management software so as to perform local stand-alone management on the local node by using the stand-alone management software.
In a second aspect, an embodiment of the present disclosure further provides a software deployment method, applied to a server, including:
receiving request information for acquiring a deployment file of the stand-alone management software, which is sent by a client;
based on the request information, sending deployment file downloading information to a client so that the client generates a file downloading request based on the deployment file downloading information;
and sending the deployment file of the stand-alone management software to a client based on the file downloading request.
In a third aspect, an embodiment of the present disclosure further provides a software deploying apparatus, applied to a client, including:
the sending module is used for sending request information for acquiring a deployment file of the stand-alone management software to the server;
the receiving module is used for receiving the deployment file downloading information fed back by the server aiming at the request information;
the download module is used for downloading the deployment file of the stand-alone management software from the server based on the received deployment file download information;
and the deployment module is used for deploying the stand-alone management software at a local node based on the downloaded deployment file of the stand-alone management software so as to perform local stand-alone management on the local node by using the stand-alone management software.
In a fourth aspect, an embodiment of the present disclosure further provides a software deployment apparatus, applied to a server, including:
the receiving module is used for receiving request information sent by a client for acquiring a deployment file of the stand-alone management software;
the sending module is used for sending deployment file downloading information to a client based on the request information so that the client generates a file downloading request based on the deployment file downloading information; and the system is also used for sending the deployment file of the stand-alone management software to a client based on the file downloading request.
In a fifth aspect, an embodiment of the present disclosure further provides an electronic device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the electronic device is running, the machine-readable instructions when executed by the processor performing the steps of the first aspect or any of the possible implementations of the first aspect, and the second aspect or any of the possible implementations of the second aspect.
In a sixth aspect, the disclosed embodiments also provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, performs the steps in the first aspect or any one of the possible implementations of the first aspect, and any one of the possible implementations of the second aspect or the second aspect.
According to the software deployment method, the software deployment device, the electronic equipment and the computer readable storage medium, the single machine management software is stored in the server, when local single machine management is carried out on the server node, the local single machine management software is read from the server and is deployed in the local node, and compared with the prior art that the single machine management software is stored in a nonvolatile memory of the server node, the storage space of a local nonvolatile memory is saved. And when the local stand-alone management software is updated, compared with the prior art that each node connected with the server needs to be updated one by one, the local stand-alone management software stored in the server only needs to be updated, so that the management convenience of the local stand-alone management software is improved.
In order to make the aforementioned objects, features and advantages of the present disclosure more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
To more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present disclosure and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings may be obtained from the drawings without inventive effort.
Fig. 1 shows a schematic structural diagram of a server to which the embodiment of the present disclosure is applied;
FIG. 2 is a flow chart illustrating a method for deploying software provided by an embodiment of the present disclosure;
FIG. 3 is a flow chart illustrating another software deployment method provided by an embodiment of the present disclosure;
FIG. 4 is a flow chart illustrating another software deployment method provided by an embodiment of the present disclosure;
FIG. 5 is a schematic structural diagram of a software deploying apparatus provided in an embodiment of the present disclosure;
FIG. 6 is a schematic structural diagram of another software deploying apparatus provided in the embodiments of the present disclosure;
fig. 7 shows a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure;
fig. 8 shows a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, not all of the embodiments. The components of the embodiments of the present disclosure, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present disclosure, presented in the figures, is not intended to limit the scope of the claimed disclosure, but is merely representative of selected embodiments of the disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the disclosure without making creative efforts, shall fall within the protection scope of the disclosure.
As shown in fig. 1, an existing server 100, such as a blade server, a tower server, etc., generally includes a server 101 and at least one node 102. The server can be roughly divided into two functions: a switch function module 111 (switch, SW) and an administration function module 112(OAManager, OM), the server 101 is connected to at least one node 102 through the SW111, the server 101 can communicate with each node 102, and the server 101 can also communicate with the external server 103 through the SW111 as long as the external network is connected to the server 101.
Here, one node 102 is a server unit, and specifically, for a blade server, one node 102 is a card server unit.
At present, a node 102 connected to a server 101 implements functions of configuring a disk Array (RAID), installing an operating system, installing a driver, diagnosing equipment, and the like through a stand-alone management software, such as an integrated Fast Intelligent Scalable Toolkit (ifst), so as to implement basic RAID configuration and operating system installation on a server 100.
The desktop management software is stored in a nonvolatile memory, such as nand flash, of the server 100, and does not occupy a hard disk space provided by the server 100 for a user, however, the storage space of the nonvolatile memory, such as nand flash, is limited, such as nand flash only has 4G, and the nand flash is virtually divided into 4 partitions, each of which has a respective purpose, and the partition capacity that can be allocated to the desktop management software is less than 2 GB. And with the continuous increase of the functions of the stand-alone management software, the space occupied by the stand-alone management software is also continuously increased, and the problem of insufficient storage space may exist. And each node 102 connected to the server 101 needs to perform local stand-alone management, so each node 102 needs to install and run local stand-alone management software, and if the version of the local stand-alone management software needs to be updated, each node 102 connected to the server needs to be updated one by one, which is inconvenient for the management of the local stand-alone management software.
Based on this, the embodiments of the present disclosure provide a software deployment method, apparatus, electronic device, and computer-readable storage medium, where the single-machine management software is stored in a server, and when performing local single-machine management on a server node, the local single-machine management software is read from the server and deployed locally in the node of the server. And when the local stand-alone management software is updated, compared with the prior art that each node connected with the server needs to be updated one by one, the local stand-alone management software stored in the server only needs to be updated, so that the management convenience of the local stand-alone management software is improved.
To facilitate understanding of the present embodiment, a detailed description is first given of a software deployment method disclosed in the embodiments of the present disclosure.
Example one
The software deployment method provided by the embodiment of the disclosure can be applied to any server comprising a server with a management function and at least one node, such as a blade server, a tower server, and the like. As shown in fig. 2, the software deployment method provided in the embodiment of the present disclosure is applied to a client in a node connected to a server, and includes:
s201: sending request information for acquiring a deployment file of the stand-alone management software to a server, and receiving deployment file downloading information fed back by the server according to the request information.
In an existing server structure, a server side of a server usually includes a management function module, where the management function module may be implemented by a management board, and a preboot execution environment (PXE) is installed on the management board, where the PXE usually includes a Dynamic Host Configuration Protocol (DHCP) server and at least one file transfer Protocol server. Wherein, the DHCP server mainly comprises the following functions: the method is used for automatically allocating an Internet Protocol Address (IP Address) to each node in an internal network formed by a server and each node connected with the server; the method is used for performing central management on all nodes in an internal network formed by a server and each node connected with the server. The File Transfer Protocol server is used for transmitting files between the server and the node, and the File Transfer Protocol server may use a File Transfer Protocol (FTP), a simple File Transfer Protocol (TFTP), or a Hypertext Transfer Protocol (HTTP).
In order to send request information for acquiring the deployment file of the stand-alone management software to the server, the client included in the node sends request information for the DHCP server to the PXE installed in the server. In the specific implementation, since the node does not know the location of the DHCP server when it starts working, the node sends a two-layer broadcast message DHCP Discover and waits for the response of the DHCP server of the server. Since the DHCP Discover message sent by the node is a broadcast message, not only the DHCP server on the server side located in the same server as the node receives the broadcast message, but also the external DHCP server receives the broadcast message if the node is connected to the external DHCP server through the SW. In order to avoid interference caused by an external DHCP server, the request information sent in the embodiment of the present disclosure carries first preset identity information, so that the server performs identity authentication based on the first preset identity information, and feeds back the deployment file download information when the identity authentication is passed. Specifically, for example, a DHCP Discover message carrying a customized option a (option a) may be sent as the request information. And then, receiving deployment file downloading information fed back by the server aiming at the request information carrying the first preset identity information. The external DHCP server cannot identify the first preset identity information, and therefore cannot feed back the deployment file downloading information meeting the preset requirements.
S202: and downloading the deployment file of the stand-alone management software from the server based on the received deployment file downloading information.
In order to distinguish the deployment file download information fed back by the external DHCP server after receiving the request information, in the software deployment method provided in the embodiment of the present disclosure, the deployment file download information fed back by the DHCP server on the internal server carries second preset identity information. Therefore, after receiving the deployment file download information fed back by the server for the request information, the node needs to determine whether the deployment file download information carries second preset identity information; and downloading the deployment file of the stand-alone management software from the server based on the deployment file downloading information when the deployment file downloading information carries second preset identity information. Specifically, the deployment file download information fed back by the DHCP server on the server is a DHCP Offer message, the second identity preset message is a self-defined Option B (Option B) carried in the DHCP Offer message, and when the DHCP Offer message carries the Option B, the deployment file of the standalone management software is downloaded from the server based on the received deployment file download information. And if the DHCP Offer message does not carry the Option B, discarding the message.
The deployment file downloading information comprises: the image name of the deployment file and the address of the server where the deployment file is located. In addition, the method can also comprise the following steps: the DHCP server on the server side distributes an IP address for a local node sending request information, the local node establishes a service port communication network port based on the IP address, and communication connection is established between the server side and the local node through the IP address.
In the embodiment of the present disclosure, the image file of the desktop management software is stored in the memory of the server, and specifically, in the case that the ifst software is deployed and run by the local node, the image file of the ifst software is stored in the memory of the server. And the local node sends a downloading request to the server based on the image name of the deployment file and the address of the server where the deployment file is located, which are included in the deployment file downloading information, so that the deployment file of the stand-alone management software is downloaded from the server.
S203: and deploying the stand-alone management software at a local node based on the downloaded deployment file of the stand-alone management software so as to perform local stand-alone management on the local node by using the stand-alone management software.
Specifically, under the condition that the local node deploys and runs the ifst software, the downloaded deployment file of the single machine management software may include a kernel file of the ifst software, the ifst software is deployed based on the kernel file of the ifst software, the ifst software may be run after the deployment is completed, and the ifst software is used to perform local single machine management on the local node, for example, to implement functions of configuring an RAID, installing an operating system, installing a driver, diagnosing equipment, and the like.
The embodiment of the disclosure provides a software deployment method, which is characterized in that single-machine management software is stored in a server, and when local single-machine management is performed on a server node, the local single-machine management software is read from the server and is deployed in the node local of the server, so that the storage space of a local nonvolatile memory is saved, and the management convenience of the local single-machine management software is improved.
Example two
As shown in fig. 3, the software deployment method provided by the embodiment of the present disclosure is applied to a server, and includes:
s301: and receiving request information for acquiring the deployment file of the stand-alone management software, which is sent by the client.
Here, the client is included in a node connected to the server, and the server receives request information for acquiring the deployment file of the desktop management software sent by the client in the node. In specific implementation, when the node starts to work, the node does not know the location of the DHCP server, so that the node sends a two-layer broadcast message DHCP Discover at this time, and the received request information is a broadcast message DHCP Discover at this time.
S302: and sending deployment file downloading information to the client based on the request information so that the client generates a file downloading request based on the deployment file downloading information.
In order to avoid interference caused by an external DHCP server, request information sent by a client carries first preset identity information, and therefore, a server needs to first judge whether the deployment file download information carries the first preset identity information; and when the deployment file downloading information carries first preset identity information, sending the deployment file downloading information to a client. Specifically, the first preset identity information is a self-defined option a (option a) carried in a DHCP Discover message. And when the DHCP Discover message carries the Option A, sending deployment file downloading information to the client based on the request information. And if the DHCP Discover message does not carry the Option A, the server does not respond.
The server side sends deployment file downloading information to the client side based on the request information, wherein the deployment file downloading information comprises: the image name of the deployment file and the address of the server where the deployment file is located. The deployment file downloading information further comprises: and the DHCP server on the server side allocates an IP address for the node where the client side sending the request information is located. And establishing communication connection between the server and the node where the client sending the request information is located through the IP address. The deployment file downloading information further comprises: and second preset identity information so that the client generates a file downloading request based on the second identity information. And receiving a file downloading request sent by a node where the client sending the request information is located through the communication connection.
S303: and sending the deployment file of the stand-alone management software to a client based on the file downloading request.
Here, each time the server receives a file download request, the server sends the deployment file of the stand-alone management software corresponding to the file download request to the client.
The embodiment of the disclosure provides a software deployment method, which is characterized in that single-machine management software is stored in a server, and when local single-machine management is performed on a server node, the local single-machine management software is read from the server and is deployed in the node local of the server, so that the storage space of a local nonvolatile memory is saved, and the management convenience of the local single-machine management software is improved.
EXAMPLE III
Fig. 4 shows a software deployment method provided by a third embodiment of the present disclosure, which is specifically applied to a process and data transmission when ifst software is deployed, and includes:
s401: and the client on the node sends request information for acquiring the deployment file of the stand-alone management software.
In specific implementation, when a user needs to start the desktop management software On the local node, for example, the ifst software, the server needs to be started or restarted, and the ifst software is started according to F10 On a Basic Input Output System Power-On-Self-Test (BIOS POST) interface. After selecting the Launch iFIST option to start the iFIST software, the client on the node sends a request message for acquiring the deployment file of the stand-alone management software to the management board OA of the server, wherein the request file comprises a DHCP Dicsover message.
S402: and the DHCP server judges whether the request information is legal request information.
In the implementation, the request information is sent to the PXE installed on the management board OA of the server, and the DHCP server in the PXE serves as a management unit to receive the request information and determine whether the request information is legal. The legal request information includes a DHCP Discover broadcast message, and the DHCP Discover broadcast message carries an options.
And under the condition that the request information is a DHCP Discover broadcast message and carries an Option option, returning deployment file downloading information to the client of the node, and if the request information is not legal request information, not returning any information by a DHCP server on the server.
S403: and the DHCP server returns the download information of the deployment file.
In specific implementation, the deployment file downloading information includes: the system comprises an IP address, second preset identity information, a mirror image name of iFIST software and an address of a server where an iFIST software mirror image is located, wherein the IP address is distributed to a node where a client side sending request information is located. And establishing communication connection between the server and the node where the client sending the request information is located through the IP address.
S404: a client on a node requests to transmit a bootstrap.
In specific implementation, the legal deployment file downloading information is a DHCP Offer message carrying a customized Option B, the client on the node verifies second preset identity information in the deployment file downloading information, and if the deployment file downloading information carries the Option B, a downloading request is generated based on a mirror name of ifst software and an address of a server where an ifst software mirror image is located, which are included in the deployment file downloading information. Firstly, a download request for bootstrap is generated and sent to a file transfer protocol server TFTP of a server side.
S405: the TFTP server asks whether it is agreed to transmit data of the specified transport block size.
The TFTP server of the server inquires whether the client on the node agrees to transmit the data with the specified transmission block size, and the data with the specified transmission block size is the data of bootstrap.
S406: the client on the node sends an approval instruction.
And the client on the node sends an agreement instruction for agreeing to transmit bootstrap to the TFTP server of the server.
S407: the TFTP server sends bootstrap.
After receiving the agreement instruction sent by the client on the node, the TFTP server of the server side sends bootstrap to the client on the node. The size of the bootstrap is sent as the size of the specified transport block.
S408: the client on the node executes bootstrap.
The client on the node executes bootstrap. Pxelinux.0 was installed.
S409: a client on a node requests a transfer of a configuration file.
A client on a node sends a download file request for transmitting a configuration file pxelinux.config to a TFTP server of a server.
S410: the client on the node reads the configuration file.
And after receiving the configuration file sent by the TFTP server of the server, reading the configuration file.
S411: the client on the node requests to transmit the Linux kernel.
And the client on the node sends a file downloading request for transmitting the Linux kernel to the TFTP server of the server. The Linux kernel is a Linux kernel part in an iFIST software deployment file.
S412: the TFTP server sends the Linux kernel.
And the TFTP server of the server side sends the Linux kernel to the client side on the node.
S413: the client on the node requests to transmit the Linux root file system.
And the client on the node sends a file downloading request for transmitting the Linux root file system to the TFTP server of the server. The Linux root file system is a Linux root file system part in an iFIST software deployment file.
S414: the TFTP server sends a Linux root file system.
And the TFTP server of the server side sends a Linux root file system to the client side on the node.
S415: the client on the node runs the ifst software.
And starting a Linux kernel in the parameter iFIST software deployment file configured by the configuration file so as to start the mirror image of the iFIST software, so that the iFIST software can be used for configuring the RAID, installing an operating system, installing a driver, diagnosing equipment and the like.
The embodiment of the disclosure provides a software deployment method, which is characterized in that single-machine management software is stored in a server, and when local single-machine management is performed on a server node, the local single-machine management software is read from the server and is deployed in the node local of the server, so that the storage space of a local nonvolatile memory is saved, and the management convenience of the local single-machine management software is improved.
Based on the same technical concept, embodiments of the present disclosure also provide a software deployment apparatus, an electronic device, a computer storage medium, and the like, which can be specifically referred to in the following embodiments.
Example four
As shown in fig. 5, a software deploying apparatus provided in the embodiment of the present disclosure is applied to a client, and includes:
a sending module 501, configured to send request information for obtaining a deployment file of the stand-alone management software to a server;
a receiving module 502, configured to receive deployment file downloading information fed back by the server for the request information;
a downloading module 503, configured to download the deployment file of the standalone management software from the server based on the received deployment file downloading information;
the deployment module 504 is configured to deploy the desktop management software at a local node based on the downloaded deployment file of the desktop management software, so as to perform local desktop management on the local node by using the desktop management software.
In a possible implementation manner, the request information carries first preset identity information, so that the server performs identity authentication based on the first preset identity information, and feeds back the deployment file download information when the identity authentication is passed.
In a possible implementation manner, the downloading module 503 is further configured to:
judging whether the deployment file downloading information carries second preset identity information or not;
and when the deployment file downloading information carries second preset identity information, downloading the deployment file of the stand-alone management software from the server based on the deployment file downloading information.
In one possible embodiment, the deployment file downloading information includes: the image name of the deployment file and the address of the server where the deployment file is located.
The embodiment of the disclosure provides a software deployment device, which stores single machine management software in a server, reads the local single machine management software from the server when performing local single machine management on a server node, and deploys the local single machine management software in the node local of the server, so that the storage space of a local nonvolatile memory is saved, and the management convenience of the local single machine management software is improved.
EXAMPLE five
As shown in fig. 6, an embodiment of the present disclosure further provides a software deployment apparatus, applied to a server, including:
a receiving module 601, configured to receive request information sent by a client to obtain a deployment file of a stand-alone management software;
a sending module 602, configured to send deployment file downloading information to a client based on the request information, so that the client generates a file downloading request based on the deployment file downloading information; and the system is also used for sending the deployment file of the stand-alone management software to a client based on the file downloading request.
In a possible implementation manner, the request information carries first preset identity information.
The sending module 602 is further configured to:
judging whether the deployment file downloading information carries first preset identity information or not;
and when the deployment file downloading information carries first preset identity information, sending the deployment file downloading information to a client.
In one possible embodiment, the deployment file downloading information includes: and second preset identity information so that the client generates a file downloading request based on the second identity information.
The embodiment of the disclosure provides a software deployment device, which stores single machine management software in a server, reads the local single machine management software from the server when performing local single machine management on a server node, and deploys the local single machine management software in the node local of the server, so that the storage space of a local nonvolatile memory is saved, and the management convenience of the local single machine management software is improved.
EXAMPLE six
Referring to fig. 7, an electronic device 700 provided by the embodiment of the present disclosure includes a processor 701, a memory 702, and a bus 703.
The memory 702 stores machine-readable instructions executable by the processor 701 (such as execution instructions corresponding to the sending module 501, the receiving module 502, the downloading module 503, and the deploying module 504 in fig. 5, etc.), when the electronic device 700 is operated, the processor 701 communicates with the memory 702 through the bus 703, and when the processor 701 executes the following processes:
sending request information for acquiring a deployment file of the stand-alone management software to a server, and receiving deployment file downloading information fed back by the server aiming at the request information;
downloading the deployment file of the stand-alone management software from the server based on the received deployment file downloading information;
and deploying the stand-alone management software at a local node based on the downloaded deployment file of the stand-alone management software so as to perform local stand-alone management on the local node by using the stand-alone management software.
The specific processing flow of the processor 701 may refer to the description of the first embodiment, and is not described herein again.
Referring to fig. 8, an electronic device 800 provided by the embodiment of the present disclosure includes a processor 801, a memory 802, and a bus 803.
The memory 802 stores machine-readable instructions executable by the processor 801 (such as execution instructions corresponding to the receiving module 601 and the sending module 602 in fig. 6, etc.), when the electronic device 800 operates, the processor 801 communicates with the memory 802 via the bus 803, and when the processor 801 executes the following processes:
receiving request information for acquiring a deployment file of the stand-alone management software, which is sent by a client;
based on the request information, sending deployment file downloading information to a client so that the client generates a file downloading request based on the deployment file downloading information;
and sending the deployment file of the stand-alone management software to a client based on the file downloading request.
The specific processing flow of the processor 801 may refer to the description of the above embodiments, and is not described herein again.
The electronic equipment provided by the embodiment of the disclosure stores the single machine management software in the server, and when local single machine management is performed on the server node, the local single machine management software is read from the server and deployed locally in the node of the server, so that the storage space of a local nonvolatile memory is saved, and the management convenience of the local single machine management software is improved.
EXAMPLE seven
The embodiment of the present disclosure further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program executes the steps of the software deployment method in the first embodiment, the software deployment method in the second embodiment, and/or the software deployment method in the third embodiment.
Specifically, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, or the like, and when a computer program on the storage medium is executed, the location retrieval method can be executed, so that the standalone management software is stored in the server, and when local standalone management is performed on the server node, the local standalone management software is read from the server and deployed in the node local of the server, thereby saving the storage space of the local nonvolatile memory and improving the management convenience of the local standalone management software.
The computer program product for performing the software deployment method provided in the embodiment of the present disclosure includes a computer-readable storage medium storing a nonvolatile program code executable by a processor, where instructions included in the program code may be used to execute the method described in the foregoing method embodiment, and specific implementation may refer to the method embodiment, which is not described herein again.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present disclosure. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Finally, it should be noted that: the above-mentioned embodiments are merely specific embodiments of the present disclosure, which are used for illustrating the technical solutions of the present disclosure and not for limiting the same, and the scope of the present disclosure is not limited thereto, and although the present disclosure is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive of the technical solutions described in the foregoing embodiments or equivalent technical features thereof within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present disclosure, and should be construed as being included therein. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims (11)

1. A software deployment method is applied to a client and comprises the following steps:
when local stand-alone management is carried out on a local node of a server, request information for acquiring a deployment file of stand-alone management software is sent to a server side storing the stand-alone management software, and the deployment file downloading information fed back by the server side aiming at the request information is received; the server local node and the server belong to the same server;
downloading the deployment file of the stand-alone management software from the server based on the received deployment file downloading information;
and deploying the stand-alone management software at a local node based on the downloaded deployment file of the stand-alone management software so as to perform local stand-alone management on the local node by using the stand-alone management software.
2. The method according to claim 1, wherein the request information carries first preset identity information, so that the server performs identity authentication based on the first preset identity information, and feeds back the deployment file download information when the identity authentication is passed.
3. The method according to claim 1, wherein the downloading the deployment file of the desktop management software from the server based on the received deployment file downloading information comprises:
judging whether the deployment file downloading information carries second preset identity information or not;
and when the deployment file downloading information carries second preset identity information, downloading the deployment file of the stand-alone management software from the server based on the deployment file downloading information.
4. The method of claim 1, wherein the deployment file download information comprises: the image name of the deployment file and the address of the server where the deployment file is located.
5. A software deployment method is applied to a server and comprises the following steps:
the server side stores stand-alone management software, and receives request information for acquiring a deployment file of the stand-alone management software, which is sent by the client side, when local stand-alone management is performed on a local node of the server; the server side and the local node of the server belong to the same server;
based on the request information, sending deployment file downloading information to a client so that the client generates a file downloading request based on the deployment file downloading information;
and sending the deployment file of the stand-alone management software to a client based on the file downloading request.
6. The method of claim 5, wherein the request message carries a first default identity message,
the sending of the deployment file download information to the client based on the request information includes:
judging whether the deployment file downloading information carries first preset identity information or not;
and when the deployment file downloading information carries first preset identity information, sending the deployment file downloading information to a client.
7. The method of claim 5, wherein the deployment file download information comprises: and second preset identity information so that the client generates a file downloading request based on the second preset identity information.
8. A software deployment device, applied to a client, includes:
the sending module is used for sending request information for acquiring a deployment file of the stand-alone management software to a server side storing the stand-alone management software when local stand-alone management is carried out on a local node of the server; the server local node and the server belong to the same server;
the receiving module is used for receiving the deployment file downloading information fed back by the server aiming at the request information;
the download module is used for downloading the deployment file of the stand-alone management software from the server based on the received deployment file download information;
and the deployment module is used for deploying the stand-alone management software at a local node based on the downloaded deployment file of the stand-alone management software so as to perform local stand-alone management on the local node by using the stand-alone management software.
9. A software deployment device is applied to a server, wherein the server stores a stand-alone management software, and comprises:
the receiving module is used for receiving request information which is sent by a client and used for acquiring a deployment file of the stand-alone management software when local stand-alone management is carried out on a local node of the server; the server side and the local node of the server belong to the same server;
the sending module is used for sending deployment file downloading information to a client based on the request information so that the client generates a file downloading request based on the deployment file downloading information; and the system is also used for sending the deployment file of the stand-alone management software to a client based on the file downloading request.
10. An electronic device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when the electronic device is operating, the machine-readable instructions when executed by the processor performing the steps of the software deployment method of any of claims 1 to 4 or any of claims 5 to 7.
11. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, performs the steps of the software deployment method of any one of claims 1 to 4 or of any one of claims 5 to 7.
CN201910153067.1A 2019-02-28 2019-02-28 Software deployment method and device, electronic equipment and computer-readable storage medium Active CN110099095B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910153067.1A CN110099095B (en) 2019-02-28 2019-02-28 Software deployment method and device, electronic equipment and computer-readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910153067.1A CN110099095B (en) 2019-02-28 2019-02-28 Software deployment method and device, electronic equipment and computer-readable storage medium

Publications (2)

Publication Number Publication Date
CN110099095A CN110099095A (en) 2019-08-06
CN110099095B true CN110099095B (en) 2022-04-08

Family

ID=67443961

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910153067.1A Active CN110099095B (en) 2019-02-28 2019-02-28 Software deployment method and device, electronic equipment and computer-readable storage medium

Country Status (1)

Country Link
CN (1) CN110099095B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111628889B (en) * 2020-05-11 2023-04-07 Oppo(重庆)智能科技有限公司 Heat deployment method and device, electronic device, and storage medium
CN111625828B (en) * 2020-07-29 2021-02-26 杭州海康威视数字技术股份有限公司 Lesovirus defense method and device and electronic equipment
CN112346766A (en) * 2020-11-10 2021-02-09 交控科技股份有限公司 Dynamic deployment method and system of vehicle-mounted application software
CN113645068B (en) * 2021-08-06 2023-11-10 福建星网视易信息系统有限公司 Method for realizing automatic deployment and computer readable storage medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8843238B2 (en) * 2011-09-30 2014-09-23 Johnson Controls Technology Company Systems and methods for controlling energy use in a building management system using energy budgets
CN107526618A (en) * 2017-09-04 2017-12-29 深圳互联先锋科技有限公司 system installation method and device

Also Published As

Publication number Publication date
CN110099095A (en) 2019-08-06

Similar Documents

Publication Publication Date Title
CN110099095B (en) Software deployment method and device, electronic equipment and computer-readable storage medium
CN112087493B (en) Request processing method, system on chip and public cloud management component
CN104360883B (en) A kind of configuration Raid method and system
CN108833163B (en) Linux virtual server creating method and device, computer equipment and storage medium
US7802084B2 (en) System and method for management and installation of operating system images for computers
CN109992311B (en) Starting method and device of operating system, storage medium and client
CN104572372A (en) System and method for building server performance testing environment
CN109840096B (en) Installation method and device of operating system
CN106657444B (en) A kind of method and device for the IP address configuring BMC
CN103024079B (en) Obtain the method for server resource information, resource pool management system and server
CN106873970B (en) Installation method and device of operating system
CN108540509B (en) Processing method and device of terminal browser, server and intelligent terminal
CN113282342A (en) Deployment method, device, system, electronic equipment and readable storage medium
CN111078305A (en) Information acquisition method and device, server and information management system
CN115080479B (en) Transmission method, server, device, bare metal instance and baseboard management controller
CN110753119A (en) Application package deployment system based on K8s cluster
CN110971689A (en) System installation method, device, system, equipment and storage medium
EP3091435A1 (en) Resource management method and device for terminal system
CN111061496A (en) PXE installation method and device for Linux operating system
CN114860271A (en) PXE starting method, system and device and readable storage medium
CN111124437A (en) Bare computer resource configuration information acquisition method, system and equipment based on OpenStack
CN110633086B (en) Blade server
KR20150029916A (en) Apparatus and method for setting up computting environments
CN113268253A (en) Distributed database deployment method and related equipment
CN109669699B (en) Application program distribution method, wireless controller and wireless access point

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant