CN114879977A - Application deployment method, device and storage medium - Google Patents

Abstract

Embodiments of the present invention provide an application deployment method, device, and storage medium. The method includes: determining a list of machines to be deployed and applications to be deployed; dividing deployment batches according to the list of machines to be deployed; wherein, each deployment batch at least includes A to-be-deployed machine; generates deployment tasks for applications to be deployed, and sends the deployment tasks in parallel to the to-be-deployed machines in each deployment batch in an asynchronous manner, so that the to-be-deployed machines can wait according to the deployment tasks. Deploy the deployment of the application. The application deployment method, device and storage medium provided by the embodiments of the present invention effectively improve application deployment efficiency by sending deployment tasks to machines to be deployed in an asynchronous manner between deployment batches and within a deployment batch in parallel.

Description

Application deployment method, device and storage medium

technical field

Embodiments of the present invention relate to the field of computer technologies, and in particular, to an application deployment method, device, and storage medium.

Background technique

Due to the particularity of the business, some applications can only be deployed on Windows servers, so how to deploy Windows applications efficiently and reliably is very important. However, Internet companies mostly use Linux systems as servers, and there are few mature and easy-to-use deployment solutions for Windows deployment.

An existing Windows application deployment method is based on Jenkins+Openssh for application deployment. When deploying an application, Jenkins is remotely connected to the machine to be deployed through SSH. Jenkins is an open source software project. It is a continuous integration tool developed based on Java. It is used to monitor continuous and repetitive work. It aims to provide an open and easy-to-use software platform that enables continuous integration of software projects. Jenkins features include: continuous software release/testing projects, monitoring work performed by external calls. OpenSSH is a free and open source implementation of the SSH (Secure SHell) protocol. The SSH protocol suite can be used for remote control, or to transfer files between computers.

The existing Jenkins+Openssh windows application deployment method requires Jenkins to establish connections with the machines to be deployed in sequence, and batch deployment of applications on multiple machines to be deployed is a serial operation, resulting in low deployment efficiency.

SUMMARY OF THE INVENTION

In view of the defects existing in the prior art, the embodiments of the present invention provide an application deployment method, an apparatus, and a storage medium.

An embodiment of the present invention provides an application deployment method, including: determining a list of machines to be deployed and applications to be deployed; dividing deployment batches according to the list of machines to be deployed; wherein, each deployment batch includes at least one of the The machine to be deployed; the deployment task of the application to be deployed is generated, and the deployment task is sent in parallel to the to-be-deployed machine in each of the deployment batches in an asynchronous manner among the deployment batches, so as to for the to-be-deployed machine to deploy the to-be-deployed application according to the deployment task.

According to an application deployment method provided by an embodiment of the present invention, the deployment tasks are sent in parallel to the machines to be deployed in the deployment batches in an asynchronous manner between the deployment batches, The method includes: writing the deployment task to the task queue corresponding to the to-be-deployed machine in each of the deployment batches in parallel in an asynchronous manner among the deployment batches.

According to an application deployment method provided by an embodiment of the present invention, the method further includes: receiving deployment process data sent by the machine to be deployed; wherein the deployment process data includes a task state of the deployment task.

According to an application deployment method provided by an embodiment of the present invention, the task status includes at least one of task queuing, waiting for ready, starting, successful, and failed, wherein: the deployment task has not been consumed by the to-be-deployed machine , the task status is task queuing; the to-be-deployed machine consumes the deployment task, and the task status is waiting for ready; the to-be-deployed machine consumes the deployment task and meets the deployment conditions of the deployment task , the task state is starting; wherein, when the task state is starting, the to-be-deployed machine executes the action of deploying the application to be deployed according to the deployment task; If the task of deploying the application to be deployed is successfully executed, the task status is successful; the action of deploying the application to be deployed according to the deployment task fails to be executed, and the task status is failed.

According to an application deployment method provided by an embodiment of the present invention, in the asynchronous manner between the deployment batches, the deployment task is sent to the machines to be deployed in the deployment batches in parallel Afterwards, the method further includes: generating a batch ID corresponding to the deployment batch and a task ID corresponding to the to-be-deployed machine in the deployment batch; wherein the batch ID and the deployment batch The to-be-deployed machines included in the batch correspond; the deployment process data is queried according to the batch ID and/or the task ID.

According to an application deployment method provided by an embodiment of the present invention, the determining a list of machines to be deployed includes: on a web page, in response to the selection of the application to be deployed, displaying a list of machines associated with the application to be deployed; The to-be-deployed machine is selected from the machine list associated with the to-be-deployed application, and the to-be-deployed machine list is determined according to the selection result.

According to an application deployment method provided by an embodiment of the present invention, the method further includes: in response to the deployment environment being a test environment, acquiring the code of the application to be deployed, compiling and packaging the code to generate a product, and compiling the product uploading to a preset database; in response to the deployment environment being an online environment, determining a product of the to-be-deployed application in the preset database that has passed the test of the to-be-deployed application; wherein the product includes version information.

According to an application deployment method provided by an embodiment of the present invention, the deploying the application to be deployed according to the deployment task includes: in response to the machine to be deployed currently running the application to be deployed, stopping the application to be deployed the application to be deployed; download the product of the corresponding version of the application to be deployed by accessing the preset database; replace the application to be deployed according to the product; start the application to be deployed.

An embodiment of the present invention further provides an application deployment device, comprising: a determination module, used for: determining a list of machines to be deployed and applications to be deployed; a batching module, used for: dividing deployment batches according to the list of machines to be deployed; wherein , each said deployment batch includes at least one said to-be-deployed machine; a deployment module is used to: generate a deployment task of said to-be-deployed application; The deployment task is sent in parallel to the to-be-deployed machines in each of the deployment batches, so that the to-be-deployed machines can deploy the to-be-deployed application according to the deployment task.

An embodiment of the present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements any of the applications described above when the processor executes the program The steps of the deployment method.

Embodiments of the present invention further provide a non-transitory computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of any of the foregoing application deployment methods.

Embodiments of the present invention further provide a computer program product, including a computer program, which implements the steps of any of the foregoing application deployment methods when the computer program is executed by a processor.

The application deployment method, device and storage medium provided by the embodiments of the present invention effectively improve application deployment efficiency by sending deployment tasks to machines to be deployed in an asynchronous manner between deployment batches and in parallel within the same deployment batch.

Description of drawings

In order to illustrate the technical solutions of the present invention more clearly, the following briefly introduces the accompanying drawings used in the description of the embodiments. Obviously, the accompanying drawings in the following description are some embodiments of the present invention, which are of great significance to the art. For those of ordinary skill, other drawings can also be obtained from these drawings without any creative effort.

FIG. 1 is one of the schematic flowcharts of the application deployment method provided by the embodiment of the present invention;

2 is a second schematic flowchart of an application deployment method provided by an embodiment of the present invention;

3 is a third schematic flowchart of an application deployment method provided by an embodiment of the present invention;

4 is a schematic diagram of a task state machine representing task state flow in an application deployment method provided by an embodiment of the present invention;

5 is a schematic structural diagram of an application deployment apparatus provided by an embodiment of the present invention;

6 is a schematic structural diagram of an application deployment system provided by an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of an electronic device provided by an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention clearer, the technical solutions in the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention. , not all examples. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The application deployment method provided by the embodiment of the present invention is applicable to the deployment of a window machine, and is also applicable to the deployment of other machines such as linux.

FIG. 1 is a schematic flowchart of an application deployment method provided by an embodiment of the present invention. As shown in Figure 1, the method includes:

Step S1: Determine a list of machines to be deployed and applications to be deployed.

The application deployment method provided by the embodiment of the present invention can be applied to a server, the list of machines to be deployed includes at least one machine to be deployed, and the machine to be deployed is regarded as a client of the server. The server can set a deployment platform (also called a publishing platform) to manage and operate application deployment. The server can interact with the machine to be deployed through the API.

The application to be deployed is an application to be deployed on the machine to be deployed, and determining the application to be deployed includes determining the version of the application to be deployed.

Step S2: Divide deployment batches according to the list of machines to be deployed; wherein, each of the deployment batches includes at least one of the machines to be deployed.

To improve deployment efficiency, deploy applications in batches. The deployment batches are divided according to the number of machines to be deployed in the list of to-be-deployed machines. When dividing the deployment batches, if the number of machines in each deployment batch is determined in advance, the deployment machines are allocated according to the number of machines in each deployment batch. The machines to be deployed in the list are divided into deployment batches. If there are 105 machines to be deployed in the list of to-be-deployed machines, and each 10 to-be-deployed machines is predetermined as a batch, it can be divided into 11 batches for deployment, of which 10 of the first 10 batches are to be deployed. Deploy machines. There are 5 machines to be deployed in the last batch due to insufficient quantity. If there is no requirement for the number of machines in each deployment batch, the number of machines to be deployed in each deployment batch can be determined according to actual needs. Each deployment batch includes at least one machine to be deployed.

Of course, if the number of to-be-deployed machines in the to-be-deployed machine list is small, deployment can also be performed in one deployment batch.

Step S3, generating a deployment task of the application to be deployed, and sending the deployment task in parallel to the to-be-deployed machines in each of the deployment batches in an asynchronous manner among the deployment batches for use in the deployment batches. The to-be-deployed machine deploys the to-be-deployed application according to the deployment task.

A deployment task of the application to be deployed is generated, and the deployment task includes information of the application to be deployed, so as to determine the application to be deployed to be deployed. The information of the application to be deployed may be embodied in the form of task parameters, for example, the task parameter includes version information of the application to be deployed. After the deployment task of the application to be deployed is generated, the deployment task is sent in parallel to the to-be-deployed machines in each deployment batch in an asynchronous manner between each deployment batch. After the machine to be deployed obtains the deployment task, it deploys the application to be deployed according to the deployment task.

For the machines to be deployed in the same deployment batch, the deployment tasks are sent to each of the machines to be deployed in parallel. Between each deployment batch, the deployment task is sent to the machines to be deployed in each deployment batch in an asynchronous manner, that is, without waiting for the deployment of the previous batch to be completed, the processing of the machines to be deployed in the subsequent batch is started. Sending of deployment tasks. After the previous batch of machines to be deployed are deployed, the deployment result can be called back to the server.

In the embodiment of the present invention, deployment tasks are sent to the machines to be deployed in an asynchronous manner between deployment batches and in parallel within the same deployment batch, which greatly improves application deployment efficiency. Experimental data shows that the deployment time can be shortened from 4 hours to 10 minutes.

The application deployment method provided by the embodiment of the present invention effectively improves the application deployment efficiency by sending deployment tasks to the machines to be deployed in an asynchronous manner between deployment batches and within the same deployment batch in parallel.

According to an application deployment method provided by an embodiment of the present invention, the deployment tasks are sent in parallel to the machines to be deployed in the deployment batches in an asynchronous manner between the deployment batches, The method includes: writing the deployment task to the task queue corresponding to the to-be-deployed machine in each of the deployment batches in parallel in an asynchronous manner among the deployment batches.

A task queue can be set up for each machine to be deployed. The task queue can contain deployment tasks of multiple applications to be deployed sent by the server. Therefore, when the deployment tasks are sent in parallel to the machines to be deployed in each deployment batch in an asynchronous manner between each deployment batch, the deployment tasks can be written in parallel to each deployment batch in an asynchronous manner. The task queue corresponding to the machines to be deployed in the deployment batch. The to-be-deployed machine can set a monitoring module to monitor the status of the deployment tasks in the task queue, and obtain the deployment tasks in the task queue to deploy the corresponding to-be-deployed tasks.

