CN112306551A - Method, system and device for acquiring historical configuration information - Google Patents

Abstract

The application relates to a method, a system, a device, a computer device and a storage medium for acquiring historical configuration information. The method comprises the following steps: the method comprises the steps that a configuration information management server responds to a historical configuration information acquisition request triggered by a client and determines a configuration identifier and a first configuration version identifier corresponding to historical configuration information to be acquired; querying a revision identification matched with the configuration identification and the first configuration version identification from a revision identification library; querying historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base to serve as historical configuration information to be acquired; and returning the historical configuration information to be acquired to the client. By adopting the method, the historical configuration information can be inquired and compared through the revision identification after the configuration information is covered through the combination of the configuration information management server and the revision identification library and the configuration information library, so that the acquisition efficiency of the historical configuration information is improved.

Description

Method, system and device for acquiring historical configuration information

Technical Field

The present application relates to the field of information acquisition technologies, and in particular, to a method, a system, an apparatus, a computer device, and a storage medium for acquiring historical configuration information.

Background

With the development of information technology, a microservice architecture system composed of a plurality of small components or services which are loosely coupled and can be independently deployed appears, and in the development process, in order to distinguish a testing environment from a formal environment or frequently read or modify some contents, a configuration file is often required to be introduced to assist the system in development.

At present, configuration files are often modified through editing in a management system, however, on-line configuration may have incomplete testing or modification of the configuration files under the condition that multiple persons edit and cover each other at the same time, if misoperation occurs, historical information is difficult to compare, and the historical configuration information acquisition efficiency is low.

Disclosure of Invention

In view of the above, it is necessary to provide a method, a system, an apparatus, a computer device and a storage medium for acquiring historical configuration information.

A historical configuration information acquisition method is applied to a configuration information management server and comprises the following steps:

responding to a historical configuration information acquisition request triggered by a client, and determining a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired;

querying a revision identification matching the configuration identification and the first configuration version identification from a revision identification repository;

querying historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base to serve as the historical configuration information to be acquired;

and returning the historical configuration information to be acquired to the client.

In one embodiment, the method further comprises: if the revision identification is not stored in the revision identification library, acquiring the maximum configuration version identification corresponding to the configuration identification from the configuration information library as a second configuration version identification; if the first configuration version identification is smaller than the second configuration version identification, acquiring a maximum configuration version identification corresponding to the configuration identification stored in the revision identification library as a third configuration version identification; wherein the second configuration version identification is greater than the third configuration version identification; traversing the configuration version identifiers between the second configuration version identifier and the third configuration version identifier according to a descending order to obtain a plurality of configuration version identifiers; if the target configuration version identifications with the same first configuration version identification are stored in the plurality of configuration version identifications, acquiring target revision identifications corresponding to the target configuration version identifications, and taking the target revision identifications and the configuration information corresponding to the configuration identifications as the historical configuration information to be acquired.

In one embodiment, after obtaining the plurality of configuration version identifiers, the method includes: determining revision identifications corresponding to the configuration version identifications; and storing the configuration identification, the configuration version identifications and the revision identification corresponding to the configuration version identifications into the revision identification library.

In one embodiment, the method further comprises: obtaining a plurality of historical configuration information by using revision identifications corresponding to the configuration version identifications and the configuration identifications; acquiring a compression identifier of each historical configuration information; and if the compression identifier is that the historical configuration information is compressed, stopping traversing the configuration version identifier between the second configuration version identifier and the third configuration version identifier.

In one embodiment, the method further comprises the following steps: if the target configuration version identifier is not stored in the plurality of configuration version identifiers, determining that the state information of the historical configuration information to be acquired is that the historical configuration information to be acquired is compressed; and/or if the compression identifier of the corresponding historical configuration information indicates that the historical configuration information is compressed, confirming that the state information of the historical configuration information to be acquired is that the historical configuration information to be acquired is compressed; and returning the state information to the client.

In one embodiment, after acquiring the maximum configuration version identifier corresponding to the configuration identifier from the configuration information base as the second configuration version identifier, the method further includes: if the first configuration version identification is larger than the second configuration version identification, determining that the state information of the historical configuration information to be acquired does not exist; and returning the state information to the client.

In one embodiment, the method further comprises: responding to a configuration information storage request triggered by the client, and determining a configuration identifier to be stored and configuration information to be stored, which correspond to the configuration information storage request; storing the configuration identifier to be stored and the configuration information to be stored into the configuration information base, and inquiring a fourth configuration version identifier corresponding to the configuration information to be stored and a current revision identifier of the configuration information base in the configuration information base based on the configuration identifier to be stored; and storing the configuration identifier to be stored, the fourth configuration version identifier and the current revision identifier into the revision identifier library.

In one embodiment, the configuration information storage request further carries a user token for identifying a user identity; the storing the configuration identifier to be saved and the configuration information to be saved into the configuration information base includes: acquiring user information corresponding to the user token, performing authority verification on the user information, and acquiring an authority verification identifier of the user information; if the authority verification identification passes verification, storing the configuration identification to be stored and the configuration information to be stored into the configuration information base; the storing the configuration identifier to be saved, the fourth configuration version identifier and the current revision identifier into the revision identifier library includes: and storing the user information, the configuration identifier to be stored, the fourth configuration version identifier and the current revision identifier into the revision identifier library.

In one embodiment, the method further comprises: responding to a historical configuration list acquisition request triggered by the client 1, and determining a list configuration identifier corresponding to a historical configuration list to be acquired; querying a historical configuration list corresponding to the list configuration identifier by using the revision identifier library to serve as a historical configuration list to be acquired; and returning the historical configuration list to be acquired to the client.

A historical configuration information acquisition system comprising: the system comprises a configuration information management server, a client, a revision identification library and a configuration information library, wherein the client, the revision identification library and the configuration information library are in communication connection with the configuration information management server; wherein the content of the first and second substances,

the client is used for triggering a historical configuration information acquisition request and sending the historical configuration information acquisition request to the configuration information management server;

the configuration information management server is used for responding to the historical configuration information acquisition request, determining a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired, and inquiring a revision identifier matched with the configuration identifier and the first configuration version identifier from a revision identifier library;

the configuration information management server is further configured to query historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base, and use the historical configuration information as the historical configuration information to be acquired; returning the historical configuration information to be acquired to the client;

and the client is used for receiving the historical configuration information to be acquired.

A historical configuration information acquisition apparatus applied to a configuration information management server, the apparatus comprising:

the configuration request acquisition module is used for responding to a historical configuration information acquisition request triggered by a client and determining a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired;

the revision identification acquisition module is used for inquiring revision identifications matched with the configuration identifications and the first configuration version identifications from a revision identification library;

the configuration information acquisition module is used for inquiring historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base to be used as the historical configuration information to be acquired;

and the configuration information sending module is used for returning the historical configuration information to be acquired to the client.

A computer device comprising a memory storing a computer program and a processor implementing the steps of the above method when executing the computer program.

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 above-mentioned method.

According to the historical configuration information acquisition method, the historical configuration information acquisition system, the historical configuration information acquisition device, the computer equipment and the storage medium, the configuration information management server responds to a historical configuration information acquisition request triggered by the client and determines the configuration identifier and the first configuration version identifier corresponding to the historical configuration information to be acquired; querying a revision identification matched with the configuration identification and the first configuration version identification from a revision identification library; querying historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base to serve as historical configuration information to be acquired; and returning the historical configuration information to be acquired to the client. The historical configuration information acquisition method can be used for inquiring the historical configuration information through the revision identification after the configuration information is covered through the combination of the configuration information management server, the revision identification library and the configuration information library, so that the historical configuration information acquisition efficiency is improved.

Drawings

FIG. 1 is a diagram of an application environment of a historical configuration information acquisition method in one embodiment;

FIG. 2 is a flowchart illustrating a method for obtaining historical configuration information according to an embodiment;

FIG. 3 is a schematic diagram illustrating a process of obtaining historical configuration information to be obtained in one embodiment;

FIG. 4 is a schematic flow chart illustrating storing configuration information in one embodiment;

FIG. 5 is a timing diagram illustrating a process for storing version information in an exemplary application;

FIG. 6 is a flow diagram illustrating a process for saving version information in an application example;

FIG. 7 is a timing diagram illustrating a process for querying historical versions of configurations in an example application;

FIG. 8 is a flow diagram illustrating a process for querying historical versions of a configuration in an application example;

FIG. 9 is a diagram showing the structure of a historical-configuration-information acquisition system in one embodiment;

FIG. 10 is a block diagram showing the configuration of a history configuration information acquiring apparatus according to an embodiment;

FIG. 11 is a diagram illustrating an internal structure of a computer device in one embodiment.

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.

The historical configuration information acquisition method provided by the application can be applied to the application environment shown in fig. 1. Wherein, the client 101 communicates with the configuration information management server 102 through a network, and the configuration information management server 102 communicates with the revision identification repository 103 and the configuration information repository 104 through a network. Specifically, the client 101 may send a historical configuration information acquisition request for acquiring the historical configuration information to be acquired to the configuration information management server 102 through the network, and the configuration information management server 102 may respond to the request to obtain the configuration identifier and the configuration version identifier corresponding to the historical configuration information to be acquired, obtain the revision identifier of the configuration information base 104 adapted to the configuration identifier and the configuration version identifier through the revision identifier base 103, and query the configuration information base 104 using the configuration identifier and the revision identifier to obtain the corresponding historical configuration information as the historical configuration information to be acquired and return the historical configuration information to the client 101. The client 101 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the configuration information management server 102, the revision identification library 103, and the configuration information library 104 may be implemented by independent servers or a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 2, a method for obtaining historical configuration information is provided, which is described by taking the method as an example applied to the configuration information management server 102 in fig. 1, and includes the following steps:

in step S201, the configuration information management server 102 determines, in response to a historical configuration information acquisition request triggered by the client 101, a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired.

The client 101 is a client of a user that needs to obtain historical configuration information, the historical configuration information to be obtained is historical configuration information that the user wants to obtain through the client 101, and the configuration identifier may be an identifier for identifying a configuration file, may correspond to a plurality of configuration version identifiers, and may be represented by different configuration version numbers, for example, for a configuration file of a certain configuration identifier a, multiple configurations may be performed, so that the configuration version identifiers V1, V2, V3, and the like may be corresponding. Specifically, the user may log in the configuration information management server 102 through the client 101 to query the historical configuration information to be acquired, and in this way, the triggered historical configuration information acquisition request may be transmitted to the configuration information management server 102. After obtaining the historical configuration information acquisition request, the configuration information management server 102 may respond to the request, so as to extract a configuration identifier corresponding to the historical configuration information to be acquired and a first configuration version identifier, where the first configuration version identifier is a configuration version identifier corresponding to the historical configuration information to be acquired.

In step S202, the configuration information management server 102 inquires of the revision identification matching the configuration identification and the first configuration version identification from the revision identification repository 103.

The revision identification may be a revision number of the configuration information base 104, and whenever the configuration file changes, the revision identification of the configuration information base 104 also changes. The revision identification library 103 may be a sql database or a mysql database, and the revision identification library 103 stores a plurality of configuration version identifications stored by each configuration identification and revision identifications corresponding to each configuration version identification, so that the configuration information management server 102 may query the revision identification library 103 by using the configuration identifications and the first configuration version identification to obtain corresponding revision identifications.

Step S203, the configuration information management server 102 inquires the historical configuration information corresponding to the revision identification and the configuration identification from the configuration information base 104 as the historical configuration information to be acquired;

in step S204, the configuration information management server 102 returns the historical configuration information to be acquired to the client 101.

The configuration information base 104 may be an etcd database, which stores multiple sets of historical configuration information corresponding to each configuration identifier, and supports multi-version concurrency control, so that even if the configuration version identifier is covered, all historical configuration information of the configuration identifier from creation to deletion can be queried through the revision identifier and the configuration identifier. Specifically, the configuration information management server 102 may query the configuration information base 104 by using the revision identification obtained in step S202 and the configuration identification corresponding to the historical configuration information to be acquired, and use the obtained historical configuration information as the historical configuration information to be acquired, which is required to be obtained by the client 101, and return the obtained historical configuration information to the client 101.

In the historical configuration information acquisition method, the configuration information management server 102 responds to a historical configuration information acquisition request triggered by the client 101 and determines a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired; querying a revision identification matching the configuration identification and the first configuration version identification from a revision identification repository 103; querying historical configuration information corresponding to the revision identification and the configuration identification from the configuration information base 104 as historical configuration information to be acquired; and returning the historical configuration information to be acquired to the client 101. According to the historical configuration information acquisition method, the configuration information management server 102, the revision identification library 103 and the configuration information library 104 are combined, and after the configuration information is covered, the historical configuration information can be inquired through the revision identification for comparison, so that the historical configuration information acquisition efficiency is improved.

In one embodiment, as shown in fig. 3, since the configuration of the system may be directly performed through the configuration information base 104, there may be a case where the revision identification base 103 does not store the latest configuration version identification, the historical configuration information obtaining method may further include:

step S301, if the revision identification is not stored in the revision identification library 103, the configuration information management server 102 obtains the maximum configuration version identification corresponding to the configuration identification from the configuration information library 104 as the second configuration version identification;

step S302, if the first configuration version identification is smaller than the second configuration version identification, the configuration information management server 102 obtains the maximum configuration version identification corresponding to the configuration identification stored in the revision identification library 103 as a third configuration version identification; and the second configuration version identification is larger than the third configuration version identification.

Since this is the case where the revision identification repository 103 does not store the latest configuration version identification, the maximum configuration version identification stored in the revision identification repository 103, i.e., the third configuration version identification, is necessarily smaller than the actual latest configuration version identification stored in the configuration information repository 104, i.e., the second configuration version identification. Specifically, if the revision identification is not stored in the revision identification library 103, it is possible that the first configuration version identification is located between the second configuration version identification and the third configuration version identification, and therefore the configuration information management server 102 needs to compare the sizes of the first configuration version identification and the second configuration version identification first, and acquire the third configuration version identification if the first configuration version identification is smaller than the second configuration version identification.

If the first configuration version identifier is larger than the second configuration version identifier, it indicates that the configuration version identifier is an incorrect configuration version identifier, so the configuration information management server 102 directly determines that the status information of the historical configuration information to be acquired does not exist the historical configuration information to be acquired, and feeds back the historical configuration information not to be acquired to the client 101.

Step S303, the configuration information management server 102 traverses the configuration version identifiers between the second configuration version identifier and the third configuration version identifier in a descending order to obtain a plurality of configuration version identifiers.

Specifically, the configuration information management server 102 may traverse all the configuration version identifiers between the second configuration version identifier and the third configuration version identifier based on the second configuration version identifier and the third configuration version identifier, and arrange them in a descending order, thereby obtaining a plurality of configuration version identifiers. For example, the second configuration version identification may be V5, and the third configuration version identification may be V2, and the plurality of configuration version identifications may include V3 and V4. The configuration information management server 102 may perform a subtraction process on the configuration version identifiers in sequence from the second configuration version identifier until the configuration version identifiers reach the third configuration version identifier.

Step S304, if the target configuration version identifiers with the same first configuration version identifier are stored in the plurality of configuration version identifiers, the configuration information management server 102 obtains the target revision identifier corresponding to the target configuration version identifier, and uses the target revision identifier and the configuration information corresponding to the configuration identifier as the historical configuration information to be obtained.

If the target configuration version identifiers with the same first configuration version identifier are stored in the obtained configuration version identifiers, the configuration information management server 102 may determine the target revision identifiers corresponding to the target configuration version identifiers, for example, by looking up a table, when the system configuration is directly completed through the configuration information base 104 each time, the configuration information base 104 may record the current configuration version identifiers and the corresponding revision identifiers in a table form, after the configuration information management server 102 finds the target configuration version identifiers, the corresponding target revision identifiers may be found by using the table, and finally, the configuration information corresponding to the configuration identifiers and the target revision identifiers is used as the historical configuration information to be obtained.

Further, after step S303, the method may further include: the configuration information management server 102 determines revision identifications corresponding to the configuration version identifications; the configuration identifier, each configuration version identifier and the revision identifier corresponding to each configuration version identifier are stored in the revision identifier repository 103.

In addition, after obtaining a plurality of configuration version identifiers, the configuration information management server 102 may determine the revision identifier corresponding to each configuration version identifier, and the determination process may be performed not only by the above-mentioned table lookup, but also by obtaining the revision identifier corresponding to the second configuration version identifier and corresponding to the last modification of the configuration identifier, and queries the configuration information base 104 with the configuration identifier and the last revision identifier of the revision identifier that was last modified by the configuration identifier, thereby obtaining the historical configuration information as the historical configuration information of the last configuration version identification of the second configuration version identification, and meanwhile, a revision identification corresponding to the last modification of the configuration identification and corresponding to the last configuration identification of the second configuration identification is obtained, and the process is repeated until the last configuration identification is the third configuration identification, so that the revision identification corresponding to each configuration identification can be obtained.

For example: the third configuration version identifier for the configuration identifier a is V2, the second configuration version identifier is V5, and each modification of the configuration file includes that the configuration identifier a changes to the configuration version identifier V3, the revision identifier is modified to R1, the configuration identifier B changes to the configuration version identifier V1, the revision identifier R2, the configuration identifier a changes to the configuration version identifier V4, the revision identifier R3, the configuration identifier B changes to the configuration version identifier V2, the revision identifier R4, the configuration identifier a changes to the configuration version identifier V5, and the revision identifier R5. Then the revision identification of the last modification corresponding to the second configuration version identification, i.e. R5, for the configuration identification a may be obtained first, and the last revision identification, i.e. R4, of R5 is queried with the configuration identification a in the configuration information base 104, and the obtained historical configuration information may be used as the historical configuration information corresponding to the configuration version identification V4 in the configuration identification a, and the revision identification of the last modification corresponding to the configuration version identification V4, i.e. R3, may also be obtained, and then the above-mentioned process is repeated to obtain the revision identification of the last modification corresponding to V3 as R1, and obtain the historical configuration information of V3.

Finally, after the configuration information management server 102 obtains the revision identification of the last modification corresponding to each configuration version identification, the configuration identification, each configuration version identification, and the revision identification of the last modification corresponding to each configuration version identification may be stored in the revision identification library 103 for filing.

In addition, the historical configuration information acquisition method may further include: the configuration information management server 102 obtains a plurality of historical configuration information by using the revision identification and the configuration identification corresponding to each configuration version identification; acquiring a compression identifier of each historical configuration information; and if the compression identifier is that the historical configuration information is compressed, stopping traversing the configuration version identifiers between the second configuration version identifier and the third configuration version identifier.

Specifically, after the configuration information management server 102 obtains the revision identifier corresponding to each configuration version identifier, a plurality of pieces of historical configuration information can be obtained by using the revision identifier and the configuration identifier, and at the same time, a compression identifier of each piece of historical configuration information can be obtained, the compression identifier is used for identifying whether the historical configuration information is compressed, and if the historical configuration information is compressed, the configuration information management server 102 stops traversing the process of traversing the configuration version identifiers between the second configuration version identifier and the third configuration version identifier.

For example, if the second configuration version id may be V5 and the third configuration version id may be V2, the traversal procedure is in the order of V5-V4-V3-V2, and if the historical configuration information corresponding to V3 is found to be compressed, the traversal procedure is directly stopped.

Therefore, in the above case, a situation may occur that the first configuration version identifier corresponding to the to-be-acquired historical configuration information does not exist in the plurality of configuration version identifiers between the second configuration version identifier and the third configuration version identifier, that is, the historical configuration information corresponding to the first configuration version identifier is compressed, and at this time, the historical information acquiring method may further include: if the target configuration version identifier is not stored in the plurality of configuration version identifiers, the configuration information management server 102 determines that the state information of the historical configuration information to be acquired is that the historical configuration information to be acquired is compressed; the state information is returned to the client 101.

In the above embodiment, the configuration information management server 102 may obtain the historical configuration information to be obtained through the target revision identifier by traversing the configuration version identifiers between the second configuration version identifier and the third configuration version identifier, and finding the target configuration version identifier that is the same as the first configuration version identifier and the target revision identifier corresponding to the target configuration version identifier, and may also obtain the historical configuration information by querying when the latest configuration version identifier is not stored in the revision identifier library 103. Meanwhile, the corresponding revision identification is determined by each configuration version identification obtained in the traversal process and is stored in the revision identification library 103, so that the filing of the revision identification library 103 can be realized. In addition, if it is found that the historical configuration information is compressed in the traversal process, the configuration information management server 102 stops the traversal, and if the target configuration version identifier is not stored in the plurality of configuration version identifiers, the information management server 102 returns that the historical configuration information to be acquired is compressed, so that the acquisition efficiency is improved, the confidentiality of the configuration information is ensured, the validity of the first configuration version identifier can be checked, that is, whether the first configuration version identifier is larger than the second configuration version identifier is judged, if so, the historical configuration information to be acquired does not exist, and the efficiency of acquiring the historical configuration information can be further improved.

In one embodiment, after step S203, the method may further include: if the compression identifier of the corresponding historical configuration information is that the historical configuration information is compressed, the configuration information management server 102 determines that the state information of the historical configuration information to be acquired is that the historical configuration information to be acquired is compressed; the state information is returned to the client 101.

If the historical configuration information obtained by the configuration information management server 102 through the configuration information base 104 is compressed, the information management server 102 confirms that the state information of the historical configuration information to be acquired is compressed, and returns the state information to the client 101.

In the above embodiment, if the historical configuration information is compressed, the configuration information management server 102 only feeds back the compressed state information to the client 101, so that the secrecy of the configuration information can be ensured.

In an embodiment, as shown in fig. 4, the method for obtaining historical configuration information may further include:

in step S401, the configuration information management server 102, in response to the configuration information saving request triggered by the client 101, determines the configuration identifier to be saved and the configuration information to be saved corresponding to the configuration information saving request.

The client 101 may also be a client of a user needing to store the configuration information, where the configuration information to be stored is the configuration information that the user wants to store through the client 101, and the configuration identifier to be stored is a configuration identifier corresponding to the configuration information to be stored, and is used to identify the configuration information to be stored. Specifically, after the user triggers a configuration information saving request through the client 101, the configuration information management server 102 may respond to the request, so as to obtain the configuration identifier to be saved and the configuration information to be saved, which correspond to the request.

Step S402, the configuration information management server 102 stores the configuration identifier to be saved and the configuration information to be saved in the configuration information base 104, and queries the fourth configuration version identifier corresponding to the configuration information to be saved in the configuration information base 104 and the current revision identifier of the configuration information base 104 based on the configuration identifier to be saved;

in step S403, the configuration information management server 102 stores the configuration identifier to be saved, the fourth configuration version identifier, and the current revision identifier in the revision identifier repository 103.

The current revision identification is a revision identification corresponding to the configuration modification, and the fourth configuration version identification is a configuration version identification of the configuration identification corresponding to the configuration information to be stored when the configuration information is stored. Specifically, the configuration information management server 102 may store the to-be-saved configuration identifier and the to-be-saved configuration information into the configuration information base 104, query the configuration information base 104 with the to-be-saved configuration identifier to obtain a fourth configuration version identifier and a current revision identifier, and store the to-be-saved configuration identifier, the fourth configuration version identifier and the current revision identifier into the revision identifier base 103.

Further, the configuration information storage request also carries a user token for identifying the user identity; step S402 may further include: the configuration information management server 102 acquires user information corresponding to the user token, performs permission verification on the user information, and acquires a permission verification identifier of the user information; if the authority verification identifier is verified to pass, storing the configuration identifier to be stored and the configuration information to be stored into the configuration information base 104; step S403 may further include: the configuration information management server 102 stores the user information, the identification of the configuration to be saved, the identification of the fourth configuration version, and the identification of the current revision into the revision identification repository 103.

The user token is mainly used to identify the user identity of the user using the client 101, before the configuration information management server 102 stores the configuration identifier to be stored and the configuration information to be stored in the configuration information base 104, the user information of the user needs to be determined through the obtained user token, and the authority of the user information is verified, so that the authority verification identifier for the user information is obtained, and the configuration identifier to be stored and the configuration information to be stored are stored in the configuration information base 104 only when the authority verification passes. Meanwhile, in the process of storing the configuration identifier to be stored, the fourth configuration version identifier and the current revision identifier into the revision identifier repository 103, the user information corresponding to the user token is also stored into the revision identifier repository 103.

In the above embodiment, the configuration information management server 102 may store the configuration identifier to be saved and the configuration information to be saved in the configuration information base 104, and store the corresponding configuration identifier to be saved, the fourth configuration version identifier and the current revision identifier in the revision identifier base 103, so as to implement real-time retention of the version information in the database without using a version management tool for version management. Meanwhile, before the configuration information is saved, the authority of the user can be verified, so that the safety of the configuration information storage is further improved.

In one embodiment, the historical configuration information obtaining method may further include: the configuration information management server 102 responds to a historical configuration list acquisition request triggered by the client 101, and determines a list configuration identifier corresponding to a historical configuration list to be acquired; querying a historical configuration list corresponding to the list configuration identifier by using the revision identifier library 103 as a historical configuration list to be acquired; and returning the to-be-acquired historical configuration list to the client 101.

If the user needs to obtain a configuration list containing a plurality of configuration information for a certain configuration identifier through the client 101, that is, a historical configuration list of the list configuration identifier, the configuration information management server 102 may respond to the historical configuration list obtaining request by triggering the historical configuration list obtaining request, so as to obtain a historical configuration list that needs to be obtained, that is, a list configuration identifier corresponding to the historical configuration list to be obtained, and query the revision identifier library 103 by using the list configuration identifier, so as to obtain the historical configuration list corresponding to the identifier and return the historical configuration list as the historical configuration list to be obtained to the client 101.

In the above embodiment, the configuration information management server 102 may query the revision identification library 103 through the list configuration identification to obtain the to-be-acquired historical configuration list and feed back the to-be-acquired historical configuration list to the client 101, thereby implementing acquisition of the historical configuration list.

In one application example, a method for managing historical configuration information is provided, and the method can be based on a configuration information base, such as an etcd database, and a revision identification base, such as a sqlite database, to manage micro-service configuration versions, save service configurations by using the configuration information base through a configuration information management server, such as a background management system service, and add a configuration history management service and a revision identification base. The configuration information base supports multi-Version Concurrency Control (multimedia-Version Concurrency Control), and is realized by revision identification of the configuration information base, namely, main key revision, and all information from creation to deletion of the same configuration identification can be obtained by querying the configuration identification and a specific revision identification.

The specific implementation content is as follows:

1. the procedure of saving version information, as shown in fig. 5 and 6:

a) a user creates/modifies configuration, fills in remarks, clicks for storage, so as to trigger a configuration information storage request, transmits configuration identification and configuration information in a parameter form, and transmits a user token for identifying the identity of the user in the request;

b) a background management service of the configuration information management server inquires corresponding user information according to the user token and calls an authority service to carry out authority verification on the user information;

c) the background management service of the configuration information management server uses a configuration information base to store the service configuration identification and the corresponding configuration information;

d) the background management system calls a configuration history management service and transmits user information, such as user id, user remark and configuration identification, in a parameter form;

e) the configuration management service inquires a configuration information base to obtain a configuration version identifier;

f) the configuration management service stores the configuration identifier, the configuration version identifier, the revision identifier when the configuration is modified and the user information in a revision identifier library.

2. Query configuration version history list process

a) A user clicks a query version, a triggered historical configuration list acquisition request is transmitted to a configuration information management server in a parameter form;

b, the configuration information management server queries the revision identification library according to the incoming configuration identification to obtain a version history list.

3. Query configuration history version process, as shown in fig. 7 and 8:

a) the user clicks the historical version number of the configuration identifier to be inquired, triggers a historical configuration information acquisition request, and transmits the configuration identifier and the first configuration version identifier to the configuration information management server in a parameter form;

b) the configuration information management server searches revision identification from a revision identification library according to the transmitted configuration identification and the first configuration version identification;

c) if the version corresponding to the first configuration version identification is found in the revision identification library, the configuration identification and the revision identification are used for configuring the information library to search the configuration information, and the configuration information is returned to the client; otherwise, entering step d;

d) inquiring the second configuration version identification, namely the current version number, comparing the first configuration version identification with the second configuration version identification, and if the first configuration version identification is greater than the second configuration version identification, returning an error to the client; otherwise, entering step e;

e) querying the database revision identification library for a third configuration version identification, i.e., the maximum version number v3, identifying the supplemental historical version from the second configuration version identification to the third configuration version: and obtaining m1 by corresponding the second configuration version identifier to the revision identifier-1, querying the configuration information base for the content corresponding to the configuration identifier and m1 to obtain a revision identifier m2 and a previous configuration version identifier v4 of a previous version (v4) of the second configuration version identifier, circulating the process of querying the revision identifier-1 again until obtaining the configuration version identifier v3 or the version is compressed, and storing the record in the revision identifier base. If the version of the first configuration version identifier exists in the loop, recording the configuration information of the first configuration version identifier, and returning when the loop is ended;

f) if the configuration information identified by the first configuration version is compressed, returning that the client configuration information is compressed.

In the application example, when the configuration file is stored online, the version information can be kept in the database in real time, and version management does not need to be carried out by relying on version management tools such as git and the like. In addition, through the combination of the configuration information management server, the revision identification library and the configuration information library, the configuration can inquire and compare historical configuration information after error modification/error operation coverage, quickly locate problems and then carry out repair/combination/rollback, thereby greatly reducing the debugging cost and the rewriting cost.

It should be understood that, although the steps in the flowcharts of the present application are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in the figures may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of execution of the steps or stages is not necessarily sequential, but may be performed alternately or in alternation with other steps or at least some of the other steps or stages.

In one embodiment, as shown in fig. 9, there is provided a historical configuration information acquisition system, which includes a configuration information management server 902, and a client 901, a revision identification repository 903, and a configuration information repository 904 communicatively connected to the configuration information management server 902; wherein the content of the first and second substances,

a client 901, configured to trigger a historical configuration information acquisition request, and send the historical configuration information acquisition request to a configuration information management server 902;

a configuration information management server 902, configured to determine, in response to the historical configuration information acquisition request, a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired, and query, from the revision identifier repository 903, a revision identifier matching the configuration identifier and the first configuration version identifier;

the configuration information management server 902 is further configured to query historical configuration information corresponding to the revision identifier and the configuration identifier from the configuration information base 904, as historical configuration information to be acquired; returning the historical configuration information to be acquired to the client 901;

the client 901 is configured to receive historical configuration information to be acquired.

The historical configuration information acquisition system provided by this embodiment can query the historical configuration information through the revision identification after the configuration information is covered by combining the configuration information management server 902 with the revision identification library 903 and the configuration information library 904, thereby improving the acquisition efficiency of the historical configuration information.

In one embodiment, as shown in fig. 10, there is provided a historical configuration information acquisition apparatus applied to a configuration information management server, including: a configuration request acquisition module 1001, a database version acquisition module 1002, a configuration information acquisition module 1003, and a configuration information sending module 1004, wherein:

a configuration request obtaining module 1001, configured to determine, in response to a historical configuration information obtaining request triggered by a client, a configuration identifier and a first configuration version identifier corresponding to historical configuration information to be obtained;

a revision identification obtaining module 1002, configured to query a revision identification matching the configuration identification and the first configuration version identification from a revision identification library;

a configuration information obtaining module 1003, configured to query, from the configuration information base, historical configuration information corresponding to the revision identifier and the configuration identifier, as historical configuration information to be obtained;

a configuration information sending module 1004, configured to return the historical configuration information to be obtained to the client.

In an embodiment, the configuration information obtaining module 1003 is further configured to, if the revision identifier is not stored in the revision identifier library, obtain, from the configuration information library, a maximum configuration version identifier corresponding to the configuration identifier as the second configuration version identifier; if the first configuration version identification is smaller than the second configuration version identification, acquiring a maximum configuration version identification corresponding to the configuration identification stored in the revision identification library as a third configuration version identification; the second configuration version identification is larger than the third configuration version identification; traversing the configuration version identifiers between the second configuration version identifier and the third configuration version identifier according to a descending order to obtain a plurality of configuration version identifiers; and if the target configuration version identifications with the same first configuration version identification are stored in the plurality of configuration version identifications, acquiring the target revision identification corresponding to the target configuration version identification, and taking the target revision identification and the configuration information corresponding to the configuration identification as the historical configuration information to be acquired.

In an embodiment, the configuration information obtaining module 1003 is further configured to determine a revision identification corresponding to each configuration version identification; and storing the configuration identifier, each configuration version identifier and the revision identifier corresponding to each configuration version identifier into a revision identifier library.

In an embodiment, the configuration information obtaining module 1003 is further configured to obtain a plurality of historical configuration information by using the revision identifier and the configuration identifier corresponding to each configuration version identifier; acquiring a compression identifier of each historical configuration information; and if the compression identifier is that the historical configuration information is compressed, stopping traversing the configuration version identifiers between the second configuration version identifier and the third configuration version identifier.

In an embodiment, the configuration information obtaining module 1003 is further configured to determine that the state information of the historical configuration information to be obtained is that the historical configuration information to be obtained is compressed if the target configuration version identifier is not stored in the plurality of configuration version identifiers; returning the state information to the client, and if the compression identifier of the corresponding historical configuration information is that the historical configuration information is compressed, determining that the state information of the historical configuration information to be acquired is that the historical configuration information to be acquired is compressed; and returning the state information to the client.

In an embodiment, the configuration information obtaining module 1003 is further configured to determine that the status information of the historical configuration information to be obtained does not exist if the first configuration version identifier is greater than the second configuration version identifier; and returning the state information to the client.

In one embodiment, the historical configuration information obtaining device further includes: the configuration information storage module is used for responding to a configuration information storage request triggered by the client and determining a configuration identifier to be stored and configuration information to be stored, which correspond to the configuration information storage request; storing the configuration identifier to be stored and the configuration information to be stored into a configuration information base, and inquiring a fourth configuration version identifier corresponding to the configuration information to be stored and a current revision identifier of the configuration information base in the configuration information base based on the configuration identifier to be stored; and storing the configuration identifier to be stored, the fourth configuration version identifier and the current revision identifier into a revision identifier library.

In one embodiment, the configuration information storage request further carries a user token for identifying the user identity; the configuration information storage module is also used for acquiring user information corresponding to the user token, performing authority verification on the user information and acquiring an authority verification identifier of the user information; if the authority verification identifier passes verification, storing the configuration identifier to be stored and the configuration information to be stored into a configuration information base; and storing the user information, the configuration identifier to be stored, the fourth configuration version identifier and the current revision identifier into a revision identifier library.

In one embodiment, the historical configuration information obtaining device further includes: the configuration list acquisition module is used for responding to a historical configuration list acquisition request triggered by a client and determining a list configuration identifier corresponding to a historical configuration list to be acquired; querying a historical configuration list corresponding to the list configuration identifier by using the revision identifier library to serve as a historical configuration list to be acquired; and returning the historical configuration list to be acquired to the client.

For specific limitations of the historical configuration information acquisition device, reference may be made to the above limitations of the historical configuration information acquisition method, which is not described herein again. The modules in the historical configuration information acquisition device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a configuration information management server, and its internal structure diagram may be as shown in fig. 11. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing 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 the historical configuration information acquisition request. 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 implement a historical configuration information acquisition method.

Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A historical configuration information acquisition method is applied to a configuration information management server, and comprises the following steps:

responding to a historical configuration information acquisition request triggered by a client, and determining a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired;

querying a revision identification matching the configuration identification and the first configuration version identification from a revision identification repository;

querying historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base to serve as the historical configuration information to be acquired;

and returning the historical configuration information to be acquired to the client.

2. The method of claim 1, further comprising:

if the revision identification is not stored in the revision identification library, acquiring the maximum configuration version identification corresponding to the configuration identification from the configuration information library as a second configuration version identification;

if the first configuration version identification is smaller than the second configuration version identification, acquiring a maximum configuration version identification corresponding to the configuration identification stored in the revision identification library as a third configuration version identification; wherein the second configuration version identification is greater than the third configuration version identification;

traversing the configuration version identifiers between the second configuration version identifier and the third configuration version identifier according to a descending order to obtain a plurality of configuration version identifiers;

if the target configuration version identifications with the same first configuration version identification are stored in the plurality of configuration version identifications, acquiring target revision identifications corresponding to the target configuration version identifications, and taking the target revision identifications and the configuration information corresponding to the configuration identifications as the historical configuration information to be acquired.

3. The method of claim 2, wherein obtaining the plurality of configuration version identifiers comprises:

determining revision identifications corresponding to the configuration version identifications;

and storing the configuration identification, the configuration version identifications and the revision identification corresponding to the configuration version identifications into the revision identification library.

4. The method of claim 3, further comprising:

obtaining a plurality of historical configuration information by using revision identifications corresponding to the configuration version identifications and the configuration identifications;

acquiring a compression identifier of each historical configuration information;

and if the compression identifier is that the historical configuration information is compressed, stopping traversing the configuration version identifier between the second configuration version identifier and the third configuration version identifier.

5. The method of claim 4, further comprising:

if the target configuration version identifier is not stored in the plurality of configuration version identifiers, determining that the state information of the historical configuration information to be acquired is that the historical configuration information to be acquired is compressed;

and/or

If the compression identifier of the corresponding historical configuration information indicates that the historical configuration information is compressed, confirming that the state information of the historical configuration information to be acquired is that the historical configuration information to be acquired is compressed;

and returning the state information to the client.

6. The method according to claim 2, wherein after obtaining the maximum configuration version identifier corresponding to the configuration identifier from the configuration information base as the second configuration version identifier, the method further comprises:

if the first configuration version identification is larger than the second configuration version identification, determining that the state information of the historical configuration information to be acquired does not exist;

and returning the state information to the client.

7. The method according to any one of claims 1 to 6, further comprising:

responding to a configuration information storage request triggered by the client, and determining a configuration identifier to be stored and configuration information to be stored, which correspond to the configuration information storage request;

storing the configuration identifier to be stored and the configuration information to be stored into the configuration information base, and inquiring a fourth configuration version identifier corresponding to the configuration information to be stored and a current revision identifier of the configuration information base in the configuration information base based on the configuration identifier to be stored;

and storing the configuration identifier to be stored, the fourth configuration version identifier and the current revision identifier into the revision identifier library.

8. The method according to claim 7, wherein the configuration information saving request further carries a user token for identifying the user identity;

the storing the configuration identifier to be saved and the configuration information to be saved into the configuration information base includes:

acquiring user information corresponding to the user token, performing authority verification on the user information, and acquiring an authority verification identifier of the user information;

if the authority verification identification passes verification, storing the configuration identification to be stored and the configuration information to be stored into the configuration information base;

the storing the configuration identifier to be saved, the fourth configuration version identifier and the current revision identifier into the revision identifier library includes:

and storing the user information, the configuration identifier to be stored, the fourth configuration version identifier and the current revision identifier into the revision identifier library.

9. A historical configuration information acquisition system, comprising: the system comprises a configuration information management server, a client, a revision identification library and a configuration information library, wherein the client, the revision identification library and the configuration information library are in communication connection with the configuration information management server; wherein the content of the first and second substances,

the client is used for triggering a historical configuration information acquisition request and sending the historical configuration information acquisition request to the configuration information management server;

the configuration information management server is used for responding to the historical configuration information acquisition request, determining a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired, and inquiring a revision identifier matched with the configuration identifier and the first configuration version identifier from a revision identifier library;

the configuration information management server is further configured to query historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base, and use the historical configuration information as the historical configuration information to be acquired; returning the historical configuration information to be acquired to the client;

and the client is used for receiving the historical configuration information to be acquired.

10. An apparatus for obtaining historical configuration information, which is applied to a configuration information management server, the apparatus comprising:

the configuration request acquisition module is used for responding to a historical configuration information acquisition request triggered by a client and determining a configuration identifier and a first configuration version identifier corresponding to the historical configuration information to be acquired;

the revision identification acquisition module is used for inquiring revision identifications matched with the configuration identifications and the first configuration version identifications from a revision identification library;

the configuration information acquisition module is used for inquiring historical configuration information corresponding to the revision identification and the configuration identification from a configuration information base to be used as the historical configuration information to be acquired;

and the configuration information sending module is used for returning the historical configuration information to be acquired to the client.

Images