CN109597655B

CN109597655B - Method and device for configuring application program

Info

Publication number: CN109597655B
Application number: CN201710900537.7A
Authority: CN
Inventors: 孙勐
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-28
Filing date: 2017-09-28
Publication date: 2020-11-10
Anticipated expiration: 2037-09-28
Also published as: CN109597655A

Abstract

The application discloses a method and a device for configuring an application program, and belongs to the technical field of virtualization. The method comprises the following steps: the method comprises the steps that a first configuration component obtains file information of a first application program deployed in a first container; the first configuration component acquires a basic file required by the first application program from a database positioned outside the first node according to the file information of the first application program; the first configuration component generates a configuration file of the first application program according to the basic file required by the first application program and the configuration parameters of the first application program. In the embodiment of the application, the configuration of the application program is realized by the configuration component outside the container, the basic file required by the configuration of the application program is acquired from the database outside the node by the configuration component, and the configuration of the application program is decoupled from the container for deploying the application program, so that the intrusive design of the container is avoided, and the subsequent change and upgrade of the application program in the container are simpler and easier.

Description

Method and device for configuring application program

Technical Field

The embodiment of the application relates to the technical field of virtualization, in particular to a method and a device for configuring an application program.

Background

Container (container) technology is a new type of virtualization technology. Referring to FIG. 1, a schematic diagram of a container deployment scenario is shown. The container 11 is deployed in a node (node)10, i.e. the node 10 is the host of the container 11. One or more containers 11 may be deployed in one node 10. The node 10 may be a virtual machine or a physical machine. Applications 12, such as Web services (Web Server) applications, database applications, etc., may be deployed in the container 11. In order to ensure that the application 12 operates normally in the container 11, it is necessary to perform relevant configuration operations on the application 12 before the application 12 starts to operate.

In a distributed application scenario (e.g., a microservice system), applications in different containers depend on each other, so that configuration parameters of the applications need to be synchronized between the different containers. The configuration parameters are parameters required for initially configuring the application program, such as an Internet Protocol (IP) address, a port number, component parameters, and the like. Referring to FIG. 2, a diagram illustrating configuration of applications in a container in a distributed application scenario is shown. The figure includes a configuration center 20, a first node 21 and a second node 22. The configuration center 20 is primarily used to provide access to configuration parameters. The first node 21 has a first container 211 deployed therein, the first container 211 has a first application 212 deployed therein, the second node 22 has a second container 221 deployed therein, the second container 221 has a second application 222 deployed therein, and the second application 222 depends on the configuration parameters of the first application 212, that is, the second application 222 is an application that needs to be synchronized with the configuration of the first application 212. As shown in fig. 2, configuration clients run in the respective containers (including the first container 211 and the second container 221), hereinafter, the configuration client running in the first container 211 is referred to as a first configuration client 213, and the configuration client running in the second container 221 is referred to as a second configuration client 223. The configuration client is usually implemented by a lightweight script and is mainly responsible for pushing, subscribing and executing configuration parameters of the application program.

The first container 211 calls an initialization script in a loading stage, reads a start parameter including a configuration parameter of the first application 212 from an environment variable (environment variables), and calls the configuration script of the first application 212. The first configuration client 213 executes the configuration script of the first application 212, writes the configuration parameters of the first application 212 into the configuration template of the first application 212, generates the configuration file of the first application 212, and then stores the configuration file of the first application 212 into the designated directory to complete the configuration process of the first application 212. Furthermore, the first configuration client 213 also sends the configuration parameters of the first application 212 to the configuration center 20 for other applications depending on the first application 212 to obtain the configuration parameters of the first application 212 from the configuration center 20.

The second container 221 calls an initialization script in the loading phase, from which the configuration script of the second application 222 is called. The second configuration client 223 executes the configuration script of the second application 222, writes the configuration parameters of the second application 222 into the configuration template of the second application 222, generates the configuration file of the second application 222, and then stores the configuration file of the second application 222 into the designated directory to complete the configuration process of the second application 222. The configuration parameters of the second application 222 are acquired from the configuration center 20 by the second configuration client 223 after receiving the configuration change notification sent by the configuration center 20, where the configuration change notification is sent by the configuration center 20 to the configuration client corresponding to another application (such as the second application 222) that needs to perform configuration synchronization with the first application 212 after receiving the configuration parameters of the first application 212 sent by the first configuration client 213.

In the prior art, a configuration client in a container executes a configuration process of an application program, and a configuration script and a configuration template required by the configuration client when configuring the application program are also stored in the container in advance. Because the configuration scripts, the configuration templates and the related configuration processes required by different applications are different, the corresponding configuration clients, the configuration scripts and the configuration templates need to be customized and developed for different containers and are pre-implanted into the containers. The customized development process belongs to an invasive design of the container, and is not beneficial to subsequent change and upgrade of the application program in the container.

Disclosure of Invention

The embodiment of the application provides a method and a device for configuring an application program, and the method and the device can be used for solving the problem that the configuration scheme for the application program in a container provided by the prior art is not beneficial to subsequent change and upgrade of the application program in the container due to the fact that different containers need to be subjected to customized development.

In one aspect, an embodiment of the present application provides a method for configuring an application, which is applied to a first node, where the first node includes a first configuration component and a first container; the method comprises the following steps: the method comprises the steps that a first configuration component obtains file information of a first application program deployed in a first container, wherein the file information of the first application program is used for indicating a basic file required by configuration of the first application program; the first configuration component acquires a basic file required by the first application program from a database positioned outside the first node according to the file information of the first application program; the first configuration component generates a configuration file of the first application program according to the basic file required by the first application program and the configuration parameters of the first application program, wherein the configuration parameters of the first application program are acquired from the environment variables of the first container.

According to the scheme provided by the embodiment of the application, the application program is configured through the configuration component outside the container, the basic file required by the configuration of the application program is acquired from the database outside the node through the configuration component, and the configuration of the application program is decoupled from the container for deploying the application program through the mode, so that the intrusive design of the container is avoided, and the subsequent change and upgrade of the application program in the container are simpler and easier.

In one possible design, the file information of the first application includes an identifier of a metadata configuration file of the first application, and the metadata configuration file of the first application includes an identifier of a basic file required by the first application; the first configuration component acquires a basic file required by the first application program from a database located outside the first node according to the file information of the first application program, and the basic file comprises: the first configuration component acquires the metadata configuration file of the first application program from the database according to the identifier of the metadata configuration file of the first application program; the first configuration component analyzes the metadata configuration file of the first application program and acquires an identifier of a basic file required by the first application program; and the first configuration component acquires the basic file required by the first application program from the database according to the identification of the basic file required by the first application program.

According to the scheme provided by the embodiment of the application, the basic files required by the configuration of the application program are obtained from the external database of the node by the configuration component, and the configuration of the application program and the container for deploying the application program are decoupled by the mode, so that the intrusive design of the container is avoided, and the subsequent change and upgrade of the application program in the container are simpler and easier.

In one possible design, the base file includes a configuration script and a configuration template; the metadata configuration file of the first application program comprises a configuration script sequence and a configuration template list; the configuration script sequence comprises an identifier of a configuration script required by the first application program, and the arrangement sequence of the identifier of the configuration script required by the first application program in the configuration script sequence is used for indicating the execution sequence of the configuration script required by the first application program; the configuration template list comprises an identifier of a configuration template required by the first application program and a file storage path corresponding to each configuration template, wherein the file storage path is used for indicating a storage path of a configuration file generated according to the configuration template.

In one possible design, after the first configuration component generates the configuration file of the first application according to the basic file required by the first application and the configuration parameters of the first application, the method further includes: the first configuration component sends the configuration parameters of the first application program to a configuration center located outside the first node; the first configuration component sends a configuration change notification to a second configuration component in the second node, the configuration change notification being used for notifying the second configuration component to acquire the configuration parameters of the first application from the configuration center.

In one possible design, the first configuration component sends the configuration change notification to a second configuration component in the second node, including: the first configuration component sends a configuration change notification to the second configuration component over the short connection. Specifically, a first configuration component sends a connection establishment request to a second configuration component, wherein the connection establishment request is used for requesting to establish communication connection with the second configuration component; after the communication connection is successfully established, the first configuration component sends a configuration change notification to the second configuration component; after the configuration change notification is sent successfully, the first configuration component disconnects the communication connection.

