CN112269634A - Method and system for deploying Ambari component based on Docker container - Google Patents
Method and system for deploying Ambari component based on Docker container Download PDFInfo
- Publication number
- CN112269634A CN112269634A CN202011091628.9A CN202011091628A CN112269634A CN 112269634 A CN112269634 A CN 112269634A CN 202011091628 A CN202011091628 A CN 202011091628A CN 112269634 A CN112269634 A CN 112269634A
- Authority
- CN
- China
- Prior art keywords
- docker
- agent
- mirror image
- command
- file
- 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.)
- Granted
Links
- 240000000797 Hibiscus cannabinus Species 0.000 title claims abstract description 51
- 235000002905 Rumex vesicarius Nutrition 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000009434 installation Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000009286 beneficial effect Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 5
- 239000002699 waste material Substances 0.000 description 4
- 230000008859 change Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45587—Isolation or security of virtual machine instances
Abstract
The invention discloses a method and a system for deploying Ambari components based on a Docker container, wherein the method comprises the following steps: the method comprises the steps that a Server is used for sending a command to an Agent of a node, the Agent makes a Docker File file and constructs a mirror image according to the command sent by the Server, the Agent pulls a component mirror image from the Docker mirror image, the Agent starts and deploys components according to the made Docker File, and the system comprises modules corresponding to the steps of the method.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a system for deploying Ambari (full name Apache Ambari is a web-based tool and is composed of an Ambari Server and an Ambari Agent) component based on a Docker (open source application container engine) container.
Background
Under the Ambari technical system, an installation instruction is sent to a command queue through a Server (fully called Ambari Server, Ambari's Server program), then an Agent of a child node (fully called Ambari Agent, Ambari's Agent program) calls a script to execute a command for installation, a great resource waste exists in the existing Ambari component deployment mode, each time a component is deployed, configuration needs to be read from a Server end, then the instruction is sent to an installation script, and then a component installation package needing to be installed is drawn from an yum (fully qualified Update, Modified, front-end software package manager) source, the installed components are completely consistent due to the deployment characteristics of large data components, but only due to the distributed requirement, the components need to be deployed on large-scale nodes, the same installation package is drawn from a yum source every time, the great resource waste is caused, and a new community thought is provided in recent container growth, therefore, there is a need for a method and system for deploying Ambari components based on a Docker container, so as to partially solve the problems in the prior art.
Disclosure of Invention
In this summary, concepts in a simplified form are introduced that are further described in the detailed description. This summary of the invention is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
To at least partially solve the above problems, the present invention provides a method for deploying Ambari components based on a Docker container, comprising:
sending a command to an Agent of a node by using a Server;
the Agent makes a Docker File (a text file used for constructing an image in a Docker container) file and constructs the image according to a Server sending command;
the Agent pulls the component mirror image from the Docker mirror image;
and the Agent starts and deploys the components according to the manufactured DockerFile file.
Further, the sending an installation instruction to an Agent of a node by using a Server includes:
storing the Server sending command in an ActionQueue (queue);
sending all commands in the ActionQueue to the Agent;
and processing the command execution result according to the report of the Agent.
Further, the Server sending command includes a register command, a report status command, an execute task command, a cancel task command, and an update Alert (used in the HTML DOM)Scripting language) Defining commands and executing Alert commands.
Further, the Agent makes the Docker File file and constructs a mirror image according to a Server sending command, including:
compiling a Docker File file through a format command;
an image of a file is built by a Docker build (Docker command for creating an image using Docker file).
Further, the sending a command to an Agent of a node by using a Server further includes:
the Agent periodically sends a Heartbeat request, pulls the Server sending command to execute, and returns the execution result through the next Heartbeat request.
Further, before the Agent pulls the component image from the Docker image, the method further includes:
pulling a non-public mirror image in the Docker mirror image, and directly using a command Docker login (Docker command for logging in a Docker mirror image warehouse);
a mirror image warehouse server is appointed in the Docker, and if the server does not provide legal https (full name Hyper Text Transfer Protocol over secure Security Protocol) service, the configuration file in the Docker is reconfigured;
adding a mirror image source in a configuration file in the Docker, and accelerating the pulling of the component mirror image in the Docker mirror image.
Further, the Agent pulls the component image from the Docker image by using a Docker pull (Docker command for pulling or updating the image from the image repository) instruction to pull the image.
Further, the Agent starts and deploys component mirror images according to the manufactured Docker File, including
Executing the pulled component mirror image by using a Docker run command;
the program will automatically perform component deployment upon execution of a Docker run (Docker command to create a new container and allow a command) command.
Further, after the Agent starts and deploys the components according to the manufactured Docker File, the method further comprises the following steps:
and returning to the home page of the Ambari management page, and finishing the deployment of the Ambari component after confirming that all services run normally.
A system for deploying Ambari components based on a Docker container, comprising:
the sending module is used for sending a command to an Agent of the node by using the Server;
the building module is used for enabling the Agent to make a Docker File file and build a mirror image according to a Server sending command;
the acquisition module is used for enabling the Agent to pull the component mirror image from the Docker mirror image;
and the deployment module is used for enabling the Agent to start and deploy the components according to the manufactured Docker File.
Compared with the prior art, the invention at least comprises the following beneficial effects:
the invention relates to a method and a system for deploying Ambari components based on a Docker container, wherein a Server is used for sending a command to an Agent of a node, the Agent makes a Docker File file and constructs a mirror image according to the command sent by the Server, the Agent pulls the component mirror image from the Docker mirror image, the Agent starts and deploys the components according to the made Docker File, based on the existing Ambari component deployment mode, the steps of pulling configuration, writing into cache and the like are uniformly packaged in the Docker mirror image file, in the repeated deployment of a large number of cluster nodes, the deployment efficiency is improved, the resources consumed by IO are reduced, the stability and the version consistency are obviously improved, due to the perfection of containerization community in recent years and the maturity of the technology, the component deployment model of the original Ambari can be found to be too conservative, the Docker container is used for modular deployment, the efficiency can be improved, the version consistency of the components is ensured, and the later maintenance is convenient, the method completely replaces the original method for deploying the components through shell commands, the configuration of the components and the like are packaged and containerized through Docker, and the Agent can directly pull the mirror image through the nodes for installation, so that the efficiency and the stability are improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
FIG. 1 is a flow chart of a method for deploying Ambari components based on a Docker container according to the present invention;
FIG. 2 is a schematic flow chart of a method for deploying Ambari components based on a Docker container according to the present invention;
FIG. 3 is a block diagram of a system for deploying Ambari components based on a Docker container according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be 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.
As shown in fig. 1 to 3, the present invention provides a method and a system for deploying Ambari components based on a Docker container, comprising: the method comprises the following steps:
s1, sending a command to an Agent of the node by using the Server;
s2, the Agent makes Docker File files and constructs mirror images according to the Server sending command;
s3, the Agent pulls the component mirror image from the Docker mirror image;
and S4, the Agent starts and deploys the components according to the manufactured Docker File.
The working principle of the technical scheme is as follows: firstly, sending a command to an Agent of a node by using a Server, the Agent periodically sending a Heartpoint request, pulling the Server sending command to execute, and returning an execution result by the next Heartpoint request, wherein the Server sending command comprises a registration command, a report state command, a task executing command, a task canceling command, an Alert definition updating command and an Alert executing command, then the Agent makes and constructs a mirror image of a Docker File file according to the Server sending command, then the Agent pulls a component mirror image from the Docker mirror image, and finally the Agent starts and deploys the component according to the made Docker File file.
The beneficial effects of the above technical scheme are that: the method comprises the steps that a Server is used for sending commands to agents of nodes, the agents make Docker File files and construct mirror images according to the commands sent by the Server, and the agents pull component mirror images from Docker mirror images. The Agent starts and deploys the components according to the manufactured Docker File, the original method for deploying the components through shell commands is completely replaced, the configuration of the components and the like are packaged and containerized through Docker, the Agent can be installed through directly pulling a mirror image through the nodes, the efficiency and the stability are improved, the steps of pulling configuration, writing the configuration into a cache and the like are uniformly packaged in the Docker mirror image file based on the existing Ambari component deployment mode, the deployment efficiency is improved, the resources consumed by IO are reduced in repeated deployment of a large number of cluster nodes, and the stability and the version consistency are remarkably improved.
In one embodiment, the sending, by the Server, an install instruction to an Agent of the node includes:
s101, storing a Server sending command in an ActionQueue;
s102, all commands in the ActionQueue are sent to the Agent;
and S103, processing the command execution result according to the report of the Agent.
The working principle of the technical scheme is as follows: firstly, the Server can not directly push the command to be executed to the Agent, the Server sends the command to be stored in the ActionQueue, the Server sends the command to comprise a registration command, a report state command, a task execution command, a task cancellation command, an Alert definition updating command and an Alert execution command, secondly, all the commands in the ActionQueue are sent to the Agent, and finally, the command execution result is processed according to the report of the Agent, wherein the Agent sends a Heartbeat (cluster system component) request periodically, pulls the Server send command to execute, and returns the execution result through the next Heartbeat request.
The beneficial effects of the above technical scheme are that: the method has the advantages that the Server sending command is stored in the ActionQueue, the problem that the command needing to be executed cannot be directly pushed to the Agent is solved, all commands in the ActionQueue are issued to the Agent, and therefore the problem that the command can not be executed due to the fact that the command needing to be executed is directly pushed to the Agent is solved, execution efficiency is improved, the commands are grouped and the priority of tasks is set according to the report of the Agent and the execution result of the commands, execution is conducted according to the dependency relationship among the tasks and the priority of the tasks, the utilization rate of a Server CPU is improved, parallelization processing capacity is high, the tasks are processed according to the priority, and task scheduling efficiency is improved.
In one embodiment, the Agent makes a Docker File file and constructs an image according to a Server sending command, including:
s201, compiling a Docker File file through a format command;
s202, constructing an image of the file through the Docker build.
The working principle of the technical scheme is as follows: the method comprises the steps of firstly writing a Docker File file through a format command, wherein the Docker File file is written through the format command, the Docker File file is a text file used for constructing an image, the text content comprises a command and a description required for constructing the image, the format command comprises FROM used for specifying a basic image, MAINTAINER used for specifying information of a maintainer, ENV used for setting environment variables and arbitrarily referencing in the Docker File, RUN used for constructing the image, EXPOSE used for specifying an external interaction port, CMD used for specifying a command executed when a container is started, a plurality of containers only enable the last container, ENTRYPOINT used for specifying the command executed when the container is started, an additional operation executed, VOLUME used for hanging a data VOLUME, and finally constructing the image of the file through Docker build.
The beneficial effects of the above technical scheme are that: the Docker File file is written through the format command, so that the Docker File file format is wrongly written, the problem that the Docker File file cannot be executed due to the Docker File is avoided, the program rigidness is improved, the mirror image of the file is built through the Docker build, the building time is saved, the problem of dead processes in the building process is solved, sharing among users is facilitated, and the change of the mirror image can be known.
In one embodiment, the Agent is included before pulling the component image from the Docker image. The method comprises the steps of pulling a non-public mirror image in a Docker mirror image, directly using a command Docker logic, designating a mirror image warehouse server in the Docker, if the server does not provide legal https service, reconfiguring a configuration file in the Docker, adding a mirror image source in the configuration file in the Docker, accelerating the pulling of a component mirror image in the Docker mirror image, pulling the component mirror image from the Docker mirror image by the Agent, performing mirror image pulling by the Agent according to a Docker pull instruction, performing component mirror image starting and deployment by the Agent according to a manufactured Docker File file, executing the pulled component mirror image by the Docker run instruction, automatically performing component deployment according to the execution of the Docker run instruction by a program, starting and deploying the component according to the manufactured Docker File file, returning to a homepage, and finishing the deployment of Ambari components after confirming that all services normally operate.
The working principle of the technical scheme is as follows: before the mirror image is pulled, firstly knowing a non-public mirror image in a pulled Docker mirror image, directly using a command Docker logic, wherein a mirror image warehouse server is appointed in the Docker, if the server does not provide legal https service, a configuration file in the Docker is reconfigured, a mirror image source is added in the configuration file in the Docker, pulling of a component mirror image in the Docker mirror image is accelerated, secondly, the Agent pulls the component mirror image from the Docker mirror image and performs mirror image pulling by using a Docker pull instruction, the Agent performs component mirror image starting and deployment according to a manufactured Docker File file, executes the pulled component mirror image by using a Docker run instruction, automatically performs component deployment according to the execution of the Docker run instruction, and finally returns to a homepage of an Ambari management page after deployment, and after all services are confirmed to normally operate, Ambari component deployment is completed.
The beneficial effects of the above technical scheme are that: a Docker container deploys Ambari components, the problem that the existing Ambari component deployment mode has great resource waste is solved, the components need to be deployed each time to read configuration from a Server, then an instruction is sent to an installation script, and then a component installation package needing to be installed is pulled from a yum source.
The invention provides a system for deploying Ambari components based on a Docker container, which comprises:
the sending module is used for sending a command to an Agent of the node by using the Server;
the building module is used for enabling the Agent to make a Docker File file and build a mirror image according to a Server sending command;
the acquisition module is used for enabling the Agent to pull the component mirror image from the Docker mirror image;
and the deployment module is used for enabling the Agent to start and deploy the components according to the manufactured Docker File.
The working principle of the technical scheme is as follows: firstly, a sending module sends a command to an Agent of a node by using a Server, the Server sends the command including a registration command, a report state command, a task execution command, a task cancellation command, an Alert definition update command and an Alert execution command, then a construction module makes a Docker File file and constructs a mirror image according to the Server sending command through the Agent, then an acquisition module pulls a component mirror image from the Docker mirror image through the Agent, and finally a deployment module starts and deploys the component according to the made Docker File file through the Agent.
The beneficial effects of the above technical scheme are that: the method comprises the steps that a Server is used for sending commands to agents of nodes, the agents make Docker File files and construct mirror images according to the commands sent by the Server, and the agents pull component mirror images from Docker mirror images. The Agent starts and deploys the components according to the manufactured Docker File, the original method for deploying the components through shell commands is completely replaced, the configuration of the components and the like are packaged and containerized through Docker, the Agent can be installed through directly pulling a mirror image through the nodes, the efficiency and the stability are improved, the steps of pulling configuration, writing the configuration into a cache and the like are uniformly packaged in the Docker mirror image file based on the existing Ambari component deployment mode, the deployment efficiency is improved, the resources consumed by IO are reduced in repeated deployment of a large number of cluster nodes, and the stability and the version consistency are remarkably improved.
In one embodiment, the sending module comprises:
the storage command module is used for storing the Server sending command in the ActionQueue;
the transmission command module issues all commands in the ActionQueue to the Agent;
and the command execution module is used for processing a command execution result according to the report of the Agent.
The working principle of the technical scheme is as follows: firstly, the Server can not directly push the command to be executed to the Agent, the storage module stores the Server sending command in ActionQueue, the Server sending command comprises a registration command, a report state command, a task executing command, a task canceling command, an Alert definition updating command and an Alert executing command, secondly, the transmission module sends all the commands in ActionQueue to the Agent, and finally, the execution module processes the command execution result according to the report of the Agent.
The beneficial effects of the above technical scheme are that: the method has the advantages that the Server sending command is stored in the ActionQueue, the problem that the command needing to be executed cannot be directly pushed to the Agent is solved, all commands in the ActionQueue are issued to the Agent, and therefore the problem that the command can not be executed due to the fact that the command needing to be executed is directly pushed to the Agent is solved, execution efficiency is improved, the commands are grouped and the priority of tasks is set according to the report of the Agent and the execution result of the commands, execution is conducted according to the dependency relationship among the tasks and the priority of the tasks, the utilization rate of a Server CPU is improved, parallelization processing capacity is high, the tasks are processed according to the priority, and task scheduling efficiency is improved.
In one embodiment, the building module comprises:
the file compiling module is used for compiling Docker File files through format commands;
and acquiring a mirror image module, and constructing a mirror image of the file through the Docker build.
The working principle of the technical scheme is as follows: the method comprises the steps of firstly writing a Docker File file through a format command, wherein the Docker File file is written through the format command, the Docker File file is a text file used for constructing an image, the text content comprises a command and a description required for constructing the image, the format command comprises FROM used for specifying a basic image, MAINTAINER used for specifying information of a maintainer, ENV used for setting environment variables and arbitrarily referencing in the Docker File, RUN used for constructing the image, EXPOSE used for specifying an external interaction port, CMD used for specifying a command executed when a container is started, a plurality of containers only enable the last container, ENTRYPOINT used for specifying the command executed when the container is started, an additional operation executed, VOLUME used for hanging a data VOLUME, and finally constructing the image of the file through Docker build.
The beneficial effects of the above technical scheme are that: the Docker File file is written through the format command, so that the Docker File file format is wrongly written, the problem that the Docker File file cannot be executed due to the Docker File is avoided, the program rigidness is improved, the mirror image of the file is built through the Docker build, the building time is saved, the problem of dead processes in the building process is solved, sharing among users is facilitated, and the change of the mirror image can be known.
In one embodiment, the obtaining module further comprises a configuration module used for adding a mirror image source in a configuration file in a Docker, pulling of a component mirror image in the Docker mirror image is accelerated, the obtaining module pulls the component mirror image from the Docker mirror image according to the Agent and uses a Docker pull instruction to pull the mirror image, the deployment module starts and deploys the component mirror image according to the Agent and a manufactured Docker File file, the pulled component mirror image is executed by using a Docker run command, a program automatically deploys the component according to the execution of the Docker run command, and the deployment module further comprises a test module used for returning a homepage of an Ambari management page and confirming that Ambari components are deployed after all services run normally.
The working principle of the technical scheme is as follows: firstly, a configuration module is used for adding a mirror image source in a configuration file in a Docker to accelerate the pulling of a component mirror image in the Docker mirror image, secondly, an acquisition module pulls the component mirror image from the Docker mirror image according to the Agent and utilizes a Docker pull instruction to pull the mirror image, a deployment module starts and deploys the component mirror image according to the Agent and a manufactured Docker File file, a Docker run command is used for executing the pulled component mirror image, a program can automatically deploy the component according to the execution of the Docker run command, and finally a test module returns a homepage of an Ambari management page and finishes Ambari component deployment after all services are confirmed to run normally.
The beneficial effects of the above technical scheme are that: a Docker container deploys Ambari components, the problem that the existing Ambari component deployment mode has great resource waste is solved, the components need to be deployed each time to read configuration from a Server, then an instruction is sent to an installation script, and then a component installation package needing to be installed is pulled from a yum source.
While embodiments of the invention have been disclosed above, it is not limited to the applications set forth in the description and the embodiments, which are fully applicable in various fields of endeavor to which the invention pertains, and further modifications may readily be made by those skilled in the art, it being understood that the invention is not limited to the details shown and described herein without departing from the general concept defined by the appended claims and their equivalents.
Claims (10)
1. A method for deploying Ambari components based on a Docker container is characterized by comprising the following steps: the method comprises the following steps:
sending a command to an Agent of a node by using a Server;
the Agent makes a DockerFile file and constructs a mirror image according to a Server sending command;
the Agent pulls the component mirror image from the Docker mirror image;
and the Agent starts and deploys the components according to the manufactured DockerFile file.
2. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: the method for sending the installation instruction to the Agent of the node by using the Server comprises the following steps:
storing the Server transmission command in ActionQueue;
sending all commands in the ActionQueue to the Agent;
and processing the command execution result according to the report of the Agent.
3. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: the Server sends commands including one or more types of registration commands, report status commands, task execution commands, task cancellation commands, Alert definition updating commands and Alert command execution commands.
4. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: the Agent makes DockerFile files and constructs mirror images according to the Server sending command, and the method comprises the following steps:
compiling a Docker File file through a format command;
the mirror of the Docker File is built through Docker build.
5. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: the sending of the command to the Agent of the node by using the Server further comprises:
the Agent sends a Heartbeat request periodically, pulls the Server sending command to execute, and returns the execution result through the next Heartbeat request.
6. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: before the Agent pulls the component mirror image from the Docker mirror image, the method further comprises the following steps:
pulling a non-public mirror image in the Docker mirror image, and directly using a command Docker logic;
a mirror image warehouse server is appointed in the Docker, and if the server does not provide legal https service, the configuration file in the Docker is reconfigured;
adding a mirror image source in a configuration file in the Docker, and accelerating the pulling of the component mirror image in the Docker mirror image.
7. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: and the Agent pulls the component mirror image from the Docker mirror image and utilizes a Docker pull instruction to pull the mirror image.
8. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: the Agent starts and deploys component mirror images according to the manufactured DockerFile file, including
Executing the pulled component mirror image by using a Docker run command;
the Docker container will automatically deploy components upon execution of the Docker run command.
9. The method for deploying Ambari components based on a Docker vessel as claimed in claim 1, wherein: the Agent also comprises the following steps after component starting and deployment are carried out according to the manufactured DockerFile:
and returning to the home page of the Ambari management page, and finishing the deployment of the Ambari component after confirming that all services run normally.
10. A system for deploying Ambari components based on a Docker container is characterized in that: the system comprises:
the sending module is used for sending a command to an Agent of the node by using the Server;
the building module is used for enabling the Agent to make a Docker File file and build a mirror image according to a Server sending command;
the acquisition module is used for enabling the Agent to pull the component mirror image from the Docker mirror image;
and the deployment module is used for enabling the Agent to start and deploy the components according to the manufactured Docker File.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011091628.9A CN112269634B (en) | 2020-10-13 | 2020-10-13 | Method and system for deploying Ambari component based on Docker container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011091628.9A CN112269634B (en) | 2020-10-13 | 2020-10-13 | Method and system for deploying Ambari component based on Docker container |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112269634A true CN112269634A (en) | 2021-01-26 |
| CN112269634B CN112269634B (en) | 2022-12-09 |
Family
ID=74337997
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011091628.9A Active CN112269634B (en) | 2020-10-13 | 2020-10-13 | Method and system for deploying Ambari component based on Docker container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112269634B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590213A (en) * | 2021-06-24 | 2021-11-02 | 深圳开源互联网安全技术有限公司 | Component maintenance method, electronic device, and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106325975A (en) * | 2016-09-09 | 2017-01-11 | 浪潮软件股份有限公司 | Method for automatically deploying and managing big data clusters through Docker container |
| US20170085419A1 (en) * | 2015-09-18 | 2017-03-23 | Le Holdings (Beijing) Co., Ltd. | System and method for deploying an application |
| CN106790483A (en) * | 2016-12-13 | 2017-05-31 | 武汉邮电科学研究院 | Hadoop group systems and fast construction method based on container technique |
-
2020
- 2020-10-13 CN CN202011091628.9A patent/CN112269634B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170085419A1 (en) * | 2015-09-18 | 2017-03-23 | Le Holdings (Beijing) Co., Ltd. | System and method for deploying an application |
| CN106325975A (en) * | 2016-09-09 | 2017-01-11 | 浪潮软件股份有限公司 | Method for automatically deploying and managing big data clusters through Docker container |
| CN106790483A (en) * | 2016-12-13 | 2017-05-31 | 武汉邮电科学研究院 | Hadoop group systems and fast construction method based on container technique |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590213A (en) * | 2021-06-24 | 2021-11-02 | 深圳开源互联网安全技术有限公司 | Component maintenance method, electronic device, and storage medium |
| CN113590213B (en) * | 2021-06-24 | 2023-04-25 | 深圳开源互联网安全技术有限公司 | Component maintenance method, electronic device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112269634B (en) | 2022-12-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110851145B (en) | Container arrangement-based edge cloud installation and maintenance method and system | |
| CN110752947A (en) | K8s cluster deployment method and device, and deployment platform | |
| CN112329945A (en) | Model deployment and reasoning method and device | |
| CN104021078B (en) | Software supervision device and method | |
| CN108243012B (en) | Charging application processing system, method and device in OCS (online charging System) | |
| Nikolov et al. | Conceptualization and scalable execution of big data workflows using domain-specific languages and software containers | |
| Rademacher et al. | Specific model-driven microservice development with interlinked modeling languages | |
| CN112269634B (en) | Method and system for deploying Ambari component based on Docker container | |
| CN114756357A (en) | Non-blocking distributed planned task scheduling method based on JVM (Java virtual machine) | |
| CN111602115A (en) | Model driving method for application program development based on ontology | |
| CN111683005B (en) | Internet of things intelligent gateway equipment and construction method thereof | |
| CN111580804B (en) | Method and device for developing software project | |
| CN116301951B (en) | Micro-service application installation upgrading method and device based on kubernetes | |
| CN111522623B (en) | Modularized software multi-process running system | |
| US10268496B2 (en) | System and method for supporting object notation variables in a process defined by a process execution language for execution in a SOA middleware environment | |
| CN114443239A (en) | Method and device for filling container | |
| CN116192670A (en) | Environment deployment method, device, equipment and medium | |
| Gui et al. | A Hybrid real-time component model for reconfigurable embedded systems | |
| CN112685051A (en) | Method, device, platform and storage medium for automatically executing shell script | |
| CN113835827A (en) | Application deployment method and device based on container Docker and electronic equipment | |
| CN112463289A (en) | Method, system, equipment and medium for realizing application service based on virtual machine | |
| CN115604101B (en) | System management method and related equipment | |
| US10223142B2 (en) | System and method for supporting javascript activities in a process defined by a process execution language for execution in a SOA middleware environment | |
| CN113126961B (en) | Pipeline processing method, device and storage medium | |
| CN113312429B (en) | Intelligent contract management system, method, medium, and article in a blockchain |
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 |