Micro-service configuration management system and method of electric power internet of things platform

Abstract

The invention discloses a micro-service configuration management system and method of an electric power internet of things platform. The method comprises a configuration management module, a parameter management module, a template management module and a historical version module. Wherein the configuration management module sets four states for the configuration file, namely published, newly added and unpublished, modified and unpublished, and deleted and unpublished, after the newly added configuration file or the published file is edited or deleted, the newly added configuration file or the published file is firstly stored, and then the state of the newly added configuration file or the published file is correspondingly modified into newly added and unpublished, modified and unpublished, and deleted and unpublished; and uniformly publishing and modifying the state into a published state. According to the method, configuration modification and release are decoupled, so that online accidents caused by manual misoperation in a production environment can be greatly reduced, and the safety and flexibility of configuration management are ensured.

Description

Technical Field

[0001] The present invention relates to microservice configuration management, and in particular to a microservice configuration management system and method for an electric power Internet of Things platform. Background Art

[0002] The Internet of Things Management Platform (referred to as the "Electricity Internet of Things Platform") used in the Electric Power Internet of Things is the digital middle platform of the enterprise. It is responsible for managing the access and data collection of edge and terminal devices, and for processing and reporting data. Since the Electric Power Internet of Things Platform needs to meet the different business needs of each site, as well as some performance and security requirements, the platform code volume is huge, so the microservice architecture is used to modularize the platform functions. Figure 1 As shown in the figure, the number of microservices that the platform is split into is generally more than 10, mainly including device management service, object model service, device shadow service, gateway service, access unit and rule engine.

[0003] As mentioned above, since the number of microservices divided into the power IoT platform is large, and each microservice has a configuration file (the operation of the microservice depends on its own configuration file information), the management and maintenance of these configuration files accounts for a large proportion of the daily work of field personnel. Since code changes often require synchronous modifications to the configuration files, each time the system is upgraded and deployed, the on-site operation and maintenance personnel need to modify the configuration files one by one, and perform the release operation after the modification is completed, so that the modified configuration takes effect in the microservice. For another example, when the power IoT platform has problems in the field operation, it is necessary to combine the log information for problem analysis and cause location. The operation and maintenance personnel can reduce the level of log printing in the configuration file to obtain more log information from the microservice.

[0004] The existing available microservice configuration management software and the power IoT platform are independent of each other, and have their own URLs and operation interfaces on the WEB browser. Moreover, in the production environment, the two are generally deployed on different servers. Due to unreasonable permission management, the operation and maintenance personnel may only be able to access the operation page of the power IoT platform, but not the operation page of the configuration management software, which brings great inconvenience to the on-site operation and maintenance work. Summary of the invention

[0005] Purpose of the invention: The purpose of the present invention is to provide a microservice configuration management system and method for an electric power Internet of Things platform with high ease of use, security and flexibility.

[0006] Technical solution: The microservice configuration management system of the power Internet of Things platform described in the present invention includes a configuration management module and a parameter management module;

[0007] The configuration management module sets four states for the configuration files, namely, published, newly added but not published, modified but not published, and deleted but not published. After a newly added configuration file or an edited or deleted published file is saved first, then its state is modified to newly added but not published, modified but not published, or deleted but not published, and then it is published uniformly and its state is modified to published;

[0008] The parameter management module is used to add, define, delete, edit, list and filter configuration parameters and perform recommended value inspection.

[0009] Furthermore, the method for inspecting the recommended values ​​of configuration parameters in the parameter management module includes:

[0010] (1) Obtain the current configuration information of all microservices;

[0011] (2) For each microservice configuration, check whether each parameter has a recommended value;

[0012] (3) If a parameter has a recommended value, determine whether the current value of the parameter is the same as its recommended value;

[0013] (4) If the current value of the parameter is different from its recommended value, record the parameter name and the name of the microservice to which it belongs;

[0014] (5) After completing the above check on each parameter of all microservices, obtain the parameter set that meets the condition (parameter value ≠ recommended value & configuration release time > 2h) in each microservice;

[0015] (6) Assemble alarm information in the format of "{microservice-1: [parameter-1, parameter-2, ..., parameter-n], microservice-2: [parameter-1, parameter-2, ..., parameter-n] ..., microservice-N: [parameter-1, parameter-2, ..., parameter-n]}", and actively push this information to the Kafka message component. The power IoT platform will then forward the alarm information to other business systems. After the operation and maintenance personnel observe the alarm, they will conduct corresponding investigation and processing;

[0016] (7) Repeat steps (1) to (6) above every hour.

[0017] Furthermore, the parameter management module is also used to verify the configuration parameters, set corresponding verification rules for different data types, and then verify whether the input configuration parameters meet the verification rules when defining parameters.

[0018] Furthermore, the configuration management module displays and edits the configuration file in text and / or image form.

[0019] Furthermore, the configuration files in properties format are displayed in a table format, and the configuration files in yaml format are displayed in a tree format.

[0020] Furthermore, the system also includes a historical version module, which generates a historical version record each time a configuration file is released.

[0021] Furthermore, the system also includes a template management module, which generates corresponding templates from the configuration service framework and / or component configuration definition, and adds the template to the configuration file by graphically dragging and dropping when a new configuration file is added.

[0022] The microservice configuration management method of the power Internet of Things platform described in the present invention performs new definition, deletion, editing, list screening and recommended value inspection of configuration parameters through a parameter management module; and performs status management of newly added, edited and / or deleted configuration files through the configuration management module.

[0023] The electronic device described in the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and is characterized in that when the computer program is loaded into the processor, the microservice configuration management method of the power Internet of Things platform is implemented.

[0024] The computer-readable storage medium of the present invention stores a computer program, and when the computer program is executed by a processor, the microservice configuration management method of the power Internet of Things platform is implemented.

[0025] Beneficial effects: Compared with the prior art, the advantages of the present invention are: (1) The present invention sets four states for the configuration file, and the operation and maintenance personnel can uniformly modify the configuration file and then uniformly publish it; after decoupling the configuration modification and publishing, the online accidents caused by human error in the production environment can be greatly reduced; (2) The present invention supports custom parameters and related verification and inspection operations, making the system functions more flexible and rich, and improving the usability and security of the system; (3) The present invention provides a graphic and text interactive editing method, which has a two-way real-time linkage effect, making the modification of the configuration content more efficient, clear and accurate; (4) The system described in the present invention is directly embedded in the power Internet of Things platform page, and there is no need to open other software or systems. Operations can be performed directly on the power Internet of Things platform, which is convenient for operation and maintenance personnel to use. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 A diagram showing the relationship between the configuration management system and platform microservices in the background technology;

[0027] Figure 2 This is a diagram of the microservice configuration management system architecture of the present invention;

[0028] Figure 3 This is a state change diagram of a configuration file in an embodiment of the present invention;

[0029] Figure 4 The figure is a flow chart of parameter inspection in an embodiment of the present invention. DETAILED DESCRIPTION

[0030] The technical solution of the present invention is further described below in conjunction with the accompanying drawings.

[0031] like Figure 2 As shown, the microservice configuration management system of the power IoT platform includes the following four functional modules:

[0032] (1) Configuration management: supports adding, deleting, list filtering, detail viewing, content editing, publishing, version rollback, importing and exporting, operator records, graphical interactive editing and other functions of microservice configuration.

[0033] Among them, the configuration file has four states: published, added but not published, modified but not published, and deleted but not published. Figure 3 The figure shows the status change of configuration files. After the newly added configuration and the published configuration are edited or deleted, they are saved first, and their status is set to added unpublished, modified unpublished, deleted unpublished, and then they are published uniformly, their status is set to published, and the corresponding historical version is generated.

[0034] Among them, graphical interactive editing supports the display and editing of configuration files in text and graphical form. The two are linked to each other, that is, when the text is changed, the graphics will change automatically, and vice versa.

[0035] For .properties format configuration files, they are displayed in table form, and for .yaml format configuration files, they are displayed in tree form.

[0036] (2) Parameter management: supports functions such as adding / defining, deleting, editing, list filtering, verification, and recommended value inspection of parameters.

[0037] The parameter check function is optional. When defining parameters, you can choose whether to check or not. Different data types have different check rules. For example, for integer data, it supports range check of parameter values; for string types, it supports null check; for floating point types, it supports precision check. The following is an example: take the integer parameter port as an example, set its minimum value to 1 and the maximum value to 32; when the port value is set to 23108 and parameter check is performed, the result is that the parameter check fails.

[0038] Among them, the parameter inspection function regularly checks the customized parameters with recommended values, collects the parameters that have not been set to the recommended values ​​for a long time, assembles them into message packets and pushes them to the designated topic of Kafka, and then the upper-level business system conducts specific analysis of the data.

[0039] like Figure 4 As shown in the figure, the process of parameter inspection is as follows:

[0040] (a) Get the current configuration information of all microservices;

[0041] (b) For each microservice configuration, check whether each parameter therein is a parameter with a recommended value;

[0042] (c) if a parameter is a parameter with a recommended value, determining whether the current value of the parameter is the same as the recommended value;

[0043] (d) If the current value of the parameter is different from its recommended value, record the parameter name and the name of the microservice to which it belongs;

[0044] (e) After completing the above check on each parameter of all microservices, obtain the parameter set that meets the condition (parameter value ≠ recommended value & configuration release time > 2h) in each microservice;

[0045] (f) Assemble alarm information in the format of "{microservice-1: [parameter-1, parameter-2, ..., parameter-n], microservice-2: [parameter-1, parameter-2, ..., parameter-n] ..., microservice-N: [parameter-1, parameter-2, ..., parameter-n]}", and actively push this information to the Kafka message component. The power IoT platform will then forward the alarm information to other business systems. After the operation and maintenance personnel observe the alarm, they will conduct corresponding investigation and processing;

[0046] (g) Repeat steps (a) to (f) above every hour.

[0047] For example, if the recommended value of the parameter log is debug, and the value of log is set to info in the configuration file Config-1.yml, and the setting time is more than 1 hour away from the current time, an alarm message will be pushed to the iot_param_alarm_data topic in Kafka.

[0048] (3) Template management: Common microservice configuration frameworks and common component configuration definitions are defined as templates. When adding a new configuration file, the template content can be added to the configuration file by graphically dragging or checking, without the need for manual editing by operation and maintenance personnel.

[0049] (4) Historical version: Each time a configuration is released, a historical version record is generated. The functions of the historical version include storing the previous old configuration content and performing configuration rollback.

[0050] As a functional module of the power IoT platform, the system of the present invention can be directly embedded in the platform page, without opening other software or systems, and can be operated directly on the power IoT platform to achieve direct interaction with microservices, so that configuration files can take effect, which is convenient for operation and maintenance personnel to use. In addition, it can also be used as a second-layer application on existing systems such as Nacos or Apollo, and interact with microservices by indirectly calling the API of Nacos or Apollo to make the configuration files effective.

[0051] In addition, since the modification of the configuration file involves whether the microservice can run normally, for security reasons, it is necessary to add permission management to the page so that only people with corresponding permissions can operate the configuration management system.

[0052] The microservice configuration management method of the power Internet of Things platform described in the present invention performs new definition, deletion, editing, list screening and recommended value inspection of configuration parameters through a parameter management module; and performs status management of newly added, edited and / or deleted configuration files through the configuration management module.

[0053] The electronic device described in the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and is characterized in that when the computer program is loaded into the processor, the microservice configuration management method of the power Internet of Things platform is implemented.

[0054] The computer-readable storage medium of the present invention stores a computer program, and when the computer program is executed by a processor, the microservice configuration management method of the power Internet of Things platform is implemented.

[0055] The computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory, or any other medium that can be used to store program code in the form of instructions or data structures and that can be accessed by a computer.

[0056] The processor is used to execute the computer program stored in the memory to implement each step of the method involved in the above embodiment.

Claims

1. A microservice configuration management system for an electric power IoT platform, characterized in that: Including configuration management module and parameter management module; The configuration management module sets four states for the configuration files, namely, published, newly added but not published, modified but not published, and deleted but not published. After a newly added configuration file or an edited or deleted published file is saved first, then its state is modified to newly added but not published, modified but not published, or deleted but not published, and then it is published uniformly and its state is modified to published; The parameter management module is used to add, define, delete, edit, list and filter configuration parameters and perform recommended value inspection.

2. The microservice configuration management system of the power Internet of Things platform according to claim 1 is characterized in that: The method for inspecting the recommended values ​​of configuration parameters in the parameter management module includes: (1) Obtain the current configuration information of all microservices; (2) For each microservice configuration, check whether each parameter has a recommended value; (3) If a parameter has a recommended value, determine whether the current value of the parameter is the same as its recommended value; (4) If the current value of the parameter is different from its recommended value, record the parameter name and the name of the microservice to which it belongs; (5) After completing the above check on each parameter of all microservices, obtain the parameter set that meets the condition (parameter value ≠ recommended value & configuration release time > 2h) in each microservice; (6) Assemble alarm information in the format of "{microservice-1:[parameter-1, parameter-2,......, parameter-n], microservice-2:[parameter-1, parameter-2,......, parameter-n]......, microservice-N:[parameter-1, parameter-2,......, parameter-n]}", and actively push this information to the Kafka message component. The power IoT platform will then forward the alarm information to other business systems. After the operation and maintenance personnel observe the alarm, they will conduct corresponding investigation and processing; (7) Repeat steps (1) to (6) above every hour.

3. The microservice configuration management system of the power Internet of Things platform according to claim 1 is characterized in that: The parameter management module is also used to verify the configuration parameters, set corresponding verification rules for different data types, and then verify whether the input configuration parameters meet the verification rules when defining parameters.

4. The microservice configuration management system of the power Internet of Things platform according to claim 1, characterized in that: The configuration management module displays and edits the configuration files in text and / or image form.

5. The microservice configuration management system of the power Internet of Things platform according to claim 4 is characterized in that: Configuration files in properties format are displayed in table form, and configuration files in yaml format are displayed in tree form.

6. The microservice configuration management system of the power Internet of Things platform according to claim 1, characterized in that: The system also includes a historical version module, which generates a historical version record each time a configuration file is released.

7. The microservice configuration management system of the power Internet of Things platform according to claim 1, characterized in that: The system also includes a template management module, which generates corresponding templates from the configuration service framework and / or component configuration definition, and adds the template to the configuration file by graphically dragging and dropping when a new configuration file is added.

8. A microservice configuration management method for a power Internet of Things platform based on the system according to any one of claims 1 to 7, characterized in that: The parameter management module is used to define, delete, edit, filter lists and inspect recommended values ​​of configuration parameters; The configuration management module manages the status of newly added, edited and / or deleted configuration files.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the computer program is loaded into the processor, the microservice configuration management method of the power Internet of Things platform according to claim 8 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the microservice configuration management method for the power Internet of Things platform according to claim 8 is implemented.

Images