CN115658099A - Enterprise-level application operation and maintenance method and system - Google Patents

Abstract

The embodiment of the application provides an enterprise-level application operation and maintenance method and system, which belong to the technical field of server operation and maintenance, and the method comprises the following steps: acquiring a module installation package; the module installation package is obtained by packaging and processing application information of the application to be deployed; the application information at least comprises a description specification file, and the description specification file is used for describing specification information required by configuring the application to be deployed; analyzing the module installation package step by step, and restoring the application information; carrying out classification management and caching on the analyzed and restored application information; and based on the cached application information, carrying out corresponding application configuration to be deployed, and feeding back a configuration result. The scheme of the invention realizes that the application and the dependent module thereof can be automatically installed by one-time operation, and the lifecycle management of the application is supported after the installation is finished, thereby reducing the labor investment and the operation risk, standardizing the operation and maintenance work of enterprise-level application and improving the operation and maintenance efficiency.

Description

Enterprise-level application operation and maintenance method and system

Technical Field

The application relates to the technical field of server operation and maintenance, in particular to an enterprise-level application operation and maintenance method and an enterprise-level application operation and maintenance system.

Background

With the rapid development of services, service types and service processing volumes are more and more complicated, and in order to adapt to the explosive growth of the services, corresponding enterprise-level application deployment architectures are more and more complex, the specification number of the enterprise-level application deployment architectures is larger and larger, and the corresponding application release change frequency is higher and higher. At present, two main modes exist for enterprise-level application operation and maintenance, namely manual management and tool management. Wherein tool management generally implements operation and maintenance management of enterprise-level applications through a plurality of tools. If the application is deployed with a special deployment tool, the application life cycle management has a special application operation tool. The method solves the problem of manual workload to a certain extent, and reduces the complexity and risk of manual operation. However, the existing method still has obvious defects that at first, one tool is lacked to cover the complete life cycle management process of deployment, configuration, daily operation and maintenance and the like of the application, a plurality of tools are often used in a matched mode or the tools are mixed with manpower, and the workload and the complexity are increased for the management tool; then, the deployment tool is generally only suitable for the deployment of a single application module, and when the target application module depends on other modules, operation and maintenance personnel still need to clarify the dependency relationship among the modules and then construct deployment tasks one by one; in addition, the application operation and maintenance tool needs scripts to provide daily operation and maintenance functions, and often lacks a specification to uniformly manage the scripts. Aiming at the problems of poor unified script management performance and failed deployment caused by incapability of depending on the relation in the existing enterprise-level application operation and maintenance scheme, a new enterprise-level application operation and maintenance method needs to be created.

Disclosure of Invention

The embodiment of the application aims to provide an enterprise-level application operation and maintenance method and system, so as to solve the problems that the existing enterprise-level application operation and maintenance scheme is poor in script unified management performance and cannot depend on the script unified management performance, so that deployment is failed.

In order to achieve the above object, a first aspect of the present application provides an operation and maintenance method for an enterprise-level application, where the method includes: acquiring a module installation package; the module installation package is obtained by packaging and processing application information of the application to be deployed; analyzing the module installation package step by step, and restoring the application information; carrying out classification management and caching on the analyzed and restored application information; and based on the cached application information, carrying out corresponding application configuration to be deployed, and feeding back a configuration result.

In an embodiment of the present application, the application information includes: the system comprises an application body to be deployed, a corresponding configuration file, an execution script and a description specification file, wherein the execution script and the description specification file are required for configuring the application to be deployed.

In an embodiment of the present application, the description specification file includes: basic information used for describing identification information of the application to be deployed; the installation information is used for describing the installation flow information of the application to be deployed; the executable instructions are used for describing each executable instruction in the configuration process of the application to be deployed and the operation and maintenance script path; the running environment configuration information is used for describing and configuring running resources required by the application to be deployed; the installation dependence information is used for describing modules which need to be configured in advance for configuring the application to be deployed; nginx proxy configuration information, which is used for describing nginx proxy information; the database configuration information is used for describing the database configuration information of the application to be deployed; and other configuration information is used for describing user-defined configuration.

In this embodiment of the present application, analyzing the module installation package step by step includes: analyzing the module installation package to obtain a corresponding analyzed file; judging whether the analyzed file comprises the following application information: the method comprises the steps that an application body to be deployed, a corresponding configuration file, an execution script and a description specification file which are required by the configuration of the application to be deployed are obtained; if any application information of the analyzed files is lost, judging that the current module installation package is not qualified, and downloading the module installation package again; if the module installation package is still judged to be not qualified after the module installation package is downloaded again for the preset times, the module installation package stops downloading again, and corresponding alarm information is output; and if any application information of the file is not lost after the analysis, analyzing the description specification files one by one based on a preset sequence.

In this embodiment of the present application, the parsing the description specification files one by one based on a preset sequence includes: and analyzing the description specification files one by one based on the sequence of analyzing the basic information, analyzing the dependency information, analyzing the database configuration information, analyzing the nginx agent configuration information, analyzing the executable instruction, analyzing the installation information, analyzing the operating environment configuration information and analyzing other configuration information to obtain corresponding analysis information.

In this embodiment of the present application, the performing classification management on the application information that is analyzed and restored includes: presetting two classification results of necessary information and unnecessary information; the necessary information is information that must be included in the analysis result, and the unnecessary information is information that may not be included in the analysis result; the necessary information includes: an application ontology to be deployed; a corresponding configuration file; configuring an execution script required by an application to be deployed; and in the description specification file: basic information, executable instructions, and installation information; the non-essential information includes, in the description specification file: dependency information, database configuration information, nginx configuration information, runtime environment information, and other configuration information.

In an embodiment of the present application, the method further includes: judging whether all necessary information exists in the application information which is analyzed and restored; and if the necessary information is missing, terminating the configuration flow of the application to be deployed and outputting alarm information.

In this embodiment of the present application, the configuring, based on the cached application information, of the application to be deployed includes: acquiring residual resources of a target of an application to be deployed, and judging whether the residual resources meet configuration requirements or not based on the operating environment configuration information; if the residual resources meet the configuration requirement, judging whether installation dependency information exists or not, and carrying out prior configuration on the dependency module based on the installation dependency information under the condition that the installation dependency information exists; based on an installation environment created by a previous configuration module, performing to-be-deployed application body configuration based on the installation information, and feeding back a configuration completion signal; and responding to the configuration completion signal, and triggering an operation and maintenance management flow to execute an instruction.

In this embodiment of the present application, the operation and maintenance management process includes: based on the configured application, issuing a preset operation and maintenance script to a preset directory, and opening corresponding operation and maintenance operation; inquiring whether application data of which the configuration is completed exist in a preset database, if so, configuring corresponding application data, and changing the application data based on a prewritten sql statement; inquiring whether nginx information of the configured application exists in a preset number base, and if yes, performing reverse proxy and load balancing function configuration of the configured application based on the nginx information; and configuring other configuration information, and performing residual content configuration based on the user-defined configuration content to complete the deployment of the application to be deployed.

A second aspect of the present application provides an enterprise-level application operation and maintenance system, the system comprising: the acquisition unit is used for acquiring the module installation package; the module installation package is obtained by packaging and processing application information of the application to be deployed; the analysis unit is used for analyzing the module installation package step by step and restoring the application information; the processing unit is used for carrying out classification management and caching on the application information which is analyzed and restored; and the execution unit is used for configuring the corresponding application to be deployed based on the cached application information and feeding back a configuration result.

A third aspect of the present application provides a processor, wherein the processor is configured to execute the above-mentioned operation and maintenance method for enterprise-level applications.

A fourth aspect of the present application provides a machine-readable storage medium having stored thereon instructions that, when executed by a processor, cause the processor to be configured to perform the enterprise-level application operation and maintenance method described above.

A fifth aspect of the application provides a computer program product comprising a computer program which, when executed by a processor, implements the enterprise level application operation and maintenance method described above.

Through the technical scheme, the invention provides the description specification of the enterprise-level application, which is used for describing various information and configurations of the application and realizing the analysis and landing of the description specification on the basis. The method and the device have the advantages that the application and the dependency module can be automatically installed through one-time operation, the life cycle management of the application is supported after the installation is completed, the manual investment and the operation risk are reduced, meanwhile, the operation and maintenance work of the enterprise-level application is standardized, and the operation and maintenance efficiency is improved.

Additional features and advantages of embodiments of the present application will be described in detail in the detailed description which follows.

Drawings

The accompanying drawings, which are included to provide a further understanding of the embodiments of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the embodiments of the disclosure, but are not intended to limit the embodiments of the disclosure. In the drawings:

FIG. 1 is a flow chart that schematically illustrates steps of a method for enterprise-level application operation and maintenance, in accordance with an embodiment of the present application;

FIG. 2 is a diagram schematically illustrating an implementation process of an enterprise-level application operation and maintenance method according to an embodiment of the present application;

FIG. 3 is a system diagram schematically illustrating an enterprise-level application operation and maintenance system according to an embodiment of the present application;

fig. 4 schematically shows an internal structure diagram of a computer device according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the specific embodiments described herein are only used for illustrating and explaining the embodiments of the present application and are not used for limiting the embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that, if directional indications (such as up, down, left, right, front, and back … …) are involved in the embodiment of the present application, the directional indications are only used to explain the relative position relationship between the components, the motion situation, and the like in a specific posture (as shown in the drawing), and if the specific posture is changed, the directional indications are changed accordingly.

In addition, if there is a description relating to "first", "second", etc. in the embodiments of the present application, the description of "first", "second", etc. is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present application.

With the rapid development of services, the service types and the service processing amount are more and more complicated, and in order to adapt to the explosive growth of the services, the corresponding enterprise-level application deployment architecture is more and more complex, the specification number of the enterprise-level application deployment architecture is larger and larger, and the corresponding application release change frequency is higher and higher. With respect to the conventional scheme, two major problems mainly exist when application deployment is performed:

1) At present, most application deployment tools can only release and deploy enterprise-level applications, and installation dependency relationships of enterprises (certain applications need to deploy dependent applications in advance for creating corresponding deployment environments) cannot be analyzed, so that when application deployment is directly performed, deployment failure is often caused because prior deployment application support does not exist, and then one-click installation cannot be achieved from scratch.

2) At present, a deployment tool lacks a unified standard for life cycle management of an application, so that a unified processing scheme does not exist for a deployment scheme and an operation and maintenance scheme, and a deployment process is disordered. Subsequent processes of starting, stopping, uninstalling, upgrading, state query and the like cannot be scheduled in a unified standard mode.

At present, two main modes exist for enterprise-level application operation and maintenance, namely manual management and tool management. Wherein, manual management is that application developers need to prepare deployment media (including middleware, application version files, deployment scripts and the like) and relevant operation and maintenance scripts (such as start scripts, stop scripts, uninstall scripts, upgrade scripts, state query scripts and the like) in advance; and then, the operation and maintenance personnel acquire related files in an online or offline mode, transmit the files to a target machine, install and deploy application version files and a dependent database and middleware through commands, and manually configure parameters. After the application is deployed, the subsequent operation related to the application operation and maintenance is also realized by the operation and maintenance personnel manually operating the script. For example, all relevant parameters are recorded in a usb disk, and then the operation and maintenance personnel arrives at the field of the device and accesses the usb disk to the corresponding device for application installation or upgrade of the device. This approach is heavily dependent on the experience of the operation and maintenance personnel. When an application is deployed, the application often depends on a plurality of modules to normally run. This requires that the operation and maintenance personnel be able to clarify the dependencies between modules and then install the modules one by one in sequence. The incorrect installation sequence and omission of the sub-modules can cause the target module to fail to provide normal service capability. When the application needs to be started, stopped, unloaded, upgraded and the like, the operation and maintenance personnel need to log in the target machine and manually execute the operation and maintenance script. Moreover, these efforts have dramatically increased in workload and complexity in application clustering scenarios.

While tool management generally implements the operation and maintenance management of enterprise-level applications through multiple tools. If the application is deployed with a special deployment tool, the application life cycle management has a special application operation tool. The application deployment tool generally realizes the installation and deployment of the application by calling a deployment script; and the application operation and maintenance tool realizes the life cycle management of the application by calling the related operation and maintenance script. The method solves the problem of manual workload to a certain extent, and reduces the complexity and risk of manual operation. However, the existing method still has obvious defects that at first, one tool is lacked to cover the complete life cycle management process of deployment, configuration, daily operation and maintenance and the like of the application, a plurality of tools are often used in a matched mode or the tools are mixed with manpower, and the workload and the complexity are increased for the management tool; then, the deployment tool is generally only suitable for the deployment of a single application module, and when the target application module depends on other modules, operation and maintenance personnel still need to clarify the dependency relationship among the modules and then construct deployment tasks one by one; in addition, the application operation and maintenance tool needs scripts to provide daily operation and maintenance functions, and often lacks a specification to uniformly manage the scripts. There is no normative tool availability and ease of use at a large discount.

Aiming at the problems of poor unified script management performance and failed deployment caused by incapability of depending on the relation in the existing enterprise-level application operation and maintenance scheme, a new enterprise-level application operation and maintenance method is created. The scheme of the invention provides a description specification of enterprise-level application, which is used for describing various information and configurations of the application and realizing the analysis and landing of the description specification on the basis. The method and the device have the advantages that the application and the dependency module can be automatically installed through one-time operation, the life cycle management of the application is supported after the installation is completed, the manual investment and the operation risk are reduced, meanwhile, the operation and maintenance work of the enterprise-level application is standardized, and the operation and maintenance efficiency is improved.

Fig. 1 schematically shows a flowchart of an enterprise-level application operation and maintenance method according to an embodiment of the present application. As shown in fig. 1, in an embodiment of the present application, there is provided an operation and maintenance method for an enterprise-level application, including the following steps:

step S10: and acquiring a module installation package.

Specifically, when enterprise-level application deployment and operation and maintenance are performed, the difficulty mainly exists that when the former involves dependent modules, the complexity of installing the modules according to the order of the dependent relations is high, and when the latter involves numerous scripts, each application may have multiple scripts, and if the management is not unified, operation and maintenance personnel cannot perform daily operation and maintenance work of the application, and also need to expend a great deal of energy on maintaining and managing the numerous scripts. The scheme of the invention provides a corresponding solution based on the difficulties of the current enterprise-level application, namely provides a description specification for describing various information of the enterprise-level application in a standardized way, so that the whole deployment process is standardized.

Specifically, these description specification files include: basic information used for describing identification information of the application to be deployed; the installation information is used for describing the installation flow information of the application to be deployed; executable instructions for describing each executable instruction in the configuration process of the application to be deployed and an operation and maintenance script path; the running environment configuration information is used for describing running resources required by the application to be deployed; the installation dependence information is used for describing a module which needs to be configured in advance for configuring the application to be deployed; the nginx proxy configuration information is used for describing the nginx proxy information; the database configuration information is used for describing the database configuration information of the application to be deployed; and other configuration information is used for describing user-defined configuration.

In one possible implementation, the detailed deployment of these information is:

and basic information including application name, version, description, type and the like is acquired by the application operation and maintenance tool through analyzing the information.

And the installation information describes how to install the current application, and comprises an installation script name and installation parameters. And the application operation and maintenance tool calls the corresponding installation script by analyzing the part of information, so that the installation and deployment of the enterprise-level application are realized.

And the executable instruction is used for describing various executable instructions such as application starting, stopping, restarting, state inquiry, uninstalling and the like and an operation and maintenance script path of actual operation. After the operation and maintenance tool is applied to analyze the part of information, an operation and maintenance operation function can be provided, and a corresponding executable instruction is triggered after clicking.

And configuring the running environment, including resources needed by the running such as a memory, a cpu and the like. When the application operation and maintenance tool deploys the application, the running environment configuration and the configuration of the target host need to be compared, and if the configuration of the target host cannot meet the configuration resource required by the deployment of the application, the application cannot be deployed.

Installation dependency information, other modules on which the current module depends, including module name and version. And the proxy configuration is used for describing the application front-end proxy information. The application operation and maintenance tool analyzes the information to obtain the dependency relationship of the application modules, and then the dependency modules can be installed one by one according to the installation sequence, so that all modules related to the application are installed one by one.

And the nginx proxy configuration information is used for describing the nginx proxy information. If the application uses Nginx for reverse proxy or load balancing, the application operation and maintenance tool may set proxy information based on this information.

