CN115291936A

CN115291936A - Deployment document generation method and device and electronic equipment

Info

Publication number: CN115291936A
Application number: CN202210958854.5A
Authority: CN
Inventors: 杨飞
Original assignee: Industrial and Commercial Bank of China Ltd ICBC; ICBC Technology Co Ltd
Current assignee: Industrial and Commercial Bank of China Ltd ICBC; ICBC Technology Co Ltd
Priority date: 2022-08-09
Filing date: 2022-08-09
Publication date: 2022-11-04

Abstract

The invention discloses a method and a device for generating a deployment document and electronic equipment, and relates to the field of financial science and technology or other related fields, wherein the method for generating the deployment document comprises the following steps: receiving a middleware deployment request, inquiring a preset service address table based on a middleware identifier to obtain a target service address table, deploying the middleware indicated by the middleware identifier on each server by adopting a preset deployment script based on deployment parameters, converting a deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generating a deployment document based on the preset command set and a command annotation corresponding to each preset command in the preset command set. The invention solves the technical problem that the accuracy of the deployment document is easily reduced because the deployment document is manually maintained in the related technology.

Description

Deployment document generation method and device and electronic equipment

Technical Field

The invention relates to the field of financial science and technology, in particular to a method and a device for generating a deployment document and electronic equipment.

Background

In the related art, the deployment document of the middleware often needs to be written and revised manually through a file (such as a Word document), and the revision time and revision content of each revision need to be recorded at the top of the file. However, by manually maintaining the deployment document, modifications are easily missed, and manual backup is required before each modification. It is easy to cause a reduction in the accuracy of the deployment document.

In view of the above problems, no effective solution has been proposed.

Disclosure of Invention

The embodiment of the invention provides a method and a device for generating a deployment document and electronic equipment, which are used for at least solving the technical problem that the accuracy of the deployment document is easily reduced due to manual maintenance of the deployment document in the related technology.

According to an aspect of an embodiment of the present invention, there is provided a method for generating a deployment document, including: receiving a middleware deployment request, wherein the middleware deployment request at least comprises: middleware identification and deployment parameters; inquiring a preset service address table based on the middleware identification to obtain a target service address table, wherein each service address in the target service address table corresponds to one server; deploying the middleware indicated by the middleware identification on each server by adopting a preset deployment script based on the deployment parameters; and converting the deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generating a deployment document based on the preset command set and command annotations corresponding to each preset command in the preset command set.

Optionally, before receiving the middleware deployment request, the method further includes: based on a preset script format, creating a corresponding inspection script, a deployment script and an uninstalling script for each middleware, wherein the inspection script is used for inspecting the deployment state of the middleware, the deployment script is used for deploying the middleware, and the uninstalling script is used for uninstalling the middleware; and recording each middleware, the check script, the deployment script and the uninstall script corresponding to the middleware into a preset routing table.

Optionally, the step of querying a preset service address table based on the middleware identifier to obtain a target service address table includes: inquiring the preset service address table to obtain an inquiry result, wherein the inquiry result records the deployment state of deploying the middleware in each server; screening the servers which are recorded as undeployed in the query result to obtain a target server set; and generating the target service address table based on the target server set.

Optionally, before deploying the middleware indicated by the middleware identifier on each server by using a preset deployment script based on the deployment parameters, the method further includes: responding to the middleware deployment request, and generating a target task, wherein the target task is used for deploying the middleware indicated by the middleware identification to the server indicated by each service address; adding the target task into a task table, and displaying task information related to the target task in the task table on a front-end page, wherein the task information comprises: task number, task type, applicant, task progress, task log, execution details, and number of service addresses.

Optionally, after generating the target task in response to the middleware deployment request, the method further includes: calling the inspection script corresponding to the target task; adopting the inspection script to sequentially inspect whether the middleware has been deployed by each server indicated by the service address in the target task, and obtaining a plurality of inspection results, wherein the inspection results at least comprise: task number, service address, and checking state; under the condition that the checking result is converted into a first interface parameter and the first interface parameter is transmitted to a first preset rear-end interface, inserting the first interface parameter into a preset installation state table, and creating a task record corresponding to the task number; and inquiring the preset installation state table, and calling the deployment script corresponding to the target task when the number of records of the task records related to the task number is equal to the number of the service addresses and the checking state indicated by each task record is passed.

Optionally, after the deployment script corresponding to the target task is called, the method further includes: adopting the deployment script to sequentially deploy the middleware for each server indicated by the service address in the target task to obtain a plurality of deployment results, wherein the deployment results at least comprise: task number, service address, installation state; updating an installation state field of the task record associated with the task number in the preset installation state table based on the second interface parameter under the condition that the deployment result is converted into the second interface parameter and the second interface parameter is transmitted to a second preset back-end interface; under the condition that the installation state fields are not empty, determining that the server indicated by each service address in the target task is completely deployed; and under the condition that the installation state fields are all installed successfully, determining that the server indicated by each service address in the target task is deployed successfully.

Optionally, after generating a deployment document based on the preset command set and a command annotation corresponding to each preset command in the preset command set, the method further includes: under the condition that the middleware is updated, updating a check script, a deployment script and an uninstalling script corresponding to the middleware based on the update parameters of the middleware; determining updated target deployment commands in the inspection script, the deployment script and the uninstallation script; and modifying a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document.

Optionally, after modifying, based on the target deployment command, a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command to obtain an updated deployment document, the method further includes: extracting the preset command set in the deployment document; executing the preset command set in a preset test environment to deploy the middleware on a preset server to obtain a parameter file set; replacing the service address of the preset server in each parameter file in the parameter file set with a service address in a pre-production environment under the condition that the middleware is successfully deployed on the preset server to obtain a target file set; packaging the target file set after the log file is deleted to obtain a target file, and generating a target character string value based on the target file; acquiring a standard file set in the pre-commissioning environment, and deleting log files in the standard file set to obtain a target standard file set; packaging the target standard file set to obtain a standard file, and generating a standard character string value based on the standard file; determining that the deployment document is validated if the target string value is consistent with the standard string value.

According to another aspect of the embodiments of the present invention, there is further provided a deployed document generating apparatus, including: a receiving unit, configured to receive a middleware deployment request, where the middleware deployment request at least includes: middleware identification and deployment parameters; the query unit is used for querying a preset service address table based on the middleware identifier to obtain a target service address table, wherein each service address in the target service address table corresponds to one server; the deployment unit is used for deploying the middleware indicated by the middleware identifier on each server by adopting a preset deployment script based on the deployment parameters; the generating unit is used for converting the deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generating a deployment document based on the preset command set and the command annotations corresponding to each preset command in the preset command set.

Optionally, the generating device further includes: the middleware deployment method comprises the steps that a first creating module is used for creating a corresponding checking script, a corresponding deployment script and a corresponding uninstalling script for each middleware based on a preset script format before receiving a middleware deployment request, wherein the checking script is used for checking the deployment state of the middleware, the deployment script is used for deploying the middleware, and the uninstalling script is used for uninstalling the middleware; the first recording module is used for recording each middleware and the inspection script, the deployment script and the uninstalling script corresponding to the middleware into a preset routing table.

Optionally, the query unit includes: the first query module is used for querying the preset service address table to obtain a query result, wherein the query result records the deployment state of the middleware deployed in each server; the first screening module is used for screening the servers which are recorded as undeployed in the query result to obtain a target server set; a first generating module, configured to generate the target service address table based on the target server set.

Optionally, the generating device further includes: a second generating module, configured to respond to the middleware deployment request before deploying the middleware indicated by the middleware identifier on each server by using a preset deployment script based on the deployment parameter, and generate a target task, where the target task is used to deploy the middleware indicated by the middleware identifier to each server indicated by the service address; a first display module, configured to add the target task to a task table, and display task information associated with the target task in the task table on a front-end page, where the task information includes: task number, task type, applicant, task progress, task log, execution details, and number of service addresses.

Optionally, the generating device further includes: the first calling module is used for calling the inspection script corresponding to the target task after responding to the middleware deployment request and generating the target task; a first checking module, configured to sequentially check, by using the checking script, whether the middleware has been deployed by each server indicated by the service address in the target task, so as to obtain a plurality of checking results, where the checking results at least include: task number, service address, and inspection state; the first inserting module is used for inserting the first interface parameter into a preset installation state table and creating a task record corresponding to the task number under the condition that the checking result is converted into the first interface parameter and the first interface parameter is transmitted to a first preset rear-end interface; and the second calling module is used for inquiring the preset installation state table, and calling the deployment script corresponding to the target task when the number of records of the task records related to the task number is equal to the number of the service addresses and the checking state indicated by each task record passes the checking.

Optionally, the generating device further includes: a first deployment module, configured to deploy, after the deployment script corresponding to the target task is called, the middleware for the server indicated by each service address in the target task in sequence by using the deployment script, so as to obtain a plurality of deployment results, where the deployment results at least include: task number, service address, installation state; a first updating module, configured to update, based on a second interface parameter, an installation state field of the task record associated with the task number in the preset installation state table when the deployment result is converted into the second interface parameter and the second interface parameter is transmitted to a second preset backend interface; a first determining module, configured to determine that, in the case that none of the installation status fields is empty, each server indicated by the service address in the target task is completely deployed; and a second determining module, configured to determine that, when the installation status fields are all installed successfully, the server indicated by each service address in the target task is deployed successfully.

Optionally, the generating device further includes: the second updating module is used for updating the inspection script, the deployment script and the uninstalling script corresponding to the middleware based on the updating parameters of the middleware after generating a deployment document based on the preset command set and the command annotation corresponding to each preset command in the preset command set and under the condition that the middleware is updated; a third determining module, configured to determine a target deployment command updated in the inspection script, the deployment script, and the uninstallation script; and the first modification module is used for modifying a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document.

Optionally, the generating device further includes: the first extraction module is used for extracting the preset command set in the deployment document after modifying a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document; the first execution module is used for executing the preset command set in a preset test environment so as to deploy the middleware on a preset server to obtain a parameter file set; the first replacement module is used for replacing the service address of the preset server in each parameter file in the parameter file set with the service address in the pre-production environment under the condition that the middleware is successfully deployed on the preset server to obtain a target file set; the first packing module is used for packing the target file set after the log files are deleted to obtain a target file, and generating a target character string value based on the target file; the first acquisition module is used for acquiring a standard file set in the pre-commissioning environment and deleting log files in the standard file set to obtain a target standard file set; the second packing module is used for packing the target standard file set to obtain a standard file and generating a standard character string value based on the standard file; and the fourth determining module is used for determining that the deployment document is verified under the condition that the target string value is consistent with the standard string value.

According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including one or more processors and a memory, where the memory is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the method for generating a deployment document described above.

In the method, a middleware deployment request is received, a preset service address table is inquired based on a middleware identifier to obtain a target service address table, a preset deployment script is adopted to deploy the middleware indicated by the middleware identifier on each server based on deployment parameters, a deployment command in the preset deployment script when the middleware is deployed is converted into a preset command to obtain a preset command set, and a deployment document is generated based on the preset command set and a command annotation corresponding to each preset command in the preset command set. In the application, the servers needing to deploy the middleware are determined through the middleware identification carried by the middleware deployment request, then the middleware is deployed on each server by adopting the preset deployment script, meanwhile, the deployment command in the preset deployment script when the middleware is deployed is converted into the preset command, the deployment document is automatically generated according to the preset command and the command annotation corresponding to the preset command, the deployment process and the process of creating the deployment document are integrated, manual maintenance is not needed, the accuracy of the deployment document can be improved, and the technical problem that the accuracy of the deployment document is easily reduced due to manual maintenance of the deployment document in the related technology is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention and do not constitute a limitation of the invention. In the drawings:

FIG. 1 is a flow diagram of an alternative deployment document generation method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of an alternative deployment document generation apparatus according to an embodiment of the invention;

fig. 3 is a block diagram of a hardware structure of an electronic device (or a mobile device) for a method of generating a deployment document according to an embodiment of the present invention.

Detailed Description

In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that the method and the apparatus for generating a deployment document in the present disclosure may be used in the financial technology field to generate a deployment document, and may also be used in any field other than the financial technology field to generate a deployment document.

It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for presentation, analyzed data, etc.) referred to in the present disclosure are information and data authorized by the user or sufficiently authorized by each party. For example, an interface is provided between the system and the relevant user or institution, and before obtaining the relevant information, an obtaining request needs to be sent to the user or institution through the interface, and after receiving the consent information fed back by the user or institution, the relevant information needs to be obtained.

The embodiments of the invention described below may be applied to various systems/applications/devices that generate deployment documents. The invention integrates the deployment process and the process of creating the deployment document, and simultaneously can verify the consistency of the deployment result of the automatically generated deployment document and the deployment result of the production environment, thereby ensuring the accuracy of the deployment document. Moreover, the problem that the deployed document is not accurate any more along with the lapse of time can be effectively solved, the maintenance cost of the deployed document can be saved, and the satisfaction degree of customers is improved.

The present invention will be described in detail with reference to examples.

Example one

In accordance with an embodiment of the present invention, there is provided a method of deployed document generation embodiment, it being noted that the steps illustrated in the flowchart of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases, the steps illustrated or described may be performed in an order different than presented herein.

FIG. 1 is a flowchart of an alternative deployment document generation method according to an embodiment of the present invention, as shown in FIG. 1, the method includes the following steps:

step S101, receiving a middleware deployment request, wherein the middleware deployment request at least comprises: middleware identification and deployment parameters.

Step S102, based on the middleware identification, a preset service address table is inquired to obtain a target service address table, wherein each service address in the target service address table corresponds to one server.

And step S103, deploying the middleware indicated by the middleware identifier on each server by adopting a preset deployment script based on the deployment parameters.

Step S104, converting the deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generating a deployment document based on the preset command set and the command annotation corresponding to each preset command in the preset command set.

Through the steps, a middleware deployment request can be received, a preset service address table is inquired based on the middleware identification to obtain a target service address table, the middleware indicated by the middleware identification is deployed on each server based on the deployment parameters by adopting the preset deployment script, the deployment command in the preset deployment script when the middleware is deployed is converted into the preset command to obtain a preset command set, and a deployment document is generated based on the preset command set and the command annotation corresponding to each preset command in the preset command set. In the embodiment of the invention, the servers needing to deploy the middleware can be determined through the middleware identification carried by the middleware deployment request, then the middleware is deployed on each server by adopting the preset deployment script, meanwhile, the deployment command in the preset deployment script when the middleware is deployed is converted into the preset command, the deployment document is automatically generated according to the preset command and the command annotation corresponding to the preset command, and the deployment process and the process of creating the deployment document are integrated without manual maintenance, so that the accuracy of the deployment document can be improved, and the technical problem that the accuracy of the deployment document is easily reduced due to manual maintenance of the deployment document in the related technology is solved.

The following will explain the embodiments of the present invention in detail with reference to the above steps.

In an embodiment of the present invention, before receiving the middleware deployment request, an optional method further includes: based on a preset script format, creating a corresponding inspection script, a deployment script and an uninstalling script for each middleware, wherein the inspection script is used for inspecting the deployment state of the middleware, the deployment script is used for deploying the middleware, and the uninstalling script is used for uninstalling the middleware; and recording each middleware and the check script, the deployment script and the uninstall script corresponding to the middleware into a preset routing table.

In the embodiment of the present invention, a corresponding check script (agent _ check), a deployment script (agent _ install), and an uninstallation script (agent _ uninstant) may be respectively created for each middleware, and these three scripts may follow a preset script format (for example, an ansable playbook script editing format), where the check script is used to check a deployment state of the corresponding middleware on a server, the deployment script is used to deploy the corresponding middleware on the server, and the uninstallation script is used to uninstall the corresponding middleware on the server, and then each middleware, the check script, the deployment script, and the uninstallation script corresponding to the middleware may be recorded in a preset routing table, so that when a certain middleware is selected for deployment on a front-end page, the system may automatically find the corresponding check script to check the deployment state and deploy the deployment script to deploy the deployment.

In the embodiment of the present invention, a front-end page may be developed through a preset language (e.g., java language), a user may screen a middleware to be deployed on the front-end page, and after selecting the middleware, the user needs to input corresponding deployment parameters (i.e., some configuration parameters of the middleware, such as an installation path, an access port, a required memory, and the like), click to deploy to enter a task page, that is, the front-end page may generate a middleware deployment request according to a middleware identifier indicated by the selected middleware and the corresponding deployment parameters, and transmit the middleware deployment request to a back end for execution.

Optionally, the step of querying the preset service address table based on the middleware identifier to obtain a target service address table includes: inquiring a preset service address table to obtain an inquiry result, wherein the inquiry result records the deployment state of the middleware deployed in each server; screening the servers with the undeployed states recorded in the query results to obtain a target server set; based on the set of target servers, a target service address table is generated.

In the embodiment of the present invention, a backend program may access a system ledger, query a preset service address table in the system ledger according to a middleware identifier to obtain a query result, where the query may record which servers have deployed the middleware and which servers have not deployed the middleware (i.e., record, in the query result, deployment states of the middleware deployed in each server), then may screen servers whose deployment states are recorded in the query result as being undeployed to obtain a target server set, and generate a target service address table based on the target server set, so that the middleware indicated by the middleware identifier may be deployed on a server indicated by each service address in the target service address table.

In another alternative embodiment, the filtered servers without deployed middleware may be returned to the front-end page in a list format, and at this time, the user may select multiple servers in the front-end page for deployment.

Optionally, before deploying the middleware indicated by the middleware identifier on each server by using a preset deployment script based on the deployment parameter, the method further includes: responding to the middleware deployment request, and generating a target task, wherein the target task is used for deploying the middleware indicated by the middleware identification to the server indicated by each service address; adding the target task into a task table, and displaying task information related to the target task in the task table on a front-end page, wherein the task information comprises: task number, task type, applicant, task progress, task log, execution details, and number of service addresses.

In the embodiment of the invention, a back-end program can respond to a middleware deployment request to generate a target task, wherein the target task is used for deploying middleware indicated by a middleware identifier to a server indicated by each service address, then the target task is added into a task table, and task information related to the target task in the task table is displayed on a front-end page (namely when a user clicks deployment, the back-end program can create the task information of the target task, wherein the task information comprises a task number, a task type, an applicant, a task progress, a task log, execution details, the number of service addresses and the like, the tasks are executed in a background, and after the user clicks deployment, the back-end program can jump to the task page to display the task information of each task in the task table).

Table 1 is task information of a certain task in an optional task table in this embodiment, as shown in table 1:

TABLE 1

In the embodiment of the present invention, the task information includes information such as a task type and a task state (i.e., a task progress, an execution detail, and the like), and the execution detail may include time consumed for checking and installing, and the like. The latest task progress (i.e., the current task state) may be queried through a refresh button next to the task progress displayed on the task page. During the inspection, the task progress may be marked as in-inspection, and the result of the inspection is one of an inspection pass and an inspection fail. During deployment, the task progress may be marked as in-deployment, and the result of deployment is one of failure of deployment and completion of deployment. The task log in this embodiment may be downloaded, and includes a check log (check _ task number.log) and an installation log (install _ task number.log), and is mainly used for problem handling when an installation is abnormal. Meanwhile, in the task, the time consumed for inspection and the time consumed for installation can be recorded and can be used as a reference index in the subsequent optimization process.

In another optional embodiment, before deploying the middleware indicated by the middleware identifier on each server by using a preset deployment script based on the deployment parameters, the backend program may find a corresponding inspection script of the middleware according to the selected middleware identifier, check whether the server screened by the system ledger has deployed the middleware, and enter an installation process if the inspection is passed through the confirmation that the middleware is not installed. Normally, the server information provided by the system ledger is accurate, but in order to avoid repeated installation of servers with deployed middleware which are not correctly marked, the backend program calls the inspection script to sequentially inspect the related servers, and after the inspection is finished, the inspection result is uploaded to the backend program in a mode of calling the backend interface, and the page display is carried out. Due to the fact that the time for checking the plurality of servers is long, when a user clicks and deploys, the user can jump to the task page and display task information automatically created by the back-end program on the task page, and the tasks can be automatically executed by the back-end.

Optionally, after responding to the middleware deployment request and generating the target task, the method further includes: calling a checking script corresponding to the target task; adopting a checking script to check whether the server indicated by each service address in the target task has deployed the middleware in sequence to obtain a plurality of checking results, wherein the checking results at least comprise: task number, service address, and inspection state; under the condition that the checking result is converted into a first interface parameter and the first interface parameter is transmitted to a first preset rear-end interface, inserting the first interface parameter into a preset installation state table, and creating a task record corresponding to the task number; and querying a preset installation state table, and calling a deployment script corresponding to the target task under the condition that the number of records of the task records related to the task number is equal to the number of service addresses and the checking state indicated by each task record is passed.

In the embodiment of the present invention, the target task may be inserted into the task table to obtain a task record, including: the method comprises the steps of task number, task progress and the like, wherein the initialized value of a task progress field can be used in a task number log file name and a task detailed table in the process of checking, and an ipCnt (namely the number of service addresses) field is used for recording the number of the service addresses IP which need to be deployed at present. Yml scripts (i.e., check scripts corresponding to the target task) may then be called by the back-end. In the embodiment, when the deployment command is called, in addition to the deployment parameter filled in the front-end page, the task number tskId needs to be added, so that a log file named as check _ task number log can be created, and is used for recording the whole checking process, so that problems can be timely checked when abnormal checking occurs. Then, an inspection script may be adopted to sequentially inspect whether the server indicated by each service address in the target task has deployed the middleware, so as to obtain a plurality of inspection results, where the inspection results include: the method comprises the following steps that a task number, a service address, a checking state and the like are carried out, after the execution of a checking task is finished, a checking script calls a rear-end interface (namely, a first preset rear-end interface such as checkCallBack), and a checking result is transmitted into the first preset rear-end interface through the following form (namely, the checking result is converted into a first interface parameter):

http:// xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx/ansable/checkCallBacktskId =2 and ip =12. X. States =, where ansable is the format used by the script, checkCallBack is the called backend interface, tskId is the task number, ip is the service address of the server, and states is the check state: 1 represents installed middleware and 0 represents uninstalled middleware.

Then, when the checkcall back interface at the back end receives the transmitted first interface parameter, the interface data may be inserted into a preset installation state table (e.g., a dops _ install _ status table) first, and a task record corresponding to the task number is created. In this embodiment, the plurality of clients may execute the checking process asynchronously, so that a task record is created under the task number for a result executed by each client, and a checking result of the corresponding service address is recorded, so that the preset installation state table may be queried, and it is determined whether the number of data records under the task number is equal to the number of service addresses, and if the number of data records is not equal to the number of service addresses, it indicates that there is a server that has not been checked, and the obtained first interface parameter is inserted into the preset installation state table. If the checking state is installed, only the first interface parameter is inserted into the preset installation state table, and the task table state is updated to be checking failed.

If the number of data records under the task number is equal to the number of service addresses and the checking result is that the data records are not installed (namely, in the case that the number of records of the task record associated with the task number is equal to the number of service addresses and the checking state indicated by each task record is that the checking is passed), the agent _ install.

Optionally, after the deployment script corresponding to the target task is called, the method further includes: adopting a deployment script to deploy middleware for a server indicated by each service address in the target task in sequence to obtain a plurality of deployment results, wherein the deployment results at least comprise: task number, service address, installation state; under the condition that the deployment result is converted into a second interface parameter and the second interface parameter is transmitted to a second preset rear-end interface, updating an installation state field of a task record associated with the task number in a preset installation state table based on the second interface parameter; under the condition that the installation state fields are not empty, determining that the server indicated by each service address in the target task is completely deployed; and under the condition that the installation state fields are all installed successfully, determining that the server indicated by each service address in the target task is deployed successfully.

In this embodiment of the present invention, a deployment script may be adopted to sequentially deploy middleware for a server indicated by each service address in a target task, so as to obtain a plurality of deployment results, where the deployment results include: after the deployment is performed, a backend interface (a second preset backend interface, such as installCallBack) can be called back, and the deployment result can be transmitted to the second preset backend interface through the following form (i.e. the deployment result is converted into a second interface parameter):

http:// xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.ansible/installCallBacktskId =2 and ip =12. X. States =, wherein ansible is the format adopted by the script, installCallBack is the called backend interface, tskId is the task number, ip is the service address of the server, and states is the installation state: 1 represents installed middleware and 0 represents uninstalled middleware.

Then, when the installCallBack interface at the back end receives the transmitted second interface parameter (i.e., when the deployment result is converted into the second interface parameter and the second interface parameter is transmitted to the second preset back-end interface), the second interface parameter may be updated to the dps _ install _ status table (i.e., the installation status field of the task record associated with the task number in the preset installation status table is updated based on the second interface parameter). If the preset installation state table is checked to find that an installation state field (install _ status field) of the task records is empty, indicating that all the installation is not successful; if the preset installation state table is checked to find that the values of the install _ status fields are not null, the installation of all the client nodes (namely the servers) is completed (namely, under the condition that the installation state fields are not null, the servers indicated by each service address in the target task are determined to be deployed), then, whether the servers are installed successfully or not can be verified by checking the field values of the installation state fields in the preset installation state table, if the installation state fields are successful, the task state is updated to the deployment success (namely, under the condition that the installation state fields are successful, the servers indicated by each service address in the target task are determined to be deployed successfully), and if the installation state fields are not null, the updating is failed.

Alternatively, the details of task execution may be viewed by clicking a detail button next to the execution details presented on the task page.

In the embodiment of the invention, the middleware indicated by the middleware identifier can be deployed on each server through a preset deployment script according to deployment parameters (including an installation path, an access port, a required memory and the like).

In the embodiment of the present invention, since the syntax specification of the deployment command in the preset deployment script is not easy to understand, it is necessary to spend a learning cost in understanding the deployment command. In order to enable the primary operation and maintenance personnel, the primary development personnel and users who do not learn the grammar specification of the deployment command to understand, a preset command (such as a shell command) can be added to each deployment command in the deployment script, the execution result of the added preset command is consistent with that of the deployment command, command annotations corresponding to the preset command are added, and the annotations are not actually executed but added to the deployment document in the deployment process of the preset command and the command, so that the deployment document of the middleware can be automatically obtained.

Optionally, after generating the deployment document based on the preset command set and the command annotation corresponding to each preset command in the preset command set, the method further includes: under the condition that the middleware is updated, updating the inspection script, the deployment script and the uninstalling script corresponding to the middleware based on the updating parameters of the middleware; determining updated target deployment commands in the inspection script, the deployment script and the uninstallation script; and modifying a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document.

