CN111381932B - Method, device, electronic equipment and storage medium for triggering application program change - Google Patents

Abstract

The embodiment of the invention provides a method, a device, electronic equipment and a storage medium for triggering application program change, which comprise the following steps: monitoring that the configuration information of the application program changes, and acquiring the changed configuration information of the application program from a configuration file corresponding to the application program; and determining that the configuration information of the changed application program is inconsistent with the configuration information currently executed by the application program, and triggering the application program to restart so as to execute the configuration information after the change. According to the method, the device, the electronic equipment and the storage medium for triggering application program change, provided by the embodiment of the invention, through real-time monitoring of the change of the configuration information of the application program, the problem that the configuration information after the change is different from the configuration information currently executed by the application program is rapidly found, so that the application program is triggered to restart, the change of the application program is realized, and the efficiency of the application program change is improved.

Description

Methods, devices, electronic devices and storage media for triggering application changes

Technical field

The present invention relates to the field of computer technology, and in particular, to a method, device, electronic device and storage medium for triggering application program modification.

Background technique

Kubernetes is an open source application used to manage containerized applications on multiple hosts in a cloud platform. The goal of Kubernetes is to make deploying containerized applications simple and efficient. It provides application deployment, planning, updates, and maintenance. a mechanism. Kubernetes implements changes to applications installed in containers by updating the application's configuration information.

ConfigMap is a configuration file used in Kubernetes to store common configuration variables. It allows users to unify environment variables for different modules in a distributed system into one object for management. Kubernetes can change the application in the container through updates to the ConfigMap.

In Kubernetes, since the application in the container does not monitor changes in configuration information, updates to the ConfigMap do not necessarily lead to synchronous updates of the configuration information executed by the application. In the prior art, when the configuration information is updated, the new configuration information can only be loaded when the application restarts the process, or when a new application is created and the original application is terminated. Configuration information. That is, in the existing technology, there is a phenomenon that after the configuration information is updated, the application still executes the original configuration information before the update without restarting, and there is a problem that the updated configuration information is different from the configuration information currently executed by the application. .

In the prior art, it is necessary to manually restart the application program to overcome the problem that the updated configuration information is different from the configuration information currently executed by the application program. Not only is the efficiency low, but the response is not timely.

Contents of the invention

Embodiments of the present invention provide a method, a device, an electronic device, and a storage medium for triggering application program changes, so as to solve the defects of low execution efficiency and untimely response of the manual restarting application program method in the prior art.

The first embodiment of the present invention provides a method for triggering application changes, including:

Monitor changes in the configuration information of the application, and obtain the changed configuration information of the application from the configuration file corresponding to the application;

It is determined that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, and the application program is triggered to restart to execute the changed configuration information.

Based on any embodiment of the present invention, it also includes:

Monitor that the application triggers a target event, obtain the configuration information currently executed by the application, and store the configuration information currently executed by the application; wherein the target event is a creation event or read event or update of the application event.

Based on any embodiment of the present invention, it also includes:

Set a label for the object of the application program to be monitored; wherein the label includes a first field used to describe whether the configuration information of the application program has changed and a second field used to save the configuration information currently executed by the application program.

Based on any embodiment of the present invention, determining that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program includes:

Calculate the hash value of the changed configuration information of the application;

Calculate a hash value of the configuration information currently executed by the application;

It is determined that the hash value of the changed configuration information of the application program is inconsistent with the hash value of the configuration information currently executed by the application program.

Based on any embodiment of the present invention, monitoring changes in the configuration information of the application program includes: using a controller in Kubernetes to monitor changes in the configuration information of the application program.

Based on any embodiment of the present invention, monitoring the application triggering the target event includes: using a controller in Kubernetes to monitor the application triggering the target event.

Based on any embodiment of the present invention, storing the configuration information currently executed by the application program includes: storing the configuration information currently executed by the application program in a second field marked on the object of the application program.

The second embodiment of the present invention also provides a device for triggering application changes, including:

The post-change configuration information acquisition module is used to monitor changes in the configuration information of the application and obtain the post-change configuration information of the application from the configuration file corresponding to the application;

The application restart triggering module is configured to determine that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, and trigger the restart of the application program to execute the changed configuration information.

A third embodiment of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the first aspect of the present invention is implemented. Steps of a method for triggering application changes described in aspect embodiments.

The fourth embodiment of the present invention provides a non-transitory computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the application program modification is triggered as described in the first embodiment of the present invention. steps of the method.

The methods, devices, electronic devices and storage media for triggering application changes provided by embodiments of the present invention can quickly detect the problem that the changed configuration information is different from the configuration information currently executed by the application through real-time monitoring of changes in the application configuration information. This in turn triggers application restart, implements application changes, and improves the efficiency of application changes.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description These are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

Figure 1 is a flow chart of a method for triggering application changes provided by an embodiment of the present invention;

Figure 2 is a flow chart of a method for triggering application changes provided by another embodiment of the present invention;

Figure 3 is a flow chart of a method for triggering application changes provided by yet another embodiment of the present invention;

Figure 4 is a structural diagram of a device for triggering application changes provided by an embodiment of the present invention;

Figure 5 illustrates a schematic diagram of the physical structure of an electronic device.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments These are some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of the present invention.

Figure 1 is a flow chart of a method for triggering application changes provided by an embodiment of the present invention. As shown in Figure 1, the method for triggering application changes provided by an embodiment of the present invention includes:

Step 101: Monitor changes in the configuration information of the application program, and obtain the changed configuration information of the application program from the configuration file corresponding to the application program.

In the embodiment of the present invention, the status of the monitoring configuration information is subscribed through the controller mechanism in Kubernetes. Once the configuration information of the application is monitored to change, the changed configuration information of the application is obtained from the ConfigMap. Among them, the changes are updates or changes. In other embodiments of the present invention, other methods may also be used to monitor changes in application configuration information.

In the embodiment of the present invention, whether the configuration information of the application program changes is monitored by monitoring the annotations of the application program objects. For example, a first field is set in the annotation of the application object, and this field is used to reflect whether the application configuration information changes. One way of describing the first field of the annotation is annotation(update-on-config-change:true). If annotation(update-on-config-change:true) exists, it means that the application configuration information has changed. , on the contrary, the application configuration information will not change.

Step 102: Determine that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, and trigger a restart of the application program to execute the changed configuration information.

The configuration information currently executed by the application program is known information. It can be obtained in real time from the object of the application program, or it can be obtained and stored in advance, or it can be obtained in other ways that those skilled in the art can think of. , the acquisition method is not limited in the embodiment of the present invention.

In this step, after the application is restarted, the changed configuration information will be executed. At this time, the changed configuration information has become the configuration information currently executed by the application program, and the changed configuration information is stored as the configuration information currently executed by the application program. For example, a hash value of the changed configuration information is calculated, and the hash value of the changed configuration information is stored in the second field of the annotation of the application program. One description method of the second field of the annotation is annotation (version/config:hash), and the second field is used to save the configuration information currently executed by the application program. Since the configuration information currently executed by the application is the changed configuration information, the changed configuration information will be stored in the second field.

The method for triggering application changes provided by the embodiment of the present invention quickly detects the problem that the changed configuration information is different from the configuration information currently executed by the application through real-time monitoring of changes in the application configuration information, thereby triggering the application to restart and realizing the application. changes.

Based on any of the above embodiments, Figure 2 is a flow chart of a method for triggering application changes provided by another embodiment of the present invention. As shown in Figure 2, a method for triggering application changes provided by another embodiment of the present invention includes:

Step 201: Monitor the target event triggered by the application program, obtain and store the configuration information currently executed by the application program.

In the embodiment of the present invention, the monitoring of target events in the application is implemented through the controller mechanism in Kubernetes. In other embodiments of the present invention, other methods may also be used to monitor target events in the application program.

The target events are generally events that have an impact on the application, such as create events, read events, and update events.

Configuration information for the current execution of the application can be obtained from the application object.

In this embodiment of the present invention, the obtained configuration information of the currently executed application is stored in the annotation of the application object. For example, calculate the hash value of the configuration information currently executed by the application, and store the obtained hash value of the configuration information in the second field of the annotation of the application object (such as the field version/config:hash in the annotation). In other embodiments of the present invention, other storage methods may also be used.

Step 202: Monitor changes in the configuration information of the application program, and obtain the changed configuration information of the application program from the configuration file corresponding to the application program.

Step 203: Determine that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, and trigger a restart of the application program to execute the changed configuration information.

In this embodiment of the present invention, the configuration information currently executed by the application program is obtained through step 201.

The method for triggering application changes provided by the embodiment of the present invention can quickly discover the problem that the changed configuration information is different from the configuration information currently executed by the application through real-time monitoring of changes in application configuration information and monitoring of application target events, and thus Trigger application restart to implement application changes.