In the application deployment method provided by the embodiment of the present invention, the deployment tasks are written into the task queue corresponding to the to-be-deployed machines in each deployment batch in an asynchronous manner, so as to facilitate the implementation of the deployment process of the to-be-deployed machines management.

According to an application deployment method provided by an embodiment of the present invention, the method further includes: receiving deployment process data sent by the machine to be deployed; wherein the deployment process data includes a task state of the deployment task.

If there is a problem with a certain machine during the same batch of deployment, it will not only greatly prolong the deployment time, but also it is difficult to quickly identify the problem machine, and there is no reliable mechanism to confirm the deployment results of this batch. To solve the above problem, in this embodiment of the present invention, the to-be-deployed machine records deployment process data of the deployment task, and the deployment process data includes the task status. The to-be-deployed machine can send the deployment process data to the server after executing the deployment of the to-be-deployed application, and of course, it can also be sent to the server in real time.

Correspondingly, the server receives and stores the deployment process data sent by the machine to be deployed, where the deployment process data includes the task status of the deployment task.

In the application deployment method provided by the embodiment of the present invention, by receiving the deployment process data including the task status sent by the to-be-deployed machine, it is beneficial to realize the supervision of the deployment status of the deployment task, facilitate the timely discovery of the problem machine, and avoid unnecessary waste of time.

According to an application deployment method provided by an embodiment of the present invention, the task status includes at least one of task queuing, waiting for ready, starting, successful, and failed, wherein: the deployment task has not been consumed by the to-be-deployed machine , the task status is task queuing; the to-be-deployed machine consumes the deployment task, and the task status is waiting for ready; the to-be-deployed machine consumes the deployment task and meets the deployment conditions of the deployment task , the task state is starting; wherein, when the task state is starting, the to-be-deployed machine executes the action of deploying the application to be deployed according to the deployment task; If the task of deploying the application to be deployed is successfully executed, the task status is successful; the action of deploying the application to be deployed according to the deployment task fails to be executed, and the task status is failed.

In the entire deployment process, by converting the deployment operation into an asynchronous deployment task, it is used to avoid that a certain machine to be deployed has a task being processed or other failures hinder the overall deployment rhythm during deployment. The task state of the to-be-deployed task can be used to represent the deployment state of the corresponding to-be-deployed machine. The flow process of the task state of the task to be deployed can be represented by a task state machine.

The machine to be deployed can deploy the application to be deployed by consuming the deployment tasks in the task queue. Since there may be multiple deployment tasks to be deployed in the task queue, they need to be queued for processing. If the machine to be deployed has not consumed the deployment task, the task status is task queued; if the machine to be deployed has consumed the deployment task, the task status is waiting to be ready; The task being processed), the status flow changes to starting; if the deployment conditions of the application to be deployed are not met at this time, the task status is still waiting for ready. When the task status is starting, the to-be-deployed machine executes the action of deploying the to-be-deployed application according to the deployment task according to the task parameters in the deployment task.

If the machine to be deployed executes the action of deploying the application to be deployed according to the deployment task successfully, the task status is successful; if the machine to be deployed fails to execute the action of deploying the application to be deployed according to the deployment task, the task status is failed.

The above state transfer process can be pre-stored in the to-be-deployed machine as deployment process data, and the deployment process data is sent to the server after the deployment of the application to be deployed according to the deployment task is completed (whether successful or unsuccessful).

The application deployment method provided by the embodiment of the present invention improves the richness and comprehensiveness of the information acquisition of the deployment process by setting the task statuses of task queuing, waiting for ready, starting and indicating the deployment result, and is beneficial to understand the entire application deployment process.

According to an application deployment method provided by an embodiment of the present invention, in the asynchronous manner between the deployment batches, the deployment task is sent to the machines to be deployed in the deployment batches in parallel Afterwards, the method further includes: generating a batch ID corresponding to the deployment batch and a task ID corresponding to the to-be-deployed machine in the deployment batch; wherein the batch ID and the deployment batch The to-be-deployed machines included in the batch correspond; the deployment process data is queried according to the batch ID and/or the task ID.

After the deployment tasks are sent in parallel to the machines to be deployed in each deployment batch in an asynchronous manner between the deployment batches, the batch ID corresponding to the deployment batch and the machines to be deployed in the deployment batch can be generated. The corresponding task ID.

The batch ID corresponds to the to-be-deployed machine included in the deployment batch, and the deployment process data of the to-be-deployed machine in the corresponding batch can be queried according to the batch ID, such as querying the task status of the to-be-deployed machine in the corresponding batch. The task ID corresponds to the to-be-deployed machine included in the deployment batch, that is, the deployment batch and the to-be-deployed machine in the deployment batch can be determined according to the task ID. The deployment process data of each to-be-deployed machine in the to-be-deployed machine list, such as the task status, can be obtained according to the task ID.

The batch ID can be associated with the task ID of the to-be-deployed machine in the corresponding deployment batch.

In the application deployment method provided by the embodiment of the present invention, by generating a batch ID corresponding to the deployment batch and a task ID corresponding to the machine to be deployed in the deployment batch, and querying the deployment process data according to the batch ID and/or the task ID, It realizes the distinction between different deployment batches and different machines to be deployed, and improves the convenience of data query in the deployment process.

According to an application deployment method provided by an embodiment of the present invention, the determining a list of machines to be deployed includes: on a web page, in response to the selection of the application to be deployed, displaying a list of machines associated with the application to be deployed; The to-be-deployed machine is selected from the machine list associated with the to-be-deployed application, and the to-be-deployed machine list is determined according to the selection result.

The server can implement machine management, application management and deployment record management. The data information to be stored may include information of the machine to be deployed, information of the application to be deployed, and deployment record information (eg, including deployment process data). Among them, one to-be-deployed machine can be associated with multiple to-be-deployed applications, and one to-be-deployed application can have multiple deployment records. An application to be deployed can have multiple versions, and multiple deployment records can correspond to multiple versions. Of course, the same version can also be deployed multiple times.

The to-be-deployed application associated with the to-be-deployed machine represents the to-be-deployed application that needs to be deployed on the to-be-deployed machine, and the deployment of each to-be-deployed application on the to-be-deployed machine can be completed according to the deployment planning sequence. Machine and application management can perform CRUD operations (add (Create), read query (Retrieve), update (Update) and delete (Delete)) directly based on the database.

The list of machines to be deployed may be determined on the web page based on the association between the application to be deployed and the machines to be deployed. On the web page, a selection list of applications to be deployed can be set, and the applications to be deployed can be determined by selection. After the application to be deployed is determined, a list of machines associated with the application to be deployed can be displayed. The list of machines to be deployed may be determined by further selecting from the list of machines associated with the application to be deployed according to the deployment requirements.

In the application deployment method provided by the embodiment of the present invention, in response to the selection of the application to be deployed on the web page, a list of machines associated with the application to be deployed is displayed, and the machine to be deployed is selected from the list of machines associated with the application to be deployed, and the selection result is performed. Determining the list of machines to be deployed improves the simplicity of determining the list of machines to be deployed.

According to an application deployment method provided by an embodiment of the present invention, the method further includes: in response to the deployment environment being a test environment, acquiring the code of the application to be deployed, compiling and packaging the code to generate a product, and compiling the product uploading to a preset database; in response to the deployment environment being an online environment, determining a product of the to-be-deployed application in the preset database that has passed the test of the to-be-deployed application; wherein the product includes version information.

The deployment environment during application deployment includes a test environment and an online environment. The purpose of application deployment in the test environment is to test the developed application to be deployed, compile, package, and generate products during deployment and store them in a preset database. Among them, the product includes version information. The purpose of application deployment in the online environment is to put the developed application to be deployed into operation. When deploying, you need to select the product version that has passed the test.

Therefore, after determining the application to be deployed, the deployment environment can be obtained. If the deployment environment is a test environment, obtain the code of the application to be deployed, compile and package the code to generate a product, and upload the product to a preset database; for example, by calling Jenkins to compile, package, and generate a product. After the product is uploaded to the preset database, subsequent deployment operations can be performed based on the list of to-be-deployed machines, such as generating a deployment task and sending it to each to-be-deployed machine to deploy the to-be-deployed application. The version information of the product belongs to the information of the application to be deployed, and can be included in the task parameters of the task to be deployed. The version of the product can be the same as the version of the application to be deployed.

If the deployment environment is an online environment, determine the products of the to-be-deployed application that have passed the test of the to-be-deployed application in the preset database. Wherein, determining the product of the to-be-deployed application that has passed the test of the to-be-deployed application in the preset database includes determining the product version. After determining the products of the to-be-deployed application that have passed the test of the to-be-deployed application in the preset database, subsequent deployment operations can be performed based on the list of to-be-deployed machines, such as generating a deployment task and sending it to each to-be-deployed machine to deploy the to-be-deployed application .

In the application deployment method provided by the embodiment of the present invention, in response to the deployment environment being a test environment, the code of the application to be deployed is obtained, the code is compiled and packaged to generate a product, and the product is uploaded to a preset database, and in response to the deployment environment being an online environment , to determine the product of the application to be deployed that has passed the test of the application to be deployed in the preset database, so as to realize application deployment in the test environment and the online environment.

According to an application deployment method provided by an embodiment of the present invention, the deploying the application to be deployed according to the deployment task includes: in response to the machine to be deployed currently running the application to be deployed, stopping the application to be deployed the application to be deployed; download the product of the corresponding version of the application to be deployed by accessing the preset database; replace the application to be deployed according to the product; start the application to be deployed.

If the application to be deployed (which can include various versions) has been deployed on the machine to be deployed, if the application to be deployed is running when the application is deployed, it is necessary to stop the service (stop the service, that is, stop the running of the application to be deployed), and then Perform operations such as product download, application replacement, and application startup for deployment. Of course, if the application to be deployed is deployed for the first time on the machine to be deployed, the application to be deployed is not running at the time of deployment.

Therefore, when the application to be deployed is deployed according to the deployment task, the application to be deployed is stopped in response to the current application to be deployed on the machine to be deployed; the product of the corresponding version of the application to be deployed is downloaded by accessing the preset database; the application to be deployed is replaced according to the product ; Start the application to be deployed to complete the deployment of the application to be deployed.

In the application deployment method provided by the embodiment of the present invention, the application to be deployed is stopped by responding to the application to be deployed currently running on the machine to be deployed, the product of the corresponding version of the application to be deployed is downloaded by accessing a preset database, the application to be deployed is replaced according to the product, and the application to be deployed is started. Deploying the application realizes the reliable deployment of the application to be deployed.

FIG. 2 is a second schematic flowchart of an application deployment method provided by an embodiment of the present invention. The application deployment method provided by the embodiment of the present invention can be jointly implemented by the server side and the client side. The server side is mainly responsible for data storage and release management. The client side executes specific application deployment actions after receiving commands from the server side, and synchronizes the server side after the actions are completed. Among them, the server side can be divided into two parts: front-end and back-end. The front-end web page is convenient for users to deploy and operate, and the back-end is responsible for permission verification, application packaging, product upload, and generation and deployment tasks. The client (machine to be deployed) is used to consume deployment tasks, and perform operations such as service stop, product package download, and service startup according to the task parameters in the deployment task. As shown in Figure 2, the application deployment process includes:

On the server side, determine whether the user is logged in; if not, jump to the login page; if logged in, verify the publishing permission (deployment permission); ; If it is verified to have the permission to publish, select the application to be deployed.

Determine whether the current release environment (deployment environment) is a test environment (test environment) or an online environment (release environment); if it is a test environment, pull git (git is an open source distributed version control system, which can effectively and quickly Process the code of the application to be deployed in the project version management from very small to very large, compile and package to obtain the product, and upload the product to the preset database. If it is an online environment, select the product version that has passed the test. Determine the list of machines to be deployed and divide deployment batches. After the above processing is completed, the API is called to generate the deployment task of the application to be deployed, and the deployment task is sent in parallel to the to-be-deployed machines in each deployment batch in an asynchronous manner.

After the to-be-deployed machine obtains the to-be-deployed task, it performs processing such as stopping the application, downloading the product, replacing the application, and starting the application according to the task parameters. for inquiries and presentations).

FIG. 3 is a third schematic flowchart of an application deployment method provided by an embodiment of the present invention. Machine 1 and Machine 2 are the Client side, and the rest of the modules belong to the Server side. For example, the publishing platform may be an operating platform used by the server side to publish deployment tasks, query deployment results, and the like. As shown in Figure 3, the application deployment process includes:

Step 1: The deployment environment is the test environment, and the publishing platform calls Jenkins for packaging.

Step 2: Jenkins obtains the code of the application to be deployed by accessing git, and generates the product after compiling and packaging the code.

Step 3: Store the product in minio (object storage server).

Step 4: After uploading the product to minio, Jenkins calls back the publishing platform. The publishing platform will perform subsequent deployment operations based on the selected list of machines to be deployed; considering the standardization of deployment, when the deployment environment is an online environment, the products that have passed the test are directly used.

Step 5: The publishing platform sends a deployment request to the deployment api service.

Step 6: After the deployment api service receives the deployment request, it verifies the publishing parameters (which can be preset parameters for judging the specification of the publishing), and after the verification passes, generates a deployment task and writes it to Redis (a storage system) Task queue; wherein, each to-be-deployed machine in the to-be-deployed list corresponds to a task queue.

Step 7: Generate batch ID and task ID and return to the publishing platform, and the subsequent publishing platform will track the deployment task according to the batch ID and task ID.

Step 8: The service deployment module on the client side will always monitor the task queue, and will perform subsequent application deployment operations when the deployment task is fetched.

Step 9: When deploying the application, download the product of the corresponding version from minio, and perform the application deployment operation.

Step 10: After the application deployment is completed, the deployment process data callback is returned to the publishing platform.

FIG. 4 is a schematic diagram of a task state machine representing task state flow in an application deployment method provided by an embodiment of the present invention. As shown in Figure 4, the task state machine may include the following task states:

a) Initialization: After the new machine completes the initialization work: enter the machine through the publishing platform and associate the application. Since the application on the machine has never been deployed, the status is recorded as initialization.

b) Task queuing: After the user performs the publishing operation through the web page, the server side writes the deployment task into the RedisR task queue, and the client side records it as task queuing before consumption.

c) Waiting for ready: After the service deployment module on the client side consumes the published task, the task status flow changes to waiting for ready. If there is no task being processed by the application to be deployed at this time, the flow continues; otherwise, the task status is still waiting for ready.

d) Starting: If the application meets the deployment conditions without a task being processed, operations such as server shutdown, code replacement, and restart will be performed based on the task parameters.

e) If any step in step d fails, the task status flow changes to failure, otherwise the task status is successful.

The application deployment method provided by the embodiment of the present invention can solve the problems of the application deployment process taking too long to release, difficult to locate problems, and confusing machine management, etc., and better serve the business.

in:

1. Adopt the asynchronous + parallel deployment mode to optimize the deployment process.

Since business applications are mostly offline tasks, in order to avoid running tasks on the machine or problems with a certain machine blocking the overall deployment process when deploying applications, the deployment adopts the asynchronous mode to better support parallel deployment.

2. Aggregate deployment process data to monitor deployment status.

After the client side is deployed, it is called back to the server side through the API. The deployment process data is converged to the server side and stored in the database. The deployment progress and the deployment status of each machine can be queried through the web page with one click, which is convenient for tracking the deployment results of each machine. , to reduce the duration of positioning problems.

3. Unified management of machines, unified management and storage of machines of different applications to the server side, to avoid information inconsistency between multiple pieces of data.

There is a deployment mode of Jenkins+Openssh, which is managed by Jenkins job corresponding to the application, and the application may be deployed to multiple machines. Therefore, machine data is stored in multiple copies. When multiple copies of data are stored in the case of modification (for example, when a machine goes offline, all applications on the machine need to be offline), it is easy to cause data modification errors. In the embodiment of the present invention, the machine list data is stored in the database, and only one copy of the machine data is maintained. The one-to-many relationship between the machine and the application can be managed through the database foreign key association, and the unreliability of information modification is reduced through unified management. .

The embodiment of the present invention converts cluster application deployment into asynchronous publishing tasks, and application deployment of each to-be-deployed machine in the machine cluster is independent of each other and does not affect each other, which can realize true parallel publishing. And each release will generate a new task. By tracking the task status, you can know the release status of each machine, and quickly and efficiently locate the cluster problem machine.

It should be noted that, the multiple preferred implementation manners given in this embodiment can be freely combined on the premise that the logic or structure does not conflict with each other, which is not limited in the present invention.

The application deployment apparatus provided by the embodiment of the present invention is described below, and the application deployment apparatus described below and the application deployment method described above may refer to each other correspondingly.

FIG. 5 is a schematic structural diagram of an application deployment apparatus provided by an embodiment of the present invention. As shown in FIG. 5 , the device includes a determination module 10, a batching module 20 and a deployment module 30, wherein: the determining module 10 is used for: determining a list of machines to be deployed and applications to be deployed; the batching module 20 is used for: according to the The list of to-be-deployed machines is divided into deployment batches; wherein, each of the deployment batches includes at least one of the to-be-deployed machines; the deployment module 30 is configured to: generate a deployment task of the to-be-deployed application, through each of the deployment batches In an asynchronous manner between times, the deployment task is sent in parallel to the to-be-deployed machines in each of the deployment batches, so that the to-be-deployed machines can deploy the to-be-deployed application according to the deployment task.

The application deployment device provided by the embodiment of the present invention effectively improves the application deployment efficiency by sending deployment tasks to the machines to be deployed in an asynchronous manner between deployment batches and in parallel within the same deployment batch.

According to an application deployment apparatus provided by an embodiment of the present invention, the deployment module 30 is configured to send the deployment task to the deployment tasks in the deployment batches in parallel in an asynchronous manner between the deployment batches. When the to-be-deployed machine is, it is specifically used to: write the deployment task in parallel to the task queue corresponding to the to-be-deployed machine in each of the deployment batches in an asynchronous manner between the deployment batches .

The application deployment device provided by the embodiment of the present invention writes deployment tasks in parallel to the task queue corresponding to the to-be-deployed machine in each deployment batch in an asynchronous manner between each deployment batch, so as to facilitate the implementation of the deployment process of the to-be-deployed machine management.

According to an application deployment apparatus provided by an embodiment of the present invention, the deployment module 30 is further configured to: receive deployment process data sent by the to-be-deployed machine; wherein the deployment process data includes the task status of the deployment task.

The application deployment device provided by the embodiment of the present invention, by receiving the deployment process data including the task status sent by the to-be-deployed machine, facilitates the supervision of the deployment status of the deployment task, facilitates the timely discovery of problem machines, and avoids unnecessary waste of time.

According to an application deployment device provided by an embodiment of the present invention, the task status includes at least one of task queuing, waiting for ready, starting, successful, and failed, wherein: the deployment task has not been consumed by the to-be-deployed machine , the task status is task queuing; the to-be-deployed machine consumes the deployment task, and the task status is waiting for ready; the to-be-deployed machine consumes the deployment task and meets the deployment conditions of the deployment task , the task state is starting; wherein, when the task state is starting, the to-be-deployed machine executes the action of deploying the application to be deployed according to the deployment task; If the task of deploying the application to be deployed is successfully executed, the task status is successful; the action of deploying the application to be deployed according to the deployment task fails to be executed, and the task status is failed.

The application deployment device provided by the embodiment of the present invention improves the richness and comprehensiveness of the acquisition of deployment process information by setting the task statuses of task queuing, waiting for ready, starting and indicating the deployment result, and is conducive to understanding the entire application deployment process.

According to an application deployment apparatus provided by an embodiment of the present invention, in the asynchronous manner between the deployment batches, the deployment task is sent in parallel to the to-be-deployed machines in the deployment batches After that, the deployment module 30 is further configured to: generate a batch ID corresponding to the deployment batch and a task ID corresponding to the to-be-deployed machine in the deployment batch; wherein the batch ID is the same as the The to-be-deployed machines included in the deployment batch correspond; the deployment process data is queried according to the batch ID and/or the task ID.

The application deployment device provided by the embodiment of the present invention queries the deployment process data according to the batch ID and/or the task ID by generating a batch ID corresponding to the deployment batch and a task ID corresponding to the machine to be deployed in the deployment batch, It realizes the distinction between different deployment batches and different machines to be deployed, and improves the convenience of data query in the deployment process.

According to an application deployment apparatus provided by an embodiment of the present invention, when the determining module 10 is used to determine the list of machines to be deployed, it is specifically configured to: on a web page, in response to the selection of the application to be deployed, display the relevant application to be deployed. The machine list of the application; select the to-be-deployed machine from the machine list associated with the to-be-deployed application, and determine the to-be-deployed machine list according to the selection result.

The application deployment device provided by the embodiment of the present invention displays a list of machines associated with the application to be deployed on the web page in response to the selection of the application to be deployed, selects the machine to be deployed from the list of machines associated with the application to be deployed, and selects the machine to be deployed according to the selection result. Determining the list of machines to be deployed improves the simplicity of determining the list of machines to be deployed.

According to an application deployment device provided by an embodiment of the present invention, the deployment module 30 is further configured to: in response to the deployment environment being a test environment, obtain the code of the application to be deployed, compile and package the code to generate a product, and The product is uploaded to a preset database; in response to the deployment environment being an online environment, determine the product of the application to be deployed that has passed the test of the application to be deployed in the preset database; wherein the product includes Version Information.

The application deployment device provided by the embodiment of the present invention obtains the code of the application to be deployed in response to the deployment environment being a test environment, compiles and packages the code to generate a product, and uploads the product to a preset database, and responds that the deployment environment is an online environment , to determine the product of the application to be deployed that has passed the test of the application to be deployed in the preset database, so as to realize application deployment in the test environment and the online environment.

According to an application deployment apparatus provided by an embodiment of the present invention, the deployment module 30 is configured to send the deployment task to the to-be-deployed machines in each of the deployment batches in parallel, for the to-be-deployed machines Deploying the application to be deployed according to the deployment task is specifically configured to: send the deployment task to the to-be-deployed machines in each of the deployment batches in parallel, so that the to-be-deployed machines can respond to the The to-be-deployed machine currently runs the to-be-deployed application, stop the to-be-deployed application, download the product of the corresponding version of the to-be-deployed application by accessing the preset database, and replace the to-be-deployed application according to the product , and start the application to be deployed.

The application deployment device provided by the embodiment of the present invention stops the application to be deployed by responding to the application to be deployed currently running on the machine to be deployed, downloads the product of the corresponding version of the application to be deployed by accessing a preset database, replaces the application to be deployed according to the product, and starts the application to be deployed. Deploying the application realizes the reliable deployment of the application to be deployed.

FIG. 6 is a schematic structural diagram of an application deployment system provided by an embodiment of the present invention. As shown in FIG. 6 , the system includes an application deployment apparatus 100 and a machine cluster 200, wherein: the application deployment apparatus 100 is used for: determining a list of machines to be deployed and applications to be deployed; dividing deployment batches according to the list of machines to be deployed times; generating the deployment task of the application to be deployed, and sending the deployment task to the machines 201 to be deployed in each of the deployment batches in parallel in an asynchronous manner between the deployment batches; wherein, the The machine cluster 200 includes the to-be-deployed machine 201 in the to-be-deployed machine list, and each deployment batch includes at least one of the to-be-deployed machine 201;

The to-be-deployed machine 201 is configured to: receive the deployment task, and deploy the to-be-deployed application according to the deployment task.

The application deployment system provided by the embodiment of the present invention effectively improves the application deployment efficiency by sending deployment tasks to the machines to be deployed in an asynchronous manner between deployment batches and in parallel within the same deployment batch.

According to an application deployment system provided by an embodiment of the present invention, the application deployment apparatus 100 is configured to send the deployment task to all the deployment batches in parallel in an asynchronous manner between the deployment batches. When the to-be-deployed machine is described, it is specifically used to write the deployment task in parallel to the task queue corresponding to the to-be-deployed machine in each of the deployment batches in an asynchronous manner among the deployment batches.

The application deployment system provided by the embodiments of the present invention writes deployment tasks in parallel to the task queues corresponding to the machines to be deployed in each deployment batch in an asynchronous manner between each deployment batch, so as to facilitate the deployment process of the machines to be deployed management.

According to an application deployment system provided by an embodiment of the present invention, the machine 201 to be deployed is further configured to: send deployment process data to the application deployment apparatus 100; wherein the deployment process data includes the task status of the deployment task; the application deployment apparatus 100 is further configured to receive the deployment process data sent by the to-be-deployed machine 201 .

The application deployment system provided by the embodiments of the present invention, by receiving the deployment process data including the task status sent by the to-be-deployed machine, facilitates the supervision of the deployment status of the deployment task, facilitates timely discovery of problem machines, and avoids unnecessary waste of time.

According to an application deployment system provided by an embodiment of the present invention, the task status includes at least one of task queuing, waiting for ready, starting, successful, and failed, and the machine to be deployed 201 is further configured to: respond to the unconsumed the deployment task, the task status is set to task queuing; in response to consuming the deployment task, the task status is set to waiting for ready; in response to consuming the deployment task and meeting the deployment conditions of the deployment task, The task status is set to be under activation; wherein, when the task status is under activation, the executing the action of deploying the application to be deployed according to the deployment task; in response to the execution of the deployment task according to the deployment task; If the action of deploying the application to be deployed is successfully executed, the task status is set to success, and the action of deploying the application to be deployed according to the deployment task fails to be executed, and the task status is set to fail.

The application deployment system provided by the embodiment of the present invention improves the richness and comprehensiveness of the information acquisition of the deployment process by setting the task statuses of task queuing, waiting for ready, starting and indicating the deployment result, which is beneficial to understand the entire application deployment process.

According to an application deployment system provided by an embodiment of the present invention, in the asynchronous manner between the deployment batches, the deployment task is sent to the machines to be deployed in the deployment batches in parallel After that, the application deployment apparatus 100 is further configured to generate a batch ID corresponding to the deployment batch and a task ID corresponding to the to-be-deployed machine in the deployment batch; wherein the batch ID is the same as the The to-be-deployed machines included in the deployment batch correspond; the deployment process data is queried according to the batch ID and/or the task ID.

In the application deployment system provided by the embodiment of the present invention, by generating a batch ID corresponding to the deployment batch and a task ID corresponding to a machine to be deployed in the deployment batch, the deployment process data is queried according to the batch ID and/or the task ID, It realizes the distinction between different deployment batches and different machines to be deployed, and improves the convenience of data query in the deployment process.

According to an application deployment system provided by an embodiment of the present invention, when the application deployment apparatus 100 is used to determine the list of machines to be deployed, it is specifically configured to: on a web page, in response to the selection of the application to be deployed, display the application related to the to-be-deployed application. A machine list for deploying an application; selecting the to-be-deployed machine from the machine list associated with the to-be-deployed application, and determining the to-be-deployed machine list according to the selection result.

In the application deployment system provided by the embodiment of the present invention, in response to the selection of the application to be deployed on the web page, a list of machines associated with the application to be deployed is displayed, and the machine to be deployed is selected from the list of machines associated with the application to be deployed, according to the selection result. Determining the list of machines to be deployed improves the simplicity of determining the list of machines to be deployed.

According to an application deployment system provided by an embodiment of the present invention, the application deployment apparatus 100 is further configured to: in response to the deployment environment being a test environment, obtain the code of the application to be deployed, compile and package the code to generate a product, uploading the product to a preset database; in response to the deployment environment being an online environment, determine the product of the application to be deployed that has passed the test of the application to be deployed in the preset database; wherein the product includes a version information.

The application deployment system provided by the embodiment of the present invention obtains the code of the application to be deployed in response to the deployment environment being a test environment, compiles and packages the code to generate a product, and uploads the product to a preset database, and responds that the deployment environment is an online environment , to determine the product of the application to be deployed that has passed the test of the application to be deployed in the preset database, so as to realize application deployment in the test environment and the online environment.

According to an application deployment system provided by an embodiment of the present invention, when the machine to be deployed 201 is used to deploy the application to be deployed according to the deployment task, it is specifically used for: in response to the current running of the machine to be deployed the application to be deployed, stop the application to be deployed; download the product of the corresponding version of the application to be deployed by accessing the preset database; replace the application to be deployed according to the product; start the application to be deployed.

The application deployment system provided by the embodiment of the present invention stops the application to be deployed by responding to the application to be deployed currently running on the machine to be deployed, downloads the product of the corresponding version of the application to be deployed by accessing a preset database, replaces the application to be deployed according to the product, and starts the application to be deployed. Deploying the application realizes the reliable deployment of the application to be deployed.