According to the scheme provided by the embodiment of the application, the receiving and sending of the configuration parameters are realized between the configuration component and the configuration center in a short connection mode, and the occupation of connection resources of the configuration center is avoided.

In one possible design, after the first configuration component generates the configuration file of the first application according to the basic file required by the first application and the configuration parameters of the first application, the method further includes: when a third application deployed in a third container of the first node is an application that needs to be configured and synchronized with the first application, the first configuration component generates a configuration file of the third application according to a basic file needed by the third application and configuration parameters of the third application, wherein the configuration parameters of the third application include the configuration parameters of the first application.

According to the scheme provided by the embodiment of the application, when the two containers in the same node are both deployed with the application program and the application program of one container needs to depend on the application program of the other container when being configured, the configuration parameters of the application program of the other container do not need to be acquired from the configuration center, so that the efficiency of configuring the application program is improved.

In another aspect, an embodiment of the present application provides a method for configuring an application, where the method is applied to a second node, where the second node includes a second configuration component and a second container; the method comprises the following steps: the second configuration component acquires file information of a second application program deployed in a second container, wherein the file information of the second application program is used for indicating a basic file required by the second application program; the second configuration component acquires a basic file required by the second application program from a database positioned outside the second node according to the file information of the second application program; after a configuration center located outside a second node receives the configuration parameters of the first application program, a second configuration component receives the configuration parameters of the first application program sent by the configuration center, and the first application program is an application program deployed in a container of the first node; and the second configuration component generates a configuration file of the second application program according to the basic file required by the second application program and the configuration parameters of the second application program, wherein the configuration parameters of the second application program comprise the configuration parameters of the first application program.

In one possible design, the file information of the second application includes an identifier of a metadata configuration file of the second application, and the metadata configuration file of the second application includes an identifier of a basic file required by the second application; the second configuration component acquires a basic file required by the second application program from a database located outside the second node according to the file information of the second application program, and the basic file comprises: the second configuration component acquires the metadata configuration file of the second application program from the database according to the identifier of the metadata configuration file of the second application program; the second configuration component analyzes the metadata configuration file of the second application program and acquires the identification of the basic file required by the second application program; and the second configuration component acquires the basic file required by the second application program from the database according to the identification of the basic file required by the second application program.

In a possible design, before the second configuration component receives the configuration parameters of the first application sent by the configuration center, the method further includes: the second configuration component receives a configuration change notification sent by the first configuration component, and the configuration change notification is used for notifying the second configuration component to acquire the configuration parameters of the first application program from the configuration center; and the second configuration component sends an information acquisition request to the configuration center, wherein the information acquisition request is used for requesting to acquire the configuration parameters of the first application program.

In one possible design, the second configuration component receives the notification of the configuration change sent by the first configuration component, and the notification includes: the second configuration component receives a configuration change notification sent by the first configuration component over the short connection. Specifically, the second configuration component receives a connection establishment request sent by the first configuration component; the second configuration component establishes communication connection with the first configuration component according to the connection establishment request; the second configuration component receives the configuration change notification sent by the first configuration component, wherein the communication connection is disconnected after the second configuration component successfully receives the configuration change notification.

In still another aspect, an embodiment of the present invention provides an apparatus having a function of implementing the first node side in the above method example. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

In one possible design, the apparatus includes a processor and a communication interface, and the processor is configured to support the apparatus to perform corresponding functions on the first node side in the above method. The communication interface is used for supporting communication between the device and other equipment. Further, the apparatus may also include a memory for coupling with the processor that retains program instructions and data necessary for the apparatus.

In still another aspect, an embodiment of the present invention provides an apparatus having a function of implementing the second node side in the above method example. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

In one possible design, the structure of the apparatus includes a processor and a communication interface, and the processor is configured to support the apparatus to perform corresponding functions on the second node side in the above method. The communication interface is used for supporting communication between the device and other equipment. Further, the apparatus may also include a memory for coupling with the processor that retains program instructions and data necessary for the apparatus.

In still another aspect, the present application provides a computer storage medium for storing computer software instructions for the apparatus, which includes a program for executing the first node side designed in the above aspect.

In a further aspect, the present application provides a computer storage medium for storing computer software instructions for the apparatus, which includes a program for executing the second node side designed in the above aspect.

In yet another aspect, the present application provides a computer program product, which when executed, is configured to perform the method of the first node side according to the above aspect.

In yet another aspect, the present application provides a computer program product, when executed, for performing the method on the second node side according to the above aspect.

Compared with the prior art, in the embodiment of the application, the application program is configured by the configuration component outside the container, the basic file required by the configuration of the application program is acquired from the database outside the node by the configuration component, and the configuration of the application program is decoupled from the container for deploying the application program by the method, so that the intrusive design of the container is avoided, and the subsequent change and upgrade of the application program in the container are simpler and easier.

Drawings

FIG. 1 shows a schematic diagram of a container deployed in a node;

FIG. 2 is a diagram of prior art configuration of an application provided by the prior art;

FIG. 3A is a schematic diagram of an application scenario provided by an embodiment of the present application;

FIG. 3B is a schematic diagram of an application scenario provided by another embodiment of the present application;

FIG. 4A is a flow chart of a method for configuring an application provided by one embodiment of the present application;

FIG. 4B is a schematic diagram of a macro replacement provided by one embodiment of the present application;

FIG. 4C is a diagram of a metadata configuration file provided by one embodiment of the present application;

FIG. 5 is a flow chart of a method for configuring an application provided by another embodiment of the present application;

FIG. 6 is a flow chart of a method for configuring an application provided by another embodiment of the present application;

FIG. 7 is a flow chart of a method for configuring an application provided by another embodiment of the present application;

FIG. 8 is a block diagram of an apparatus for configuring an application provided by one embodiment of the present application;

FIG. 9 is a block diagram of an apparatus for configuring an application provided by another embodiment of the present application;

FIG. 10A is a schematic block diagram of an electronic device provided by one embodiment of the present application;

fig. 10B is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The system architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it can be known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the system architecture and the appearance of a new service scenario.

With combined reference to FIG. 3A, a schematic diagram of an implementation environment provided by one embodiment of the present application is shown. The implementation environment includes: a first node 30, a database 50 and a configuration center 60.

The first node 30 comprises a first configuration component 31 and n containers 32, n being a positive integer, i.e. the first node 30 may comprise one container 32 or may comprise at least two containers 32. In the present embodiment, the first container may be any one of the n containers 32 described above, and the first container is denoted by reference numeral 33. The first configuration component 31 is used to provide functionality for configuring applications deployed in respective containers 32 in the first node 30. Applications are deployed in each container 32, and one application or multiple applications may be deployed in each container 32. In the embodiment of the present application, only one application is deployed in each container 32 as an example. For example, a first application is deployed in the first container 33. The first node 30 may be a virtual machine or a physical machine (e.g., a server).

The database 50 is used to store metadata configuration files for the application, as well as the base files required by the application. The metadata configuration file is used to indicate the basic files required by the application, for example, the metadata configuration file includes the identification of the basic files required by the application. The basic file refers to a file required for configuring the application program, and for example, the basic file includes a configuration script and a configuration template. The configuration script is used for executing configuration actions, such as writing configuration parameters of the application program into a configuration template to form a configuration file. The configuration template is a template file of a configuration file of an application program, a mapping relation between the name of each configuration parameter and a parameter value is defined in the configuration template, and the configuration file can be simply and efficiently obtained by combining the configuration template with a macro replacement mode. The configuration center 60 is used to provide access to the configuration parameters of the application. Database 50 and configuration center 60 may be deployed in the same physical device (e.g., a server) or in different physical devices.

In practical applications, the implementation environment may include a plurality of nodes, and the first node 30 may be any one of the plurality of nodes. The database 50 is deployed outside each node, independent of each other node. Configuration center 60 is also deployed outside of and independent of each node.

Optionally, referring to fig. 3B in combination, the implementation environment further includes a second node 40.

The second node 40 comprises a second configuration component 41 and m containers 42, m being a positive integer, i.e. the second node 40 may comprise one container 42 or may comprise at least two containers 42. In the present embodiment, the second container may be any one of the m containers 42 described above, and is denoted by reference numeral 43. The second configuration component 41 is used to provide functionality for configuring applications deployed in respective containers 42 in the second node 40. Applications are deployed in each container 42, and one application or multiple applications may be deployed in each container 42. In the embodiment of the present application, only one application is deployed in each container 42 as an example. For example, a second application is deployed in the second container 43. The second node 40 may be a virtual machine or a physical machine (e.g., a server).