Based on any of the above embodiments, Figure 3 is a flow chart of a method for triggering application changes provided by yet another embodiment of the present invention. As shown in Figure 3, a method for triggering application changes provided by yet another embodiment of the present invention includes:

Step 301: Set annotations for the applications to be monitored.

In this embodiment of the present invention, a label is set for the application program that needs to be monitored. The annotation at least includes a single field and a second field, where the first field is used to describe whether the configuration information of the application program has changed, and the second field is used to save the configuration information currently executed by the application program.

Step 302: Monitor the target event triggered by the application program, obtain and store the configuration information currently executed by the application program.

Step 303: Monitor changes in the configuration information of the application program, and obtain the changed configuration information of the application program from the configuration file corresponding to the application program.

Step 304: Determine that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, and trigger a restart of the application program to execute the changed configuration information.

The method for triggering application changes provided by the embodiment of the present invention realizes monitoring of changes in application configuration information and storage of application configuration information through marked settings.

Based on any of the above embodiments, in a method for triggering application changes provided by yet another embodiment of the present invention, determining that the changed configuration information of the application is inconsistent with the configuration information currently executed by the application further includes:

Calculate the hash value of the changed configuration information of the application;

Calculate a hash value of the configuration information currently executed by the application;

It is determined that the hash value of the changed configuration information of the application program is inconsistent with the hash value of the configuration information currently executed by the application program.

The method for triggering application changes provided by the embodiment of the present invention calculates a hash value for the changed configuration information of the application program and the currently executed configuration information, and determines whether the changed configuration information and the currently executed configuration information are compared by comparing the hash values. Consistent, the comparison process is faster, thereby improving the efficiency of the entire method.

Based on any of the above embodiments, Figure 4 is a structural diagram of a device for triggering application changes provided by an embodiment of the present invention. As shown in Figure 4, the device for triggering application changes provided by an embodiment of the present invention includes:

The post-change configuration information acquisition module 401 is used to monitor changes in the configuration information of the application program and obtain the post-change configuration information of the application program from the configuration file corresponding to the application program;

The application restart trigger module 402 is used to determine that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, and trigger the restart of the application program to execute the changed configuration information.

The device for triggering application changes provided by the embodiment of the present invention quickly detects the problem that the changed configuration information is different from the configuration information currently executed by the application through real-time monitoring of changes in the application configuration information, thereby triggering the application to restart and realizing the application. changes.

The method for triggering application changes provided by the embodiment of the present invention will be further described below with reference to a specific example.

In this instance, a Deployment is a resource in Kubernetes that represents an application.

The relevant steps are as follows:

First, create a creation event or read event or update event of the Deployment monitored by the controller in Kubernetes. When the Deployment is created, the controller checks whether the Deployment's Pod Template exists annotation (update-on-config-change: true). If annotation does not exist, the controller will ignore the Deployment. If the annotation exists, obtain the ConfigMap through the reference of the ConfigMap in the Deployment, perform a hash operation (commonly used MD5 or SHA algorithm) on the ConfigMap, and store the obtained hash value in the annotation (version/config:hash value) of the Deployment's Pod Template ) and stores a reference to the Deployment in the controller's monitoring list. When the Deployment updates the ConfigMap, the controller will recalculate the hash value and update the annotation stored in the Deployment.

In addition, the controller also monitors the update event of ConfigMap. When ConfigMap is updated, it tracks which Deployments use the ConfigMap through Owner References, recalculates the hash value of ConfigMap and compares it with the hash value stored in the original Deployment, if it is not the same , update the hash value of the annotation (version/config:hash value) of the Deployment's Pod Template, and restart the application to load the new configuration information.

Figure 5 illustrates a schematic diagram of the physical structure of an electronic device. As shown in Figure 5, the electronic device may include: a processor (processor) 510, a communications interface (Communications Interface) 520, a memory (memory) 530 and a communication bus 540. Among them, the processor 510, the communication interface 520, and the memory 530 complete communication with each other through the communication bus 540. The processor 510 can call logical instructions in the memory 530 to perform the following method: monitor changes in the configuration information of the application program, obtain the changed configuration information of the application program from the configuration file corresponding to the application program; determine If the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, the application program is triggered to restart to execute the changed configuration information.