Database configuration information, database configuration information describing an application. And the operation and maintenance tool is used for analyzing the database configuration which can be applied, such as the type of the database, the name of the database, the user name, the password and the like.

And other configuration information describing the application, such as log file paths, firewall ports to be closed and the like. If the personalized extension configuration exists, the extension configuration can be customized.

And when designing a corresponding description specification file, a matched tool system is also provided, and the tool system can analyze the description specification and install the application according to the specification by one key. Based on the designed description specification file and the corresponding matched tool, different applications provide the description specification file according to the specification, and after the description specification file is analyzed by the operation and maintenance tool, the installation script and the dependent module information of the applications are obtained, so that the automatic installation of the application module and the dependent module is realized; meanwhile, an executable instruction of the application can be triggered in the application operation and maintenance tool, and an actual operation and maintenance script is called, so that daily operation and maintenance work of the application is realized.

Based on this, when the installation package is packaged, the execution script and the description specification file required by configuring the application to be deployed corresponding to the installation package need to be compressed and integrated with the application body to be deployed. And then when the corresponding application configuration to be deployed needs to be executed, issuing a configuration instruction to a corresponding host, and downloading the module installation package by the host. The module installation package is obtained by packaging and processing application information based on the application to be deployed. Wherein the application information comprises: the system comprises an application body to be deployed, a corresponding configuration file, an execution script and a description specification file, wherein the execution script and the description specification file are required for configuring the application to be deployed.

Step S20: and analyzing the module installation package step by step, and restoring the application information.

Specifically, the module installation package is analyzed to obtain a corresponding analyzed file; judging whether the analyzed file comprises an application body to be deployed, a corresponding configuration file, an execution script required for configuring the application to be deployed and a description specification file; if any application information of the analyzed files is lost, judging that the current module installation package is not qualified, and downloading the module installation package again; if the module installation package is still judged to be not qualified after the download is retried for the preset number of times, the retry download is stopped, and corresponding alarm information is output; and if any application information of the file is not lost after the analysis, analyzing the description specification files one by one based on a preset sequence.

In the embodiment of the present invention, when data is transmitted, data loss may be caused by network failure and the like, and if the module installation package is transmitted, the data loss is generated, which may cause a problem of failure in subsequent deployment. Furthermore, the core of the solution of the present invention to solve the corresponding technical problem is to provide the description specification file, so that when the module installation package is analyzed, it is required to ensure that the corresponding description specification file exists in the analyzed file, and then deployment is performed based on the description specification file. Therefore, when the to-be-deployed application body, the corresponding configuration file, the execution script and the description specification file required for configuring the to-be-deployed application do not exist in the analysis file, it is indicated that the subsequent deployment scheme cannot be executed according to expectation, and the subsequent deployment scheme is stopped. Further, data loss may be a sporadic reason, and certainly, the problem may also exist in the module installation package itself, in order to eliminate the sporadic reason, multiple retries of downloading and analysis are executed, if the problem still exists in the module installation package after the retries of the preset number of times, the corresponding alarm information is output, and the user is informed of troubleshooting.

Further, the description specification files are analyzed one by one based on the sequence of analyzing the basic information, analyzing the dependency information, analyzing the database configuration information, analyzing the nginx agent configuration information, analyzing the executable instruction, analyzing the installation information, analyzing the operating environment configuration information and analyzing other configuration information, and corresponding analysis information is obtained.

Step S30: and carrying out classification management and caching on the application information.

Specifically, different description specification files exist in different applications to be configured, so that not all the applications to be configured have dependent applications or have requirements on operating environments, and the scheme of the invention provides an application information classification method aiming at the difference of different applications to be deployed. Presetting two classification results of necessary information and unnecessary information; the necessary information is information which is necessary to be contained in the analysis result, and the unnecessary information is information which can not be contained in the analysis result; the necessary information includes: the method comprises the steps of configuring an application body to be deployed, corresponding configuration files and execution scripts required by the application to be deployed; and in the description specification file: basic information, executable instructions, and installation information; the non-essential information includes, in the description specification file: dependency information, database configuration information, nginx configuration information, runtime environment information, and other configuration information.