The first node 30 and the second node 40 may be two separate physical machines. Optionally, when the first node 30 and the second node 40 are both virtual machines, the first node 30 and the second node 40 may be two virtual machines deployed on the same physical machine, or two virtual machines deployed on two different physical machines.

When the first application and the second application are two instances of a certain distributed application, in this embodiment of the application, it is assumed that the second application needs to depend on the configuration of the first application, that is, the second application is an application that needs to be configured and synchronized with the first application. The configuration synchronization is to execute a related configuration operation on the second application program according to the configuration parameters of the first application program before the second application program is started to run.

In the embodiment of the application, the configuration of the application program is realized by the configuration component outside the container, the basic file required by the configuration of the application program is acquired from the database outside the node by the configuration component, and the configuration of the application program is decoupled from the container for deploying the application program by the method, so that the intrusive design of the container is avoided, and the subsequent change and upgrade of the application program in the container are simpler and easier.

The embodiments of the present application will be described in further detail below based on the common aspects related to the embodiments of the present application described above.

Referring to fig. 4A, a flowchart of a method for configuring an application according to an embodiment of the present application is shown. The method may be applied in the first node 30 in the implementation environment shown in fig. 3A or fig. 3B. The method may include several steps as follows.

In step 401, the first configuration component 31 obtains file information of the first application deployed in the first container 33.

The first configuration component 31 is disposed outside of the respective containers 32 in the first node 30. The first configuration component 31 is used to complete the configuration of applications deployed in respective containers 32 in the first node 30. Alternatively, the first configuration component 31 described above may be referred to as "config scheduler 1". The first container 33 has a first application program disposed therein. Before the first application program is started and operated normally, the configuration of the first application program needs to be completed.

The file information of the first application program is used for indicating a basic file required for configuring the first application program. The basic file required by the first application refers to a file required for configuring the first application, and for example, the basic file includes a configuration script and a configuration template.

In one example, the file information of the first application includes an identification of a metadata profile of the first application. The identity of the metadata profile is used to uniquely indicate the metadata profile, with different metadata profiles having different identities. The metadata configuration file of the first application is used for indicating the basic files required by the first application, for example, the metadata configuration file of the first application includes the identification of the basic files required by the first application.

In other examples, the file information of the first application includes an identification of the base files needed by the first application. Alternatively, the file information of the first application includes an identifier of the first application, the identifier of the first application is used for uniquely indicating the first application, and different applications have different identifiers. Optionally, the file information of the first application further comprises an identification of the first container 33 and an identification of the first node.

When the first node 30 deploys the first application to the first container 33, the file information (e.g., the identifier of the metadata configuration file) of the first application is configured in the environment variable of the first container 33. The environment variables of the first container 33 are used to specify information required for the first container 33 to start the runtime. For example, the first node 30 executes a command, docker run-e profile _ id ═ xxx, which indicates that the identifier "xxx" of the metadata configuration file is configured into the environment variables of the first container 33 when the first container 33 is started.

When the first container 33 is started, the first container 33 sends file information (such as an identification of a metadata configuration file) of the first application to the first configuration component 31. Optionally, an initialization Script (Init Script) is stored in the first container 33, the initialization Script is loaded by the first container 33 when starting, and the file information of the first application is sent to the first configuration component 31 by the initialization Script. In a possible implementation manner, the first container 33 sends the file information of the first application to the first configuration component 31 in a bridge connection manner, that is, the first container 33 calls an interface provided by the first configuration component 31, and sends the file information of the first application to the first configuration component 31 through the interface. In another possible implementation, the file information of the first application is stored in a Data Volume (Data Volume), and after the first container 33 is started, a start notification is sent to the first configuration component 31 so that the first configuration component 31 reads the file information of the first application from the Data Volume.

In step 402, the first configuration component 31 obtains the basic file required by the first application program from the database 50 located outside the first node 30 according to the file information of the first application program.

As already described above, the database 50 is used to store metadata configuration files for applications and the base files required by the applications. Alternatively, the above database 50 may be referred to as "reproducibility".

Optionally, when the file information of the first application includes an identifier of a metadata configuration file of the first application, the step 402 includes the following sub-steps:

step 402a, the first configuration component 31 obtains the metadata configuration file of the first application program from the database 50 according to the identifier of the metadata configuration file of the first application program;

optionally, the first configuration component 31 sends a first obtaining request to the physical device deployed with the database 50, where the first obtaining request is used to request to obtain the metadata configuration file of the first application, and the first obtaining request carries an identifier of the metadata configuration file of the first application, so that after the physical device deployed with the database 50 receives the first obtaining request, the first configuration component 31 obtains the metadata configuration file of the first application from the database 50 according to the identifier of the metadata configuration file of the first application, and sends the metadata configuration file of the first application to the first configuration component 31.

Step 402b, the first configuration component 31 parses the metadata configuration file of the first application program, and obtains the identifier of the basic file required by the first application program;

the metadata configuration file of the first application includes an identification of the base files needed by the first application. The identification of the basic file is used for uniquely indicating the basic file, the identification of the basic file can be the name of the basic file, and different basic files have different identifications. When the basic file comprises the configuration script and the configuration template, the metadata configuration file of the first application program comprises a configuration script sequence and a configuration template list corresponding to the first application program. Optionally, the first configuration component 31 reads an identifier of a configuration script required by the first application from a configuration script sequence corresponding to the first application, and reads an identifier of a configuration template required by the first application from a configuration template list corresponding to the first application.

The configuration script sequence of the first application program comprises the identification of the configuration script required by the first application program. And the sequence of the identifiers of the configuration scripts required by the first application in the configuration script sequence is used for indicating the execution sequence of the configuration scripts required by the first application. The identity of the configuration script is used to uniquely indicate the configuration script, with different configuration scripts having different identities. The configuration script of the first application is used for executing a configuration action for the first application, for example, writing the configuration parameters of the first application into the configuration template of the first application to obtain a configuration file of the first application.

The configuration template list corresponding to the first application program comprises the identification of the configuration template required by the first application program and the file storage path corresponding to each configuration template. For any configuration template, the file storage path corresponding to the configuration template is used to indicate the storage path of the configuration file generated according to the configuration template. The identity of the configuration template is used to uniquely identify the configuration template, with different configuration templates having different identities. The configuration template required by the first application is used for generating a configuration file of the first application. The configuration template of the first application program defines the mapping relation between the name and the parameter value of each configuration parameter of the first application program, and a configuration file corresponding to the first application program is generated through macro replacement when the first application program is subsequently configured. Reference is now made in combination to FIG. 4B, which is a block diagram illustrating macro replacement provided by an embodiment of the present application. X, Y and Z configuration parameters are defined in the configuration template, wherein the configuration parameter named X and the configuration parameter named Y are to be configured, the parameter value of the configuration parameter named Z is 3, after the parameter value 1 of the configuration parameter named X and the parameter value 2 of the configuration parameter named Y are obtained, the parameter values of the configuration parameters named X and Y are respectively written into the configuration template by adopting a macro replacement mode, and the configuration file is obtained.

With combined reference to FIG. 4C, a diagram of a metadata configuration file is shown in accordance with one embodiment of the present application. The identity of the metadata configuration file (denoted Profile id) is xxx. Optionally, the identification of the metadata profile is identified using a 64-bit (bit) string. In addition to the Profile id, the metadata configuration file also records a configuration Script sequence (denoted as Script sequence) and a configuration template list (denoted as conffiles). The configuration script sequence includes an identifier (such as a name) of the configuration script, such as script1 and script2 in the figure. The configuration template list includes identifiers (such as names) of configuration templates, such as conf1 and conf2 in the figure, and file storage paths corresponding to the respective configuration templates. Assuming that the metadata configuration file of the first application is shown in fig. 4C, when configuring the first application, it is necessary to execute the script1 first and then execute the script 2; the file storage path of the configuration file corresponding to conf1 is/ect/conf/, and the file storage path of the configuration file corresponding to conf2 is/var/lib/.

In step 402c, the first configuration component 31 obtains the basic file required by the first application program from the database 50 according to the identifier of the basic file required by the first application program.

When the identification of the base file required by the first application includes the identification of the configuration script required by the first application and the identification of the configuration template required by the first application, the first configuration component 31 obtains the configuration script and the configuration template required by the first application from the database 50.

Optionally, the first configuration component 31 sends a second obtaining request to the physical device deployed with the database 50, where the second obtaining request is used to request to obtain a basic file required by the first application, and the second obtaining request carries an identifier of the basic file required by the first application, so that after receiving the second obtaining request, the physical device deployed with the database 50 obtains the basic file required by the first application from the database 50 according to the identifier of the basic file required by the first application, and then sends the basic file required by the first application to the first configuration component 31.

In other possible examples, if the file information of the first application includes an identifier of a basic file required by the first application, the first configuration component 31 does not need to perform step 402a and step 402b, but directly sends the second acquisition request to the physical device on which the database 50 is deployed, so that after receiving the second acquisition request, the physical device on which the database 50 is deployed acquires the basic file required by the first application from the database 50 according to the identifier of the basic file required by the first application, and then sends the basic file required by the first application to the first configuration component 31.

In other possible examples, if the file information of the first application includes an identifier of the first application, the physical device on which the database 50 is deployed stores a correspondence between the identifier of the application and an identifier of the metadata configuration file. The first obtaining request sent by the first configuration component 31 to the physical device deployed with the database 50 carries an identifier of the first application program, the physical device deployed with the database 50 searches the correspondence to obtain an identifier of the metadata configuration file corresponding to the identifier of the first application program (i.e. the identifier of the metadata configuration file of the first application program), and then obtains the metadata configuration file of the first application program from the database 50 according to the identifier of the metadata configuration file of the first application program, and sends the metadata configuration file of the first application program to the first configuration component 31. After the first configuration component 31 obtains the metadata configuration file of the first application, the basic file required by the first application is obtained through the above steps 402b and 402 c.

In step 403, the first configuration component 31 generates a configuration file of the first application according to the basic file required by the first application and the configuration parameters of the first application, where the configuration parameters of the first application are obtained from the environment variables of the first container 33.

After obtaining the configuration parameters of the first application, the configuration scripts of the first application, and the configuration templates, the first configuration component 31 sequentially executes the configuration scripts of the first application according to the execution sequence of the configuration scripts defined in the metadata configuration file of the first application, and writes the configuration parameters into the configuration templates of the first application in a macro replacement manner by using the configuration scripts to obtain the configuration file of the first application. Optionally, after generating the configuration file of the first application, the first configuration component 31 stores the configuration file into a corresponding storage path according to the file storage path of each configuration file indicated by the metadata configuration file, so as to complete configuration of the first application.

In addition, in the present embodiment, since the first application is not dependent on the configuration of other applications, the configuration parameters of the first application are acquired from the environment variables of the first container 33. For example, after the initialization script is started and loaded, the first container 33 reads the configuration parameters of the first application from the environment variables by the initialization script, and then sends the configuration parameters of the first application to the first configuration component 31. For the manner of sending the configuration parameters to the first configuration component 31 by the initialization script, reference may be made to the manner of sending the file information to the first configuration component 31 by the initialization script described above, and details are not described here again.

Referring to fig. 5, a flowchart of a method for configuring an application according to another embodiment of the present application is shown. The method may be applied in the second node 40 in the implementation environment shown in fig. 3B. The method may include several steps as follows.

In step 501, the second configuration component 41 obtains file information of the second application deployed in the second container 43.

The second configuration components 41 are disposed outside of respective containers 42 in the second node 40. The second configuration component 41 is used to complete the configuration of the applications deployed in the respective containers 42 in the second node 40. Alternatively, the second configuration component 41 described above may be referred to as "config scheduler 2". A second application is deployed in the second container 43. Before the second application program is started and operated normally, the configuration of the second application program needs to be completed.

The file information of the second application is used to indicate a basic file required for configuring the second application. The basic file required by the second application refers to a file required for configuring the second application, and for example, the basic file includes a configuration script and a configuration template.

In one example, the file information of the second application includes an identification of a metadata configuration file of the second application. The identity of the metadata profile is used to uniquely indicate the metadata profile, with different metadata profiles having different identities. The metadata configuration file of the second application is used to specify the base files required by the second application, for example, the metadata configuration file of the second application includes an identification of the base files required by the second application.

In other examples, the file information of the second application includes an identification of the base files needed by the second application. Alternatively, the file information of the second application includes an identifier of the second application, the identifier of the second application is used for uniquely indicating the second application, and different applications have different identifiers. Optionally, the file information of the second application further includes an identification of the second container 43 and an identification of the second node.

When the second node 40 deploys the second application to the second container 43, the file information (e.g., the identifier of the metadata configuration file) of the second application is configured in the environment variable of the second container 43. The environment variable of the second container 43 is used to specify information required for the second container 43 to start the runtime. For example, the second node 40 executes a command that the docker run-e profile _ id is yyy, which indicates that the identifier "yyy" of the metadata configuration file is configured into the environment variable of the second container 43 when the second container 43 is started.

When the second container 43 is started, the second container 43 sends file information (such as an identification of the metadata configuration file) of the second application to the second configuration component 41. Optionally, the second container 43 stores an initialization Script (Init Script), the second container 43 loads the initialization Script when starting, and the initialization Script sends file information of the second application program to the second configuration component 41. In a possible implementation manner, the second container 43 sends the file information of the second application to the second configuration component 41 in a bridge connection manner, that is, the second container 43 calls an interface provided by the second configuration component 41, and sends the file information of the second application to the second configuration component 41 through the interface. In another possible implementation manner, the file information of the second application is stored in the data volume, and after the second container 43 is started, a start notification is sent to the second configuration component 41 so that the second configuration component 41 reads the file information of the second application from the data volume.

In step 502, the second configuration component 41 obtains the basic file required by the second application program from the database 50 located outside the second node 40 according to the file information of the second application program.

Optionally, when the file information of the second application includes an identification of a metadata configuration file of the second application, the step 502 includes the following sub-steps:

step 502a, the second configuration component 41 obtains the metadata configuration file of the second application program from the database 50 according to the identifier of the metadata configuration file of the second application program;

optionally, the second configuration component 41 sends a third obtaining request to the physical device deployed with the database 50, where the third obtaining request is used to request to obtain the metadata configuration file of the second application, and the third obtaining request carries an identifier of the metadata file of the second application, so that after the physical device deployed with the database 50 receives the third obtaining request, the metadata configuration file of the second application is obtained from the database 50 according to the identifier of the metadata configuration file of the second application, and the metadata configuration file of the second application is sent to the second configuration component 41.

Step 502b, the second configuration component 41 parses the metadata configuration file of the second application program, and obtains the identifier of the basic file required by the second application program;

the metadata configuration file for the second application includes an identification of the base files needed by the second application. The identification of the basic file is used for uniquely indicating the basic file, the identification of the basic file can be the name of the basic file, and different basic files have different identifications. And when the basic file comprises the configuration script and the configuration template, the metadata configuration file of the second application program comprises a configuration script sequence and a configuration template list corresponding to the second application program. Optionally, the second configuration component 41 reads an identifier of a configuration script required by the second application from the configuration script sequence corresponding to the second application, and reads an identifier of a configuration template required by the second application from the configuration template list corresponding to the second application.

The configuration script sequence of the second application program comprises the identification of the configuration script required by the second application program. And the arrangement sequence of the identifiers of the configuration scripts required by the second application program in the configuration script sequence is used for indicating the execution sequence of the configuration scripts required by the second application program. The identity of the configuration script is used to uniquely indicate the configuration script, with different configuration scripts having different identities. The configuration script of the second application is used for executing a configuration action for the second application, such as writing configuration parameters of the second application into a configuration template of the second application to obtain a configuration file of the second application.

The configuration template list corresponding to the second application program comprises the identification of the configuration template required by the second application program and the file storage path corresponding to each configuration template. For any configuration template, the file storage path corresponding to the configuration template is used to indicate the storage path of the configuration file generated according to the configuration template. The configuration template identifier is used to uniquely identify the configuration template, with different configuration templates having different identifiers. The configuration template required by the second application is used to generate a configuration file for the second application. The configuration template of the second application program defines the mapping relation between the name and the parameter value of each configuration parameter of the second application program, and a configuration file corresponding to the second application program is generated through macro replacement when the second application program is subsequently configured. The process for macro replacement can be seen in the example shown in FIG. 4B.

In step 502c, the second configuration component 41 obtains the basic file required by the second application program from the database 50 according to the identifier of the basic file required by the second application program.

When the identification of the base file required by the second application includes the identification of the configuration script required by the second application and the identification of the configuration template required by the second application, the second configuration component 41 obtains the configuration script and the configuration template required by the second application from the database 50.

Optionally, the second configuration component 41 sends a fourth obtaining request to the physical device deployed with the database 50, where the fourth obtaining request is used to request to obtain a basic file required by the second application, and the fourth obtaining request carries an identifier of the basic file required by the second application, so that after receiving the fourth obtaining request, the physical device deployed with the database 50 obtains the basic file required by the second application from the database 50 according to the identifier of the basic file required by the second application, and then sends the basic file required by the second application to the second configuration component 41.

In other possible examples, if the file information of the second application includes an identifier of a basic file required by the second application, the second configuration component 41 does not need to execute step 502a and step 502b, but directly sends the fourth acquisition request to the physical device on which the database 50 is deployed, so that the physical device on which the database 50 is deployed obtains the basic file required by the second application from the database 50 according to the identifier of the basic file required by the second application after receiving the fourth acquisition request, and then sends the basic file required by the second application to the second configuration component 41.

In other possible examples, if the file information of the second application includes the identifier of the second application, the physical device on which the database 50 is deployed stores the correspondence between the identifier of the application and the identifier of the metadata configuration file. The third obtaining request sent by the second configuration component 41 to the physical device deployed with the database 50 carries the identifier of the second application program, the physical device deployed with the database 50 searches the correspondence to obtain the identifier of the metadata configuration file corresponding to the identifier of the second application program (i.e. the identifier of the metadata configuration file of the second application program), then obtains the metadata configuration file of the second application program from the database 50 according to the identifier of the metadata configuration file of the second application program, and sends the metadata configuration file of the second application program to the second configuration component 41. After the second configuration component 41 obtains the metadata configuration file of the second application, the basic file required by the second application is obtained through the above steps 502b and 502 c.

After the configuration center 60 located outside the second node 40 receives the configuration parameters of the first application, the second configuration component 41 receives the configuration parameters of the first application sent by the configuration center 60, step 503.

The configuration parameters of the first application include a correspondence between the name of the configuration parameter and the parameter value. For example, a certain configuration parameter of the first application is "IP ═ 192.18.56.00", where "IP" is the name of the configuration parameter and "192.18.56.00" is the parameter value of the configuration parameter. The first application is an application deployed in a container of the first node 30 (i.e., the first container 33 introduced above).

In a possible implementation manner, after the second container 43 is started, the second configuration component 41 sends a subscription request to the configuration center 60 located outside the second node 40, where the subscription request carries a name (i.e., key) of the configuration parameter required by the second application. Wherein the configuration parameters required by the second application are read from the environment variables by the initialization script loaded after the second container 43 is started. After receiving the configuration parameters of the first application, the subsequent configuration center 60 sends the configuration parameters of the first application to the second configuration component 41 if the configuration parameters of the first application include the configuration parameters required by the second application, and the configuration parameters may be sent in the form of key-value pairs.

In addition, another possible implementation manner for the second configuration component 41 to acquire the configuration parameters of the first application program will be described in the following embodiments.

In the embodiment of the present application, the execution timing of step 503 is not limited, and step 503 may be executed before step 501, after step 501, or simultaneously with step 501.

In step 504, the second configuration component 41 generates a configuration file of the second application according to the basic file required by the second application and the configuration parameters of the second application, where the configuration parameters of the second application include the configuration parameters of the first application.

After obtaining the configuration parameters of the second application program, the configuration script of the second application program, and the configuration template, the second configuration component 41 sequentially executes each configuration script of the second application program according to the execution sequence of the configuration scripts defined in the metadata configuration file of the second application program, and writes the configuration parameters into the configuration template of the second application program in a macro replacement manner by using the configuration scripts, so as to obtain the configuration file of the second application program. Optionally, after generating the configuration file of the second application, the second configuration component 41 stores the configuration file into a corresponding storage path according to the file storage path of each configuration file indicated by the metadata configuration file, so as to complete configuration of the second application.

In addition, in the embodiment, the second application depends on the configuration of the first application, that is, the second application is an application that needs to be configured and synchronized with the first application. The configuration synchronization is to execute a related configuration operation on the second application program according to the configuration parameters of the first application program before the second application program is started to run. The configuration parameters of the second application include configuration parameters of the first application on which the second application depends. Optionally, the configuration parameters of the second application further include configuration parameters obtained from environment variables of the second container 43.

Referring to fig. 6, a flowchart of a method for configuring an application according to another embodiment of the present application is shown. The method may be applied in the implementation environment shown in fig. 3B. The method may include several steps as follows.

In step 601, the first configuration component 31 obtains file information of the first application deployed in the first container 33.

The file information of the first application is used to indicate a basic file required for configuring the first application, and the first container 33 is any one of containers in the first node 30.

In step 602, the first configuration component 31 obtains the basic file required by the first application program from the database 50 located outside the first node 30 according to the file information of the first application program.

Step 603, the first configuration component 31 generates a configuration file of the first application program according to the basic file required by the first application program and the configuration parameters of the first application program.

Wherein the configuration parameters of the first application are obtained from the environment variables of the first container 33.

The steps 601-603 are the same as the steps 401-403 in the embodiment of fig. 4A, and refer to the description in the embodiment of fig. 4A, which is not repeated herein.

In step 604, the first configuration component 31 sends the configuration parameters of the first application to the configuration center 60 located outside the first node 30.

The first configuration component 31 sends the configuration parameters of the first application to the configuration center 60 located outside the first node 30 after completing the configuration of the first application in the first container 33, so that other applications that need to be synchronized with the configuration of the first application can obtain the configuration parameters of the first application from the configuration center 60.

As already described above, the configuration center 60 is used to provide access to configuration parameters of an application.

The other application program which needs to be configured and synchronized with the first application program is the application program which needs to acquire the configuration parameters of the first application program during configuration. In practical applications, the first application deployed in the first container 33 and the other applications deployed in the other containers may be different instances of the same application, and some or all of the configuration parameters involved in configuring the other applications are identical to those of the first application, so that the configuration parameters of the first application need to be synchronized to the other applications from the configuration center 60.

Optionally, the first configuration component 31 sends the configuration parameters of the first application to the configuration center 60 located outside the first node 30 via a short connection. That is, before sending the configuration parameters of the first application, the first configuration component 31 establishes a communication connection with the physical device on which the configuration center 60 is deployed, then sends the configuration parameters through the communication connection, and after the sending is completed, disconnects the communication connection with the physical device on which the configuration center 60 is deployed.

Optionally, before sending the configuration parameters of the first application, the first configuration component 31 sends a connection establishment request to the physical device on which the configuration center 60 is deployed, where the connection establishment request is used to request establishment of a communication connection between the first configuration component 31 and the physical device on which the configuration center 60 is deployed, and the connection establishment request carries address information of the first node 30, the physical device on which the configuration center 60 is deployed sends a connection establishment response to the first configuration component 31, the connection establishment response is used to confirm that a communication connection is successfully established between the first configuration component 31 and the physical device on which the configuration center 60 is deployed, and after receiving the connection establishment response, the first configuration component 31 confirms that a communication connection is successfully established between the first configuration component 31 and the physical device on which the configuration center 60 is deployed. In addition, the first configuration component 31 disconnects communication with the physical device in which the configuration center 60 is deployed after the configuration parameters of the first application are successfully sent. Optionally, after the physical device deployed with the configuration center 60 successfully receives the configuration parameters of the first application, a first confirmation response is returned to the first configuration component 31, where the first confirmation response is used to indicate that the configuration parameters of the first application have been successfully received, and then the first configuration component 31 disconnects the communication connection according to the first confirmation response. In other possible examples, the physical device on which configuration center 60 is deployed actively disconnects communication with first configuration component 31 after the configuration parameters of the first application are successfully received.

Accordingly, the configuration center 60 located outside the first node 30 receives the configuration parameters of the first application program sent by the first configuration component 31 and stores the configuration parameters of the first application program. Optionally, the configuration parameter of the first application is sent and stored in a key-value pair (key-value pair), where a key represents a name of the configuration parameter, and a value corresponding to the key is a parameter value representing the configuration parameter corresponding to the name of the configuration parameter.

In step 605, the first configuration component 31 sends a configuration change notification to the second configuration component 41 in the second node 40.

The first configuration component 31 sends a configuration change notification to the configuration components of the various other nodes in the distributed application system. The other nodes include a second node 40, and the configuration component of the second node 40 is a second configuration component 41. The configuration change notification is used to notify the second configuration component 41 to obtain the configuration parameters of the first application from the configuration center 60. The configuration change notification includes the name, i.e., the key, of the configuration parameter sent by the first configuration component 31 to the configuration center 60. In a distributed application system, comprising a plurality of nodes, different instances of the distributed application are deployed in different nodes in a container manner, and one or more instances of the distributed application can be deployed in one node. For example, an application provided by a large e-commerce platform is a distributed application having multiple services such as order management, buyer management, seller management, commodity management, etc., and examples of the different services may be deployed in different containers and different nodes.

Optionally, the first configuration component 31 sends a configuration change notification to the second configuration component 41 in the second node 40 over a short connection. That is, the first configuration component 31 sends a connection establishment request to the second configuration component 41 in the second node 40, where the connection establishment request is used to request to establish a communication connection with the second configuration component 41, and the connection establishment request carries the communication address information of the first node 30. The second configuration component 41 sends a connection establishment response to the first configuration component 31 indicating that the communication connection between the first configuration component 31 and the second configuration component 41 has been successfully established. The first configuration component 31 sends a configuration change notification to the second configuration component 41 via the communication connection after receiving the connection establishment response, and disconnects the communication connection after the configuration change notification is sent successfully. Optionally, the second configuration component 41 returns a second confirmation response to the first configuration component 31 after successfully receiving the configuration change notification, where the second confirmation response is used to indicate that the configuration change notification has been successfully received, and then the first configuration component 31 disconnects the communication connection according to the second confirmation response. In other possible examples, the second configuration component 41 actively disconnects the communication connection with the first configuration component 31 after the configuration change notification is successfully received.

In step 606, the second configuration component 41 obtains file information of the second application deployed in the second container 43.

The file information of the second application is used to indicate the basic files required to configure the second application, and the second container 43 is any one of the containers in the second node 40.

In step 607, the second configuration component 41 obtains the basic file required by the second application program from the database 50 located outside the second node 40 according to the file information of the second application program.

The steps 606-607 are the same as the steps 501-502 in the embodiment of fig. 5, and refer to the description in the embodiment of fig. 5, which is not repeated herein.

It should be noted that, in the embodiment of the present application, the execution time of steps 606-.

At step 608, the second configuration component 41 sends an information acquisition request to the configuration center 60.

Optionally, after receiving the configuration change notification, the second configuration component 41 detects whether the name of the configuration parameter required by the second application exists in the names of the configuration parameters of the first application carried in the configuration change notification, and if so, the second configuration component 41 sends an information acquisition request to the configuration center, and if not, the step of sending the information acquisition request to the configuration center 60 is not executed. The information acquisition request is used for requesting to acquire the configuration parameters of the first application program. The information acquisition request carries a name (also called key) of the configuration parameter required by the second application program.

Optionally, before sending the information acquisition request to the configuration center 60, the second configuration component 41 establishes a communication connection with the physical device of the deployment configuration center 60, and then sends the information acquisition request to the physical device of the deployment configuration center 60 through the communication connection.

In addition, second configuration component 41, upon receiving the configuration parameters of the first application, disconnects communication with the physical devices of deployment configuration center 60. The configuration parameters are received and sent between the configuration components and the configuration center 60 in a short connection mode, so that connection resources of the configuration center 60 are prevented from being occupied.

In step 609, the configuration center 60 sends the configuration parameters of the first application to the second configuration component 41.

The configuration parameters of the first application may be all configuration parameters of the first application, or may be configuration parameters required by the second application indicated by the second configuration component 41 in the information acquisition request.

In step 610, the second configuration component 41 generates a configuration file of the second application according to the basic file required by the second application and the configuration parameters of the second application.

The configuration parameters of the second application program comprise the configuration parameters of the first application program depended by the second application program. Optionally, the configuration parameters of the second application further include configuration parameters obtained from environment variables of the second container 43. For the description of step 610, reference may be made to the description of step 504 in fig. 5, which is not repeated herein.

It should be noted that, when the third application deployed in the third container of the first node 30 depends on the first application, that is, the third application is an application that needs to be configured and synchronized with the first application. The configuration synchronization is to execute a related configuration operation on the third application program according to the configuration parameters of the first application program before the third application program is started to run. The first configuration component 31 generates a configuration file of the third application according to the base file required by the third application and the configuration parameters of the third application. The third container is any one of the containers in the first node 30 except the first container 33. The configuration parameters of the third application include configuration parameters of the first application. Optionally, the configuration parameters of the third application further include configuration parameters obtained from environment variables of the third container. In addition, the first configuration component 31 needs to perform the steps of acquiring the file information of the third application deployed in the third container and acquiring the basic file required by the third application from the database 50 located outside the first node 30 according to the file information of the third application before generating the configuration file of the third application. And the file information of the third application program is used for indicating basic files required for configuring the third application program.

In addition, the receiving and sending of the configuration parameters are realized between the configuration component and the configuration center in a short connection mode, and the occupation of connection resources of the configuration center is avoided.

Referring to fig. 7, a flowchart of a method for configuring an application according to another embodiment of the present application is shown. The method may be applied in the implementation environment shown in fig. 3B. The method may include several steps as follows.

In step 701, the second container 43 is started.

The second container 43 loads the initialization script, step 702.

In step 703, the second container 43 obtains the identifier of the metadata configuration file of the second application from the environment variables of the second container 43 through the initialization script.

In step 704, the second container 43 sends the identity of the metadata configuration file for the second application to the second configuration component 41.

In step 705, the second configuration component 41 obtains the metadata configuration file of the second application from the database 50 located outside the second node 40 according to the identifier of the metadata configuration file of the second application.

In step 706, the second configuration component 41 parses the metadata configuration file of the second application program, and obtains the configuration script and the identifier of the configuration template of the second application program.

In step 707, the second configuration component 41 obtains the configuration script and the configuration template of the second application from the database 50 located outside the second node 40 according to the identification of the configuration script and the configuration template of the second application.

At step 708, the first container 33 is activated.

At step 709, the first container 33 loads an initialization script.

At step 710, the first container 33 obtains an identification of a metadata configuration file for the first application from the environment variables of the first container 33 via the initialization script.

At step 711, the first container 33 sends the identification of the metadata configuration file for the first application to the first configuration component 31.

In step 712, the first configuration component 31 obtains the metadata configuration file of the first application from the database 50 external to the first node 30 based on the identification of the metadata configuration file of the first application.

In step 713, the first configuration component 31 parses the metadata configuration file of the first application to obtain the configuration script and the identifier of the configuration template of the first application.

In step 714, the first configuration component 31 obtains the configuration script and the configuration template of the first application from the database 50 located outside the first node 30 according to the identification of the configuration script and the configuration template of the first application.

In step 715, the first configuration component 31 generates a configuration file of the first application according to the configuration script and the configuration template of the first application and the configuration parameters of the first application.

At step 716, the first configuration component 31 sends the configuration parameters of the first application to a configuration center 60 located outside the first node 30.

In step 717, the first configuration component 31 sends a configuration change notification to the configuration components of the other nodes.

The other nodes include a second node 40.

At step 718, the first configuration component 31 sends a first configuration complete notification to the first container 33.

The first configuration completion notification is used to indicate that the first application has been configured.

At step 719, the first container 33 launches the first application.

The second configuration component 41 sends 720 an information acquisition request to the configuration center 60 located outside the second node 40.

The information acquisition request is used for requesting to acquire the configuration parameters of the first application program.

The configuration center 60 sends 721 the configuration parameters of the first application to the second configuration component 41.

In step 722, the second configuration component 41 generates a configuration file of the second application according to the configuration script and the configuration template of the second application and the configuration parameters of the second application.

The configuration parameters of the second application program comprise the configuration parameters of the first application program depended by the second application program. Optionally, the configuration parameters of the second application further include configuration parameters obtained from environment variables of the second container 43.

At step 723, the second configuration component 41 sends a second configuration complete notification to the second container 43.

The second configuration completion notification is used to indicate that the second application has been configured.

In step 724, the second container 43 starts the second application.

The above description mainly describes the scheme provided by the embodiment of the present application from the perspective of interaction between the first node 30 and the second node 40. The steps described above with respect to the first node 30 side may be implemented as a method of configuring an application program on the first node 30 side alone, and the steps described with respect to the second node 40 side may be implemented as a method of configuring an application program on the second node 40 side alone.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 8, a block diagram of an apparatus for configuring an application according to an embodiment of the present application is shown. The apparatus is applied to the first configuration component 31 of the first node 30, and the apparatus has the function of implementing the first configuration component 31 in the above method example, and the function may be implemented by hardware, or by hardware executing corresponding software. The apparatus may include: an information acquisition module 810, a file acquisition module 820, and a file generation module 830.

An information obtaining module 810, configured to obtain file information of a first application deployed in the first container 33, where the file information of the first application is used to indicate a basic file required for configuring the first application.

A file obtaining module 820, configured to obtain, according to the file information of the first application, a basic file required by the first application from a database 50 located outside the first node 30.

The file generating module 830 is configured to generate a configuration file of the first application according to the basic file required by the first application and the configuration parameter of the first application, where the configuration parameter of the first application is obtained from the environment variable of the first container 33.

In an alternative embodiment based on the embodiment shown in fig. 8, the file information of the first application includes an identifier of a metadata configuration file of the first application, and the metadata configuration file of the first application includes an identifier of a basic file required by the first application;

the file obtaining module 820 is further configured to:

acquiring the metadata configuration file of the first application program from the database 50 according to the identifier of the metadata configuration file of the first application program;

analyzing the metadata configuration file of the first application program to acquire an identifier of a basic file required by the first application program;

and acquiring the basic file required by the first application program from the database 50 according to the identification of the basic file required by the first application program.

In another alternative embodiment based on the embodiment shown in fig. 8, the apparatus further comprises: a configuration submission module 840 and a notification sending module 850.

A configuration submitting module 840, configured to send the configuration parameters of the first application to a configuration center 60 located outside the first node 30.

A notification sending module 850, configured to send a configuration change notification to the second configuration component 41 of the second node 40, where the configuration change notification is used to notify the second configuration component 41 to obtain the configuration parameters of the first application from the configuration center 60.

In another alternative embodiment based on the embodiment shown in fig. 8, the notification sending module 850 is configured to send a connection establishment request to the second configuration component 41, where the connection establishment request is used to request that a communication connection is established with the second configuration component 41; after successful establishment of the communication connection, sending the configuration change notification to the second configuration component 41; disconnecting the communication connection after the configuration change notification is successfully sent.

Referring to fig. 9, a block diagram of an apparatus for configuring an application according to another embodiment of the present application is shown. The apparatus is applied to the second configuration component 41 of the second node 40, and the apparatus has the function of implementing the second configuration component 41 in the above method example, and the function may be implemented by hardware, and may also be implemented by hardware executing corresponding software. The apparatus may include: an information acquisition module 910, a file acquisition module 920, an information receiving module 930, and a file generation module 940.

An information obtaining module 910, configured to obtain file information of a second application deployed in a second container 43, where the file information of the second application is used to indicate a basic file required for configuring the second application.

The file obtaining module 920 is configured to obtain, according to the file information of the second application program, a basic file required by the second application program from a database 50 located outside the second node 40.

An information receiving module 930, configured to receive the configuration parameter of the first application sent by the configuration center 60 after the configuration center 60 located outside the second node 40 receives the configuration parameter of the first application, where the first application is an application deployed in a container of the first node 30.

The file generating module 940 is configured to generate a configuration file of the second application according to the basic file required by the second application and the configuration parameters of the second application, where the configuration parameters of the second application include the configuration parameters of the first application.

In an alternative embodiment based on the embodiment shown in fig. 9, the file information of the second application includes an identifier of a metadata configuration file of the second application, and the metadata configuration file of the second application includes an identifier of a basic file required by the second application;

the file obtaining module 920 is further configured to:

acquiring the metadata configuration file of the second application program from the database 50 according to the identifier of the metadata configuration file of the second application program;

analyzing the metadata configuration file of the second application program to acquire an identifier of a basic file required by the second application program;

and acquiring the basic file required by the second application program from the database 50 according to the identification of the basic file required by the second application program.

In another alternative embodiment based on the embodiment shown in fig. 9, the apparatus further comprises: a request sending module 950.

The information receiving module 930 is further configured to receive a configuration change notification sent by the first configuration component 31 in the first node 30, where the configuration change notification is used to notify the second configuration component 41 to obtain the configuration parameters of the first application from the configuration center 60 located outside the second node 40.

A request sending module 950, configured to send an information obtaining request to the configuration center 60, where the information obtaining request is used to request to obtain the configuration parameters of the first application.

In an optional embodiment based on the embodiment shown in fig. 9, the information receiving module 930 is further configured to receive a connection establishment request sent by the first configuration component 31; establishing a communication connection with the first configuration component 31 according to the connection establishment request; receiving the configuration change notification sent by the first configuration component 31, wherein the communication connection is disconnected after the second configuration component 41 successfully receives the configuration change notification.

It is understood that the apparatus (or referred to as "device") for implementing the above-described functions includes corresponding hardware structures and/or software modules for performing the respective functions. The various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present teachings.

In the embodiment of the present application, functional modules of an apparatus (or referred to as "device") may be divided according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a form of hardware or a form of a software functional unit. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

Fig. 10A shows a schematic diagram of a possible structure of the device according to the above exemplary embodiment, in the case of an integrated module. The apparatus 1000 comprises: a processing module 1002 and a communication module 1003. The processing module 1002 is used for controlling and managing the operation of the apparatus 1000. For example, when the apparatus 1000 is the first node 30, the processing module 1002 is configured to implement the functions of the information obtaining module 810, the file obtaining module 820, the file generating module 830, the configuration submitting module 840 and the notification sending module 850 in the above-described embodiment of fig. 8, and in particular, the processing module 1002 is configured to support the apparatus 1000 to perform the steps 401 to 403 in fig. 4A, the steps 601 to 605 in fig. 6, and/or to perform other steps of the techniques described herein. For another example, when the apparatus 1000 is the second node 40, the processing module 1002 is configured to implement the functions of the information obtaining module 910, the file obtaining module 920, the information receiving module 930, the file generating module 940 and the request sending module 950 in the above-described fig. 9 embodiment, and specifically, the processing module 1002 is configured to support the apparatus 1000 to perform the steps 501 to 504 in fig. 5, the steps 606 to 610 in fig. 6, and/or other steps for performing the techniques described herein. The communication module 1003 is used to support the communication of the apparatus 1000 with other devices. For example, when the apparatus 1000 is the first node 30, the communication module 1003 is configured to support communication between the first node 30 and the second node 40, the database 50 and the configuration center 60, such as sending a configuration change notification to the second node 40, sending a first/second acquisition request to the database 50, sending configuration parameters of the first application to the configuration center 60, and the like under the control of the processing module 1002. For another example, when the apparatus 1000 is the second node 40, the communication module 1003 is configured to support communication between the second node 40 and the first node 30, the database 50 and the configuration center 60, such as receiving a configuration change notification sent by the first node 30, sending a third/fourth acquisition request to the database 50, sending an information acquisition request to the configuration center 60, receiving configuration parameters of the first application sent by the configuration center 60, and the like under the control of the processing module 1002. The apparatus 1000 may also include a storage module 1001 for storing program codes and data for the apparatus 1000.

The Processing module 1002 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1003 may be a communication interface, a transceiver circuit, etc., wherein the communication interface is a generic term, and may include one or more interfaces, such as an interface between a first node and a second node. The storage module 1001 may be a memory.

When the processing module 1002 is a processor, the communication module 1003 is a communication interface, and the storage module 1001 is a memory, the apparatus according to the embodiment of the present application may be the apparatus shown in fig. 10B.

Referring to fig. 10B, the apparatus 1010 includes: processor 1012, communication interface 1013, and memory 1011. Optionally, the apparatus 1010 may also include a bus 1014. Wherein, the communication interface 1013, the processor 1012, and the memory 1011 may be connected to each other by a bus 1014; the bus 1014 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus 1014 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10B, but this is not intended to represent only one bus or type of bus.

The apparatus shown in fig. 10A or fig. 10B may be the first node 30 or the second node 40.

The steps of the method described in connection with the disclosure of the embodiments of the present application may be implemented in hardware or may be implemented by a processor executing software instructions. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a device. Of course, the processor and the storage medium may reside as discrete components in an apparatus.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. The use of "first," "second," and similar terms herein do not denote any order, quantity, or importance, but rather the terms are used to distinguish one object from another.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the embodiments of the present application in further detail, and it should be understood that the above-mentioned embodiments are only specific embodiments of the present application, and are not intended to limit the scope of the embodiments of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of the embodiments of the present application.

Claims

1. A method for configuring an application, applied in a first node, the first node comprising a first configuration component and a first container; the method comprises the following steps:

the first configuration component acquires file information of a first application program deployed in a first container, wherein the file information of the first application program is used for indicating a basic file required by configuration of the first application program;

the first configuration component acquires a basic file required by the first application program from a database located outside the first node according to the file information of the first application program;

the first configuration component generates a configuration file of the first application program according to a basic file required by the first application program and configuration parameters of the first application program, wherein the configuration parameters of the first application program are acquired from environment variables of the first container;

the first configuration component sends the configuration parameters of the first application program to a configuration center located outside the first node;

and the first configuration component sends a configuration change notice to a second configuration component in a second node, wherein the configuration change notice is used for informing the second configuration component to acquire the configuration parameters of the first application program from the configuration center.

2. The method of claim 1, wherein the file information of the first application comprises an identification of a metadata configuration file of the first application, and wherein the metadata configuration file of the first application comprises an identification of a basic file required by the first application;

the first configuration component acquires a basic file required by the first application program from a database located outside the first node according to the file information of the first application program, and the basic file comprises:

the first configuration component acquires the metadata configuration file of the first application program from the database according to the identifier of the metadata configuration file of the first application program;

the first configuration component analyzes the metadata configuration file of the first application program and acquires an identifier of a basic file required by the first application program;

and the first configuration component acquires the basic file required by the first application program from the database according to the identification of the basic file required by the first application program.

3. The method of claim 1, wherein sending a configuration change notification to a second configuration component in a second node by the first configuration component comprises:

the first configuration component sends a connection establishment request to the second configuration component, wherein the connection establishment request is used for requesting to establish communication connection with the second configuration component;

after successfully establishing the communication connection, the first configuration component sending the configuration change notification to the second configuration component;

the first configuration component disconnects the communication connection after the configuration change notification is successfully sent.

4. A method of configuring an application, for use in a second node comprising a second configuration component and a second container; the method comprises the following steps:

the second configuration component acquires file information of a second application program deployed in a second container, wherein the file information of the second application program is used for indicating a basic file required for configuring the second application program;

the second configuration component acquires a basic file required by the second application program from a database located outside the second node according to the file information of the second application program;

after a configuration center located outside the second node receives configuration parameters of a first application program, the second configuration component receives the configuration parameters of the first application program sent by the configuration center, and the first application program is an application program deployed in a container of the first node;

and the second configuration component generates a configuration file of the second application program according to the basic file required by the second application program and the configuration parameters of the second application program, wherein the configuration parameters of the second application program comprise the configuration parameters of the first application program.

5. The method of claim 4, wherein the file information of the second application includes an identification of a metadata configuration file of the second application, and wherein the metadata configuration file of the second application includes an identification of a base file required by the second application;

the second configuration component acquires a basic file required by the second application program from a database located outside the second node according to the file information of the second application program, and the basic file includes:

the second configuration component acquires the metadata configuration file of the second application program from the database according to the identifier of the metadata configuration file of the second application program;

the second configuration component analyzes the metadata configuration file of the second application program and acquires an identifier of a basic file required by the second application program;

and the second configuration component acquires the basic file required by the second application program from the database according to the identification of the basic file required by the second application program.

6. The method according to claim 4 or 5, wherein before the second configuration component receives the configuration parameters of the first application program sent by the configuration center, the method further comprises:

the second configuration component receives a configuration change notification sent by a first configuration component in the first node, wherein the configuration change notification is used for notifying the second configuration component to acquire configuration parameters of the first application program from the configuration center;

and the second configuration component sends an information acquisition request to the configuration center, wherein the information acquisition request is used for requesting to acquire the configuration parameters of the first application program.

7. The method of claim 6, wherein the second configuration component receives the notification of the configuration change sent by the first configuration component in the first node, comprising:

the second configuration component receives a connection establishment request sent by the first configuration component;

the second configuration component establishes communication connection with the first configuration component according to the connection establishment request;

the second configuration component receives the configuration change notification sent by the first configuration component, wherein the communication connection is disconnected after the second configuration component successfully receives the configuration change notification.

8. An apparatus for configuring an application, wherein the apparatus is applied in a first configuration component of a first node, wherein the first node comprises the first configuration component and a first container; the device comprises:

the information acquisition module is used for acquiring file information of a first application program deployed in a first container, wherein the file information of the first application program is used for indicating a basic file required by the configuration of the first application program;

the file acquisition module is used for acquiring a basic file required by the first application program from a database positioned outside the first node according to the file information of the first application program;

the file generation module is used for generating a configuration file of the first application program according to a basic file required by the first application program and the configuration parameters of the first application program, wherein the configuration parameters of the first application program are acquired from the environment variables of the first container;

the configuration submitting module is used for sending the configuration parameters of the first application program to a configuration center located outside the first node;

a notification sending module, configured to send a configuration change notification to a second configuration component in a second node, where the configuration change notification is used to notify the second configuration component to obtain configuration parameters of the first application from the configuration center.

9. The apparatus according to claim 8, wherein the file information of the first application includes an identifier of a metadata configuration file of the first application, and the metadata configuration file of the first application includes an identifier of a basic file required by the first application;

the file acquisition module is further configured to:

acquiring the metadata configuration file of the first application program from the database according to the identifier of the metadata configuration file of the first application program;

and acquiring the basic file required by the first application program from the database according to the identification of the basic file required by the first application program.

10. The apparatus of claim 8, wherein the notification sending module is further configured to:

sending a connection establishment request to the second configuration component, the connection establishment request requesting establishment of a communication connection with the second configuration component;

after successfully establishing the communication connection, sending the configuration change notification to the second configuration component;

disconnecting the communication connection after the configuration change notification is successfully sent.

11. An apparatus for configuring an application, wherein the apparatus is applied in a second configuration component of a second node, the second node comprising the second configuration component and a second container; the device comprises:

the information acquisition module is used for acquiring file information of a second application program deployed in a second container, wherein the file information of the second application program is used for indicating a basic file required by the second application program;

the file acquisition module is used for acquiring a basic file required by the second application program from a database positioned outside the second node according to the file information of the second application program;

an information receiving module, configured to receive, after a configuration center located outside the second node receives configuration parameters of a first application program, the configuration parameters of the first application program sent by the configuration center, where the first application program is an application program deployed in a container of a first node;

and the file generation module is used for generating a configuration file of the second application program according to the basic file required by the second application program and the configuration parameters of the second application program, wherein the configuration parameters of the second application program comprise the configuration parameters of the first application program.

12. The apparatus according to claim 11, wherein the file information of the second application includes an identifier of a metadata configuration file of the second application, and the metadata configuration file of the second application includes an identifier of a basic file required by the second application;

the file acquisition module is further configured to:

acquiring the metadata configuration file of the second application program from the database according to the identifier of the metadata configuration file of the second application program;

and acquiring the basic file required by the second application program from the database according to the identification of the basic file required by the second application program.

13. The apparatus of claim 11 or 12, further comprising:

the information receiving module is further configured to receive a configuration change notification sent by a first configuration component in the first node, where the configuration change notification is used to notify the second configuration component to obtain configuration parameters of the first application from the configuration center;

and the request sending module is used for sending an information acquisition request to the configuration center, wherein the information acquisition request is used for requesting to acquire the configuration parameters of the first application program.

14. The apparatus of claim 13, wherein the information receiving module is further configured to:

receiving a connection establishment request sent by the first configuration component, establishing communication connection with the first configuration component according to the connection establishment request, and receiving the configuration change notification sent by the first configuration component, wherein after the second configuration component successfully receives the configuration change notification, the communication connection is disconnected.