WO2019090993A1

WO2019090993A1 - Deployment method and apparatus for monitoring system, computer device and storage medium

Info

Publication number: WO2019090993A1
Application number: PCT/CN2018/074934
Authority: WO
Inventors: 高泗俊; 李渊
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-11-08
Filing date: 2018-02-01
Publication date: 2019-05-16
Also published as: CN107896162A; CN107896162B

Abstract

Disclosed are a deployment method and apparatus for a monitoring system, a computer device and a storage medium. The method comprises: dividing component modules according to component information to generate category component groups; obtaining difference information and similarity information between a plurality of component modules in the same category component group; generating a container file template and storing the difference information in a configuration file; and generating a deployment arrangement file according to the container file template and the configuration file to deploy the monitoring system.

Description

Monitoring system deployment method, device, computer device and storage medium

This application claims the priority of the Chinese patent application filed on November 8, 2017, the Chinese Patent Office, the application number is 201711091445.5, and the invention name is "the deployment method, device, computer equipment and storage medium of the monitoring system". The citations are incorporated herein by reference.

Technical field

The present application relates to the field of Internet technologies, and in particular, to a method, an apparatus, a computer device, and a storage medium for deploying a monitoring system.

Background technique

At present, there are many monitoring systems for operation and maintenance on the market, such as Argus monitoring system, Zabbix monitoring system and Open-falcon monitoring system. These monitoring systems have a large number of component modules and generally include nearly 30 component modules. When deploying these monitoring systems, each component module must ensure high availability, as well as management, monitoring, upgrade, and deployment. More component modules make the deployment method very complicated. If traditional deployment methods are adopted, This workload and operation and maintenance costs will be relatively high, and deployment is not flexible enough, which in turn increases the operation and maintenance costs of the monitoring system.

Summary of the invention

The application provides a method, a device, a computer device and a storage medium for deploying a monitoring system to improve the deployment efficiency of the monitoring system.

In a first aspect, the application provides a method for deploying a monitoring system, including:

Obtain component information corresponding to each component module in the monitoring system;

And dividing the component module according to the component information to generate a category component group;

Obtaining difference information and common information between multiple component modules in the same group of component groups;

Generating a container file template based on the difference information and the common information, and storing the difference information in a configuration file;

Generating a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file;

The deployment profile is invoked to deploy the monitoring system.

In a second aspect, the present application provides a deployment apparatus for a monitoring system, including:

a first acquiring unit, configured to acquire component information corresponding to each component module in the monitoring system;

a division generating unit, configured to divide the component module according to the component information to generate a category component group;

a second obtaining unit, configured to acquire difference information and common information between the multiple component modules in the same group of component groups;

Generating a storage unit, configured to generate a container file template based on the difference information and the common information, and store the difference information in a configuration file;

a file generating unit, configured to generate a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file;

The deployment unit is invoked to invoke the deployment orchestration file to deploy the monitoring system.

In a third aspect, the present application further provides a computer device including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor implementing the program A method of deploying any of the monitoring systems provided by the application.

In a fourth aspect, the present application also provides a storage medium, wherein the storage medium stores a computer program, the computer program comprising program instructions, the program instructions, when executed by a processor, causing the processor to execute the application A method of deploying any of the monitoring systems provided.

The embodiment of the present application classifies component modules of the monitoring system, and obtains difference information and common information between the component modules of the same category; generates a container file template based on the difference information and the common information, and stores the difference information. In the configuration file, the deployment orchestration file is generated by using the configuration file and the container file template; and the monitoring system is deployed by the container cluster management system according to the deployment orchestration file. Through the processing of the component modules, the deployment efficiency of the monitoring system is improved, and the monitoring system is conveniently managed in the future.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are some embodiments of the present application, For the ordinary technicians, other drawings can be obtained based on these drawings without any creative work.

1 is a schematic flowchart of a method for deploying a monitoring system according to an embodiment of the present application;

2 is a schematic flow chart of a sub-step of the deployment method shown in FIG. 1;

3 is a schematic flow chart of another sub-step of the deployment method shown in FIG. 1;

4 is a schematic flowchart of a method for deploying a monitoring system according to another embodiment of the present application;

FIG. 5 is a schematic block diagram of a device for deploying a monitoring system according to an embodiment of the present application;

FIG. 6 is a schematic block diagram of a device for deploying a monitoring system according to another embodiment of the present application;

FIG. 7 is a schematic block diagram of a computer device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

The use of the terms "comprising", "comprising", "","," The presence or addition of a plurality of other features, integers, steps, operations, elements, components, and/or collections thereof.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a method for deploying a monitoring system according to an embodiment of the present application. As shown in FIG. 1, the deployment method of the monitoring system includes steps S101 to S106.

S101. Obtain component information corresponding to each component module in the monitoring system.

The monitoring system is mainly used for the operation and maintenance of Internet products, providing timely warning and fault location analysis and problem location analysis, such as Open-falcon monitoring system, Zabbix monitoring system or Argus monitoring system. These monitoring systems include multiple component modules, such as component modules such as agent, gateway, proxy, transfer, and query, each with different functions. When deploying a monitoring system, each component module needs to be considered, thus affecting the efficiency of the deployment.

In this implementation, component information corresponding to each component module in the monitoring system is obtained. The component information includes programming language information of the component module. Specifically, the programming language information such as the Golang language and the Python language, the component modules of the monitoring system are basically written in the Golang language and the Python language.

In an embodiment, the component information may further include status information of the component module, such as data status information and no data status information. The data status information refers to status information corresponding to the component module associated with the local data; the no data status information refers to status information corresponding to the component module not associated with the local data.

Because the deployment mode and installation environment of component modules with different component information may be different, it is necessary to distinguish between multiple component modules of the monitoring system.

S102. Divide the component module according to the component information to generate a category component group.

In this embodiment, specifically, all component modules of the monitoring system are divided according to the programming language information to generate a category component group.

For example, taking the Argus monitoring system as an example, if the Argus monitoring system includes 30 component modules, 14 of the 30 component modules are written in the Golang language, and the other 16 component modules are written in the Python language. The 30 component modules of the Argus monitoring system are divided into Golang component group and Python component group. The Golang component group includes 14 component modules written in Golang language. The Python component group includes 16 component modules written in Python language.

In an embodiment, all component modules of the monitoring system may also be divided according to state information to generate a category component group. The specific division method is similarly divided according to the programming language information, and will not be described in detail here.

S103. Obtain difference information and common information between multiple component modules in the same group of component groups.

In this embodiment, according to the above classification method, each analog component group includes a plurality of component modules, and there are difference information between the plurality of component modules, and common information exists.

For example, the gob component group hbs, transfer, judge, graph, query, alarm and other component modules. The common information of these component modules includes: common installation package, startup service, startup instructions, the same docker base image and the same service naming information; the difference information of these component modules includes: boot port, mount storage volume and number of copies, etc. information.

Specifically, it is obtained by calling the name corresponding to the common information and the difference information by the program code. For example, the name of the shared installation package, the name corresponding to the startup command, or a different name corresponding to a different startup port.

S104. Generate a container file template based on the difference information and the common information, and store the difference information in a configuration file.

In this embodiment, in order to containerize the component modules of the monitoring system, a corresponding file module needs to be created. Specifically, the container cluster management system (Kubernetes, referred to as K8s) can be used to deploy the monitoring system, and the corresponding container file template includes the Dockerfile template. , K8s deployment template and k8s orchestration template.

In the present embodiment, specifically, as shown in FIG. 2, step S104 includes sub-steps S104a to S104c.

S104a: Perform variable setting on the difference information of each of the component modules.

Specifically, different variable settings are made for the difference information of each component module. In addition, different difference parts of the difference information of each of the component modules are set with different variables. The variable setting is to set the corresponding variable for the difference part.

For example, the difference information of the transfer component module is set to correspond to the variable x. The difference information specifically includes a difference portion such as a storage volume and a copy number, and the corresponding storage variables and the number of copies are set to corresponding variables x1 and x2.

S104b. Generate a container file template according to the variable corresponding to the difference information of each component module and the common information.