In one possible implementation, the basic information of the application module is parsed, and mainly includes the name, type, version, author, description, and the like of the module. The name, version and type are mandatory items, the other items are optional items, and if the mandatory item does not exist, the resolution is directly terminated. And then analyzing the dependency information of the application module, which mainly comprises the name, version and the like of the dependent module, for example, if there are four dependent modules, the four modules will be installed in sequence when the application module is installed, and the dependency can be penetrated, that is, if there is a dependency required by the current dependent module, the dependent dependency is installed preferentially. The dependency information is optional, and if the dependency information is not filled in, the application module is directly installed. Further, the configuration information of the database is analyzed, the type, the name, the user name and the password of the application module connection database are configured, and the related configuration of the database is selectable. Furthermore, the nginx configuration information is analyzed, the nginx relevant configuration is selectable, and only when the nginx is selected to carry out reverse proxy or load balancing, filling is needed. The Nginx configuration is not expanded here. Furthermore, the executable instruction is analyzed, the executable instruction is a necessary option, a developer needs to configure scripts and parameters actually called by the executable instruction, if the scripts and the parameters are not configured, the analysis fails, and the analysis is directly quitted, wherein the executable instruction generally comprises starting, stopping, restarting, state query and unloading. Further, the installation information is parsed. And the installation information is a necessary option, and if the configuration is not available, the analysis fails, and the analysis is directly quitted. The installation information includes whether to use root authority, the number of installed cluster nodes, installation commands and parameters, and the like. Furthermore, the running environment information is analyzed and is an optional item, which explains the number of CPU cores required for installing the module, the running memory and other environment resources. Further, other configuration information is analyzed, optional items are shown, the other configuration information comprises a log file path, a firewall port needing to be closed and the like, and the configuration can be expanded in a self-defined mode. And if the analysis steps are correct, storing the analyzed information into a database to prepare for subsequent installation and configuration processes.

Step S40: and based on the cached application information, performing corresponding application configuration to be deployed, and feeding back a configuration result.

Specifically, collecting the residual resources of the target of the application to be deployed, and judging whether the residual resources meet the configuration requirements based on the operating environment configuration information; when the residual resources meet the configuration requirements, judging whether installation dependence information exists, and when the installation dependence information exists, performing prior configuration on a dependence module based on the installation dependence information; based on an installation environment created by a prior configuration module, performing to-be-deployed application body configuration based on the installation information, and feeding back a configuration completion signal; and triggering the operation and maintenance management flow to execute an instruction in response to the configuration completion signal.

Preferably, the operation and maintenance management process includes: based on the configured application, issuing a preset operation and maintenance script to a preset directory, and opening corresponding operation and maintenance operation; inquiring whether application data of which the configuration is completed exist in a preset database, if so, configuring corresponding application data, and changing the application data based on a prewritten sql statement; inquiring whether nginx information of the configured application exists in a preset number base or not, and carrying out reverse proxy and load balancing function configuration of the configured application based on the nginx information when the nginx information exists; and configuring other configuration information, and performing residual content configuration based on the user-defined configuration content to complete the deployment of the application to be deployed.

In one possible implementation, the application to be deployed is configured by:

1) The running environment information of the application module and the remaining resources of the host computer on which the module needs to be installed are checked first. Generally, the number of CPU cores and memory are checked. If the residual resources on the host are larger than the resources required by installing the application module, the host can be installed, otherwise, the host cannot be installed and needs to be reselected. If the current host does not have the standby host, the current step-by-step useless cache data is correspondingly cleared, the residual resources are expanded, and the configuration of the current application module to be deployed is ensured.

2) And searching the dependency relationship of the application module in the database. And if the application module has the dependent module, entering the step 3) to install the dependent module. And if no dependent module exists, entering the step 4) to install the application module.

3) The installation and configuration flow of the dependent module is called, that is, the dependent module also needs to prepare an installation package and a description specification file according to the requirement of the application module. Because the dependency module and the application to be deployed are the same as the preset application deployed in the host, the dependency module deployment is performed based on the deployment scheme provided by the scheme of the invention, and one-key deployment of the dependency module can also be realized. And after the dependent modules are installed, returning to the step 2) to continuously judge whether other dependent modules exist, and repeating the step when judging that other dependent modules exist until all the dependent modules are configured.

4) And searching the installation information of the application module in the database, and then calling an installation command by using a corresponding user to install the application module.

5) And after the installation is finished, the operation and maintenance script of the application is issued to the specified directory. And corresponding operation and maintenance operation can be triggered on the page subsequently, so that the life cycle management of the application is realized.

6) If the database information of the application can be found in the database, the database of the application is configured, and a pre-written sql statement can be executed to realize the change operation of the database.

7) If nginx information can be found in the database, functions of reverse proxy, load balancing and the like of the application can be configured.

8) Other information for configuring the application, including log paths, firewall ports to be closed, etc.

FIG. 2 is a flowchart illustrating an operation and maintenance method for enterprise-level applications in one embodiment. It should be understood that, although the steps in the flowchart of fig. 2 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 2 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

In one embodiment, as shown in fig. 3, there is provided an enterprise-level application operation and maintenance system, the system comprising: the acquisition unit is used for acquiring the module installation package; the module installation package is obtained by packaging and processing application information of the application to be deployed; the analysis unit is used for analyzing the module installation package step by step and restoring the application information; the processing unit is used for carrying out classification management and caching on the application information which is analyzed and restored; and the execution unit is used for configuring the corresponding application to be deployed based on the cached application information and feeding back a configuration result.

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

The embodiment of the application provides a storage medium, on which a program is stored, and when the program is executed by a processor, the method for operating and maintaining the enterprise-level application is realized.

The present application further provides a processor, wherein the processor is configured to execute the operation and maintenance method for enterprise-level applications according to the above.

In one embodiment, a computer device is provided, which may be a server, and the internal structure thereof may be as shown in fig. 4. The computer apparatus includes a processor a01, a network interface a02, a memory (not shown in the figure), and a database (not shown in the figure) connected through a system bus. Wherein the processor a01 of the computer device is arranged to provide computing and control capabilities. The memory of the computer apparatus includes an internal memory a03 and a nonvolatile storage medium a04. The nonvolatile storage medium a04 stores an operating system B01, a computer program B02, and a database (not shown). The internal memory a03 provides an environment for running the operating system B01 and the computer program B02 in the nonvolatile storage medium a04. The network interface a02 of the computer apparatus is used for communicating with an external terminal through a network connection. The computer program B02, when executed by the processor a01, implements an enterprise-level application operation and maintenance method.

Those skilled in the art will appreciate that the architecture shown in fig. 4 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the enterprise-level application operation and maintenance system provided by the present application may be implemented in the form of a computer program that is executable on a computer device as shown in fig. 4. The memory of the computer device may store various program modules constituting the enterprise-level application operation and maintenance i pain, and the computer program constituted by the various program modules makes the processor execute the steps in the enterprise-level application operation and maintenance method according to the embodiments of the present application described in the present specification.

The present application also provides a computer program product adapted to perform the above-described enterprise-level application operation and maintenance method when executed on a data processing device.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.

Computer-readable media include permanent and non-permanent, removable and non-removable media and may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.

The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (13)

1. An enterprise-level application operation and maintenance method, characterized in that the method comprises:

acquiring a module installation package; the module installation package is obtained by packaging and processing application information of the application to be deployed; wherein the content of the first and second substances,

the application information at least comprises a description specification file, and the description specification file is used for describing specification information required by configuring the application to be deployed;

analyzing the module installation package step by step, and restoring the application information;

carrying out classification management and caching on the analyzed and restored application information;

and based on the cached application information, carrying out corresponding application configuration to be deployed, and feeding back a configuration result.

2. The method of claim 1, wherein the application information further comprises:

the method comprises the steps of an application body to be deployed, a corresponding configuration file and an execution script required by the configuration of the application to be deployed.

3. The method of claim 2, wherein the description specification file comprises:

basic information used for describing identification information of the application to be deployed;

the installation information is used for describing the installation flow information of the application to be deployed;

the executable instructions are used for describing each executable instruction in the configuration process of the application to be deployed and the operation and maintenance script path;

the running environment configuration information is used for describing and configuring running resources required by the application to be deployed;

the installation dependence information is used for describing modules which need to be configured in advance for configuring the application to be deployed;

the nginx proxy configuration information is used for describing the nginx proxy information;