FIG. 7 is a schematic structural diagram of an electronic device provided by an embodiment of the present invention. As shown in FIG. 7 , the electronic device may include: a processor (processor) 710, a communications interface (Communications Interface) 720, a memory (memory) 730, and a communication bus 740 , wherein the processor 710 , the communication interface 720 , and the memory 730 communicate with each other through the communication bus 740 . The processor 710 can invoke the logic instructions in the memory 730 to execute an application deployment method, the method includes: determining a list of machines to be deployed and applications to be deployed; dividing deployment batches according to the list of machines to be deployed; wherein each of the The deployment batch includes at least one of the machines to be deployed; a deployment task of the application to be deployed is generated, and the deployment task is sent to each of the deployment batches in parallel in an asynchronous manner between the deployment batches The to-be-deployed machine in , for the to-be-deployed machine to deploy the to-be-deployed application according to the deployment task.

In addition, the above-mentioned logic instructions in the memory 730 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

On the other hand, an embodiment of the present invention further provides a computer program product, where the computer program product includes a computer program, and the computer program can be stored on a non-transitory computer-readable storage medium, and when the computer program is executed by a processor, The computer can execute the application deployment method provided by the above methods, and the method includes: determining a list of machines to be deployed and applications to be deployed; dividing deployment batches according to the list of machines to be deployed; wherein, at least one of the deployment batches Including a machine to be deployed; generating a deployment task of the application to be deployed, and sending the deployment task in parallel to the to-be-deployed in each of the deployment batches in an asynchronous manner among the deployment batches A deployment machine is used for the to-be-deployed machine to deploy the to-be-deployed application according to the deployment task.

In yet another aspect, an embodiment of the present invention further provides a non-transitory computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, it is implemented to execute the application deployment method provided by the above methods, and the method Including: determining a list of machines to be deployed and applications to be deployed; dividing deployment batches according to the list of machines to be deployed; wherein, each of the deployment batches includes at least one of the machines to be deployed; A deployment task, sending the deployment task in parallel to the to-be-deployed machines in each of the deployment batches in an asynchronous manner among the deployment batches, so that the to-be-deployed machines can perform the deployment tasks according to the deployment tasks. Deploy the application to be deployed.

The device embodiments described above are only illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed over multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. Those of ordinary skill in the art can understand and implement it without creative effort.

From the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and certainly can also be implemented by hardware. Based on this understanding, the above-mentioned technical solutions can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic A disc, an optical disc, etc., includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in various embodiments or some parts of the embodiments.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that it can still be The technical solutions described in the foregoing embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (10)

1. an application deployment method, is characterized in that, comprises: Determine the list of machines to be deployed and applications to be deployed; Divide deployment batches according to the list of to-be-deployed machines; wherein, each of the deployment batches includes at least one of the to-be-deployed machines; Generate a deployment task of the application to be deployed, and send the deployment task in parallel to the to-be-deployed machines in each of the deployment batches in an asynchronous manner for the to-be-deployed The deployment machine deploys the application to be deployed according to the deployment task. 2 . The application deployment method according to claim 1 , wherein the deployment task is sent to the said deployment batches in parallel in an asynchronous manner between the deployment batches. 3 . Machines to be deployed, including: The deployment task is written in parallel to the task queue corresponding to the to-be-deployed machine in each of the deployment batches in an asynchronous manner among the deployment batches. 3. The application deployment method according to claim 2, wherein the method further comprises: The deployment process data sent by the to-be-deployed machine is received; wherein the deployment process data includes the task status of the deployment task. 4. The application deployment method according to claim 3, wherein the task status comprises at least one of task queuing, waiting for ready, starting, success and failure, wherein: The to-be-deployed machine has not consumed the deployment task, and the task status is that the task is in queue; The to-be-deployed machine consumes the deployment task, and the task state is waiting to be ready; The to-be-deployed machine consumes the deployment task and satisfies the deployment conditions of the deployment task, and the task state is starting; wherein, when the task state is starting, the to-be-deployed machine executes the The deployment task performs the action of deploying the application to be deployed; The action of deploying the application to be deployed according to the deployment task is successfully executed, and the task status is successful; the action of deploying the application to be deployed according to the deployment task fails, the task status is successful. Status is Failed. 5 . The application deployment method according to claim 3 , wherein in the asynchronous manner between the deployment batches, the deployment task is sent to all the deployment batches in parallel. 6 . After the machine to be deployed is described, the method further includes: Generate a batch ID corresponding to the deployment batch and a task ID corresponding to the to-be-deployed machine in the deployment batch; wherein the batch ID is the same as the to-be-deployed machine included in the deployment batch Deployment machine corresponds; The deployment process data is queried according to the batch ID and/or the task ID. 6. The application deployment method according to claim 1, wherein the determining the list of machines to be deployed comprises: On the web page, in response to the selection of the application to be deployed, displaying a list of machines associated with the application to be deployed; The to-be-deployed machine is selected from the machine list associated with the to-be-deployed application, and the to-be-deployed machine list is determined according to the selection result. 7. The application deployment method according to claim 1, wherein the method further comprises: In response to the deployment environment being a test environment, obtain the code of the application to be deployed, compile and package the code to generate a product, and upload the product to a preset database; In response to the deployment environment being an online environment, determine a product of the to-be-deployed application that has passed the test of the to-be-deployed application in the preset database; wherein the product includes version information. 8. The application deployment method according to claim 7, wherein the deploying the application to be deployed according to the deployment task comprises: In response to the to-be-deployed machine currently running the to-be-deployed application, stopping the to-be-deployed application; Download the product of the corresponding version of the application to be deployed by accessing the preset database; Replace the application to be deployed according to the product; Start the application to be deployed. 9. An application deployment device, comprising: The determining module is used to: determine the list of machines to be deployed and the applications to be deployed; A batching module, configured to: divide deployment batches according to the list of machines to be deployed; wherein, each of the deployment batches includes at least one of the to-be-deployed machines; A deployment module, configured to: generate a deployment task of the application to be deployed, and send the deployment task in parallel to the to-be-deployed machines in each of the deployment batches in an asynchronous manner among the deployment batches , so that the to-be-deployed machine deploys the to-be-deployed application according to the deployment task. 10. A non-transitory computer-readable storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, the steps of the application deployment method according to any one of claims 1 to 8 are implemented .

Images