Specifically, after the difference information of each of the component modules is set, the difference information is subjected to variable replacement, and a container file template is generated according to the variable and the common information, specifically, the commonality is invoked by a container generation command. The variable corresponding to the information and the difference information of each of the component modules further generates a container file template, that is, the container template includes common information and variables corresponding to the difference information.

S104c. Store difference information set by the variable in a configuration file.

Specifically, the difference information of the component module and its corresponding variable are stored in the configuration file.

The container file template is generated based on the difference information and the common information, and the difference information is stored in the configuration file. Compared with the existing deployment method, the deployment efficiency can be improved, and the container file template and the configuration file need only be stored in two Different locations are therefore beneficial for subsequent file management.

S105. Generate a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file.

In this embodiment, the preset file generation rule refers to filling the difference information of the configuration file in a container file template according to a preset variable manner, such as a transfer component module, and the variable corresponding to the difference information of the container file template is X1 and x2, when generating the layout file corresponding to the transfer component module, x1 and x2 are preset variables, and corresponding difference information in the configuration file is filled in the container file template according to the preset variables x1 and x2. Deployment orchestration files in different environments can be dynamically generated based on container file templates and configuration files. Different environments include environments such as development, testing, or production.

Specifically, a manner of generating a layout file is generated, as shown in FIG. 3, and step S105 includes sub-steps S105a and S105b.

S105a: Calling a preset read script to read the configuration file.

Specifically, the preset read script can be called by typing a command character to read the configuration file, and the preset read script is used to read the configuration file.

S105b. Fill the difference information in the configuration file into the container file template according to the variable to generate the deployment orchestration file.

Specifically, the profile difference information is correspondingly filled in the variable included in the container file template according to the variable correspondence relationship, thereby generating a complete deployment orchestration file.

S106. Call the deployment orchestration file to deploy the monitoring system.

Specifically, the deployment orchestration file may be invoked to deploy the monitoring system by using a calling command and a name of the deployment orchestration file.

In this embodiment, specifically, using Kubernetes to invoke the deployment orchestration file has completed deployment of the monitoring system. The Kubernetes is a container cluster management system, which can automatically coordinate the component modules of the monitoring system, and deploy the monitoring system by using the deployment orchestration file generated by the above method, regardless of the resource occupation of each component module. This saves manual operations and increases the efficiency of deployment.

The embodiment of the present application classifies component modules of the monitoring system, and obtains difference information and common information between the component modules of the same category; generates a container file template based on the difference information and the common information, and stores the difference information. In the configuration file, the deployment profile file is generated by using the configuration file and the container file template; the container cluster management system completes the deployment of the monitoring system according to the deployment orchestration file, thereby improving the deployment efficiency. At the same time, the difference information is stored in the configuration file, which also facilitates the management of the component modules of the monitoring system in the future.

Referring to FIG. 4, FIG. 4 is a schematic flowchart of a method for deploying a monitoring system according to another embodiment of the present application. The deployment method of the monitoring system can be run in a server, where the server can be a stand-alone server or a server cluster composed of multiple servers. As shown in FIG. 4, the deployment method of the monitoring system includes steps S201 to S208.

S201. Obtain component information corresponding to each component module in the monitoring system, where the component information includes programming language information, where the programming language information includes a Golang language and a Python language.

In this embodiment, component information corresponding to each component module in the monitoring system is obtained, specifically: classifying the component modules according to the programming language information to generate a Golang component group and a Python component group.

Among them, according to the programming language of the component module, for example, component modules of hbs, transfer, judge, graph, query, alarm, etc. in Argus component module are written by Golang language, and component modules such as portal, dashboard, links are used. Written in the Python language.

Because component modules written in two languages are deployed in different ways, specifically the component modules written in Golang have no dependencies and can be started directly. The component module written in Python needs to start the python virtual environment to load the related dependencies in order to start the operation normally. Therefore, by analyzing the deployment characteristics of the component modules, it is convenient to make corresponding container file templates, and at the same time, the deployment efficiency can be improved.

S202. Divide the component module according to the component information to generate a category component group.

Specifically, the component modules are classified according to the programming language information to generate a Golang component group and a Python component group. For the Argus monitoring system, the Golang component group includes component modules such as hbs, transfer, judge, graph, query, and alarm; the Python component group includes component modules such as portal, dashboard, and links.

S203. Obtain difference information and common information between multiple component modules in the same group of component groups.

Specifically, acquiring common information and difference information between the plurality of component modules in the Golang component group, and acquiring common information and difference information between the plurality of component modules in the Python component group.

S204. Generate a container file template based on the difference information and the common information, and store the difference information in a configuration file.

Specifically, the variable information is set for the difference information of each of the component modules; the container file template is generated according to the variable corresponding to the difference information of each component module and the common information; and the difference information set by the variable is Stored in the configuration file.

In addition, the configuration file can also be saved in a preset database and managed by a configmap. Specifically, the configuration file of the monitoring system is centrally managed by the configmap in Kubernetes, thereby improving management efficiency.

S205. Generate a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file.

Specifically, the preset read script is invoked to read the configuration file; and the difference information in the configuration file is filled into the container file template according to the variable to generate the deployment orchestration file. The operation performed by the preset script is to read the configuration file, and describe and fill variables in the container file template according to the difference information corresponding to the variables of the configuration file, thereby generating a completed deployment orchestration file.

In this embodiment, the monitoring system is specifically deployed by using a container cluster management system (Kubernetes, K8s for short). Correspondingly, the deployment orchestration file includes a Dockerfile deployment orchestration file and a K8s deployment orchestration file.

S206. Add a host required to deploy the monitoring system to a host resource pool and mark a host in the host resource pool to generate a host tag number.

When the monitoring system is deployed by using the K8s to invoke the deployment orchestration file, the host required to deploy the monitoring system may also be obtained, and the host may be a physical machine or a virtual machine. These hosts are added to the host resource pool, and these hosts are also managed and scheduled by K8s, so that when the host fails, the component modules are migrated by K8s, and the component modules are automatically migrated to the available hosts, which greatly reduces the operation. Dimensional complexity.

Add these hosts to the host resource pool. Specifically, install client software such as docker, flannel, and Kubernetes on these hosts. Specify the administrator's IP of Kubernetes at startup, so that the host will be registered in the K8s cluster and taken over by the Kubernetes master. In order to join these hosts into the host resource pool.

The host in the host resource pool is marked to generate a host tag number. Specifically, after the host is added to the resource pool, the hosts in the resource pool are marked, for example, as hosts #1, #2, #3, and the like. These #1, #2, and #3 are the host labels.

S207. Perform scheduling management on the host in the host resource pool according to the host tag number.

In this embodiment, the hosts in the host resource pool are scheduled and managed according to the host tag number, so that the K8s can select different hosts to deploy according to the resource occupancy of the component modules.

S208. Invoking the deployment orchestration file, the monitoring system is deployed in a host in the host resource pool.

Specifically, the deployment system may be invoked to deploy the monitoring system in a host in the host resource pool by using a calling command and a name of the deployment orchestration file.

The foregoing embodiment classifies the component modules of the monitoring system according to the programming language information, and obtains difference information and common information between the component modules of the same category; generates a container file template based on the difference information and the common information, and the difference is The information is stored in the configuration file; the deployment orchestration file is generated by using the configuration file and the container file template; and the monitoring system is deployed by the container cluster management system according to the deployment orchestration file, thereby improving the deployment efficiency. At the same time, the difference information is stored in the configuration file, which also facilitates the management of the component modules of the monitoring system in the future. In addition, hosts that deploy the monitoring system are added to the resource pool for centralized management, thereby reducing the complexity of deployment and operation.

Referring to FIG. 5, FIG. 5 is a schematic block diagram of a device for deploying a monitoring system according to an embodiment of the present application. The deployment device 300 is installed in a server or a terminal, wherein the server may be a stand-alone server or a server cluster composed of multiple servers; the terminal includes a desktop computer, a laptop, a tablet, a personal digital assistant (PDA), or Smartphones, etc.

As shown in FIG. 5, the deployment apparatus 300 includes a first acquisition unit 301, a division generation unit 302, a second acquisition unit 303, a generation storage unit 304, a file generation unit 305, and a call deployment unit 306.

The first obtaining unit 301 is configured to acquire component information corresponding to each component module in the monitoring system.

The component information corresponding to each component module in the monitoring system is obtained. The component information includes programming language information of the component module. Specifically, the programming language information such as the Golang language and the Python language, the component modules of the monitoring system are basically written in the Golang language and the Python language.

The partition generation module 302 is configured to divide the component module according to the component information to generate a category component group.

Specifically, all component modules of the monitoring system are divided according to the programming language information to generate a category component group.

In an embodiment, all component modules of the monitoring system may also be divided according to state information to generate a category component group.

The second obtaining unit 303 is configured to acquire difference information and common information between the multiple component modules in the same group of category components.

The generating storage unit 304 is configured to generate a container file template based on the difference information and the common information, and store the difference information in a configuration file.

In order to containerize the component modules of the monitoring system, the corresponding file modules need to be created. The container cluster management system (Kubernetes, K8s for short) can be used to deploy the monitoring system. The corresponding container file template includes the Dockerfile template, K8s deployment template and k8s. Orchestration templates, etc.

Specifically, the generation storage unit 304 includes a variable setting sub-unit 3041, a template generation sub-unit 3042, and an information storage sub-unit 3043.

The variable setting subunit 3041 is configured to perform variable setting on the difference information of each of the component modules.

The template generation subunit 3042 is configured to generate a container file template according to the variable corresponding to the difference information of each of the component modules and the common information.

Specifically, after the difference information of each of the component modules is set, the difference information is subjected to variable replacement, and a container file template is generated according to the variable and the common information, that is, the container template includes common information and difference information. Corresponding variables.

The information storage subunit 3043 is configured to store the difference information set by the variable in a configuration file.

The file generating unit 305 is configured to generate a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file.

The preset file generation rule is to fill the difference information of the configuration file in the container file template according to the preset variable manner, thereby dynamically generating the deployment orchestration file in different environments according to the container file template and the configuration file. Different environments include environments such as development, testing, or production.

Specifically, the file generating unit 305 includes a call reading subunit 3051 and an information filling subunit 3052.

The read subunit 3051 is called to call a preset read script to read the configuration file.

The information populating sub-unit 3052 is configured to fill the difference information in the configuration file into the container file template according to the variable to generate the deployment orchestration file.

The deployment unit 306 is configured to invoke the deployment orchestration file to deploy the monitoring system.

The specific deployment of the deployment orchestration file by Kubernetes has completed the deployment of the monitoring system. The Kubernetes is a container cluster management system, which can automatically coordinate the component modules of the monitoring system, and deploy the monitoring system by using the above deployment programming files, regardless of the resource occupation of each component module. This saves manual operations and increases the efficiency of deployment.

Please refer to FIG. 6. FIG. 6 is a schematic block diagram of a device for deploying a monitoring system according to an embodiment of the present application. As shown in FIG. 6, the deployment apparatus 400 includes a first acquisition unit 401, a division generation unit 402, a second acquisition unit 403, a generation storage unit 404, a file generation unit 405, a join marker unit 406, a schedule management unit 407, and a call deployment unit. 408.

The first obtaining unit 401 is configured to acquire component information corresponding to each component module in the monitoring system, where the component information includes programming language information, where the programming language information includes a Golang language and a Python language.

In this embodiment, the first obtaining unit 401 is specifically configured to: classify the component modules according to the programming language information to generate a Golang component group and a Python component group.

For example, component modules of hbs, transfer, judge, graph, query, alarm, etc. in Argus component modules are written in Golang language, and component modules such as portal, dashboard, links, etc. are written in Python language.

The division generating unit 402 is configured to divide the component module according to the component information to generate a category component group.

The second obtaining unit 403 is configured to acquire difference information and common information between the multiple component modules in the same group of category component groups.

The method is specifically configured to obtain common information and difference information between the plurality of component modules in the Golang component group, and obtain common information and difference information between the plurality of component modules in the Python component group.

The generating storage unit 404 is configured to generate a container file template based on the difference information and the common information, and store the difference information in the configuration file.

Specifically, the variable information is set for each difference component of the component module; the container file template is generated according to the variable corresponding to the difference information of each component module and the common information; and the difference that is set by the variable is The information is stored in a configuration file.

