CN112799681A - Task deployment method, system, electronic equipment and storage medium - Google Patents
Task deployment method, system, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112799681A CN112799681A CN202110145597.9A CN202110145597A CN112799681A CN 112799681 A CN112799681 A CN 112799681A CN 202110145597 A CN202110145597 A CN 202110145597A CN 112799681 A CN112799681 A CN 112799681A
- Authority
- CN
- China
- Prior art keywords
- deployment
- task
- target
- deployed
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000008569 process Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 7
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a task deployment method, a system, an electronic device and a storage medium, wherein the task deployment method comprises the following steps: the rapid deployment subsystem generates a task to be deployed based on received task deployment information input by a user, acquires a corresponding target file, determines a target deployment server based on the task deployment information, and sends a query instruction to a deployment springboard corresponding to the target deployment server; the deployment springboard sends the acquired deployed file to the rapid deployment subsystem according to the query instruction; the rapid deployment subsystem compares the target file with the deployed file and determines whether to redeploy the target deployment server; if so, the rapid deployment subsystem deploys the target file in the target deployment server. Therefore, the rapid deployment subsystem determines the deployment springboard corresponding to the target deployment server through the task to be deployed and directly deploys the target task to the target deployment server through the deployment springboard, so that the deployment efficiency and the deployment convenience are improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a task deployment method, system, electronic device, and storage medium.
Background
The system administrator or operation and maintenance personnel can log in the board jump machine firstly and then log in a remote server through the board jump machine.
Deployment means that the developed product can run in a certain environment. However, in the prior art, the external network cannot be directly connected to the internal network, when a large number of tasks need to be remotely deployed, a trigger needs to be logged in first for authentication, the target server can be operated after the authentication is passed, and the steps need to be repeated each time the tasks are deployed. Obviously, this deployment approach is very time consuming and presents the problem of inefficient deployment.
Disclosure of Invention
In view of this, an object of the present application is to provide a task deployment method, a task deployment system, an electronic device, and a storage medium, in which a rapid deployment subsystem determines a deployment springboard corresponding to a target deployment server through a generated task to be deployed, directly deploys the target task to the target deployment server through the deployment springboard, and a springboard authentication operation is not required to be repeatedly performed every time task deployment is performed, so that deployment efficiency and convenience of deployment are improved.
The embodiment of the application provides a task deployment method, which comprises the following steps:
the rapid deployment subsystem generates a task to be deployed based on received task deployment information input by a user and acquires a target file corresponding to the task to be deployed;
the rapid deployment subsystem determines a target deployment server of the task to be deployed based on the task deployment information and sends a query instruction to a deployment springboard corresponding to the target deployment server;
the deployment springboard responds to the query instruction, obtains a deployed file in the target deployment server, and sends the deployed file to the rapid deployment subsystem;
the rapid deployment subsystem compares the target file with the deployed file and determines whether to redeploy the target deployment server;
if so, the rapid deployment subsystem deploys the target file in the target deployment server through the deployment springboard.
Further, the target file corresponding to the task to be deployed is obtained through the following steps:
the rapid deployment subsystem pulls a code to be deployed corresponding to the task to be deployed from a pre-constructed code library according to task deployment information corresponding to the task to be deployed;
and the rapid deployment subsystem compiles and packages the code to be deployed to generate a target file corresponding to the task to be deployed.
Further, the rapid deployment subsystem deploys the target file in the target deployment server through the deployment springboard, including:
the rapid deployment subsystem sends the target file to the target deployment server through the deployment springboard;
and the deployment springboard runs the target file based on a secure shell protocol to end the process of the deployed file.
Further, the fast deploying subsystem sends the target file to the target deploying server through the deploying springboard, and includes:
the deployment springboard receives the target file transmitted by the rapid deployment subsystem based on a secure socket protocol;
and the deployment springboard sends the target file to the target deployment server based on a secure shell protocol so as to realize the coverage of the deployed file.
Further, the receiving, by the deployment springboard, the target file transmitted by the rapid deployment subsystem based on a secure socket protocol includes:
and the deployment springboard receives the target file transmitted by the rapid deployment subsystem through a firewall and/or a gateway and/or a proxy server based on a secure socket protocol.
Further, the comparing the target file with the deployed file to determine whether to redeploy the target deployment server comprises:
the rapid deployment subsystem compares the creation time of the target file with the creation time of the deployed file;
and when the creation time of the target file is later than that of the deployed file, the target deployment server is redeployed.
The embodiment of the present application further provides a task deployment system, where the task deployment system includes a rapid deployment subsystem and a deployment springboard:
the rapid deployment subsystem is used for generating a task to be deployed based on received task deployment information input by a user, acquiring a target file corresponding to the task to be deployed, determining a target deployment server of the task to be deployed based on the task deployment information, and sending a query instruction to a deployment springboard corresponding to the target deployment server;
the deployment springboard is used for responding to the query instruction, acquiring a deployed file in the target deployment server and sending the deployed file to the rapid deployment subsystem;
the rapid deployment subsystem is further configured to compare the target file with the deployed file, and determine whether to redeploy the target deployment server, and if so, deploy the target file in the target deployment server through the deployment springboard by the rapid deployment subsystem.
Further, when the rapid deployment subsystem is configured to obtain the target file corresponding to the task to be deployed through the following steps, the rapid deployment subsystem is configured to:
pulling a code to be deployed corresponding to the task to be deployed from a pre-constructed code library according to the task deployment information corresponding to the task to be deployed;
compiling and packaging the code to be deployed to generate a target file corresponding to the task to be deployed.
Further, when the task deployment system deploys the target file in the target deployment server through the deployment springboard by using the rapid deployment subsystem, the task deployment system is configured to:
the rapid deployment subsystem sends the target file to the target deployment server through the deployment springboard;
and the deployment springboard runs the target file based on a secure shell protocol to end the process of the deployed file.
Further, when the task deployment system sends the target file to the target deployment server through the deployment springboard by using the rapid deployment subsystem, the task deployment system is configured to:
the deployment springboard receives the target file transmitted by the rapid deployment subsystem based on a secure socket protocol;
and the deployment springboard sends the target file to the target deployment server based on a secure shell protocol so as to realize the coverage of the deployed file.
Further, when the deployment springboard is configured to receive the target file transmitted by the rapid deployment subsystem based on a secure socket protocol, the deployment springboard is configured to:
and receiving the target file transmitted by the rapid deployment subsystem through a firewall and/or a gateway and/or a proxy server based on a secure socket protocol.
Further, when the rapid deployment subsystem is configured to compare the target file with the deployed file and determine whether to redeploy the target deployment server, the rapid deployment subsystem is configured to:
comparing the creation time of the target file with the creation time of the deployed file;
and when the creation time of the target file is later than that of the deployed file, the target deployment server is redeployed.
An embodiment of the present application 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 operating, the machine-readable instructions when executed by the processor performing the steps of the task deployment method as described above.
Embodiments of the present application further provide 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 performs the steps of the task deployment method as described above.
The task deployment method, the system, the electronic device and the storage medium provided by the embodiment of the application comprise the following steps: the rapid deployment subsystem generates a task to be deployed based on received task deployment information input by a user and acquires a target file corresponding to the task to be deployed; the rapid deployment subsystem determines a target deployment server of the task to be deployed based on the task deployment information and sends a query instruction to a deployment springboard corresponding to the target deployment server; the deployment springboard responds to the query instruction, obtains a deployed file in the target deployment server, and sends the deployed file to the rapid deployment subsystem; the rapid deployment subsystem compares the target file with the deployed file and determines whether to redeploy the target deployment server; if so, the rapid deployment subsystem deploys the target file in the target deployment server through the deployment springboard.
Therefore, the rapid deployment subsystem determines the deployment springboard corresponding to the target deployment server through the generated task to be deployed, directly deploys the target task to the target deployment server through the deployment springboard, and does not need to repeatedly perform the authentication operation of the springboard machine when the task is deployed every time, so that the deployment efficiency and the deployment convenience are improved.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, 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 application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a flowchart of a task deployment method according to an embodiment of the present application;
FIG. 2 is a process diagram of task deployment provided herein;
fig. 3 is a schematic structural diagram of a task deployment system according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, 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 application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. Every other embodiment that can be obtained by a person skilled in the art without making creative efforts based on the embodiments of the present application falls within the protection scope of the present application.
Research shows that the prior art cannot be directly connected to an intranet through an external network for task deployment, when a large number of tasks need to be remotely deployed, a trigger jump machine needs to be logged in for authentication, the target server can be operated after the authentication is passed, and the steps need to be repeated when the task deployment is performed every time, so that the problems of long time consumption and low deployment efficiency exist.
Based on this, the embodiment of the application provides a task deployment method, the rapid deployment subsystem determines a deployment springboard corresponding to a target deployment server through a generated task to be deployed, directly deploys the target task to the target deployment server through the deployment springboard, and does not need to repeatedly perform authentication operation of the springboard machine when task deployment is performed every time, so that deployment efficiency and deployment convenience are improved.
Referring to fig. 1, fig. 1 is a flowchart of a task deployment method according to an embodiment of the present disclosure. As shown in fig. 1, a task deployment method provided in an embodiment of the present application includes:
s101, the rapid deployment subsystem generates a task to be deployed based on received task deployment information input by a user and acquires a target file corresponding to the task to be deployed.
In the step, a user logs in a rapid deployment subsystem by inputting an account and a password, and task deployment information is input in the rapid deployment subsystem according to the deployment requirement of the user, so that the rapid deployment subsystem can determine a task to be deployed according to the received task deployment information; and the target file corresponding to the task to be deployed is regenerated by the rapid deployment subsystem.
Here, deployment is to let the product being developed run in a certain environment; the rapid deployment subsystem is a system which is used for a user to log in through an account password and perform operations such as deployment selection, command transmission, file transmission and the like; the deployment requirement is a specific deployment task that a user needs to execute, for example, the user needs to update a program on a certain server; inputting task deployment information, and selecting a certain target deployment server to deploy and selecting specific deployment information options and the like through interface information displayed by a rapid deployment subsystem after a user logs in the rapid deployment subsystem; after the task deployment information is determined, the rapid deployment subsystem receives the task deployment information input by the user, can identify the task deployment information, determines the specific task to be deployed of the user, and then generates a target file of the corresponding task to be deployed according to the determined task to be deployed.
The task to be deployed may be updating a file in a certain server, or may include operations such as deleting a file on a certain server.
Further, the target file corresponding to the task to be deployed is obtained through the following steps: the rapid deployment subsystem pulls a code to be deployed corresponding to the task to be deployed from a pre-constructed code library according to task deployment information corresponding to the task to be deployed; and the rapid deployment subsystem compiles and packages the code to be deployed to generate a target file corresponding to the task to be deployed.
In the step, after the rapid deployment subsystem receives task information corresponding to a task to be deployed, which is input by a user, the rapid deployment subsystem pulls a code to be deployed, which is required by the task to be deployed, from a pre-constructed code library according to the received task deployment information, and after the code to be deployed is pulled, the rapid deployment subsystem compiles and packages the code to be deployed to generate a target file corresponding to the task to be deployed.
Here, the code library is used to store a large amount of code that the developer has written in advance.
And S102, the rapid deployment subsystem determines a target deployment server of the task to be deployed based on the task deployment information and sends a query instruction to a deployment springboard corresponding to the target deployment server.
In the step, after receiving task deployment information input by a user, the rapid deployment subsystem determines on which target deployment server the user specifically needs to execute a deployment task according to the received task deployment information, and then the rapid deployment subsystem sends a query instruction for querying a deployed file on the target server to a deployment springboard connected with the determined target deployment server.
Here, the task deployment information input by the user includes an IP address of the target deployment server, wherein, the rapid deployment subsystem stores IP addresses of all target deployment servers input in advance by developers, managers and other personnel with the authority of operating the rapid deployment subsystem and the connection relation between the target deployment servers and the deployment springboard, and the connection between the rapid deployment subsystem and the deployment springboard is configured in advance, after a user logs in the rapid deployment subsystem by using an account and a password, according to the page display of the rapid deployment subsystem, a user directly selects a certain target deployment server to perform task deployment, the rapid deployment subsystem determines the IP address of the target deployment server and a deployment springboard connected with the target deployment server according to the selection of the user, and then the rapid deployment subsystem sends a query instruction for querying the deployed files on the target deployment server to a deployment springboard connected with the target deployment server.
The deployment springboard can be more than one, each deployment springboard can be connected with a plurality of target deployment servers, the target deployment servers can also be divided into a plurality of service clusters, each service cluster comprises a plurality of target deployment servers, and the connection between the rapid deployment subsystem and the deployment springboard is a secret-free connection, so that the rapid deployment function is realized.
S103, the deployment springboard responds to the query instruction, obtains the deployed file in the target deployment server, and sends the deployed file to the rapid deployment subsystem.
In the step, the rapid deployment subsystem sends a query instruction for querying the deployed file to the deployment springboard, after the deployment springboard receives the query instruction sent by the rapid deployment subsystem, the query instruction is identified, a certain target deployment server to be queried specifically is determined, then the deployment springboard is deployed to the corresponding target deployment server to query the deployed file, and after the query is finished, the queried deployed file is sent to the rapid deployment subsystem.
Here, the sending of the deployed file to the rapid deployment subsystem by the deployment springboard may send a query result of the deployed file to the rapid deployment subsystem for the deployment springboard. The deployed file is a file of the same name and type as the target file.
The query result of the deployed file comprises the relevant information of the deployed file, and examples of the query result of the deployed file comprise information such as file size, file creation time, file attribute, file name, file readability and the like. When the deployed file is not inquired by the deployment springboard, an empty file can be returned to the rapid deployment subsystem.
S104, the rapid deployment subsystem compares the target file with the deployed file and determines whether to redeploy the target deployment server.
In the step, after the rapid deployment subsystem receives the deployed file returned by the deployment springboard, the rapid deployment subsystem compares the target file of the task to be deployed with the deployed file returned by the deployment springboard to obtain a comparison result, and judges whether task deployment needs to be performed on the target deployment server again according to the obtained comparison result.
Further, the fast deployment subsystem compares the target file with the deployed file to determine whether to redeploy the target deployment server, including: the rapid deployment subsystem compares the creation time of the target file with the creation time of the deployed file; when the creation time of the target file is later than that of the deployed file, the rapid deployment subsystem redeployes the target deployment server.
In the step, after the rapid deployment subsystem receives the deployed file returned by the deployment springboard, the rapid deployment subsystem compares the creation time of the target file corresponding to the task to be deployed with the creation time of the deployed file returned by the deployment springboard, and when the creation time of the target file is later than the creation time of the deployed file, it indicates that the version of the target file is updated compared with the version of the deployed file, and the rapid deployment subsystem can redeploy the target deployment server.
Here, when the creation time of the deployed file is later than the creation time of the target file, indicating that the version of the deployed file is updated compared to the version of the target file, the fast deployment subsystem may not redeploy the target deployment server, and the task deployment is ended.
And S105, if so, deploying the target file in the target deployment server by the rapid deployment subsystem through the deployment springboard.
In this step, when the target deployment server needs to be redeployed, the rapid deployment subsystem deploys the target file corresponding to the task to be deployed to the target deployment server through the deployment springboard connected with the target deployment server.
Further, the rapid deployment subsystem deploys the target file in the target deployment server through the deployment springboard, including: the rapid deployment subsystem sends the target file to the target deployment server through the deployment springboard; and the deployment springboard runs the target file based on a secure shell protocol to end the process of the deployed file.
In the step, the rapid deployment subsystem deploys the target file in the target deployment server through a deployment springboard, and the method is that the rapid deployment subsystem transmits the target file to the target deployment server through the deployment springboard connected with the target deployment server, after the transmission is completed, the deployment springboard can feed back a transmission completion signal to the rapid deployment subsystem, then the rapid deployment subsystem can transmit a starting instruction to the deployment springboard, and the deployment springboard remotely starts the target file on the target deployment server through a secure shell protocol SSH according to the received starting instruction, so that the target file can be operated, and the deployment springboard remotely ends the process of the deployed file based on the secure shell protocol SSH.
Here, the deployment springboard may be configured to receive an instruction from the fast deployment subsystem, operate the intranet target deployment server through SSH, return an execution result to the fast deployment subsystem, and perform work such as obtaining file information and updating a file.
Here, the process that finishes the deployed file may be a process that is killed, and the process cannot be restarted.
Further, the fast deploying subsystem sends the target file to the target deploying server through the deploying springboard, and includes: the deployment springboard receives the target file transmitted by the rapid deployment subsystem based on a secure socket protocol; and the deployment springboard sends the target file to the target deployment server based on a secure shell protocol so as to realize the coverage of the deployed file.
In this step, the rapid deployment subsystem sends the target file to the target deployment server by deploying the springboard, which is implemented in the following manner. The rapid deployment subsystem is connected with a deployment springboard through a secure socket protocol (SSL), the deployment springboard is connected with a target deployment server based on a secure shell protocol, firstly, the rapid deployment subsystem sends a target file to the deployment springboard, the deployment springboard determines the target deployment server to be sent after receiving the target file, then the deployment springboard sends the target file to the determined target deployment server, and covers the deployed file on the target deployment server, namely the old file.
Further, the receiving, by the deployment springboard, the target file transmitted by the rapid deployment subsystem based on a secure socket protocol includes: and the deployment springboard receives the target file transmitted by the rapid deployment subsystem through a firewall and/or a gateway and/or a proxy server based on a secure socket protocol.
In this step, when the deployment springboard receives the target file transmitted by the rapid deployment subsystem based on the secure socket protocol, in order to ensure the communication security, the following method may be further included: the rapid deployment subsystem is connected with a firewall and/or a gateway and/or a proxy server through a secure socket protocol (SSL), then the firewall and/or the gateway and/or the proxy server are connected with a deployment springboard through the secure socket protocol (SSL), and the rapid deployment subsystem sends a target file to the deployment springboard through the firewall and/or the gateway and/or the proxy server based on the secure socket protocol.
For example, please refer to fig. 2, fig. 2 is a schematic process diagram of task deployment provided in the present application. The process of task deployment provided by the present application is further explained in conjunction with fig. 2:
s201, a user logs in the rapid deployment subsystem by inputting an account and a password, inputs task deployment information and generates a task to be deployed.
S202, the rapid deployment subsystem pulls codes from the code base, compiles and packages the codes according to the generated tasks to be deployed, and generates a target file.
S203, the rapid deployment subsystem is safely connected to the deployment springboard through SSL, a query instruction is sent to the deployment springboard, the deployment springboard queries deployed file information on a specified target deployment server according to the received query instruction, and after the query is completed, the deployment springboard returns the deployed files (related information of the deployed files) to the rapid deployment subsystem.
S204, the rapid deployment subsystem compares whether the creation time of the target file is later than the creation time of the deployed file or not according to the received deployed file.
S205, when the creation time of the target file is later than the creation time of the deployed file, the rapid deployment subsystem uploads the target file to the deployment springboard through SSL (secure sockets layer) secure connection, the deployment springboard sends the file to the target deployment server and covers the deployed file on the target deployment server, the rapid deployment subsystem sends a starting instruction to the deployment springboard, the deployment springboard kills the process of the deployed file on the target deployment server through an SSH (secure Shell) remote instruction according to the starting instruction, the program in the target file is operated, and task deployment is finished.
S206, when the creation time of the target file is not later than the creation time of the deployed file, the task deployment is finished.
The task deployment method provided by the embodiment of the application comprises the following steps: the rapid deployment subsystem generates a task to be deployed based on received task deployment information input by a user and acquires a target file corresponding to the task to be deployed; the rapid deployment subsystem determines a target deployment server of the task to be deployed based on the task deployment information and sends a query instruction to a deployment springboard corresponding to the target deployment server; the deployment springboard responds to the query instruction, obtains a deployed file in the target deployment server, and sends the deployed file to the rapid deployment subsystem; the rapid deployment subsystem compares the target file with the deployed file and determines whether to redeploy the target deployment server; if so, the rapid deployment subsystem deploys the target file in the target deployment server through the deployment springboard.
Therefore, the rapid deployment subsystem determines the deployment springboard corresponding to the target deployment server through the generated task to be deployed, directly deploys the target task to the target deployment server through the deployment springboard, and does not need to repeatedly perform the authentication operation of the springboard machine when the task is deployed every time, so that the deployment efficiency and the deployment convenience are improved.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a task deployment system according to an embodiment of the present application. As shown in fig. 3, the task deployment system 300 includes a rapid deployment subsystem 310 and a deployment springboard 320:
the rapid deployment subsystem 310 is configured to generate a task to be deployed based on received task deployment information input by a user, acquire a target file corresponding to the task to be deployed, determine a target deployment server of the task to be deployed based on the task deployment information, and send a query instruction to a deployment springboard 320 corresponding to the target deployment server;
the deployment springboard 320 is configured to, in response to the query instruction, obtain a deployed file in the target deployment server, and send the deployed file to the rapid deployment subsystem 310;
the rapid deployment subsystem 310 is further configured to compare the target file with the deployed file, and determine whether to redeploy the target deployment server, if so, the rapid deployment subsystem 310 deploys the target file in the target deployment server through the deployment springboard 320.
Further, when the rapid deployment subsystem 310 is configured to obtain the target file corresponding to the task to be deployed through the following steps, the rapid deployment subsystem 310 is configured to:
pulling a code to be deployed corresponding to the task to be deployed from a pre-constructed code library according to the task deployment information corresponding to the task to be deployed;
compiling and packaging the code to be deployed to generate a target file corresponding to the task to be deployed.
Further, when the task deployment system 300 deploys the target file in the target deployment server through the deployment springboard 320 by the rapid deployment subsystem 310, the task deployment system 300 is configured to:
the rapid deployment subsystem 310 sends the target file to the target deployment server through the deployment springboard 320;
the deployment springboard 320 runs the target file based on a secure shell protocol to end the process of the deployed file.
Further, when the task deployment system 300 uses the rapid deployment subsystem 310 to send the target file to the target deployment server through the deployment springboard 320, the task deployment system 300 is configured to:
the deployment springboard 320 receives the target file transmitted by the rapid deployment subsystem 310 based on a secure socket protocol;
the deployment springboard 320 sends the target file to the target deployment server based on a secure shell protocol to implement the overlay of the deployed file.
Further, when the deployment springboard 320 is configured to receive the target file transmitted by the rapid deployment subsystem 310 based on a secure socket protocol, the deployment springboard 320 is configured to:
the target file transmitted by the rapid deployment subsystem 310 is received through a firewall and/or a gateway and/or a proxy server based on a secure socket protocol.
Further, when the rapid deployment subsystem 310 is configured to compare the target file with the deployed file and determine whether to redeploy the target deployment server, the rapid deployment subsystem 310 is configured to:
comparing the creation time of the target file with the creation time of the deployed file;
and when the creation time of the target file is later than that of the deployed file, the target deployment server is redeployed.
The task deployment system provided by the embodiment of the application comprises: the rapid deployment subsystem is used for generating a task to be deployed based on received task deployment information input by a user, acquiring a target file corresponding to the task to be deployed, determining a target deployment server of the task to be deployed based on the task deployment information, and sending a query instruction to a deployment springboard corresponding to the target deployment server; the deployment springboard is used for responding to the query instruction, acquiring a deployed file in the target deployment server and sending the deployed file to the rapid deployment subsystem; the rapid deployment subsystem is further configured to compare the target file with the deployed file, and determine whether to redeploy the target deployment server, and if so, deploy the target file in the target deployment server through the deployment springboard by the rapid deployment subsystem.
Therefore, the rapid deployment subsystem determines the deployment springboard corresponding to the target deployment server through the generated task to be deployed, directly deploys the target task to the target deployment server through the deployment springboard, and does not need to repeatedly perform the authentication operation of the springboard machine when the task is deployed every time, so that the deployment efficiency and the deployment convenience are improved.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. As shown in fig. 4, the electronic device 400 includes a processor 410, a memory 420, and a bus 430.
The memory 420 stores machine-readable instructions executable by the processor 410, when the electronic device 400 runs, the processor 410 communicates with the memory 420 through the bus 430, and when the machine-readable instructions are executed by the processor 410, the steps of the task deployment method in the method embodiments shown in fig. 1 and fig. 2 may be performed.
An embodiment of the present application 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 steps of the task deployment method in the method embodiments shown in fig. 1 and fig. 2 may be executed.
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 application, 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 application 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 application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 application. 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 only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application 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 the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the exemplary embodiments of the present application, and are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A task deployment method, characterized in that the task deployment method comprises:
the rapid deployment subsystem generates a task to be deployed based on received task deployment information input by a user and acquires a target file corresponding to the task to be deployed;
the rapid deployment subsystem determines a target deployment server of the task to be deployed based on the task deployment information and sends a query instruction to a deployment springboard corresponding to the target deployment server;
the deployment springboard responds to the query instruction, obtains a deployed file in the target deployment server, and sends the deployed file to the rapid deployment subsystem;
the rapid deployment subsystem compares the target file with the deployed file and determines whether to redeploy the target deployment server;
if so, the rapid deployment subsystem deploys the target file in the target deployment server through the deployment springboard.
2. The task deployment method according to claim 1, wherein the target file corresponding to the task to be deployed is obtained by the following steps:
the rapid deployment subsystem pulls a code to be deployed corresponding to the task to be deployed from a pre-constructed code library according to task deployment information corresponding to the task to be deployed;
and the rapid deployment subsystem compiles and packages the code to be deployed to generate a target file corresponding to the task to be deployed.
3. The task deployment method of claim 1, wherein the rapid deployment subsystem deploys the target file in the target deployment server through the deployment springboard, and comprises:
the rapid deployment subsystem sends the target file to the target deployment server through the deployment springboard;
and the deployment springboard runs the target file based on a secure shell protocol to end the process of the deployed file.
4. The task deployment method of claim 3, wherein the fast deployment subsystem sends the target file to the target deployment server through the deployment springboard, and comprises:
the deployment springboard receives the target file transmitted by the rapid deployment subsystem based on a secure socket protocol;
and the deployment springboard sends the target file to the target deployment server based on a secure shell protocol so as to realize the coverage of the deployed file.
5. The task deployment method of claim 4, wherein the receiving, by the deployment springboard, the target file transmitted by the rapid deployment subsystem based on a secure socket protocol comprises:
and the deployment springboard receives the target file transmitted by the rapid deployment subsystem through a firewall and/or a gateway and/or a proxy server based on a secure socket protocol.
6. The task deployment method of claim 1, wherein the fast deployment subsystem compares the target file with the deployed file to determine whether to redeploy the target deployment server, comprising:
the rapid deployment subsystem compares the creation time of the target file with the creation time of the deployed file;
when the creation time of the target file is later than that of the deployed file, the rapid deployment subsystem redeployes the target deployment server.
7. A task deployment system, comprising a rapid deployment subsystem and a deployment springboard:
the rapid deployment subsystem is used for generating a task to be deployed based on received task deployment information input by a user, acquiring a target file corresponding to the task to be deployed, determining a target deployment server of the task to be deployed based on the task deployment information, and sending a query instruction to a deployment springboard corresponding to the target deployment server;
the deployment springboard is used for responding to the query instruction, acquiring a deployed file in the target deployment server and sending the deployed file to the rapid deployment subsystem;
the rapid deployment subsystem is further configured to compare the target file with the deployed file, and determine whether to redeploy the target deployment server, and if so, deploy the target file in the target deployment server through the deployment springboard by the rapid deployment subsystem.
8. The task deployment system of claim 7, wherein when the rapid deployment subsystem is configured to obtain the target file corresponding to the task to be deployed by the following steps, the rapid deployment subsystem is configured to:
pulling a code to be deployed corresponding to the task to be deployed from a pre-constructed code library according to the task deployment information corresponding to the task to be deployed;
compiling and packaging the code to be deployed to generate a target file corresponding to the task to be deployed.
9. 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 an electronic device is run, the machine-readable instructions when executed by the processor performing the task deployment method of any one of claims 1 to 6.
10. 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 task deployment method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110145597.9A CN112799681A (en) | 2021-02-02 | 2021-02-02 | Task deployment method, system, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110145597.9A CN112799681A (en) | 2021-02-02 | 2021-02-02 | Task deployment method, system, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112799681A true CN112799681A (en) | 2021-05-14 |
Family
ID=75813739
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110145597.9A Pending CN112799681A (en) | 2021-02-02 | 2021-02-02 | Task deployment method, system, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112799681A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434151A (en) * | 2021-06-10 | 2021-09-24 | 中国铁道科学研究院集团有限公司电子计算技术研究所 | Service deployment method, server and system |
| CN114363163A (en) * | 2021-12-09 | 2022-04-15 | 北京六方云信息技术有限公司 | HTTPS-based equipment deployment method, system, equipment and medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107786593A (en) * | 2016-08-25 | 2018-03-09 | 阿里巴巴集团控股有限公司 | Task deployment method, example deployment method, apparatus and equipment |
| CN108509203A (en) * | 2018-03-13 | 2018-09-07 | 腾讯科技（深圳）有限公司 | Across the cloud dispositions method of software, computer equipment and storage medium |
| CN110365692A (en) * | 2019-07-23 | 2019-10-22 | 秒针信息技术有限公司 | A kind of server log method and system |
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| CN110830436A (en) * | 2019-09-17 | 2020-02-21 | 网宿科技股份有限公司 | User login method and springboard machine |
| CN110881059A (en) * | 2019-10-12 | 2020-03-13 | 平安银行股份有限公司 | Application deployment system and method, release engine and computer equipment |
| CN112131544A (en) * | 2020-09-27 | 2020-12-25 | 江苏云柜网络技术有限公司 | Shell script method for user management of springboard machine |
-
2021
- 2021-02-02 CN CN202110145597.9A patent/CN112799681A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107786593A (en) * | 2016-08-25 | 2018-03-09 | 阿里巴巴集团控股有限公司 | Task deployment method, example deployment method, apparatus and equipment |
| CN108509203A (en) * | 2018-03-13 | 2018-09-07 | 腾讯科技（深圳）有限公司 | Across the cloud dispositions method of software, computer equipment and storage medium |
| CN110365692A (en) * | 2019-07-23 | 2019-10-22 | 秒针信息技术有限公司 | A kind of server log method and system |
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| CN110830436A (en) * | 2019-09-17 | 2020-02-21 | 网宿科技股份有限公司 | User login method and springboard machine |
| CN110881059A (en) * | 2019-10-12 | 2020-03-13 | 平安银行股份有限公司 | Application deployment system and method, release engine and computer equipment |
| CN112131544A (en) * | 2020-09-27 | 2020-12-25 | 江苏云柜网络技术有限公司 | Shell script method for user management of springboard machine |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434151A (en) * | 2021-06-10 | 2021-09-24 | 中国铁道科学研究院集团有限公司电子计算技术研究所 | Service deployment method, server and system |
| CN114363163A (en) * | 2021-12-09 | 2022-04-15 | 北京六方云信息技术有限公司 | HTTPS-based equipment deployment method, system, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4923058B2 (en) | Automated device driver management | |
| CN110752947A (en) | K8s cluster deployment method and device, and deployment platform | |
| CN111367534B (en) | Service arrangement method and system based on application environment | |
| CN112799681A (en) | Task deployment method, system, electronic equipment and storage medium | |
| CN110224854B (en) | Block chain node deployment method and device and storage medium | |
| US9317268B2 (en) | Recovery automation in heterogeneous environments | |
| US11561782B2 (en) | Upgrade recommendations | |
| CN111538625B (en) | Ambari cluster deployment and data backup method based on Docker technology and electronic equipment | |
| JP2016103144A (en) | Virtual machine deployment method, virtual machine deployment program and virtual machine deployment system | |
| CN112860282A (en) | Upgrading method and device of cluster plug-in and server | |
| CN113900670B (en) | Cluster server application deployment system | |
| JP2019522834A (en) | Code package variant | |
| CN111913719B (en) | Deployment method, device and apparatus of high-availability software and computer storage medium | |
| CN110099095B (en) | Software deployment method and device, electronic equipment and computer-readable storage medium | |
| CN111399860A (en) | Light application deployment method and device, computer equipment and storage medium | |
| CN107678969B (en) | Test version release method and device, version control equipment and test machine | |
| CN108241545B (en) | Debugging method and device for system fault | |
| CN113821303A (en) | Method and device for deploying hardor cluster and readable storage medium | |
| JP5905313B2 (en) | Information processing apparatus, information processing method, information processing system, and program | |
| JP2015106314A (en) | Configuration management system, control method of configuration management system, and program | |
| CN111611160B (en) | Software testing method, device, equipment and storage medium | |
| CN114237633A (en) | Application configuration method, device, equipment and storage medium | |
| US10798181B2 (en) | Storage medium containing a program, information processing device, and processing method for deploying an application generated to a cloud environment | |
| CN116431122B (en) | Compiling method and device for development effect and readable storage medium | |
| CN115372803B (en) | Motherboard test system, method, device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210514 |
|
| RJ01 | Rejection of invention patent application after publication |