CN110825425A - Configuration data management method and device, electronic equipment and storage medium - Google Patents
Configuration data management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN110825425A CN110825425A CN201810903412.4A CN201810903412A CN110825425A CN 110825425 A CN110825425 A CN 110825425A CN 201810903412 A CN201810903412 A CN 201810903412A CN 110825425 A CN110825425 A CN 110825425A
- Authority
- CN
- China
- Prior art keywords
- configuration data
- acquisition request
- data acquisition
- client
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The disclosure relates to a method and a device for managing configuration data, electronic equipment and a storage medium, which relate to the technical field of computers, and the method comprises the following steps: receiving a configuration data acquisition request aiming at a client, and judging whether the configuration data acquisition request is a gray level strategy or not; if the configuration data acquisition request belongs to the gray level strategy, returning gray level configuration data corresponding to the configuration data acquisition request; and if the configuration data acquisition request belongs to a non-gray level strategy, returning the on-line configuration data corresponding to the configuration data acquisition request. The present disclosure can realize configuration data gradation change and can reduce the influence on the on-line user.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a configuration data management method, a configuration data management apparatus, an electronic device, and a computer-readable storage medium.
Background
With the development of e-commerce platform services, changes of on-line configuration data are more and more frequent, for example, a configuration file is frequently modified, and partial functions are degraded. Misoperation caused by any configuration change can cause certain influence on the environment on the line, and user experience can be influenced in serious cases, even ordering and payment cannot be made.
In the related technology, a function of notifying data change in real time can be realized through a watch mechanism of a zookeeper, all configuration data of the zookeeper can be loaded into a memory when a service system is started, the memory data can be updated when the data are changed, and the service system only reads the configuration data from the memory. In the scheme, any change of the configuration data is full, and gray level changes such as a white list, a client, a version and the like cannot be realized; errors caused by manual operation can cause full operation to affect online users, and the operation of verifying before full operation cannot be performed, so that a certain risk exists in configuring a system.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the present disclosure is to provide a method and apparatus for managing configuration data, an electronic device, and a storage medium, thereby overcoming, at least to some extent, the problem that the configuration data does not support a change in grayscale due to the limitations and disadvantages of the related art.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to an aspect of the present disclosure, there is provided a configuration data management method including: receiving a configuration data acquisition request aiming at a client, and judging whether the configuration data acquisition request is a gray level strategy or not; if the configuration data acquisition request belongs to the gray level strategy, returning gray level configuration data corresponding to the configuration data acquisition request; and if the configuration data acquisition request belongs to a non-gray level strategy, returning the on-line configuration data corresponding to the configuration data acquisition request.
In an exemplary embodiment of the disclosure, before receiving the configuration data acquisition request for the client, the method further comprises: adding gray nodes to a storage structure in a configuration system; and adding gray level storage for the storage structure of the memory data of the client according to the gray level nodes to generate the gray level configuration data.
In an exemplary embodiment of the present disclosure, the determining whether the configuration data acquisition request is a grayscale policy includes: and judging whether the configuration data acquisition request is the gray scale strategy or not according to request parameters in the configuration data acquisition request, wherein the request parameters comprise at least one of memory white list data, client data and version data.
In an exemplary embodiment of the disclosure, the determining whether the configuration data acquisition request is the grayscale policy according to a request parameter in the configuration data acquisition request includes: comparing the memory white list data in the request parameters with reference white list data of a client; and if the memory white list data is matched with the reference white list data, determining that the configuration data acquisition request belongs to the gray scale strategy.
In an exemplary embodiment of the disclosure, the determining whether the configuration data acquisition request is the grayscale policy according to a request parameter in the configuration data acquisition request includes: comparing client data contained in the request parameters with reference data of the client; and if the client data contained in the request parameters are matched with the reference data of the client, determining that the configuration data acquisition request belongs to the gray level strategy.
In an exemplary embodiment of the present disclosure, the client data includes a version of the client.
In an exemplary embodiment of the disclosure, the request parameter in the configuration data obtaining request is stored in the thread cache through a filter.
In an exemplary embodiment of the present disclosure, the method further comprises: and if the gray configuration data or the on-line configuration data are not read, returning default configuration data corresponding to the configuration data acquisition request.
According to an aspect of the present disclosure, there is provided a configuration data management apparatus including: the request judging module is used for receiving a configuration data acquisition request aiming at a client and judging whether the configuration data acquisition request is a gray level strategy or not; the gray configuration module is used for returning the gray configuration data corresponding to the configuration data acquisition request if the configuration data acquisition request belongs to the gray strategy; and the on-line configuration module is used for returning the on-line configuration data corresponding to the configuration data acquisition request if the configuration data acquisition request belongs to a non-gray level strategy.
According to an aspect of the present disclosure, there is provided an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any of the above described configuration data management methods via execution of the executable instructions.
According to an aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a configuration data management method as recited in any one of the above.
In a configuration data management method, a configuration data management apparatus, an electronic device, and a computer-readable storage medium provided in exemplary embodiments of the present disclosure, on one hand, by determining whether a configuration data acquisition request is a grayscale policy, and determining to return grayscale configuration data or on-line configuration data, the configuration data can be made to support grayscale change; on the other hand, by judging whether the corresponding configuration data is returned for the gray level strategy or not, the problem that the configuration data is in full effect when being modified is avoided, the influence on the online user is avoided, the security of the configuration system is improved, and the user experience is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
FIG. 1 schematically illustrates a system architecture diagram for implementing configuration data management in an exemplary embodiment of the disclosure;
FIG. 2 is a schematic diagram illustrating a configuration data management method in an exemplary embodiment of the present disclosure;
FIG. 3 schematically illustrates a system architecture diagram of configuration changes in an exemplary embodiment of the present disclosure;
FIG. 4 is a schematic diagram illustrating a configuration system storage structure in an exemplary embodiment of the present disclosure;
FIG. 5 schematically illustrates a detailed flow chart for obtaining configuration data in an exemplary embodiment of the present disclosure;
FIG. 6 schematically illustrates a detailed flow chart of initializing configuration data in an exemplary embodiment of the disclosure;
FIG. 7 schematically illustrates a detailed flow chart of altering configuration data in an exemplary embodiment of the present disclosure;
FIG. 8 schematically illustrates a block diagram of a configuration data management apparatus in an exemplary embodiment of the present disclosure;
FIG. 9 schematically illustrates a block diagram of an electronic device in an exemplary embodiment of the disclosure;
fig. 10 schematically illustrates a program product in an exemplary embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The present exemplary embodiment first provides a system architecture for implementing a configuration data management method, which may be applied to an application scenario for generating configuration data for a client. Referring to fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send request instructions or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a photo processing application, a shopping application, a web browser application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server that provides various services, such as a background management server (for example only) that processes configuration data acquisition requests sent by users using the terminal devices 101, 102, 103. And may feed back the processing result (e.g., matching result, etc.) to the terminal device.
It should be noted that the configuration data management method provided in the embodiment of the present application is generally executed by the server 105, and accordingly, the configuration data management apparatus is generally provided in the terminal device 101.
Based on the system architecture 100, a configuration data management method is provided in this example, and as shown in fig. 2, the configuration data management method may include the following steps:
in step S210, receiving a configuration data acquisition request for a client, and determining whether the configuration data acquisition request is a grayscale policy;
in step S220, if the configuration data acquisition request belongs to the grayscale policy, returning grayscale configuration data corresponding to the configuration data acquisition request;
in step S230, if the configuration data obtaining request belongs to a non-grayscale policy, the on-line configuration data corresponding to the configuration data obtaining request is returned.
In the configuration data management method provided in the present exemplary embodiment, on the one hand, by determining whether the configuration data acquisition request is a grayscale policy, and determining to return grayscale configuration data or on-line configuration data, the configuration data can be made to support grayscale change; on the other hand, by judging whether the corresponding configuration data is returned for the gray level strategy or not, the problem that the configuration data is in full effect when being modified is avoided, the influence on the online user is avoided, the security of the configuration system is improved, and the user experience is improved.
Next, the specific steps of the configuration data management method in the present exemplary embodiment will be further explained with reference to the drawings.
In step S210, a configuration data acquisition request for a client is received, and it is determined whether the configuration data acquisition request is a grayscale policy.
In the present exemplary embodiment, the client refers to an application program that provides a local service to a user, corresponding to the server. Referring to fig. 3, the system mainly includes an SOA (service-oriented architecture), a client memory data, and a configuration system. Among them, a Service Oriented Architecture (SOA) is a component model that ties different functional units of an application to each other through well-defined interfaces and contracts between these services. The memory data of the client refers to a storage structure of the memory data in the client.
In the exemplary embodiment, the configuration function for the client may be implemented by an open source configuration system such as Feature, Consul, etcd, Eureka, Zookeeper, or the like. Wherein, the use of Eureka requires explicit configuration of health check support; zookeeper, Etcd are unhealthy in the event of loss of connectivity to the service process. Consul completes synchronization across data centers through the Gossip protocol of the WAN. In addition to the Eureka, other configuration systems can provide storage services for external support KV, Zookeeper support server-side push changes of CAP theory in product design are chosen, and Eureka, Consul and Etcd all realize perception of changes through long polling.
In this example, the configuration system is described as a Zookeeper configuration system. Referring to fig. 3, the system mainly includes an SOA, a client memory data, a Zookeeper configuration system, and a watch mechanism of the Zookeeper configuration system, so as to detect data change through the watch mechanism. Referring to fig. 4, the configuration system includes an online node, where the online node includes an application, and the application specifically includes an online service configuration and an online switch configuration. To implement gray scale distribution, a gray scale function is added to the configuration system, thereby generating gray scale configuration data. Specifically, on the basis of the nodes on the line, a gray node is added to the storage structure for configuring the system Zookeeper, for example, as shown in fig. 4. Based on the added gray node, gray storage can be added to the storage structure of the memory data of the client, so that gray configuration data is generated. The gray level node includes an application, and the application specifically includes white list data, client data, version data, and the like, and in addition, may also include an online service configuration and an online switch configuration.
The configuration data obtaining request may include request parameters for describing the client, where the request parameters include, but are not limited to, at least one of memory white list data, client data, and version data. After obtaining the request parameters, it may be determined whether the configuration data acquisition request is a grayscale policy according to the request parameters. The gray scale strategy here refers to gray scale distribution, and gray scale distribution refers to a distribution method that can smoothly transition between black and white. For example, AB test is a gray-scale publishing method, in which a part of users continue to use a, a part of users start to use B, and if the users do not have any objection to B, the range is gradually expanded, and all users are migrated to B. The stability of the whole system can be ensured through gray release, the problems can be found and adjusted in the initial gray process, and new function modification can be verified quickly to ensure the influence degree.
Specifically, whether the configuration data acquisition request is a grayscale policy may be determined by a request parameter in the configuration data acquisition request. Specifically, the method may include three ways, for example, only through the determination by the memory white list data, or only through the determination by the client data, or through the determination by the memory white list data and the client data at the same time. The memory white list data refers to a predetermined account number pin, namely a user account number of the client. The client data includes specific data of the client type and a version number corresponding to each client type, such as a name, a version number, an identifier, and the like. The client type may include, for example, IOS, android, and page type H5, and the version number refers to different versions corresponding to the application program, and may include, for example, a test version, a stable version, a formal version, and the like. Or client 1 android version 9.2, client 2 IOS version 9.2, and so on.
It should be noted that request parameters, such as memory white list data and client data, included in the configuration data acquisition request may be stored in a thread cache in advance through a filter, where the thread cache may be, for example, threaded local, and the threaded local creates a copy in each thread for a variable, so that each thread may access its internal copy variable, and data security is ensured. In the exemplary embodiment, the request parameters are stored in the thread cache, so that the request parameters stored in the thread cache can be directly matched and compared with the reference values stored in the client, and the operation efficiency is improved. It should be added that the precondition for storing the request parameters in the thread cache is that the parameter format is agreed with the configuration data acquisition requester, or the requester realizes an agreed interface by itself, which also encapsulates the memory white list data and the client data.
Next, the determination of whether or not the gradation policy is adopted will be specifically described. In the first mode, when the memory white list data is used for judging whether the configuration data acquisition request is a gray scale strategy, the memory white list data in the request parameters can be compared with the reference white list data of the client; and if the memory white list data is matched with the reference white list data, determining that the configuration data acquisition request belongs to the gray scale strategy. The reference white list data of the client may be, for example, user accounts belonging to the white list data determined according to the history data in the client, and for example, the reference white list data may include account 1, account 2, account 3, account 4, and the like. The memory white list data in the request parameters may or may not be completely consistent with the reference white list data. And the data of the memory white list are different aiming at different clients. For example, the memory white list data in the request parameter includes the account 2, and since the memory white list data exists in the reference white list data of the client, the two may be considered to be successfully matched, so that it may be determined that the configuration data acquisition request belongs to the grayscale policy. For another example, the memory white list data in the request parameter includes the account 5, and since the reference white list data of the client does not include the memory white list data, it may be determined that the configuration data acquisition request does not belong to the grayscale policy.
In the second mode, the specific steps when determining whether the client data is a grayscale policy include: comparing client data contained in the request parameters with reference data of the client; and if the client data contained in the request parameters are matched with the reference data of the client, determining that the configuration data acquisition request belongs to the gray level strategy. Since it is not necessary to adopt a grayscale policy for all versions of the client, the client data in this example refers to a certain version of each type of the client, and specifically, which version can be determined according to actual needs. For example, the client data is a name, version number, and identifier of 9.2 android version 1 of the client, and the reference data of the client is data of a certain version of the client, such as a name, version number, and identifier corresponding to 9.2 android version 1 of the client. Next, the client data of the client 1 android version 9.2 contained in the request parameter may be compared and matched with the name, version number, identifier, and the like corresponding to the client 1 android version 9.2, and if all the matches are successful, it may be determined that the configuration data acquisition request belongs to a grayscale policy; if any of the client data fails to match, it is determined that the configuration data acquisition request does not belong to the grayscale policy.
In addition, whether the configuration data acquisition request belongs to the gray policy may be determined by combining the white list data of the memory with the client data, and the specific process is similar to the process of using only the white list data of the memory and only the client data, so that the detailed description is omitted here.
In the exemplary embodiment, the storage structure of the configuration system is added with gray scale storage, and the problem that the business function cannot partially store gray scale is solved. In addition, a verification process of the gray strategy is added, so that the configuration data supports white list verification and gray change, and is released according to the gray of the client and the version.
In step S220, if the configuration data acquisition request belongs to the grayscale policy, returning grayscale configuration data corresponding to the configuration data acquisition request.
In the present exemplary embodiment, the grayscale configuration data refers to configuration data of a client satisfying the grayscale policy, and may be, for example, configuration data for a client in an inline stage, and a range of the grayscale configuration data may be larger than a range of configuration data of a client on-line in an inline manner. In this example, gray level nodes are added to the storage structure of the Zookeeper configuration system, and gray level storage is added to the storage structure of the memory data of the client based on the added gray level nodes, so as to generate gray level configuration data. The gray configuration data may include, but is not limited to, the name, version number, profile, logo, icon, charging status, screen shot, time and amount of gray publication, and user attribute information of the delivered object. When the configuration data is manually changed, only the gradation configuration data can be changed without affecting the other configuration data. And if the configuration data acquisition request meets the gray level strategy, performing gray level release on the client according to the gray level configuration data.
By the method in the exemplary embodiment, the problem that the configuration data is modified manually to cause total effect after misoperation is avoided, and the influence on the online user is avoided, so that the change range of the configuration data is controllable, the configuration system is more complete, and the user experience is improved.
In step S230, if the configuration data obtaining request belongs to a non-grayscale policy, the on-line configuration data corresponding to the configuration data obtaining request is returned.
In this exemplary embodiment, if the memory white list data in the request parameter does not match the reference white list data of the client, or the client data in the request parameter does not match the reference data of the client, it may be considered that the configuration data acquisition request of the client does not belong to the grayscale policy. The online configuration data refers to configuration data corresponding to the online client, and the online configuration data may include, but is not limited to, configuration parameters such as the name, version number, profile, identifier, icon, charging status, screenshot, time and number of gray release, and user attribute information of the drop object of the client, but specific values of the configuration parameters may be different from the gray configuration data. And if the configuration data acquisition request does not meet the gray-scale strategy, reading the configuration data on the line.
It should be added that if the gray configuration data is not read, and the on-line configuration data is not read, the default configuration data corresponding to the configuration data acquisition request is returned. The default configuration data may be set in advance according to actual requirements, and is not particularly limited herein.
By adding gray scale storage to the storage structure of the configuration system in the exemplary embodiment, the problem that the business function cannot be partially changed in gray scale is solved. In addition, a verification process of the gray strategy is added, so that the verification of the white list is supported, and the gray strategy is released according to the gray of the client and the version. In addition, the problem that the configuration data is modified manually to cause total effect after misoperation is avoided, and the influence on the online user is avoided, so that the change range of the configuration data is controllable, the configuration system is more complete, and the user experience is improved.
Fig. 5 to 7 show specific flowcharts for managing configuration data, where fig. 5 includes a process for acquiring configuration data, and the specific steps include:
step S500, acquiring configuration data. Step S501, reads request parameters such as memory white list data, client data, version data, and the like. Step S502, comparing and judging whether the configuration data acquisition request is a gray level strategy or not according to the request parameters. Step S503, determining whether the configuration data acquisition request is a grayscale policy. Step S504, if the strategy is the gray level strategy, the gray level configuration data is returned. And step S505, if the data does not belong to the gray strategy, returning to the on-line configuration data. Step S506, determining whether to read the gray configuration data and the on-line configuration data. If so, the whole process is ended. In step S507, if the grayscale configuration data and the on-line configuration data are not read, the default configuration data is returned.
Fig. 6 includes a process of initializing configuration data, which specifically includes: step S610, initializing a configuration file. Step S611, reading the configuration data from the configuration system Zookeeper. Step S612, determine whether the reading is successful. If the reading is successful, step S613 is executed to load the configuration data into the memory. Step S614, adding a gray level data storage structure for the storage structure of the memory data in the client. Step S615, determine whether the loading to the memory is successful. Step S616, add data change monitoring. If the reading fails, step S617 is executed to obtain the configuration data from the local file. In step S618, it is determined whether reading from the local file is successful. If successful, go to step S613. If not, go to step S619 to determine the boot failure.
In addition, fig. 7 includes a process of changing configuration data, which specifically includes: step S720, the configuration data is changed. Step S721, determining the configuration data change through the configuration system Zookeeper. In step S722, the listener is notified of the change. Step S723, the memory data change is controlled. Step S724 listens for the changed node again.
Through the configuration data management method in fig. 5 to 7, the problem that the configuration data is modified manually to cause a total effect after misoperation is avoided, and the influence on the online user is avoided, so that the change range of the configuration data is controllable, the configuration system is more complete, and the user experience is improved.
In an exemplary embodiment of the present disclosure, there is also provided a configuration data management apparatus, as shown in fig. 8, the apparatus 800 includes:
a request determining module 801, configured to receive a configuration data acquisition request for a client, and determine whether the configuration data acquisition request is a grayscale policy;
a gray configuration module 802, configured to, if the configuration data acquisition request belongs to the gray policy, return gray configuration data corresponding to the configuration data acquisition request;
an on-line configuration module 803, configured to, if the configuration data acquisition request belongs to a non-grayscale policy, return the on-line configuration data corresponding to the configuration data acquisition request.
In an exemplary embodiment of the disclosure, before receiving the configuration data acquisition request for the client, the apparatus further includes: the node adding module is used for adding gray nodes into a storage structure in the configuration system; and the storage structure adjusting module is used for increasing gray storage for the storage structure of the memory data of the client according to the gray nodes so as to generate the gray configuration data.
In an exemplary embodiment of the present disclosure, the request determining module includes: and the judgment control module is used for judging whether the configuration data acquisition request is the gray scale strategy or not according to request parameters in the configuration data acquisition request, wherein the request parameters comprise at least one of memory white list data, client data and version data.
In an exemplary embodiment of the present disclosure, the determination control module includes: the first comparison module is used for comparing the memory white list data in the request parameters with reference white list data of a client; a first determining module, configured to determine that the configuration data acquisition request belongs to the grayscale policy if the memory white list data matches the reference white list data.
In an exemplary embodiment of the present disclosure, the determination control module includes: the second comparison module is used for comparing the client data contained in the request parameters with the reference data of the client; and the second determining module is used for determining that the configuration data acquisition request belongs to the gray level strategy if the client data contained in the request parameter is matched with the reference data of the client.
In an exemplary embodiment of the present disclosure, the client data includes a version of the client.
In an exemplary embodiment of the disclosure, the request parameter in the configuration data obtaining request is stored in the thread cache through a filter.
In an exemplary embodiment of the present disclosure, the apparatus further includes: and the default reading module is used for returning default configuration data corresponding to the configuration data acquisition request if the gray configuration data or the on-line configuration data is not read.
It should be noted that, the specific details of each module in the configuration data management apparatus have been described in detail in the corresponding configuration data management method, and therefore are not described herein again.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 900 according to this embodiment of the invention is described below with reference to fig. 9. The electronic device 900 shown in fig. 9 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present invention.
As shown in fig. 9, the electronic device 900 is embodied in the form of a general purpose computing device. Components of electronic device 900 may include, but are not limited to: the at least one processing unit 910, the at least one memory unit 920, and a bus 930 that couples various system components including the memory unit 920 and the processing unit 910.
Wherein the storage unit stores program code that is executable by the processing unit 910 to cause the processing unit 910 to perform steps according to various exemplary embodiments of the present invention described in the above section "exemplary methods" of the present specification. For example, the processing unit 910 may perform the steps as shown in fig. 2.
The storage unit 920 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM)9201 and/or a cache memory unit 9202, and may further include a read only memory unit (ROM) 9203.
The electronic device 900 may also communicate with one or more external devices 1100 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 900, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 900 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interface 950. Also, the electronic device 900 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet) via the network adapter 960. As shown, the network adapter 960 communicates with the other modules of the electronic device 900 via the bus 930. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 10, a program product 1000 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (11)
1. A method for configuration data management, comprising:
receiving a configuration data acquisition request aiming at a client, and judging whether the configuration data acquisition request is a gray level strategy or not;
if the configuration data acquisition request belongs to the gray level strategy, returning gray level configuration data corresponding to the configuration data acquisition request;
and if the configuration data acquisition request belongs to a non-gray level strategy, returning the on-line configuration data corresponding to the configuration data acquisition request.
2. The method of claim 1, wherein prior to receiving a configuration data acquisition request for a client, the method further comprises:
adding gray nodes to a storage structure in a configuration system;
and adding gray level storage for the storage structure of the memory data of the client according to the gray level nodes to generate the gray level configuration data.
3. The method of claim 1, wherein determining whether the configuration data acquisition request is a grayscale policy comprises:
and judging whether the configuration data acquisition request is the gray scale strategy or not according to request parameters in the configuration data acquisition request, wherein the request parameters comprise at least one of memory white list data, client data and version data.
4. The method according to claim 3, wherein determining whether the configuration data acquisition request is the grayscale policy according to a request parameter in the configuration data acquisition request comprises:
comparing the memory white list data in the request parameters with reference white list data of a client;
and if the memory white list data is matched with the reference white list data, determining that the configuration data acquisition request belongs to the gray scale strategy.
5. The method according to claim 3, wherein determining whether the configuration data acquisition request is the grayscale policy according to a request parameter in the configuration data acquisition request comprises:
comparing client data contained in the request parameters with reference data of the client;
and if the client data contained in the request parameters are matched with the reference data of the client, determining that the configuration data acquisition request belongs to the gray level strategy.
6. The configuration data management method according to claim 5, wherein the client data comprises a version of the client.
7. The method according to claim 3, wherein the request parameter in the configuration data obtaining request is stored in a thread cache through a filter.
8. The method of configuration data management according to claim 1, the method further comprising:
and if the gray configuration data or the on-line configuration data are not read, returning default configuration data corresponding to the configuration data acquisition request.
9. A configuration data management apparatus, comprising:
the request judging module is used for receiving a configuration data acquisition request aiming at a client and judging whether the configuration data acquisition request is a gray level strategy or not;
the gray configuration module is used for returning the gray configuration data corresponding to the configuration data acquisition request if the configuration data acquisition request belongs to the gray strategy;
and the on-line configuration module is used for returning the on-line configuration data corresponding to the configuration data acquisition request if the configuration data acquisition request belongs to a non-gray level strategy.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the configuration data management method of any of claims 1-9 via execution of the executable instructions.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the configuration data management method according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810903412.4A CN110825425A (en) | 2018-08-09 | 2018-08-09 | Configuration data management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810903412.4A CN110825425A (en) | 2018-08-09 | 2018-08-09 | Configuration data management method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110825425A true CN110825425A (en) | 2020-02-21 |
Family
ID=69541576
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810903412.4A Pending CN110825425A (en) | 2018-08-09 | 2018-08-09 | Configuration data management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110825425A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111538529A (en) * | 2020-04-27 | 2020-08-14 | 中国银行股份有限公司 | Gray scale publishing method and device |
| CN111897887A (en) * | 2020-08-06 | 2020-11-06 | 北京沃东天骏信息技术有限公司 | Parameter configuration method, device, system, electronic equipment and storage medium |
| CN113495747A (en) * | 2020-04-07 | 2021-10-12 | 北京京东振世信息技术有限公司 | Gray scale publishing method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105099988A (en) * | 2014-04-24 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Method used for supporting gray releasing, access method, devices and system |
| US20160048384A1 (en) * | 2014-08-12 | 2016-02-18 | Xiaomi Inc. | Method and device for grayscale-upgrading |
| CN105515872A (en) * | 2015-12-23 | 2016-04-20 | 北京奇虎科技有限公司 | Method, apparatus and system for updating configuration information |
| CN105677404A (en) * | 2015-12-31 | 2016-06-15 | 拉扎斯网络科技（上海）有限公司 | Zookeeper based configuration updating method and device |
| CN106502874A (en) * | 2016-10-26 | 2017-03-15 | 南京途牛科技有限公司 | A kind of call chain tracking |
| CN106998369A (en) * | 2017-05-26 | 2017-08-01 | 努比亚技术有限公司 | Gray scale dissemination method, gateway blocker and computer-readable recording medium |
| CN107818024A (en) * | 2017-11-22 | 2018-03-20 | 北京汇通金财信息科技有限公司 | A kind of request ID transmission methods and system based on spring blockers |
| CN107920112A (en) * | 2017-11-01 | 2018-04-17 | 重庆金融资产交易所有限责任公司 | Support configuration file method for pushing, central server and the storage medium of grayscale mode |
-
2018
- 2018-08-09 CN CN201810903412.4A patent/CN110825425A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105099988A (en) * | 2014-04-24 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Method used for supporting gray releasing, access method, devices and system |
| US20160048384A1 (en) * | 2014-08-12 | 2016-02-18 | Xiaomi Inc. | Method and device for grayscale-upgrading |
| CN105515872A (en) * | 2015-12-23 | 2016-04-20 | 北京奇虎科技有限公司 | Method, apparatus and system for updating configuration information |
| CN105677404A (en) * | 2015-12-31 | 2016-06-15 | 拉扎斯网络科技（上海）有限公司 | Zookeeper based configuration updating method and device |
| CN106502874A (en) * | 2016-10-26 | 2017-03-15 | 南京途牛科技有限公司 | A kind of call chain tracking |
| CN106998369A (en) * | 2017-05-26 | 2017-08-01 | 努比亚技术有限公司 | Gray scale dissemination method, gateway blocker and computer-readable recording medium |
| CN107920112A (en) * | 2017-11-01 | 2018-04-17 | 重庆金融资产交易所有限责任公司 | Support configuration file method for pushing, central server and the storage medium of grayscale mode |
| CN107818024A (en) * | 2017-11-22 | 2018-03-20 | 北京汇通金财信息科技有限公司 | A kind of request ID transmission methods and system based on spring blockers |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113495747A (en) * | 2020-04-07 | 2021-10-12 | 北京京东振世信息技术有限公司 | Gray scale publishing method and device |
| CN113495747B (en) * | 2020-04-07 | 2023-09-26 | 北京京东振世信息技术有限公司 | Gray scale release method and device |
| CN111538529A (en) * | 2020-04-27 | 2020-08-14 | 中国银行股份有限公司 | Gray scale publishing method and device |
| CN111897887A (en) * | 2020-08-06 | 2020-11-06 | 北京沃东天骏信息技术有限公司 | Parameter configuration method, device, system, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108153670B (en) | Interface testing method and device and electronic equipment | |
| US10361916B2 (en) | Cloud system order and configuration using customized templates | |
| JP6291034B2 (en) | User-influenced placement of virtual machine instances | |
| US10901696B2 (en) | Validating computer documentation via error detection in a natural language of the computer documentation | |
| US11288055B2 (en) | Model-based differencing to selectively generate and deploy images in a target computing environment | |
| CN110825425A (en) | Configuration data management method and device, electronic equipment and storage medium | |
| US11429429B2 (en) | Prefetch chaining for optimizing data read-ahead for workflow and analytics | |
| CN111061956A (en) | Method and apparatus for generating information | |
| CN112463154A (en) | Page generation method, device and system and electronic equipment | |
| CN104067262A (en) | Server-side minimal download and error failover | |
| CN114048415A (en) | Form generation method and device, electronic equipment and computer readable storage medium | |
| CN113204425A (en) | Method and device for process management internal thread, electronic equipment and storage medium | |
| CN111258618A (en) | File configuration method and device, computer equipment and storage medium | |
| CN116382761A (en) | Application management method, electronic equipment and storage medium | |
| CN107562461B (en) | Feature calculation system, feature calculation method, storage medium, and electronic device | |
| US10554770B2 (en) | Dynamic cognitive optimization of web applications | |
| CN114741294A (en) | Page debugging method, device, equipment and storage medium | |
| CN113312900A (en) | Data verification method and device | |
| CN113791819A (en) | Interface document generation method and device, storage medium and electronic equipment | |
| CN113448960A (en) | Method and device for importing form file | |
| CN113515328A (en) | Page rendering method and device, electronic equipment and storage medium | |
| CN113760356B (en) | Differential configuration method, device, equipment and medium of program product | |
| US20230396686A1 (en) | Configurable and adaptive resiliency in microservice architectures | |
| CN109587224B (en) | Data processing method and device, electronic equipment and computer readable medium | |
| CN117873549A (en) | Configuration method and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |