CN110673881A

CN110673881A - Configuration management method and device for micro-service cluster and computer equipment

Info

Publication number: CN110673881A
Application number: CN201910841913.9A
Authority: CN
Inventors: 张明
Original assignee: Shenzhen Ping An Communication Technology Co Ltd
Current assignee: Shenzhen Ping An Communication Technology Co Ltd
Priority date: 2019-09-06
Filing date: 2019-09-06
Publication date: 2020-01-10
Anticipated expiration: 2039-09-06
Also published as: CN110673881B

Abstract

The application provides a configuration management method and device of a micro-service cluster, computer equipment and a computer readable storage medium, and relates to the technical field of micro-service architecture. And the configuration agent circularly requests the configuration center for configuration updating, and configures and caches corresponding authorization information after the latest configuration is obtained. Each micro service in the micro service cluster circularly requests the configuration update to the configuration agent in a micro service calling mode, and the configuration update related judgment and the configuration file acquisition are carried out at the configuration agent end, so that the configuration update requests which are originally required to be sent to the configuration center are greatly reduced, the load capacity of the configuration center is effectively enhanced, and the efficiency of the configuration management of each micro service is improved.

Description

Configuration management method and device for micro-service cluster and computer equipment

Technical Field

The present application relates to the field of micro service architecture technologies, and in particular, to a method and an apparatus for configuration management of a micro service cluster, and a computer device.

Background

With the increasing complexity of software systems, the user requirements and the frequent software update, configuration management gradually becomes an important control process in the software lifecycle, and plays an increasingly important role in the software development process. With the gradual development of software architecture into distributed and micro-services, a single system can be split into a plurality of micro-services, and each micro-service has its own configuration. In order to implement configuration management of a distributed system such as a microserver architecture, a configuration method for a Config-Server (configuration center) to manage a plurality of systems has been developed, for example, a configuration is stored in a Git in a file manner, a Spring Cloud Config for hot update is implemented through a message bus, or a configuration is stored in a database, and a carry-over Apollo for hot update is implemented through polling check configuration. However, in the existing configuration method, each micro service performs configuration polling to the configuration center, and when the number of the micro services is too large, the load pressure of the configuration center is too large, and corresponding configuration management cannot be performed in time.

Disclosure of Invention

The application mainly aims to provide a configuration management method, a configuration management device and computer equipment for a micro-service cluster, and aims to solve the defect that the load of a configuration center is overlarge due to the fact that update requests of an existing configuration management method are too concentrated.

In order to achieve the above object, the present application provides a method for configuration management of a microservice cluster, which is applied to a Config-Agent, wherein a single Config-Agent is used for managing a single microservice cluster, and the microservice cluster is composed of a plurality of microservices, the method comprising:

sending a first updating request to a Config-Server according to a first preset period, and judging whether the latest configuration fed back by the Config-Server is received in a first interval time period corresponding to the first preset period;

if the latest configuration fed back by the Config-Server is received, performing Portal-Server related information configuration on the latest configuration to obtain authorized latest configuration;

caching the latest authorization configuration, and receiving a second updating request sent by each micro service corresponding to the Config-Agent according to a second preset period;

screening the first micro-service which needs to be configured and updated currently from the micro-services according to the second updating requests;

and sending the latest authorization configuration to the corresponding first micro service in a second interval time period corresponding to the second preset period, and sending preset information to a second micro service after the second interval time period, wherein the second micro service is the rest micro services except the first micro service in the micro service cluster.

Further, the step of screening the first microservice currently needing configuration updating from each microservice according to each second updating request includes:

screening a plurality of initially selected microservices, of which the second configuration permission information is consistent with the corresponding second permission verification information, from each microservice according to each microservice name;

respectively judging whether the current configuration abstract of each initially selected micro service is consistent with the corresponding latest configuration abstract;

if the current configuration abstract is inconsistent with the latest configuration abstract, marking a plurality of primary micro services with inconsistent current configuration abstract and latest configuration abstract as the first micro service;

and if the current configuration abstract is consistent with the corresponding latest configuration abstract, marking the plurality of the initially selected micro services with the current configuration abstract consistent with the latest configuration abstract as the second micro services.

Further, before the step of sending a first update request to the Config-Server according to a first preset period and determining whether a latest configuration fed back by the Config-Server is received within a first interval time period corresponding to the first preset period, the method includes:

sending an initialization instruction to the micro-service cluster;

receiving feature information of each micro service fed back by the micro service cluster, wherein the feature information comprises each micro service name and a configuration abstract corresponding to each micro service name;

generating authority information corresponding to each micro service name;

and respectively performing associated entry on each authority information serving as the second authority verification information and the corresponding characteristic information of the micro service, and sending the authority information to the corresponding micro service serving as the second configuration authority information.

Further, the step of performing associated entry by using each piece of authority information as the second authority verification information and the corresponding feature information of the micro service includes:

respectively constructing a configuration database corresponding to each micro service name, and generating a mapping relation table of the micro service names and the configuration database;

taking each authority information as the second authority verification information, and associating the second authority verification information with the corresponding micro service name and the corresponding configuration abstract;

and storing the associated second authority verification information, the associated micro service names and the associated configuration abstracts into the corresponding configuration database.

Further, the step of performing Portal-Server related information configuration on the latest configuration to obtain authorized latest configuration includes:

storing the latest configuration into the corresponding configuration database according to the mapping relation table of the micro service name and the configuration database;

and respectively writing the Portal-Server related information into the latest configuration in each configuration database to obtain the authorized latest configuration, and updating the configuration abstract in the configuration database.

Further, after the step of sending the authorized latest configuration to the corresponding first microservice within a second interval time period corresponding to the second preset period, the method includes:

and controlling each first micro service to load the corresponding authorized latest configuration and delete the currently failed configuration file.

The application also provides a configuration management device of the micro-service cluster, which is applied to a Config-Agent, wherein the Config-Agent is used for managing a single micro-service cluster, the micro-service cluster is composed of a plurality of micro-services, and the configuration management device comprises:

the device comprises a judging module, a first updating module and a second updating module, wherein the judging module is used for sending a first updating request to a Config-Server according to a first preset period and judging whether the latest configuration fed back by the Config-Server is received in a first interval time period corresponding to the first preset period;

the configuration module is used for carrying out Portal-Server related information configuration on the latest configuration to obtain the authorized latest configuration if the latest configuration fed back by the Config-Server is received;

the first receiving module is used for caching the latest authorization configuration and receiving a second updating request sent by each micro-service corresponding to the Config-Agent according to a second preset period;

the screening module is used for screening the first micro-service which needs to be configured and updated currently from the micro-services according to the second updating requests;

a first sending module, configured to send the latest authorization configuration to the corresponding first micro service within a second interval time period corresponding to the second preset period, and send preset information to a second micro service after the second interval time period, where the second micro service is a remaining micro service in the micro service cluster except the first micro service.

Further, the Config-Agent prestores a microservice name, a latest configuration abstract and second permission verification information corresponding to each microservice, and the screening module includes:

the screening unit is used for screening a plurality of initially selected microservices, of which the second configuration permission information is consistent with the corresponding second permission verification information, from each microservice according to the microservice name;

a judging unit, configured to respectively judge whether the current configuration abstract of each of the primarily selected microservices is consistent with the corresponding latest configuration abstract;

a first marking unit, configured to mark, if the current configuration summary is inconsistent with the latest configuration summary, the first microservices of the plurality of primary microservices with inconsistent current configuration summary and latest configuration summary as the first microservices;

and the second marking unit is used for marking the plurality of the initially selected micro services of which the current configuration abstract is consistent with the latest configuration abstract as the second micro services if the currently selected micro services are consistent with the latest configuration abstract.

Further, the configuration management apparatus further includes:

a second sending module, configured to send an initialization instruction to the micro service cluster;

a second receiving module, configured to receive feature information of each micro service fed back by the micro service cluster, where the feature information includes each micro service name and a configuration abstract corresponding to each micro service name;

the generating module is used for generating authority information corresponding to each micro service name;

and the association module is used for performing association entry on each piece of authority information serving as the second authority verification information and the corresponding feature information of the micro service respectively, and sending the authority information to the corresponding micro service serving as the second configuration authority information.

Further, the association module includes:

the construction unit is used for respectively constructing a configuration database corresponding to each micro service name and generating a mapping relation table of the micro service name and the configuration database;

the association unit is used for associating each authority information serving as the second authority verification information with the corresponding micro service name and the corresponding configuration abstract;

and the entry unit is used for storing the associated second authority verification information, the associated micro service names and the associated configuration abstracts into the corresponding configuration database.

Further, the configuration module includes:

the storage unit is used for storing the latest configuration into the corresponding configuration database according to the mapping relation table of the micro service name and the configuration database;

and the writing unit is used for respectively writing the Portal-Server related information into the latest configuration in each configuration database to obtain the authorized latest configuration and updating the configuration abstract in the configuration database.

Further, the configuration management apparatus further includes:

and the control module is used for controlling each first micro-service to load the corresponding authorized latest configuration and delete the current invalid configuration file.

The present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any one of the above methods when executing the computer program.

The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method of any of the above.

In the configuration management method, device and computer equipment for the micro-service cluster, the Config-Server is provided with a plurality of Config-agents, and a single Config-Agent correspondingly manages a single micro-service cluster. And the Config-Agent circularly requests the configuration update to the Config-Server, and configures and caches corresponding authorization information after the latest configuration is obtained. Then, each micro service in the micro service cluster circularly requests the Config-Agent for configuration updating in a micro service calling mode, and the related judgment of the configuration updating and the acquisition of the configuration file are carried out at the Config-Agent end, so that the configuration updating requests which are originally required to be sent to the Config-Server are greatly reduced, the load capacity of the Config-Server is effectively increased, and the efficiency of configuration management of each micro service is improved.

Drawings

FIG. 1 is a schematic diagram illustrating steps of a method for configuration management of a microservice cluster according to an embodiment of the present application;

fig. 2 is a block diagram of an overall structure of a configuration management apparatus of a microservice cluster in an embodiment of the present application;

fig. 3 is a block diagram schematically illustrating a structure of a computer device according to an embodiment of the present application.

The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

Referring to fig. 1, in an embodiment of the present application, a method for configuration management of a microservice cluster is provided, where the method is applied to a Config-Agent, and a single Config-Agent is used to manage a single microservice cluster, where the microservice cluster is composed of several microservices, and the method includes:

s1: sending a first updating request to a Config-Server according to a first preset period, and judging whether the latest configuration fed back by the Config-Server is received in a first interval time period corresponding to the first preset period;

s2: if the latest configuration fed back by the Config-Server is received, performing Portal-Server related information configuration on the latest configuration to obtain authorized latest configuration;

s3: caching the latest authorization configuration, and receiving a second updating request sent by each micro service corresponding to the Config-Agent according to a second preset period;

s4: screening the first micro-service which needs to be configured and updated currently from the micro-services according to the second updating requests;

s5: and sending the latest authorization configuration to the corresponding first micro service in a second interval time period corresponding to the second preset period, and sending preset information to a second micro service after the second interval time period, wherein the second micro service is the rest micro services except the first micro service in the micro service cluster.

In this embodiment, one micro service cluster is correspondingly provided with one Config-Agent (configuration Agent), the micro service cluster is composed of a plurality of underlying micro services, the Config-Agent is used for managing configuration update of each micro service on line, and data exchange with each micro service is performed in a closed internal environment. The plurality of Config-agents are respectively connected with a Config-Server (configuration center) and obtain updating configuration from the Config-Server, wherein the configuration center stores any configuration content realized by the extended micro-service, such as system fault-tolerant configuration, address configuration of a log center, address configuration of a database and the like. The data interaction mode between each Config-Agent and the Config-Server is the same, and one of the Config-agents is taken as an example for the description in this embodiment. The method comprises the steps that a first updating request is sent to a Config-Server by the Config-Agent according to a first preset period in a circulating mode, wherein the first updating request carries a current configuration abstract and first configuration authority information of each micro-service, and the configuration abstract is similar to version information. After receiving the first updating request, the Config-Server firstly verifies the first configuration permission information according to the first permission verification information generated in advance, judges whether the first configuration permission information and the first configuration permission information are consistent, and if the first configuration permission information and the first configuration permission verification information are consistent, the Config-Server indicates that the Config-Agent has the permission to acquire the updating configuration from the Config-Server. Then, the current configuration abstracts carried by the configuration abstract are respectively compared with the corresponding latest configuration abstracts, so that the latest configuration which needs to be updated in the current request is screened out, and the latest configuration is sent to the Config-Agent within the interval time of the first preset period. If the latest configuration needing to be updated is not screened in the first time, the request is suspended, and if the latest configuration is not found after the interval time corresponding to the first preset period, the Config-Server feeds back a status code indicating no update to the Config-Agent. After receiving the latest configuration returned by the Config-Server, the Config-Agent needs to configure the relevant address and authorization information of the Portal-Server for the latest configuration to ensure the security of data, obtain the authorized latest configuration, then cache the authorized latest configuration, and update the latest configuration abstract of the corresponding microservice recorded inside. Meanwhile, the Config-Agent also needs to release the thread sending the first update request to the Config-Server, so as to save resources. And each micro service in the micro service cluster corresponding to the Config-Agent sends a second updating request to the Config-Agent according to a second preset period, wherein each second updating request carries a current configuration abstract, second configuration request permission information and a micro service name corresponding to the micro service, and each micro service requests the Config-Agent in a mode of carrying out micro service calling through a default Config-Agent service name. After receiving each second updating request, the Config-Agent firstly compares the pre-generated second permission verification information with the second configuration request permission information, and verifies the configuration acquisition permission of the microservice. After the authority verification is passed, screening the first micro-service which needs to be configured and updated in the current request according to the current configuration abstract from each micro-service, specifically, comparing the current configuration abstract of each micro-service with the configuration abstract of the latest configuration authorized in the Config-Agent, thereby determining one or more micro-services of which the current configuration abstract and the configuration abstract of the latest configuration authorized in the micro-service cluster are inconsistent, namely the first micro-service. And then, sending the latest configuration of the authorization to the first micro service corresponding to the micro service name within the interval time corresponding to the second preset period, and sending preset information to the second micro service after the interval time corresponding to the second preset period, wherein the second micro service is the rest micro services except the first micro service in the micro service cluster, and the preset information is a status code indicating no update. After receiving the authorized latest configuration, the microservice realizes the hot update of the configuration by reloading the configuration for refreshing.

s401: screening a plurality of initially selected microservices, of which the second configuration permission information is consistent with the corresponding second permission verification information, from each microservice according to each microservice name;

s402: respectively judging whether the current configuration abstract of each initially selected micro service is consistent with the corresponding latest configuration abstract;

s403: if the current configuration abstract is inconsistent with the latest configuration abstract, marking a plurality of primary micro services with inconsistent current configuration abstract and latest configuration abstract as the first micro service;

s404: and if the current configuration abstract is consistent with the corresponding latest configuration abstract, marking the plurality of the initially selected micro services with the current configuration abstract consistent with the latest configuration abstract as the second micro services.

In this embodiment, the Config-Agent stores therein a micro service name, a latest configuration summary and pre-generated second permission verification information corresponding to each micro service in the micro service cluster, and the second update request carries the micro service name, the second configuration permission information and the current configuration summary corresponding to each micro service, where the second configuration permission information may be a configuration request token. The Config-Agent compares each piece of second configuration authority information with corresponding second authority verification information according to identification information of each micro service, such as a micro service name, and judges whether the two pieces of second configuration authority information are consistent. And if the second configuration authority information is consistent with the corresponding second authority information, judging that the corresponding micro service has the authority to acquire the updating configuration from the Config-Agent, and marking the updating configuration as the primary selection micro service. Then, the Config-Agent compares the current configuration abstract of each initially selected microservice with the corresponding latest configuration abstract respectively, and judges whether the two are consistent. And the Config-Agent marks one or more primary microservices of which the current configuration abstract is inconsistent with the latest configuration abstract as a first microservice so as to send a corresponding file packet which authorizes the latest configuration in a later period. And, the Config-Agent marks one or more micro-services of which the current configuration abstract is consistent with the latest abstract as second micro-services so as to send preset information later.

s6: sending an initialization instruction to the micro-service cluster;

s7: receiving feature information of each micro service fed back by the micro service cluster, wherein the feature information comprises each micro service name and a configuration abstract corresponding to each micro service name;

s8: generating authority information corresponding to each micro service name;

s9: and respectively performing associated entry on each authority information serving as the second authority verification information and the corresponding characteristic information of the micro service, and sending the authority information to the corresponding micro service serving as the second configuration authority information.

In this embodiment, the Config-Agent corresponds to a single micro-service cluster, and is initialized before use, so that the Config-Agent matches parameters of each micro-service in the micro-service cluster. And the Config-Agent sends an initialization instruction to the micro-service cluster, and the micro-service cluster automatically sends the characteristic information of each micro-service in the cluster to the Config-Agent after receiving the initialization instruction. The feature information of the microservice includes a microservice name and a configuration abstract of each current configuration, such as a name of the configuration and corresponding version information. After receiving the feature information of each micro service, the Config-Agent first generates corresponding authority information, such as token, according to each micro service name, and is used for subsequently verifying whether the micro service has a corresponding configuration update authority. And then, the Config-Agent associates the currently generated authority information as second authority verification information with the characteristic information of the corresponding micro-service and records the second authority verification information into an internal database, and sends the authority information to the micro-service cluster, and the micro-service cluster distributes the authority information to the corresponding micro-service as second configuration authority information according to the micro-service name to complete the whole initialization of the Config-Agent.

s901: respectively constructing a configuration database corresponding to each micro service name, and generating a mapping relation table of the micro service names and the configuration database;

s902: taking each authority information as the second authority verification information, and associating the second authority verification information with the corresponding micro service name and the corresponding configuration abstract;

s903: and storing the associated second authority verification information, the associated micro service names and the associated configuration abstracts into the corresponding configuration database.

In this embodiment, a separate configuration database is built in the Config-Agent according to different micro services, so as to store relevant data of different micro services, such as a downloaded file package for updating configuration, a configuration abstract, a micro service name, and the like, respectively, which is convenient for management. When the Config-Agent constructs each configuration database, a mapping relation table of the micro-service names and the configuration database is generated, and the configuration database of the corresponding micro-service can be inquired according to the micro-service names. For example, microservice a corresponds to configuration database a, and microservice B corresponds to configuration database B. After the configuration database is built, the Config-Agent uses the authority information of each micro service generated at the current time as second authority verification information, associates the second authority verification information with the characteristic information of the corresponding micro service, namely information such as a micro service name and a configuration abstract, and stores the second authority verification information in the corresponding configuration database.

s201: storing the latest configuration into the corresponding configuration database according to the mapping relation table of the micro service name and the configuration database;

s203: and respectively writing the Portal-Server related information into the latest configuration in each configuration database to obtain the authorized latest configuration, and updating the configuration abstract in the configuration database.

In this embodiment, after acquiring one or more latest configurations to be updated, the Config-Agent stores each latest configuration in the configuration database corresponding to each microservice according to the mapping relationship table between the microservice name and the configuration database, so as to facilitate acquisition of configurations in subsequent microservice updates. After the storage is finished, in order to ensure the safety of data, the Config-Agent configures the relative address and authorization information of the Portal-Server for each latest configuration to obtain the authorized latest configuration, and updates the configuration abstract in the current database according to the abstract information of the latest configuration to finish all data updating of the configuration.

s10: and controlling each first micro service to load the corresponding authorized latest configuration and delete the currently failed configuration file.

In this embodiment, the authorized latest configuration carries the configuration name, and after the Config-Agent sends the authorized latest configuration to the corresponding first microservice, the first microservice reloads the received authorized latest configuration according to the relevant control instruction, and deletes the configuration file currently in the failure state according to the configuration name, so as to complete configuration update of the first microservice.

In the configuration management method for a microserver provided by this embodiment, a Config-Server is provided with a plurality of Config-agents, and a single Config-Agent correspondingly manages a single microserver. And the Config-Agent circularly requests the configuration update to the Config-Server, and configures and caches corresponding authorization information after the latest configuration is obtained. Then, each micro service in the micro service cluster circularly requests the Config-Agent for configuration updating in a micro service calling mode, and the related judgment of the configuration updating and the acquisition of the configuration file are carried out at the Config-Agent end, so that the configuration updating requests which are originally required to be sent to the Config-Server are greatly reduced, the load capacity of the Config-Server is effectively increased, and the efficiency of configuration management of each micro service is improved.

Referring to fig. 2, in an embodiment of the present application, a configuration management apparatus for a microservice cluster is further provided, where the configuration management apparatus is applied to a Config-Agent, a single Config-Agent is used to manage a single microservice cluster, and the microservice cluster is composed of several microservices, and the configuration management apparatus includes:

the system comprises a judging module 1, a first updating module and a second updating module, wherein the judging module is used for sending a first updating request to a Config-Server according to a first preset period and judging whether the latest configuration fed back by the Config-Server is received in a first interval time period corresponding to the first preset period;

the configuration module 2 is used for carrying out Portal-Server related information configuration on the latest configuration to obtain the authorized latest configuration if the latest configuration fed back by the Config-Server is received;

the first receiving module 3 is configured to cache the latest authorization configuration, and receive a second update request sent by each microservice corresponding to the Config-Agent according to a second preset period;

the screening module 4 is configured to screen, according to each second update request, a first microservice that needs to be configured and updated currently from each microservice;

a first sending module 5, configured to send the latest authorization configuration to the corresponding first micro service in a second interval time period corresponding to the second preset period, and send preset information to a second micro service after the second interval time period, where the second micro service is the rest micro services except the first micro service in the micro service cluster.

Further, the Config-Agent prestores a microservice name, a latest configuration summary and second permission verification information corresponding to each microservice, and the screening module 4 includes:

Further, the configuration management apparatus further includes:

a second sending module 6, configured to send an initialization instruction to the micro service cluster;

a second receiving module 7, configured to receive feature information of each micro service fed back by the micro service cluster, where the feature information includes each name of the micro service and a corresponding configuration abstract;

a generating module 8, configured to generate authority information corresponding to each micro service name;

and the association module 9 is configured to perform association entry on each piece of authority information as the second authority verification information and the corresponding feature information of the micro service, and send the authority information to the corresponding micro service as the second configuration authority information.

Further, the association module 9 includes:

Further, the configuration module 2 includes:

Further, the configuration management apparatus further includes:

and the control module 10 is configured to control each of the first micro services to load the corresponding authorized latest configuration, and delete the currently failed configuration file.

In the configuration management device for a microserver according to this embodiment, a Config-Server is provided with a plurality of Config-agents, and a single Config-Agent correspondingly manages a single microserver. And the Config-Agent circularly requests the configuration update to the Config-Server, and configures and caches corresponding authorization information after the latest configuration is obtained. Then, each micro service in the micro service cluster circularly requests the Config-Agent for configuration updating in a micro service calling mode, and the related judgment of the configuration updating and the acquisition of the configuration file are carried out at the Config-Agent end, so that the configuration updating requests which are originally required to be sent to the Config-Server are greatly reduced, the load capacity of the Config-Server is effectively increased, and the efficiency of configuration management of each micro service is improved.

Referring to fig. 3, a computer device, which may be a server and whose internal structure may be as shown in fig. 3, is also provided in the embodiment of the present application. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer designed processor is used to provide computational and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as a configuration database. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to realize a configuration management method of a micro-service cluster, and the method is applied to a Config-Agent, wherein a single Config-Agent is used for managing a single micro-service cluster, and the micro-service cluster consists of a plurality of micro-services.

The processor executes the steps of the configuration management method of the microservice cluster:

s6: sending an initialization instruction to the micro-service cluster;

s8: generating authority information corresponding to each micro service name;

An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored thereon, and when the computer program is executed by a processor, the computer program implements a method for configuration management of a microservice cluster, where the method is applied to a Config-Agent, and a single Config-Agent is used to manage a single microservice cluster, where the microservice cluster is composed of a plurality of microservices, and specifically includes:

s6: sending an initialization instruction to the micro-service cluster;

s8: generating authority information corresponding to each micro service name;

It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware associated with instructions of a computer program, which may be stored on a non-volatile computer-readable storage medium, and when executed, may include processes of the above embodiments of the methods. Any reference to memory, storage, database, or other medium provided herein and used in the examples may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (SSRSDRAM), Enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.

The above description is only for the preferred embodiment of the present application and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are intended to be included within the scope of the present application.

Claims

1. A configuration management method for micro-service cluster is characterized in that the method is applied to a Config-Agent, a single Config-Agent is used for managing a single micro-service cluster, and the micro-service cluster is composed of a plurality of micro-services, and the method comprises the following steps:

2. The method for configuration management of a microservice cluster according to claim 1, wherein the Config-Agent pre-stores a microservice name, a latest configuration abstract and second authority verification information corresponding to each microservice, the second update request carries the microservice name, the second configuration authority information and a current configuration abstract corresponding to the microservice, and the step of screening the first microservice currently requiring configuration update from each microservice according to each second update request includes:

3. The method according to claim 2, wherein before the step of sending a first update request to the Config-Server according to a first preset period and determining whether a latest configuration fed back by the Config-Server is received within a first interval time period corresponding to the first preset period, the method comprises:

sending an initialization instruction to the micro-service cluster;

generating authority information corresponding to each micro service name;

4. The method for configuration management of a microservice cluster according to claim 3, wherein the step of performing associated entry of each piece of authority information as the second authority verification information and the corresponding feature information of the microservice comprises:

5. The method of claim 4, wherein the step of configuring the latest configuration with Portal-Server related information to obtain an authorized latest configuration comprises:

6. The method for configuration management of a microservice cluster according to claim 1, wherein the step of sending the authorized latest configuration to the corresponding first microservice within a second interval time period corresponding to the second preset period comprises, after the step of sending the authorized latest configuration to the corresponding first microservice:

7. A configuration management apparatus for a microservice cluster, the apparatus being applied to a Config-Agent, a single Config-Agent being used to manage a single microservice cluster, the microservice cluster being composed of several microservices, the configuration management apparatus comprising:

8. The apparatus of claim 7, wherein the Config-Agent pre-stores a microservice name, a latest configuration digest, and second permission verification information corresponding to each microservice, and the screening module comprises:

9. A computer device comprising a memory and a processor, the memory having stored therein a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.