the database configuration information is used for describing the database configuration information of the application to be deployed;

and other configuration information is used for describing user-defined configuration.

4. The method of claim 3, wherein parsing the module installation package stage by stage comprises:

analyzing the module installation package to obtain a corresponding analyzed file;

judging whether the analyzed file comprises the following application information: the method comprises the steps that an application body to be deployed, a corresponding configuration file, an execution script and a description specification file which are required by the configuration of the application to be deployed are obtained;

if any application information of the analyzed files is lost, judging that the current module installation package is not qualified, and downloading the module installation package again;

if the module installation package is still judged to be not qualified after the module installation package is downloaded again for the preset times, the module installation package is stopped from being downloaded again, and corresponding alarm information is output;

and if any application information of the file is not lost after the analysis, analyzing the description specification files one by one based on a preset sequence.

5. The method according to claim 4, wherein said parsing the description specification files one by one based on a preset order comprises:

and analyzing the description specification files one by one based on the sequence of analyzing the basic information, analyzing the dependency information, analyzing the database configuration information, analyzing the nginx agent configuration information, analyzing the executable instruction, analyzing the installation information, analyzing the operating environment configuration information and analyzing other configuration information to obtain corresponding analysis information.

6. The method according to claim 1, wherein the performing classification management on the application information of the parsing and restoring includes:

presetting two classification results of necessary information and unnecessary information; the necessary information is information that must be included in the analysis result, and the unnecessary information is information that may not be included in the analysis result;

the necessary information includes: an application ontology to be deployed; a corresponding configuration file; configuring an execution script required by an application to be deployed; and in the description specification file: basic information, executable instructions, and installation information;

the non-essential information includes, in the description specification file: dependency information, database configuration information, nginx configuration information, runtime environment information, and other configuration information.

7. The method of claim 6, further comprising:

judging whether all necessary information exists in the application information which is analyzed and restored;

and if the necessary information is missing, terminating the configuration flow of the application to be deployed and outputting alarm information.

8. The method of claim 3, wherein the configuring the corresponding application to be deployed based on the cached application information comprises:

acquiring residual resources of a target of an application to be deployed, and judging whether the residual resources meet configuration requirements or not based on the running environment configuration information;

if the residual resources meet the configuration requirement, judging whether installation dependency information exists or not, and carrying out prior configuration on the dependency module based on the installation dependency information under the condition that the installation dependency information exists;

based on an installation environment created by a previous configuration module, performing to-be-deployed application body configuration based on the installation information, and feeding back a configuration completion signal;

and triggering the operation and maintenance management flow to execute an instruction in response to the configuration completion signal.

9. The method of claim 8, wherein the operation and maintenance management process comprises:

based on the configured application, issuing a preset operation and maintenance script to a preset directory, and opening corresponding operation and maintenance operation;

inquiring whether application data of which the configuration is completed exist in a preset database, if so, configuring corresponding application data, and changing the application data based on a prewritten sql statement;

inquiring whether nginx information of the configured application exists in a preset number base, and if yes, performing reverse proxy and load balancing function configuration of the configured application based on the nginx information;

and configuring other configuration information, and performing residual content configuration based on the user-defined configuration content to complete the deployment of the application to be deployed.

10. An enterprise-level application operation and maintenance system, the system comprising:

the acquisition unit is used for acquiring the module installation package; the module installation package is obtained by packaging and processing application information of the application to be deployed; wherein, the first and the second end of the pipe are connected with each other,

the application information at least comprises a description specification file, and the description specification file is used for describing specification information required by configuring the application to be deployed;

the analysis unit is used for analyzing the module installation package step by step and restoring the application information;

the processing unit is used for carrying out classification management and caching on the analyzed and restored application information;

and the execution unit is used for configuring the corresponding application to be deployed based on the cached application information and feeding back a configuration result.

11. A processor, characterized in that the processor is configured to execute the enterprise-level application operation and maintenance method according to any one of claims 1 to 9.

12. A machine-readable storage medium having instructions stored thereon, which when executed by a processor causes the processor to be configured to perform the enterprise-level application operation and maintenance method according to any one of claims 1 to 9.

13. A computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the enterprise level application operation and maintenance method according to any of claims 1 to 9.

Images