In addition, a saving management unit is further included, wherein the saving management unit is further configured to save the configuration file in a preset database and manage the configuration file through a configmap. Specifically, the configuration file of the monitoring system is centrally managed by the configmap in Kubernetes, thereby improving management efficiency.

The file generating unit 405 is configured to generate a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file.

Specifically, the method is: calling a preset read script to read the configuration file; and filling the difference information in the configuration file into the container file template according to the variable to generate the deployment orchestration file. The operation performed by the preset script is to read the configuration file, and describe and fill variables in the container file template according to the difference information corresponding to the variables of the configuration file, thereby generating a completed deployment orchestration file.

The tagging unit 406 is configured to join the host required to deploy the monitoring system to the host resource pool and mark the host in the host resource pool to generate a host tag number.

The scheduling management unit 407 is configured to perform scheduling management on the hosts in the host resource pool according to the host tag number.

The deployment unit 408 is configured to invoke the deployment orchestration file to deploy the monitoring system in a host in the host resource pool.

The above apparatus may be embodied in the form of a computer program that can be run on a computer device as shown in FIG.

Please refer to FIG. 7. FIG. 7 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 device can be a terminal or a server.

Referring to FIG. 7, the computer device 500 includes a processor 520, a memory, and a network interface 550 connected by a system bus 510, wherein the memory can include a non-volatile storage medium 530 and an internal memory 540.

The non-volatile storage medium 530 can store an operating system 531 and a computer program 532. When the computer program 532 is executed, the processor 520 can be caused to perform a deployment method of the monitoring system.

The processor 520 is used to provide computing and control capabilities to support the operation of the entire computer device 500.

The internal memory 540 provides a cached operating environment for the operating system 531 and the computer program 532 in the non-volatile storage medium 530.

The network interface 550 is used for network communication, such as sending assigned tasks and the like. It will be understood by those skilled in the art that the structure shown in FIG. 7 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device 500 to which the solution of the present application is applied, and a specific computer device. 500 may include more or fewer components than shown, or some components may be combined, or have different component arrangements.

The processor 520 is configured to run program code stored in the memory to implement the following program:

Obtaining component information corresponding to each component module in the monitoring system; dividing the component module according to the component information to generate a category component group; acquiring difference information and common information between multiple component modules in the same group component group Generating a container file template based on the difference information and the common information and storing the difference information in a configuration file; generating a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file; and invoking the deployment The orchestration file deploys the monitoring system.

In an embodiment, when the processor 520 generates the container file template based on the difference information and the common information, and stores the difference information in the configuration file, the processor 520 specifically executes the following procedure:

Performing variable setting on the difference information of each of the component modules; generating a container file template according to the variable corresponding to the difference information of each component module and the common information; and storing the difference information set by the variable in the configuration In the file.

In an embodiment, when the processor 520 generates the deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file, the processor 520 executes the following procedure:

Calling a preset read script to read the configuration file; populating the difference information in the configuration file into the container file template according to the variable to generate the deployment orchestration file.

In an embodiment, the processor 520 is configured to execute program code stored in the memory to implement the following program:

Obtaining component information corresponding to each component module in the monitoring system; dividing the component module according to the component information to generate a category component group; acquiring difference information and common information between multiple component modules in the same group component group Generating a container file template based on the difference information and the common information and storing the difference information in a configuration file; generating a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file; the monitoring is to be deployed The host required by the system joins the host resource pool and marks the host in the host resource pool to generate a host tag number; and performs scheduling management on the host in the host resource pool according to the host tag number; The deployment orchestration file deploys the monitoring system in a host in the host resource pool.

It should be understood that, in the embodiment of the present application, the processor 520 may be a central processing unit (CPU), and the processor 520 may also be other general-purpose processors, a digital signal processor (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Those skilled in the art will appreciate that the computer device 500 architecture illustrated in FIG. 7 does not constitute a limitation to computer device 500, may include more or fewer components than illustrated, or may combine certain components, or different components. Arrangement.

In another embodiment of the present application, a storage medium is provided, the storage medium being a computer readable storage medium storing a computer program, wherein the computer program includes program instructions. This program instruction is implemented when executed by the processor:

In an embodiment, when the program instruction is executed by the processor to generate the container file template based on the difference information and the common information, and the difference information is stored in the configuration file, the specific implementation is:

In an embodiment, the program instruction is executed by the processor, and when the deployment file is generated according to the preset file generation rule according to the container file template and the configuration file, the specific implementation is:

In an embodiment, the program instructions are executed by the processor and further implement:

The computer readable storage medium may be any medium that can store program code, such as a USB flash drive, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, for clarity of hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the deployment apparatus and the unit of the above-mentioned monitoring system can be referred to the corresponding process in the foregoing method embodiments, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of each unit is only a logical function division, and there may be another division manner in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.

The steps in the method of the embodiment of the present application may be sequentially adjusted, merged, and deleted according to actual needs. The units in the apparatus of the embodiment of the present application may be combined, divided, and deleted according to actual needs.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the 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 standalone product, can be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be in essence or part of the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. There are a number of instructions for causing a computer device (which may be a personal computer, terminal, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any equivalents can be easily conceived by those skilled in the art within the technical scope disclosed in the present application. Modifications or substitutions are intended to be included within the scope of the present application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

A method of deploying a monitoring system, comprising:

Obtain component information corresponding to each component module in the monitoring system;

And dividing the component module according to the component information to generate a category component group;

Obtaining difference information and common information between multiple component modules in the same group of component groups;

Generating a container file template based on the difference information and the common information, and storing the difference information in a configuration file;

Generating a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file;

The deployment profile is invoked to deploy the monitoring system.
The method for deploying a monitoring system according to claim 1, wherein the generating a container file template based on the difference information and the common information and storing the difference information in a configuration file includes:

Performing variable setting on the difference information of each of the component modules;

Generating a container file template according to the variable corresponding to the difference information of each of the component modules and the common information;

The difference information set by the variable is stored in the configuration file.
The method for deploying a monitoring system according to claim 2, wherein the generating the deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file comprises:

Calling a preset read script to read the configuration file;

The difference information in the configuration file is populated into the container file template according to the variable to generate the deployment orchestration file.
The method of deploying a monitoring system according to claim 1, wherein the component information comprises programming language information, the programming language information comprising a Golang language and a Python language;

The classifying the component modules according to the component information to generate a category component group includes:

Classifying the component modules according to the programming language information to generate a Golang component group and a Python component group;

And obtaining the common information and the difference information between the multiple component modules in the same group of component groups, including: acquiring common information and difference information between the multiple component modules in the Golang component group, and acquiring the Common information and difference information between multiple of the component modules in a Python component group.
The method for deploying a monitoring system according to claim 1, wherein before the invoking the deployment orchestration file to deploy the monitoring system, the method further includes:

Adding hosts required to deploy the monitoring system to a host resource pool and marking hosts in the host resource pool to generate host tag numbers;

Scheduling management of hosts in the host resource pool according to the host tag number;

The invoking the deployment orchestration file to deploy the monitoring system includes:

The deployment orchestration file is invoked to deploy the monitoring system in a host in the host resource pool.
The method for deploying a monitoring system according to claim 1, wherein the filling the difference information in the configuration file into the container file template according to the variable to generate the deployment orchestration file comprises:

The profile difference information is correspondingly filled with variables included in the container file template according to the variable correspondence to generate the deployment orchestration file.
The method for deploying a monitoring system according to claim 1, wherein the generating a container file template based on the difference information and the common information and storing the difference information in the configuration file further includes:

The configuration file is saved in a preset database and managed by a configmap.
The method of deploying a monitoring system according to claim 1, wherein the component information may further include status information of the component module; and the dividing the component module according to the component information to generate a category component group comprises:

All component modules of the monitoring system are divided according to the status information to generate a category component group.
A deployment device for a monitoring system, comprising:

a first acquiring unit, configured to acquire component information corresponding to each component module in the monitoring system;

a division generating unit, configured to divide the component module according to the component information to generate a category component group;

a second obtaining unit, configured to acquire difference information and common information between the multiple component modules in the same group of component groups;

Generating a storage unit, configured to generate a container file template based on the difference information and the common information, and store the difference information in a configuration file;

a file generating unit, configured to generate a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file;

The deployment unit is invoked to invoke the deployment orchestration file to deploy the monitoring system.
The apparatus for deploying a monitoring system according to claim 9, wherein the generating the storage unit comprises:

a variable setting subunit, configured to perform variable setting on difference information of each of the component modules;

a template generating subunit, configured to generate a container file template according to the variable corresponding to the difference information of each of the component modules and the common information;

An information storage subunit for storing difference information set by the variable in a configuration file.
A computer apparatus comprising: a memory, a processor, and a computer program stored on the memory and operative on the processor, the processor executing the computer program to implement the following steps:

Obtain component information corresponding to each component module in the monitoring system;

And dividing the component module according to the component information to generate a category component group;

Obtaining difference information and common information between multiple component modules in the same group of component groups;

Generating a container file template based on the difference information and the common information, and storing the difference information in a configuration file;

Generating a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file;

The deployment profile is invoked to deploy the monitoring system.
The computer apparatus according to claim 11, wherein when said processor executes said computer program, the following steps are specifically implemented:

Performing variable setting on the difference information of each of the component modules;

Generating a container file template according to the variable corresponding to the difference information of each of the component modules and the common information;

The difference information set by the variable is stored in the configuration file.
The computer apparatus according to claim 12, wherein when said processor executes said computer program, the following steps are further embodied:

Calling a preset read script to read the configuration file;

The difference information in the configuration file is populated into the container file template according to the variable to generate the deployment orchestration file.
The computer device according to claim 11, wherein the component information comprises programming language information, the programming language information comprising a Golang language and a Python language; and when the processor executes the computer program, the following steps are specifically implemented:

Classifying the component modules according to the programming language information to generate a Golang component group and a Python component group;

And obtaining the common information and the difference information between the multiple component modules in the same group of component groups, including: acquiring common information and difference information between the multiple component modules in the Golang component group, and acquiring the Common information and difference information between multiple of the component modules in a Python component group.
The computer apparatus according to claim 11, wherein when said processor executes said computer program, the following steps are further implemented:

Adding hosts required to deploy the monitoring system to a host resource pool and marking hosts in the host resource pool to generate host tag numbers;

Scheduling management of hosts in the host resource pool according to the host tag number;

The deployment orchestration file is invoked to deploy the monitoring system in a host in the host resource pool.
A storage medium storing a computer program, the computer program comprising program instructions that, when executed by a processor, cause the processor to perform the following steps:

Obtain component information corresponding to each component module in the monitoring system;

And dividing the component module according to the component information to generate a category component group;

Obtaining difference information and common information between multiple component modules in the same group of component groups;

Generating a container file template based on the difference information and the common information, and storing the difference information in a configuration file;

Generating a deployment orchestration file according to the preset file generation rule according to the container file template and the configuration file;

The deployment profile is invoked to deploy the monitoring system.
The storage medium of claim 16 wherein said program instructions, when executed by a processor, cause said processor to perform the following steps:

Performing variable setting on the difference information of each of the component modules;

Generating a container file template according to the variable corresponding to the difference information of each of the component modules and the common information;

The difference information set by the variable is stored in the configuration file.
The storage medium of claim 17 wherein said program instructions, when executed by a processor, cause said processor to perform the following steps:

Calling a preset read script to read the configuration file;

The difference information in the configuration file is populated into the container file template according to the variable to generate the deployment orchestration file.
The storage medium of claim 16, wherein the component information comprises programming language information, the programming language information comprising a Golang language and a Python language; the program instructions, when executed by a processor, cause the processor to execute the following step:

Classifying the component modules according to the programming language information to generate a Golang component group and a Python component group;

And obtaining the common information and the difference information between the multiple component modules in the same group of component groups, including: acquiring common information and difference information between the multiple component modules in the Golang component group, and acquiring the Common information and difference information between multiple of the component modules in a Python component group.
The storage medium of claim 16 wherein said program instructions, when executed by a processor, cause said processor to perform the following steps:

Adding hosts required to deploy the monitoring system to a host resource pool and marking hosts in the host resource pool to generate host tag numbers;

Scheduling management of hosts in the host resource pool according to the host tag number;

The deployment orchestration file is invoked to deploy the monitoring system in a host in the host resource pool.