In the embodiment of the present invention, with optimization of the middleware, the preset command and the corresponding command annotation may be added or modified in the middleware script (i.e., the inspection script, the deployment script, and the uninstallation script corresponding to the middleware) (i.e., in a case that the middleware is updated, the inspection script, the deployment script, and the uninstallation script corresponding to the middleware are updated based on the update parameter of the middleware, and the updated target deployment command in the inspection script, the deployment script, and the uninstallation script is determined, and the preset command corresponding to the target deployment command and the command annotation corresponding to the preset command are modified based on the target deployment command).

Optionally, after modifying the preset command corresponding to the target deployment command and the command annotation corresponding to the preset command based on the target deployment command to obtain the updated deployment document, the method further includes: extracting a preset command set in the deployment document; executing a preset command set in a preset test environment to deploy middleware on a preset server to obtain a parameter file set; under the condition that the middleware is successfully deployed on the preset server, replacing the service address of the preset server in each parameter file in the parameter file set with the service address in the pre-production environment to obtain a target file set; packaging the target file set after the log file is deleted to obtain a target file, and generating a target character string value based on the target file; acquiring a standard file set in a pre-commissioning environment, and deleting log files in the standard file set to obtain a target standard file set; packaging the target standard file set to obtain a standard file, and generating a standard character string value based on the standard file; and determining that the deployment document is verified under the condition that the target string value is consistent with the standard string value.

In the embodiment of the present invention, before the updated deployment document is displayed on the task page, consistency between the deployment document and the deployment document in the production environment needs to be verified, specifically, preset commands in the deployment document may be sequentially extracted and executed in a preset test environment, and after the execution, whether the installation on the preset server is successful or not may be confirmed by the check script of the middleware (that is, a preset command set in the deployment document is extracted and the preset command set is executed in the preset test environment, so as to deploy the middleware on the preset server, thereby obtaining a parameter file set). After the successful installation is checked, the test environment replaces the service address of the preset server in each parameter file in the parameter file set with the service address in the pre-delivery environment, and meanwhile, the target file set from which the log file is deleted is packaged to obtain a target file, and a target string value (such as an MD5 value, which has uniqueness) is generated based on the target file. Similarly, a standard file set in the pre-production environment is obtained, a log file in the standard file set is deleted to obtain a target standard file set, the target standard file set is packaged to obtain a standard file, a standard string value (such as an MD5 value, the standard string value has uniqueness) is generated based on the standard file, and when the target string value is consistent with the standard string value, it is determined that the deployment document is verified to be passed (that is, it indicates that the automatically updated deployment document is consistent with the deployment document in the production environment).

In the embodiment of the invention, the deployment process and the deployment document creation process are integrated, and meanwhile, the consistency of the deployment result of the automatically generated deployment document and the deployment result of the production environment can be verified, so that the accuracy of the deployment document can be ensured. Moreover, the problem that the deployed document is not accurate any more along with the lapse of time can be effectively solved, the maintenance cost of the deployed document can be saved, and the satisfaction degree of customers is improved.

The following is a detailed description of another embodiment.

Example two

The generation device for the deployment document provided in this embodiment includes a plurality of implementation units, and each implementation unit corresponds to a respective implementation step in the first embodiment.

Fig. 2 is a schematic diagram of an alternative deployment document generation apparatus according to an embodiment of the present invention, and as shown in fig. 2, the generation apparatus may include: a receiving unit 20, a querying unit 21, a deployment unit 22, a generating unit 23, wherein,

a receiving unit 20, configured to receive a middleware deployment request, where the middleware deployment request at least includes: middleware identification and deployment parameters;

the query unit 21 is configured to query a preset service address table based on the middleware identifier to obtain a target service address table, where each service address in the target service address table corresponds to one server;

the deployment unit 22 is configured to deploy the middleware indicated by the middleware identifier on each server by using a preset deployment script based on the deployment parameters;

the generating unit 23 is configured to convert the deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generate a deployment document based on the preset command set and a command annotation corresponding to each preset command in the preset command set.

The generation device may receive a middleware deployment request through the receiving unit 20, query a preset service address table through the query unit 21 based on a middleware identifier to obtain a target service address table, deploy, through the deployment unit 22, a middleware indicated by the middleware identifier on each server by using a preset deployment script based on a deployment parameter, convert, through the generation unit 23, a deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generate a deployment document based on the preset command set and a command comment corresponding to each preset command in the preset command set. In the embodiment of the invention, the servers needing to deploy the middleware are determined through the middleware identification carried by the middleware deployment request, then the middleware is deployed on each server by adopting the preset deployment script, meanwhile, the deployment command in the preset deployment script when the middleware is deployed is converted into the preset command, the deployment document is automatically generated according to the preset command and the command annotation corresponding to the preset command, and the deployment process and the process of creating the deployment document are integrated without manual maintenance, so that the accuracy of the deployment document can be improved, and the technical problem that the accuracy of the deployment document is easily reduced due to manual maintenance of the deployment document in the related technology is solved.

Optionally, the generating device further includes: the system comprises a first creating module, a second creating module and a third creating module, wherein the first creating module is used for creating a corresponding checking script, a corresponding deployment script and a corresponding unloading script for each middleware based on a preset script format before receiving a middleware deployment request, the checking script is used for checking the deployment state of the middleware, the deployment script is used for deploying the middleware, and the unloading script is used for unloading the middleware; and the first recording module is used for recording each middleware and the inspection script, the deployment script and the uninstallation script corresponding to the middleware into a preset routing table.

Optionally, the query unit includes: the first query module is used for querying a preset service address table to obtain a query result, wherein the query result records the deployment state of the middleware deployed in each server; the first screening module is used for screening the servers with the undeployed states recorded in the query results to obtain a target server set; and the first generation module is used for generating a target service address table based on the target server set.

Optionally, the generating device further includes: the second generation module is used for responding to the middleware deployment request and generating a target task before deploying the middleware indicated by the middleware identifier on each server by adopting a preset deployment script based on the deployment parameters, wherein the target task is used for deploying the middleware indicated by the middleware identifier to the server indicated by each service address; the first display module is used for adding the target task into the task table and displaying task information related to the target task in the task table on a front-end page, wherein the task information comprises: task number, task type, applicant, task progress, task log, execution details, and number of service addresses.

Optionally, the generating device further includes: the first calling module is used for calling the checking script corresponding to the target task after responding to the middleware deployment request and generating the target task; the first checking module is used for sequentially checking whether the middleware has been deployed in the server indicated by each service address in the target task by using the checking script to obtain a plurality of checking results, wherein the checking results at least comprise: task number, service address, and inspection state; the first inserting module is used for inserting the first interface parameter into the preset installation state table and creating a task record corresponding to the task number under the condition that the checking result is converted into the first interface parameter and the first interface parameter is transmitted to the first preset rear-end interface; and the second calling module is used for inquiring the preset installation state table, and calling the deployment script corresponding to the target task when the number of the records of the task records related to the task number is equal to the number of the service addresses and the checking state indicated by each task record is the checking pass.

Optionally, the generating device further includes: the first deployment module is used for deploying middleware for the server indicated by each service address in the target task in sequence by adopting the deployment script after the deployment script corresponding to the target task is called, so as to obtain a plurality of deployment results, wherein the deployment results at least comprise: task number, service address, installation state; the first updating module is used for updating the installation state field of the task record associated with the task number in the preset installation state table based on the second interface parameter under the condition that the deployment result is converted into the second interface parameter and the second interface parameter is transmitted to the second preset back-end interface; the first determining module is used for determining that the server indicated by each service address in the target task is completely deployed under the condition that the installation state field is not empty; and the second determining module is used for determining that the server indicated by each service address in the target task is successfully deployed under the condition that the installation state fields are all installed successfully.

Optionally, the generating device further includes: the second updating module is used for updating the inspection script, the deployment script and the uninstalling script corresponding to the middleware based on the updating parameters of the middleware under the condition that the middleware is updated after the deployment document is generated based on the preset command set and the command annotation corresponding to each preset command in the preset command set; the third determining module is used for determining the updated target deployment command in the inspection script, the deployment script and the uninstallation script; and the first modification module is used for modifying the preset command corresponding to the target deployment command and the command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document.

Optionally, the generating device further includes: the first extraction module is used for extracting a preset command set in the deployment document after modifying a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document; the first execution module is used for executing a preset command set in a preset test environment so as to deploy middleware on a preset server to obtain a parameter file set; the first replacement module is used for replacing the service address of the preset server in each parameter file in the parameter file set with the service address in the pre-production environment under the condition that the middleware is successfully deployed on the preset server to obtain a target file set; the first packing module is used for packing the target file set after the log files are deleted to obtain a target file, and generating a target character string value based on the target file; the first acquisition module is used for acquiring a standard file set in a pre-delivery environment and deleting log files in the standard file set to obtain a target standard file set; the second packing module is used for packing the target standard file set to obtain a standard file and generating a standard character string value based on the standard file; and the fourth determining module is used for determining that the deployment document passes the verification under the condition that the target character string value is consistent with the standard character string value.

The above generation device may further include a processor and a memory, where the above receiving unit 20, the querying unit 21, the deploying unit 22, the generating unit 23, and the like are all stored in the memory as program units, and the processor executes the above program units stored in the memory to implement corresponding functions.

The processor comprises a kernel, and the kernel calls a corresponding program unit from the memory. The kernel can be set with one or more than one, the deployment command in the preset deployment script during the deployment of the middleware is converted into the preset command by adjusting the kernel parameters to obtain a preset command set, and the deployment document is generated based on the preset command set and the command annotation corresponding to each preset command in the preset command set.

The memory may include volatile memory in a computer readable medium, random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.

The present application also provides a computer program product adapted to perform a program for initializing the following method steps when executed on a data processing device: the method comprises the steps of receiving a middleware deployment request, inquiring a preset service address table based on a middleware identifier to obtain a target service address table, deploying the middleware indicated by the middleware identifier on each server by adopting a preset deployment script based on deployment parameters, converting a deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generating a deployment document based on the preset command set and a command annotation corresponding to each preset command in the preset command set.

According to another aspect of the embodiments of the present invention, there is also provided an electronic device including one or more processors and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the above-described method for generating a deployment document.

Fig. 3 is a block diagram of a hardware configuration of an electronic device (or a mobile device) for a method of generating a deployment document according to an embodiment of the present invention. As shown in fig. 3, the electronic device may include one or more (shown as 302a, 302b, \8230;, 302 n) processors 302 (processor 302 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), memory 304 for storing data. In addition, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a keyboard, a power supply, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 3 is only an illustration and is not intended to limit the structure of the electronic device. For example, the electronic device may also include more or fewer components than shown in FIG. 3, or have a different configuration than shown in FIG. 3.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present invention, the description of each embodiment has its own emphasis, and reference may be made to the related description of other embodiments for parts that are not described in detail in a certain embodiment.

In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple 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 coupling or direct coupling or communication connection between each other may be an indirect coupling or communication connection through some interfaces, units or modules, and may be electrical or in other forms.

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 position, or may be distributed on a plurality of 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 invention 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 integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is substantially or partly contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. A method for generating a deployment document, comprising:

receiving a middleware deployment request, wherein the middleware deployment request at least comprises: middleware identification and deployment parameters;

inquiring a preset service address table based on the middleware identification to obtain a target service address table, wherein each service address in the target service address table corresponds to one server;

deploying the middleware indicated by the middleware identification on each server by adopting a preset deployment script based on the deployment parameters;

and converting the deployment command in the preset deployment script when the middleware is deployed into a preset command to obtain a preset command set, and generating a deployment document based on the preset command set and command annotations corresponding to each preset command in the preset command set.

2. The generation method according to claim 1, before receiving the middleware deployment request, further comprising:

based on a preset script format, creating a corresponding inspection script, a deployment script and an uninstalling script for each middleware, wherein the inspection script is used for inspecting the deployment state of the middleware, the deployment script is used for deploying the middleware, and the uninstalling script is used for uninstalling the middleware;

and recording each middleware, the check script, the deployment script and the uninstall script corresponding to the middleware into a preset routing table.

3. The method according to claim 1, wherein the step of querying a preset service address table to obtain a target service address table based on the middleware identifier comprises:

inquiring the preset service address table to obtain an inquiry result, wherein the inquiry result records the deployment state of deploying the middleware in each server;

screening the servers, which are recorded as undeployed in the query result, to obtain a target server set;

and generating the target service address table based on the target server set.

4. The generation method according to claim 2, further comprising, before deploying the middleware indicated by the middleware identifier on each of the servers using a preset deployment script based on the deployment parameters:

responding to the middleware deployment request, and generating a target task, wherein the target task is used for deploying the middleware indicated by the middleware identification to the server indicated by each service address;

adding the target task into a task table, and displaying task information related to the target task in the task table on a front-end page, wherein the task information comprises: task number, task type, applicant, task progress, task log, execution details, and number of service addresses.

5. The generation method according to claim 4, further comprising, after generating the target task in response to the middleware deployment request:

calling the inspection script corresponding to the target task;

adopting the inspection script to sequentially inspect whether the middleware has been deployed by each server indicated by the service address in the target task, and obtaining a plurality of inspection results, wherein the inspection results at least comprise: task number, service address, and inspection state;

under the condition that the checking result is converted into a first interface parameter and the first interface parameter is transmitted to a first preset rear-end interface, inserting the first interface parameter into a preset installation state table, and creating a task record corresponding to the task number;

and inquiring the preset installation state table, and calling the deployment script corresponding to the target task when the number of records of the task records related to the task number is equal to the number of the service addresses and the checking state indicated by each task record is passed.

6. The generation method according to claim 5, further comprising, after invoking the deployment script corresponding to the target task:

adopting the deployment script to sequentially deploy the middleware for each server indicated by the service address in the target task to obtain a plurality of deployment results, wherein the deployment results at least comprise: task number, service address, installation state;

updating an installation state field of the task record associated with the task number in the preset installation state table based on the second interface parameter under the condition that the deployment result is converted into the second interface parameter and the second interface parameter is transmitted to a second preset back-end interface;

under the condition that the installation state fields are not empty, determining that the server indicated by each service address in the target task is completely deployed;

and under the condition that the installation state fields are all installed successfully, determining that the server indicated by each service address in the target task is deployed successfully.

7. The generating method according to claim 1, after generating a deployment document based on the preset command set and a command annotation corresponding to each preset command in the preset command set, further comprising:

under the condition that the middleware is updated, updating a check script, a deployment script and an uninstall script corresponding to the middleware based on the update parameters of the middleware;

determining updated target deployment commands in the inspection script, the deployment script and the uninstallation script;

and modifying a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document.

8. The generation method according to claim 7, further comprising, after modifying a preset command corresponding to the target deployment command and a command annotation corresponding to the preset command based on the target deployment command to obtain an updated deployment document:

extracting the preset command set in the deployment document;

executing the preset command set in a preset test environment to deploy the middleware on a preset server to obtain a parameter file set;

under the condition that the middleware is successfully deployed on the preset server, replacing the service address of the preset server in each parameter file in the parameter file set with a service address in a pre-production environment to obtain a target file set;

packaging the target file set after the log file is deleted to obtain a target file, and generating a target character string value based on the target file;

acquiring a standard file set in the pre-commissioning environment, and deleting log files in the standard file set to obtain a target standard file set;

packaging the target standard file set to obtain a standard file, and generating a standard character string value based on the standard file;

determining that the deployment document is validated if the target string value is consistent with the standard string value.

9. A deployment document generation apparatus, comprising:

a receiving unit, configured to receive a middleware deployment request, where the middleware deployment request at least includes:

middleware identification and deployment parameters;

the query unit is used for querying a preset service address table based on the middleware identifier to obtain a target service address table, wherein each service address in the target service address table corresponds to one server;

the deployment unit is used for deploying the middleware indicated by the middleware identification on each server by adopting a preset deployment script based on the deployment parameters;

the generating unit is used for converting the deployment command in the preset deployment script during deployment of the middleware into a preset command to obtain a preset command set, and generating a deployment document based on the preset command set and the command annotations corresponding to each preset command in the preset command set.

10. An electronic device comprising one or more processors and memory storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of generating a deployment document of any of claims 1-8.