It should be noted that the electronic device in this embodiment can be a server, a PC, or other devices during specific implementation, as long as its structure includes the processor 510 and the communication interface 520 as shown in Figure 5 , memory 530 and communication bus 540, where the processor 510, the communication interface 520, and the memory 530 complete communication with each other through the communication bus 540, and the processor 510 can call the logical instructions in the memory 530 to execute the above method. This embodiment does not limit the specific implementation form of the electronic device.

In addition, the above-mentioned logical instructions in the memory 530 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .

Further, an embodiment of the present invention discloses a computer program product. The computer program product includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, During execution, the computer can execute the methods provided by the above method embodiments, for example, including: monitoring changes in the configuration information of the application program, and obtaining the changed configuration information of the application program from the configuration file corresponding to the application program. ; Determine that the changed configuration information of the application program is inconsistent with the configuration information currently executed by the application program, and trigger a restart of the application program to execute the changed configuration information.

On the other hand, embodiments of the present invention also provide a non-transitory computer-readable storage medium on which a computer program is stored. The computer program is implemented when executed by a processor to perform the methods provided by the above embodiments, for example, including: Monitoring changes in the configuration information of the application program, obtaining the changed configuration information of the application program from the configuration file corresponding to the application program; determining the changed configuration information of the application program and the current execution of the application program The configuration information is inconsistent, triggering the application to restart to execute the changed configuration information.

The device embodiments described above are only illustrative. The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they may be located in One location, or it can be distributed across multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. Persons of ordinary skill in the art can understand and implement the method without any creative effort.

Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the part of the above technical solution that essentially contributes to the existing technology can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., including a number of instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that it can still be used Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent substitutions are made to some of the technical features; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (6)

1. A method of triggering an application change, comprising:

setting labels for objects of the application program to be monitored; the label comprises a first field for describing whether the configuration information of the application program changes or not and a second field for storing the configuration information currently executed by the application program;

monitoring the triggering target event of the application program, acquiring the configuration information currently executed by the application program, calculating the hash value of the configuration information currently executed by the application program, and storing the hash value of the configuration information currently executed by the application program in the second field; the target event is a creation event or a reading event or an updating event of the application program;

monitoring that the configuration information of the application program changes, and acquiring the changed configuration information of the application program from a configuration file corresponding to the application program;

determining that the configuration information after the change of the application program is inconsistent with the configuration information currently executed by the application program, and triggering the application program to restart so as to execute the configuration information after the change;

the determining that the configuration information of the application program after the change is inconsistent with the configuration information currently executed by the application program comprises the following steps:

calculating a hash value of the changed configuration information of the application program;

determining that the hash value of the configuration information after the change of the application program is inconsistent with the hash value of the configuration information currently executed by the application program;

the method further comprises the steps of: and updating the hash value of the changed configuration information of the application program to the second field and storing the reference of the application program in a monitoring list.

2. The method of claim 1, wherein monitoring for changes in configuration information of an application comprises: the controller in Kubernetes is used to monitor the configuration information of the application program for changes.

3. The method of triggering an application modification according to claim 1, wherein the monitoring for an application trigger target event comprises: the controller in Kubernetes is employed to monitor the application for triggering a target event.

4. An apparatus for triggering an application change, comprising:

the setting module is used for setting labels for the objects of the application program to be monitored; the label comprises a first field for describing whether the configuration information of the application program changes or not and a second field for storing the configuration information currently executed by the application program;

the current execution configuration information acquisition module is used for monitoring the application program triggering target event, acquiring the configuration information currently executed by the application program, calculating the hash value of the configuration information currently executed by the application program, and storing the hash value of the configuration information currently executed by the application program in the second field; the target event is a creation event or a reading event or an updating event of the application program;

the post-change configuration information acquisition module is used for monitoring the change of the configuration information of the application program and acquiring the post-change configuration information of the application program from a configuration file corresponding to the application program;

an application restart triggering module, configured to determine that the configuration information after the change of the application is inconsistent with the configuration information currently executed by the application, and trigger the application to restart to execute the configuration information after the change;

the determining that the configuration information of the application program after the change is inconsistent with the configuration information currently executed by the application program comprises the following steps:

calculating a hash value of the changed configuration information of the application program;

determining that the hash value of the configuration information after the change of the application program is inconsistent with the hash value of the configuration information currently executed by the application program;

the device is also for: and updating the hash value of the changed configuration information of the application program to the second field and storing the reference of the application program in a monitoring list.

5. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor performs the steps of the method of triggering an application modification as claimed in any one of claims 1 to 3 when the program is executed.

6. A non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the method of triggering an application modification as claimed in any of claims 1 to 3.