CN110543328B - Cross-platform component management method, system, terminal and storage medium based on Ambari - Google Patents
Cross-platform component management method, system, terminal and storage medium based on Ambari Download PDFInfo
- Publication number
- CN110543328B CN110543328B CN201910683332.7A CN201910683332A CN110543328B CN 110543328 B CN110543328 B CN 110543328B CN 201910683332 A CN201910683332 A CN 201910683332A CN 110543328 B CN110543328 B CN 110543328B
- Authority
- CN
- China
- Prior art keywords
- component
- configuration file
- script
- information
- maintenance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 52
- 235000002905 Rumex vesicarius Nutrition 0.000 title claims abstract description 38
- 240000000797 Hibiscus cannabinus Species 0.000 title claims abstract description 37
- 238000013515 script Methods 0.000 claims abstract description 140
- 238000012423 maintenance Methods 0.000 claims abstract description 71
- 230000010354 integration Effects 0.000 claims abstract description 20
- 238000009434 installation Methods 0.000 claims abstract description 14
- 238000004806 packaging method and process Methods 0.000 claims abstract description 13
- 238000000034 method Methods 0.000 claims description 20
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 3
- 230000006837 decompression Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 230000000712 assembly Effects 0.000 description 2
- 238000000429 assembly Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 244000207667 Rumex vesicarius Species 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 210000004556 brain Anatomy 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013079 data visualisation Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000002054 transplantation Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention provides a cross-platform component management method, a system, a terminal and a storage medium based on Ambari, comprising the following steps: compiling and outputting the components into TAR packets through a packaging script; acquiring web configuration information by setting a placeholder of a configuration file template, and generating a component integration configuration file; setting a corresponding operation and maintenance script according to the component name; and acquiring component information and corresponding operation and maintenance script information to generate a meta-information configuration file, and deploying and managing the TAR package component according to the meta-information configuration file and the component integration configuration file. The invention abandons the traditional RPM or DEB installation mode, and simultaneously, because most of large data components are Java items, the large data components can be integrated into Ambari in a TAR packet mode to carry out unified configuration management. The trouble of cross-platform management is saved, and the problem of transplanting heterogeneous platform components is solved.
Description
Technical Field
The invention relates to the technical field of big data platform deployment, in particular to a cross-platform component management method, a cross-platform component management system, a cross-platform component management terminal and a storage medium based on Ambari.
Background
Big data, which may be referred to as the last two years of the IT world's firest noun. At present, big data components are developed vigorously, and domestic and foreign IT companies do not break away from various components developed by own companies, including message queues, resource management, data storage, data integration, data calculation, query analysis, data visualization, task scheduling and other big data component systems meeting business requirements of the companies. This document summarizes the components that are currently more widely used in the industry and are more community-active. The display is mainly shown in the forms of brain images, framework images and column images. The large data platform is built by a plurality of components with different functions, and the deployment and the later maintenance of the components are very important projects.
Ambari is a common deployment monitoring and operation and maintenance management tool for large data components and clusters at present. Ambari uses the traditional mode of software release by RPM and DEB packages, needs to make special installation packages aiming at different systems and platforms, and is not beneficial to cross-platform and component transplantation.
Disclosure of Invention
In view of the above-mentioned deficiencies of the prior art, the present invention provides a method, a system, a terminal and a storage medium for cross-platform component management based on Ambari, so as to solve the above-mentioned technical problems.
In a first aspect, the invention provides a cross-platform component management method based on Ambari, comprising:
compiling and outputting the components into TAR packets through a packaging script;
acquiring web configuration information by setting a placeholder of a configuration file template, and generating a component integration configuration file;
setting a corresponding operation and maintenance script according to the component name;
and acquiring component information and corresponding operation and maintenance script information to generate a meta-information configuration file, and deploying and managing the TAR package component according to the meta-information configuration file and the component integration configuration file.
Further, the acquiring the web configuration information by setting the placeholder of the configuration file template includes:
presetting a web page configuration item list, and generating a configuration file editing page in a web form of a component according to the list;
inputting a real parameter value to the configuration file editing page;
writing a configuration file template by adopting a Jinja2 template language, replacing placeholders of the configuration file template with real parameter values of the configuration file editing page, and generating a configuration file by using the configuration file template after replacement.
Further, the setting of the corresponding operation and maintenance script according to the component name includes:
compiling an operation and maintenance script set comprising an installation script, a starting script, a stopping script, an operation state monitoring script and a user-defined operation script for each component;
and marking the component number of the corresponding component by the operation and maintenance script set.
Further, the acquiring component information and corresponding operation and maintenance script information generates a meta-information configuration file, and deployment management is performed on the TAR package component according to the meta-information configuration file and the component integration configuration file, including:
acquiring script information under a script set corresponding to the component according to the corresponding relation between the component and the operation and maintenance script set;
generating a meta-information configuration file according to the component information and the operation and maintenance script information and the corresponding relation between the component information and the operation and maintenance script information;
and decompressing the components in the TAR packet, and calling corresponding operation and maintenance scripts of the components corresponding to the components according to the pre-specified component management strategy and the meta-information configuration file to perform management operation on the components.
In a second aspect, the invention provides an Ambari-based cross-platform component management system, comprising:
the component packaging unit is configured for compiling and outputting the components into TAR packets through the packaging scripts;
the file generation unit is configured to acquire web configuration information by setting a placeholder of a configuration file template and generate a component integration configuration file;
the script compiling unit is configured for setting a corresponding operation and maintenance script according to the component name;
and the component management unit is configured for acquiring component information and corresponding operation and maintenance script information to generate a meta-information configuration file, and deploying and managing the TAR package component according to the meta-information configuration file and the component integration configuration file.
Further, the file generation unit includes:
the page generation module is used for presetting a web page configuration item list and generating a configuration file editing page in a web form of the component according to the list;
the parameter input module is configured to input a real parameter value to the configuration file editing page;
and the template replacing module is configured for writing a configuration file template by adopting a Jinja2 template language, replacing the placeholder of the configuration file template with the real parameter value of the configuration file editing page, and generating a configuration file by the configuration file template after replacement.
Further, the script writing unit includes:
the script compiling module is configured for compiling an operation and maintenance script set comprising an installation script, a starting script, a stopping script, an operation state monitoring script and a user-defined operation script for each component;
and the script marking module is configured for marking the component numbers of the corresponding components of the operation and maintenance script set.
Further, the component management unit includes:
the information acquisition module is configured for acquiring script information under the script set corresponding to the component according to the corresponding relation between the component and the operation and maintenance script set;
the configuration generation module is configured for generating a meta-information configuration file according to the component information and the operation and maintenance script information and the corresponding relation between the component information and the operation and maintenance script information;
and the decompression management module is configured for decompressing the components in the TAR packet, managing the components according to a pre-specified component management strategy and calling corresponding operation and maintenance scripts of the components corresponding to the components according to the meta-information configuration file to manage the components.
In a third aspect, a terminal is provided, including:
a processor, a memory, wherein,
the memory is used for storing a computer program which,
the processor is used for calling and running the computer program from the memory so as to make the terminal execute the method of the terminal.
In a fourth aspect, a computer storage medium is provided having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.
The beneficial effect of the invention is that,
according to the Ambari-based cross-platform component management method, system, terminal and storage medium, a large number of functional components are distributed in a TAR package mode, and constraints of the system and a platform structure are avoided. The invention can combine the openness of the Ambari platform and the advantages of the TAR package cross-platform, and perfectly realize the management of the Ambari cross-platform assembly. Meanwhile, the installation and configuration processes of the assemblies in the TAR package form are normalized and scripted, and the automatic batch deployment of the assemblies can be realized by combining the Ambari automatic management capability. While Ambari provides a form of graphical web page to maintain the configuration file. Batch configuration updating and switching of multiple configuration file versions can be achieved. The invention abandons the traditional installation mode of RPM or DEB, and simultaneously, because most of large data components are Java items, the large data components can be integrated into Ambari to carry out unified configuration management in a TAR packet mode. The trouble of cross-platform management is saved, and the problem of transplanting heterogeneous platform components is solved.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 2 is a schematic block diagram of a system of one embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. 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 invention.
The following explains key terms appearing in the present invention.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention. The execution subject in fig. 1 may be an Ambari-based cross-platform component management system.
As shown in fig. 1, the method 100 includes:
and 140, acquiring the component information and the corresponding operation and maintenance script information to generate a meta-information configuration file, and deploying and managing the TAR package component according to the meta-information configuration file and the component integration configuration file.
Optionally, as an embodiment of the present invention, the acquiring web configuration information by setting a placeholder of a configuration file template includes:
presetting a web page configuration item list, and generating a configuration file editing page in a web form of a component according to the list;
inputting real parameter values to the configuration file editing page;
writing a configuration file template by adopting a Jinja2 template language, replacing placeholders of the configuration file template with real parameter values of the configuration file editing page, and generating a configuration file by using the configuration file template after replacement.
Optionally, as an embodiment of the present invention, the setting a corresponding operation and maintenance script according to a component name includes:
compiling an operation and maintenance script set comprising an installation script, a starting script, a stopping script, an operation state monitoring script and a user-defined operation script for each component;
and marking the component number of the corresponding component by the operation and maintenance script set.
Optionally, as an embodiment of the present invention, the acquiring component information and corresponding operation and maintenance script information generates a meta-information configuration file, and the deploying and managing a TAR package component according to the meta-information configuration file and the component integration configuration file includes:
acquiring script information under a script set corresponding to the component according to the corresponding relation between the component and the operation and maintenance script set;
generating a meta-information configuration file according to the component information and the operation and maintenance script information and the corresponding relation between the component information and the operation and maintenance script information;
and decompressing the components in the TAR packet, managing the components according to a pre-specified component management strategy and calling corresponding operation and maintenance scripts of the components corresponding to the components according to the meta-information configuration file.
In order to facilitate understanding of the present invention, the Ambari-based cross-platform component management method provided by the present invention is further described below with reference to the principle of the Ambari-based cross-platform component management method of the present invention and the process of managing cross-platform components in the embodiments.
Specifically, the Ambari-based cross-platform component management method includes:
s1, compiling and outputting the assembly into a TAR package through a packaging script.
And (3) writing an automatic packaging script by calling an Ant task in the Maven by using Maven-anti-plug. And (4) arranging and packaging the compiled output files of the component items into a release version in a TAR format according to the software architecture of each component. The components are distributed in TAR format.
S2, acquiring web configuration information by setting a placeholder of a configuration file template, and generating a component integration configuration file.
Ambari provides the functionality to modify a configuration file on a web page. When the components are integrated, a set of web page configuration item list and a configuration file template need to be provided. The list of the web page configuration items is a configuration file in an XML format, and the name, description, value type and value range information of each configuration item need to be indicated. Ambari reads this information and can generate a configuration file editing page in the form of a web form specific to the component.
Another one that needs to be written is a profile template. The profile template is written in Ambari using Jinja2 template language. When the Ambari installs the components, replacing placeholders in the configuration file template with real values filled in by a system administrator in the web configuration editing page to generate real configuration files, and storing the real configuration files in a configuration file management directory according to the requirements of the components.
And S3, setting a corresponding operation and maintenance script according to the component name.
This step requires providing an operation and maintenance script for the component, which is written using Python. After a system administrator issues an operation command to the component in the Ambari management page, the Ambari can automatically call the Python operation and maintenance script corresponding to the operation.
The component operation and maintenance script set required to be provided comprises the following script types:
-component installation script
-component start-up script
-component stop script
Component operating status monitoring script
Component custom action scripts (e.g. data rebalancing for HDFS, database execution backup, etc.)
Each component corresponds to an operation and maintenance script set, the operation and maintenance script set is marked with the number of the corresponding component, a mapping relation is conveniently established between the operation and maintenance script set and the component, and the operation and maintenance script set can be called conveniently at the later stage.
And S4, acquiring component information and corresponding operation and maintenance script information to generate a meta-information configuration file, and deploying and managing the TAR package component according to the meta-information configuration file and the component integration configuration file.
Ambari treats each component as a service (service) as a unit of management for Ambari. Each service has a corresponding configuration file (metainfo. The file records the service name, description, version and operation and maintenance script configuration in detail. The important part is the operation and maintenance script configuration. The file name, path, script type and timeout of the script are specified. With this configuration, ambari can obtain completion information for the component. Thereby realizing the management function of Ambari on the component.
The meta-information configuration file calls a corresponding operation and maintenance script of the component needing to be installed or updated, and the operation and maintenance script performs operations such as installation or updating on the component according to parameters in the configuration file of the component.
As shown in fig. 2, the system 200 includes:
a component packaging unit 210 configured to compile and output the component as a TAR package by a packaging script;
the file generating unit 220 is configured to obtain the web configuration information by setting a placeholder of a configuration file template, and generate a component integration configuration file;
a script writing unit 230 configured to set a corresponding operation and maintenance script according to the component name;
and the component management unit 240 is configured to collect component information and corresponding operation and maintenance script information to generate a meta-information configuration file, and perform deployment management on the TAR package component according to the meta-information configuration file and the component integration configuration file.
Optionally, as an embodiment of the present invention, the file generating unit includes:
the page generation module is used for presetting a web page configuration item list and generating a configuration file editing page in a web form of the component according to the list;
the parameter input module is configured to input a real parameter value to the configuration file editing page;
and the template replacing module is configured for writing a configuration file template by adopting a Jinja2 template language, replacing the placeholder of the configuration file template with the real parameter value of the configuration file editing page, and generating a configuration file by the configuration file template after replacement.
Optionally, as an embodiment of the present invention, the script writing unit includes:
the script compiling module is configured for compiling an operation and maintenance script set comprising an installation script, a starting script, a stopping script, an operation state monitoring script and a user-defined operation script for each component;
and the script marking module is configured for marking the component numbers of the components corresponding to the operation and maintenance script set.
Optionally, as an embodiment of the present invention, the component management unit includes:
the information acquisition module is configured for acquiring script information under the script set corresponding to the component according to the corresponding relation between the component and the operation and maintenance script set;
the configuration generation module is configured to generate a meta-information configuration file according to the component information and the operation and maintenance script information and the corresponding relationship between the component information and the operation and maintenance script information;
and the decompression management module is configured for decompressing the components in the TAR packet, managing the components according to a pre-specified component management strategy and calling corresponding operation and maintenance scripts of the components corresponding to the components according to the meta-information configuration file to manage the components.
Fig. 3 is a schematic structural diagram of a terminal system 300 according to an embodiment of the present invention, where the terminal system 300 may be used to execute an Ambari-based cross-platform component management method according to an embodiment of the present invention.
The terminal system 300 may include: a processor 310, a memory 320, and a communication unit 330. The components communicate via one or more buses, and those skilled in the art will appreciate that the architecture of the servers shown in the figures is not intended to be limiting, and may be a bus architecture, a star architecture, a combination of more or less components than those shown, or a different arrangement of components.
The memory 320 may be used for storing instructions executed by the processor 310, and the memory 320 may be implemented by any type of volatile or non-volatile storage terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The executable instructions in memory 320, when executed by processor 310, enable terminal 300 to perform some or all of the steps in the method embodiments described below.
The processor 310 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by operating or executing software programs and/or modules stored in the memory 320 and calling data stored in the memory. The processor may be composed of an Integrated Circuit (IC), for example, a single packaged IC, or a plurality of packaged ICs connected with the same or different functions. For example, the processor 310 may include only a Central Processing Unit (CPU). In the embodiment of the present invention, the CPU may be a single operation core, or may include multiple operation cores.
A communication unit 330, configured to establish a communication channel so that the storage terminal can communicate with other terminals. And receiving user data sent by other terminals or sending the user data to other terminals.
The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
Therefore, the present invention avoids system and platform architecture constraints by distributing a large number of functional components using TAR packages. The invention can combine the openness of the Ambari platform and the advantages of the TAR package cross platform, and perfectly realize the management of the Ambari cross platform assembly. Meanwhile, the installation and configuration process of the TAR package type component is standardized and scripted, and the automatic batch deployment of the component can be realized by combining the Ambari automatic management capability. While Ambari provides a form of graphical web page to maintain the configuration file. Batch configuration updating and switching of multiple configuration file versions can be achieved. The invention abandons the traditional installation mode of RPM or DEB, and simultaneously, because most of large data components are Java items, the large data components can be integrated into Ambari to carry out unified configuration management in a TAR packet mode. The trouble of cross-platform management is saved, and the problem of transplanting heterogeneous platform components is solved, so that the technical effect achieved by the embodiment can be referred to the description above, and the details are not repeated here.
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in the form of a software product, where the computer software product is stored in a storage medium, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, and the storage medium can store program codes, and includes instructions for enabling a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, and the like) to perform all or part of the steps of the method in the embodiments of the present invention.
The same and similar parts among the various embodiments in this specification may be referred to each other. Especially, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant points, reference may be made to the description in the method embodiment.
In the several embodiments provided in the present invention, it should be understood that the disclosed system, system and method may be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, systems or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
Although the present invention has been described in detail in connection with the preferred embodiments with reference to the accompanying drawings, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (8)
1. A cross-platform component management method based on Ambari is characterized by comprising the following steps:
compiling and outputting the components into TAR packets through a packaging script;
acquiring web configuration information by setting a placeholder of a configuration file template, and generating a component integration configuration file;
setting a corresponding operation and maintenance script according to the component name;
acquiring component information and corresponding operation and maintenance script information to generate a meta-information configuration file, and deploying and managing the TAR package component according to the meta-information configuration file and the component integration configuration file;
the acquiring of the web configuration information by setting the placeholder of the configuration file template includes:
presetting a web page configuration item list, and generating a configuration file editing page in a web form of a component according to the list;
inputting a real parameter value to the configuration file editing page;
writing a configuration file template by adopting a Jinja2 template language, replacing placeholders of the configuration file template with real parameter values of the configuration file editing page, and generating a configuration file by using the configuration file template after replacement.
2. The method of claim 1, wherein setting the corresponding operation and maintenance script according to the component name comprises:
compiling an operation and maintenance script set comprising an installation script, a starting script, a stopping script, an operation state monitoring script and a user-defined operation script for each component;
and marking the component number of the corresponding component by the operation and maintenance script set.
3. The method of claim 1, wherein the collecting component information and corresponding operation and maintenance script information generates a meta-information configuration file, and the deploying management of the TAR package component according to the meta-information configuration file and the component integration configuration file comprises:
acquiring script information under a script set corresponding to the component according to the corresponding relation between the component and the operation and maintenance script set;
generating a meta-information configuration file according to the component information and the operation and maintenance script information and the corresponding relation between the component information and the operation and maintenance script information;
and decompressing the components in the TAR packet, and calling corresponding operation and maintenance scripts of the components corresponding to the components according to the pre-specified component management strategy and the meta-information configuration file to perform management operation on the components.
4. An Ambari-based cross-platform component management system, comprising:
the component packaging unit is configured for compiling and outputting the components into TAR packets through the packaging scripts;
the file generation unit is configured to acquire web configuration information by setting a placeholder of a configuration file template and generate a component integration configuration file;
the script compiling unit is configured for setting a corresponding operation and maintenance script according to the component name;
the component management unit is configured for acquiring component information and corresponding operation and maintenance script information to generate a meta-information configuration file, and deploying and managing the TAR package component according to the meta-information configuration file and the component integration configuration file;
the file generation unit includes:
the page generation module is configured for presetting a web page configuration item list and generating a configuration file editing page of a component in a web form according to the list;
the parameter input module is configured to input a real parameter value to the configuration file editing page;
and the template replacing module is configured for writing a configuration file template by adopting a Jinja2 template language, replacing the placeholder of the configuration file template with the real parameter value of the configuration file editing page, and generating a configuration file by the configuration file template after replacement.
5. The system according to claim 4, wherein the script writing unit comprises:
the script compiling module is configured for compiling an operation and maintenance script set comprising an installation script, a starting script, a stopping script, an operation state monitoring script and a user-defined operation script for each component;
and the script marking module is configured for marking the component numbers of the corresponding components of the operation and maintenance script set.
6. The system of claim 4, wherein the component management unit comprises:
the information acquisition module is configured for acquiring script information under the script set corresponding to the component according to the corresponding relation between the component and the operation and maintenance script set;
the configuration generation module is configured for generating a meta-information configuration file according to the component information and the operation and maintenance script information and the corresponding relation between the component information and the operation and maintenance script information;
and the decompression management module is configured for decompressing the components in the TAR packet, managing the strategies according to the pre-specified components, and calling the corresponding operation and maintenance scripts of the components corresponding to the components according to the meta-information configuration files to manage the components.
7. A terminal, comprising:
a processor;
a memory for storing instructions for execution by the processor;
wherein the processor is configured to perform the method of any one of claims 1-3.
8. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910683332.7A CN110543328B (en) | 2019-07-26 | 2019-07-26 | Cross-platform component management method, system, terminal and storage medium based on Ambari |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910683332.7A CN110543328B (en) | 2019-07-26 | 2019-07-26 | Cross-platform component management method, system, terminal and storage medium based on Ambari |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110543328A CN110543328A (en) | 2019-12-06 |
| CN110543328B true CN110543328B (en) | 2022-10-18 |
Family
ID=68709865
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910683332.7A Active CN110543328B (en) | 2019-07-26 | 2019-07-26 | Cross-platform component management method, system, terminal and storage medium based on Ambari |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110543328B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111158743B (en) * | 2019-12-29 | 2022-04-22 | 北京浪潮数据技术有限公司 | Big data operation and maintenance management platform |
| CN113138772B (en) * | 2020-01-19 | 2023-12-05 | 北京京东振世信息技术有限公司 | Construction method and device of data processing platform, electronic equipment and storage medium |
| CN111610976B (en) * | 2020-04-08 | 2023-04-07 | 中科曙光(南京)计算技术有限公司 | Heterogeneous application transplanting method and device and computer equipment |
| CN111258589A (en) * | 2020-05-06 | 2020-06-09 | 成都四方伟业软件股份有限公司 | Multi-platform adaptation method for big data operation and maintenance monitoring |
| CN112230976B (en) * | 2020-09-01 | 2023-07-18 | 麒麟软件有限公司 | Method for simultaneously supporting two software package managers and supporting software package interdependence and conflict detection |
| CN112738112B (en) * | 2020-12-30 | 2023-02-24 | 北京浪潮数据技术有限公司 | Access method, device and medium for third-party component based on Ambari |
| CN113504917A (en) * | 2021-07-29 | 2021-10-15 | 青岛以萨数据技术有限公司 | Method and medium for integrating big data components by Ambari big data platform |
| CN114327599A (en) * | 2021-12-30 | 2022-04-12 | 深圳华云网科技有限公司 | Remote interaction method of intelligent terminal, intelligent terminal and operation and maintenance platform |
| CN117131516B (en) * | 2023-10-26 | 2024-02-09 | 中国证券登记结算有限责任公司 | Operation and maintenance method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080127175A1 (en) * | 2006-11-01 | 2008-05-29 | Microsoft Corporation | Packaging software products as single-file executables containing scripting logic |
| CN107864052A (en) * | 2017-10-30 | 2018-03-30 | 广东亿迅科技有限公司 | Method and its system based on lasting application deployment configuration automatic updating |
| CN107896162A (en) * | 2017-11-08 | 2018-04-10 | 平安科技（深圳）有限公司 | Dispositions method, device, computer equipment and the storage medium of monitoring system |
-
2019
- 2019-07-26 CN CN201910683332.7A patent/CN110543328B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080127175A1 (en) * | 2006-11-01 | 2008-05-29 | Microsoft Corporation | Packaging software products as single-file executables containing scripting logic |
| CN107864052A (en) * | 2017-10-30 | 2018-03-30 | 广东亿迅科技有限公司 | Method and its system based on lasting application deployment configuration automatic updating |
| CN107896162A (en) * | 2017-11-08 | 2018-04-10 | 平安科技（深圳）有限公司 | Dispositions method, device, computer equipment and the storage medium of monitoring system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110543328A (en) | 2019-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110543328B (en) | Cross-platform component management method, system, terminal and storage medium based on Ambari | |
| CN101707399B (en) | Method and system for acquiring electric energy information | |
| CN110515673B (en) | Plug-in system and method thereof | |
| CN105550001A (en) | Distributed automatic construction method and system | |
| CN107783975A (en) | The method and apparatus of distributed data base synchronization process | |
| CN105260315A (en) | Method for debugging log in embedded system process | |
| CN112988153A (en) | Data processing method and framework based on micro front end | |
| CN109032590B (en) | Configuration method, device, terminal and storage medium of visual development environment | |
| JP2011516987A (en) | Method and apparatus for managing mobile device software | |
| CN112463211A (en) | System architecture transformation method compatible with multiple development architectures and system architecture | |
| CN111064626B (en) | Configuration updating method, device, server and readable storage medium | |
| CN114327678A (en) | Real-time data processing system and method supporting multiple engines | |
| CN112257008B (en) | Online custom flow operation system, method, medium and server | |
| CN108399095B (en) | Method, system, device and storage medium for supporting dynamic management of timed tasks | |
| CN112565416B (en) | Cloud-native-based large-scale edge android equipment nanotube system and nanotube method thereof | |
| CN116450165A (en) | Method, system, terminal and storage medium for quickly building environment and deploying program | |
| CN114443294B (en) | Big data service component deployment method, system, terminal and storage medium | |
| CN111143193B (en) | Big data service testing method, system, terminal and storage medium based on RobotFramework | |
| CN114237634A (en) | Application release risk identification method, device, equipment, medium and program product | |
| CN114020368A (en) | Information processing method and device based on state machine and storage medium | |
| CN114564213A (en) | Pre-installed software deployment method, system, terminal and storage medium | |
| CN111984275A (en) | System deployment method, system, terminal and storage medium based on CPU architecture type | |
| CN113515293A (en) | Method and system for managing DevOps tool chain | |
| CN110858806B (en) | Generation method and device of node deployment file, node deployment method and device and electronic equipment | |
| CN103297479A (en) | Distributed detection method and device with upgraded plugin |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |