CN114936048B - Configuration management method, device, electronic equipment and storage medium - Google Patents

Configuration management method, device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114936048B
CN114936048B CN202210532236.4A CN202210532236A CN114936048B CN 114936048 B CN114936048 B CN 114936048B CN 202210532236 A CN202210532236 A CN 202210532236A CN 114936048 B CN114936048 B CN 114936048B
Authority
CN
China
Prior art keywords
resource object
configuration information
new resource
container
changed
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.)
Active
Application number
CN202210532236.4A
Other languages
Chinese (zh)
Other versions
CN114936048A (en
Inventor
陈凯
洪雨林
高杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202210532236.4A priority Critical patent/CN114936048B/en
Publication of CN114936048A publication Critical patent/CN114936048A/en
Application granted granted Critical
Publication of CN114936048B publication Critical patent/CN114936048B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45587—Isolation or security of virtual machine instances
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The disclosure relates to a configuration management method, a device, an electronic device and a storage medium, wherein the method comprises the following steps: under the condition that the changed configuration information of the historical resource object meets the preset condition, creating a new resource object corresponding to the historical resource object according to the changed configuration information; determining a target service container from a plurality of service containers associated with the historical resource object; according to the changed configuration information, the historical resource object associated with the target service container is adjusted to be the new resource object; and under the condition that the target service container associated with the new resource object is in a normal operation state, the historical resource objects associated with the service containers except the target service container in the service containers are adjusted to be the new resource object. The method can control the influence range within a certain range when the changed configuration information is in a problem, and reduce risks.

Description

Configuration management method, device, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a configuration management method, an apparatus, an electronic device, a storage medium, and a program product.
Background
In the actual production process, some variables possibly modified are often written into the configuration file in the form of configuration variables, so that in the service operation process, only the configuration can be changed without changing the operation program, and the change can be conveniently performed for various service scenes.
At present, configuration release is mostly based on the native release capability of kubernetes (an open-source container arrangement engine for automatically deploying, expanding and contracting and managing containerized applications), however, the native release method based on kubernetes is to update all service containers using the configuration in a full amount at a time when each configuration is changed, and if the changed configuration has a problem, all service containers have problems, and the risk is high.
Disclosure of Invention
The disclosure provides a configuration management method, a device, an electronic apparatus, a storage medium and a program product, so as to at least solve the technical problem of greater risk of a configuration release method in the related art. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a configuration management method, including:
Under the condition that the changed configuration information of the historical resource object meets the preset condition, creating a new resource object corresponding to the historical resource object according to the changed configuration information; the new resource object stores the changed configuration information;
determining a target service container from a plurality of service containers associated with the historical resource object;
according to the changed configuration information, the historical resource object associated with the target service container is adjusted to be the new resource object;
and under the condition that the target service container associated with the new resource object is in a normal operation state, the historical resource objects associated with the service containers except the target service container in the service containers are adjusted to be the new resource object.
In an exemplary embodiment, the method further comprises:
acquiring changed configuration information for the historical resource object;
analyzing the changed configuration information to obtain a configuration identifier of the changed configuration information;
and under the condition that the configuration identifier is different from the configuration identifier of the history configuration information stored in the history resource object, determining that the changed configuration information meets the preset condition.
In an exemplary embodiment, the method further comprises:
monitoring the synchronous state information of the new resource object changed to the target service container;
returning corresponding synchronous state information to a release terminal under the condition that the new resource object is monitored to be changed to the target service container, so that the release terminal displays the synchronous state information of the new resource object; the release terminal is a terminal for releasing the changed configuration information.
In an exemplary embodiment, the changed configuration information is stored in the new resource object in the form of a configuration file, and the method further includes:
acquiring a first identifier of each configuration file included in a resource object currently associated with the target service container and a second identifier of each configuration file included in the new resource object;
in the case that the first identifier and the second identifier of each configuration file are the same, determining that the new resource object is synchronized into the target service container.
In an exemplary embodiment, after adjusting the historical resource object associated with the target service container to the new resource object according to the changed configuration information, the method further includes:
Generating a business process restart instruction in the target business container if it is determined that the new resource object has been synchronized into the target business container; restarting the business process of the target business container according to the business process restarting instruction, so that the target business container operates based on the new resource object.
In an exemplary embodiment, after creating a new resource object corresponding to the historical resource object according to the changed configuration information, the method further includes:
generating a version identifier of the new resource object;
and obtaining the version configuration information of the new resource object based on the version identifier and the configuration information of the new resource object, and recording the version configuration information.
In an exemplary embodiment, the method further comprises:
any two versions of configuration information of the history record are obtained;
obtaining difference information between the two version configuration information based on a comparison result between the two version configuration information;
and sending the two versions of configuration information and the difference information to a release terminal for display.
According to a second aspect of the embodiments of the present disclosure, there is provided a configuration management apparatus, including:
A creation unit configured to create a new resource object corresponding to a history resource object according to changed configuration information if the changed configuration information for the history resource object satisfies a preset condition; the new resource object stores the changed configuration information;
a determining unit configured to perform determining a target service container from a plurality of service containers associated with the history resource object;
a first adjustment unit configured to perform adjustment of the history resource object associated with the target service container to the new resource object according to the changed configuration information;
and a second adjustment unit configured to perform adjustment of a history resource object associated with a service container other than the target service container among the plurality of service containers to the new resource object in a case where the target service container associated with the new resource object is in a normal operation state.
In an exemplary embodiment, the creating unit is further configured to perform obtaining changed configuration information for the historical resource object; analyzing the changed configuration information to obtain a configuration identifier of the changed configuration information; and under the condition that the configuration identifier is different from the configuration identifier of the history configuration information stored in the history resource object, determining that the changed configuration information meets the preset condition.
In an exemplary embodiment, the apparatus further comprises a listening unit configured to perform listening for synchronization status information of the new resource object changing to the target service container; returning corresponding synchronous state information to a release terminal under the condition that the new resource object is monitored to be changed to the target service container, so that the release terminal displays the synchronous state information of the new resource object; the release terminal is a terminal for releasing the changed configuration information.
In an exemplary embodiment, the changed configuration information is stored in the new resource object in the form of a configuration file, and the apparatus further includes a state determining unit configured to perform obtaining a first identifier of each configuration file included in the resource object currently associated with the target service container and a second identifier of each configuration file included in the new resource object; in the case that the first identifier and the second identifier of each configuration file are the same, determining that the new resource object is synchronized into the target service container.
In an exemplary embodiment, the apparatus further comprises a restart unit configured to execute a service process restart instruction in the target service container in case it is determined that the new resource object has been synchronized into the target service container; restarting the business process of the target business container according to the business process restarting instruction, so that the target business container operates based on the new resource object.
In an exemplary embodiment, the apparatus further comprises a management unit configured to perform generating a version identification of the new resource object; and obtaining the version configuration information of the new resource object based on the version identifier and the configuration information of the new resource object, and recording the version configuration information.
In an exemplary embodiment, the management unit is further configured to perform any two versions of configuration information of the acquisition history; obtaining difference information between the two version configuration information based on a comparison result between the two version configuration information; and sending the two versions of configuration information and the difference information to a release terminal for display.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of any of the above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the method as set forth in any one of the preceding claims.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising instructions therein, which when executed by a processor of an electronic device, enable the electronic device to perform the method of any one of the above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
under the condition that the changed configuration information of the historical resource object meets the preset condition, creating a new resource object corresponding to the historical resource object according to the changed configuration information; determining a target service container from a plurality of service containers associated with the historical resource objects; according to the changed configuration information, the historical resource object associated with the target service container is adjusted to be a new resource object; and under the condition that the target service container associated with the new resource object is in a normal operation state, the historical resource objects associated with the service containers except the target service container in the service containers are adjusted to be the new resource object. According to the method, the historical resource objects associated with the target service container are firstly adjusted to be new resource objects, and when the target service container is in a normal running state, the historical resource objects associated with the other service containers are adjusted to be new resource objects, so that when the changed configuration information is in a problem, the influence range is controlled within a certain range, and the risk is reduced, and the defects that all service containers are easy to cause and the risk is high in the conventional one-time full-quantity updating method are overcome.
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 disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
Fig. 1 is a flow diagram illustrating a configuration management method according to an exemplary embodiment.
Fig. 2 is a flow chart illustrating a step of matching the changed configuration information with the preset condition according to an exemplary embodiment.
Fig. 3 is a flow chart illustrating a configuration management method according to another exemplary embodiment.
FIG. 4 is a schematic diagram of a platform architecture of a configuration management system in an edge computing application scenario, according to an example embodiment.
Fig. 5 is a block diagram illustrating a configuration management apparatus according to an exemplary embodiment.
Fig. 6 is a block diagram of an electronic device, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the embodiments described in the following exemplary examples do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. It should be further noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for presentation, analyzed data, etc.) related to the present disclosure are information and data authorized by the user or sufficiently authorized by each party.
In an exemplary embodiment, as shown in fig. 1, a configuration management method is provided, where this embodiment is applied to a terminal to illustrate the method, it is understood that the method may also be applied to a server, and may also be applied to a system including a terminal and a server, and implemented through interaction between the terminal and the server. The terminal can be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things equipment and portable wearable equipment, and the internet of things equipment can be smart speakers, smart televisions, smart air conditioners, smart vehicle-mounted equipment and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers. In this embodiment, the method includes the steps of:
In step S110, when the changed configuration information for the history resource object satisfies the preset condition, creating a new resource object corresponding to the history resource object according to the changed configuration information; the new resource object stores the changed configuration information.
Where a resource object (configmap) may represent an API object in a kubernetes system for storing non-confidential data, such as configuration information.
The Kubernetes is abbreviated as K8S, and is an open-source container orchestration engine used for automatically deploying, expanding and managing containerized applications. Meanwhile, the Kubernetes system also provides various resource objects in a form and endows each resource object with different purposes. For example, secret type resources are used to store sensitive information such as passwords; the ConfigMap type resource is used for storing configuration information of the application program.
In the service operation process, when the service scene needs to be changed, the change can be realized through changing the configuration information, so that the operation program does not need to be changed.
In a specific implementation, when a terminal receives an instruction for changing the history configuration information stored for any history resource object and receives the changed configuration information, a new resource object associated with the same service container corresponding to the history resource object can be created according to the changed configuration information.
More specifically, before creating a new resource object according to the changed configuration information, in order to avoid creating multiple resource objects with the same configuration information, it may also be determined whether the changed configuration information satisfies a preset condition, that is, whether the changed configuration information and the history configuration information are repeated.
In one implementation, the configuration identifier of the changed configuration information and the configuration identifier of the history configuration information may be obtained respectively, and compared, if the configuration identifier of the changed configuration information and the configuration identifier of the history configuration information are the same, the corresponding resource object is created based on the changed configuration information, otherwise, if the configuration identifier of the changed configuration information and the configuration identifier of the history configuration information are different, the corresponding resource object is not created based on the changed configuration information, and a new resource object may be created based on the changed configuration information, and the changed configuration information may be stored by the new resource object.
In step S120, a target service container is determined from among the plurality of service containers associated with the history resource object.
Wherein a business container can be understood as a mirrored image of an application program after being containerized.
In a specific implementation, after a new resource object is obtained, since the running state of the service container when running based on the new resource object is unknown, the abnormal running state can occur. Therefore, in order to avoid the problem that the operation states of the service containers associated with the historical resource objects are abnormal, which leads to uncontrollable risks, a part of target service containers can be determined from a plurality of service containers associated with the historical resource objects, the historical resource objects associated with the target service containers are firstly adjusted to be new resource objects, and when the operation is normal, the historical resource objects associated with the rest service containers are then adjusted to be new resource objects.
More specifically, in one embodiment, the target service container may be determined from a plurality of service containers according to container information of the target service container submitted by the user; in another embodiment, a service container with a corresponding proportion may be randomly selected from a plurality of service containers according to a preset proportion, and the service container is used as a target service container. For example, if the preset ratio is 40%, and there are 20 service containers associated with the history resource object, 20×40% =8 service containers may be selected as the target service containers from the plurality of service containers associated with the history resource object.
In step S130, the historical resource object associated with the target service container is adjusted to a new resource object according to the changed configuration information.
In a specific implementation, after the target service container is determined, the historical resource object associated with the target service container can be adjusted to be a new resource object according to the changed configuration information. More specifically, the decoupling processing can be performed on the target service container and the history resource object mounted on the target service container, and then the new resource object is mounted in the target service container, so as to realize the change of the configuration information of the target service container.
In practical application, the terminal may also receive any version of the resource object specified by the user, and adjust the resource object currently associated with the target service container to be any version of the resource object.
In step S140, when the target service container to which the new resource object is associated is in the normal operation state, the history resource objects associated with the service containers other than the target service container among the plurality of service containers are adjusted to the new resource object.
In a specific implementation, when the target service container associated with the new resource object is in a normal running state, it indicates that the target service container is not abnormal based on the running of the new resource object, so that the decoupling processing with the history resource object can be performed one by one on other service containers except for the target service container in the plurality of service containers associated with the history resource object, and the new resource object is mounted in other service containers, thereby completing the change of the configuration information of each service container associated with the history resource object.
For example, if the service containers associated with the historical resource objects include A1, A2, …, and a10, and the target service containers determined from the service containers are A1 and A3, after obtaining a new resource object, the historical resource objects associated with the target service containers A1 and A3 may be adjusted to be new resource objects, and when the target service containers A1 and A3 are in a normal running state, the historical resource objects associated with the remaining service containers A2, A4, A5, …, and a10 are adjusted to be new resource objects one by one.
In the configuration management method, when the changed configuration information of the historical resource object meets the preset condition, a new resource object corresponding to the historical resource object is created according to the changed configuration information; determining a target service container from a plurality of service containers associated with the historical resource objects; according to the changed configuration information, the historical resource object associated with the target service container is adjusted to be a new resource object; and under the condition that the target service container associated with the new resource object is in a normal operation state, the historical resource objects associated with the service containers except the target service container in the service containers are adjusted to be the new resource object. According to the method, the historical resource objects associated with the target service container are firstly adjusted to be new resource objects, and when the target service container is in a normal running state, the historical resource objects associated with the other service containers are adjusted to be new resource objects, so that when the changed configuration information is in a problem, the influence range is controlled within a certain range, and the risk is reduced, and the defects that all service containers are easy to cause and the risk is high in the conventional one-time full-quantity updating method are overcome.
In an exemplary embodiment, as shown in fig. 2, in step S110, whether the changed configuration information meets the preset condition may be specifically implemented by the following steps:
in step S110a, changed configuration information for the history resource object is acquired;
in step S110b, the changed configuration information is analyzed to obtain a configuration identifier of the changed configuration information;
in step S110c, if the configuration identifier is different from the configuration identifier of the history configuration information stored in the history resource object, it is determined that the changed configuration information satisfies the preset condition.
The configuration identifier may be an identifier that characterizes the uniqueness of the configuration information, for example, the configuration identifier may be a hash value (hash value) obtained on the configuration information.
In a specific implementation, after each change of the configuration information of the resource object (configmap), analysis processing can be performed on the configuration information after each change, so as to obtain configuration identifiers of a plurality of historical configuration information, and the configuration identifiers obtained each time can be associated with corresponding historical configuration information and stored. After the changed configuration information of the historical resource object is obtained and the configuration identifier of the changed configuration information is obtained, the configuration identifier of the changed configuration information can be compared with the stored configuration identifiers of the historical configuration information, and when the configuration identifiers of the historical configuration information are different from the configuration identifiers of the changed configuration information, the changed configuration information is indicated to be changed, so that the changed configuration information can be determined to meet the preset condition, and a new resource object can be created according to the changed configuration information.
For example, assume that the version of a resource object is identified as: the configuration name and version number are configured, the configured historical resource objects comprise 4 versions of my-config-V1, my-config-V2, …, my-config-V4 and the like, hash values of configuration information of each version are respectively hash1, hash2, … and hash4, when the configuration information is changed again, the hash value of the changed configuration information is calculated and recorded as hash5, the hash5 is compared with the hash1, hash2 … and hash4, if the hash1, hash2 … and hash4 are different from the hash5, the changed configuration information is determined to meet preset conditions, and a new resource object my-config-V5 can be created according to the changed configuration information.
In this embodiment, by acquiring the configuration identifier of the changed configuration information and comparing the configuration identifier with the configuration identifier corresponding to the historical resource object, a new resource object is created according to the changed configuration information only when the configuration identifier and the configuration identifier are different, so that the problem that resource objects of multiple versions are created according to the same configuration information can be avoided.
In an exemplary embodiment, the method further includes: monitoring the synchronous state information of the new resource object changed to the target service container; returning corresponding synchronous state information to the release terminal under the condition that the new resource object is monitored to be changed to the target service container, so that the release terminal displays the synchronous state information of the new resource object; the distribution terminal is a terminal for distributing the changed configuration information.
The synchronization state information is used for representing the progress or state of changing the new resource object to the target service container.
In a specific implementation, since the process of adjusting the historical resource object associated with the target service container to the request of the new resource object is asynchronous, and the process of actually changing the new resource object to the target service container is asynchronous, after the adjustment request is issued, the user cannot accurately know whether the change is effective, so the embodiment proposes a mode of monitoring the process of changing the new resource to the target service container, and when the new resource object is monitored to be changed to the target service container, the corresponding synchronous state information is returned to the release terminal, so that the release terminal displays the synchronous state information of the new resource object for the user to check, so that the user can know the process of changing the new resource object to the target service container conveniently.
In this embodiment, by monitoring the process of changing the new resource to the target service container, and returning the obtained synchronization status information to the release terminal, and displaying the synchronization status information at the release terminal, the user can clearly and intuitively understand the progress and synchronization status of the configuration change.
In an exemplary embodiment, the changed configuration information is stored in the new resource object in the form of a configuration file, and the method further includes: acquiring a first identifier of each configuration file included in a resource object currently applied by a target service container and a second identifier of each configuration file included in a new resource object; in the case that the first identity and the second identity of each profile are the same, then it is determined that the new resource object has been synchronized into the target business container.
The first identifier and the second identifier may be identifiers that characterize the uniqueness of the configuration file, and may be understood as IDs of the file, for example, the first identifier and the second identifier may be md5 values of the configuration file.
In a specific implementation, the method for creating the new resource object according to the changed configuration information may be: generating a plurality of configuration files according to the changed configuration information, and obtaining new resource objects according to the configuration files, so that the configuration information is stored in the new resource objects in the form of the configuration files, and whether the new resource objects are changed into the target service container or not can be determined by the identification of the configuration files.
More specifically, the first identifier of each configuration file with the same file name and the second identifier of each configuration file can be obtained from the resource object currently associated with the target service container, that is, the first identifier of each configuration file included in the actually used resource object, and the second identifier of each configuration file included in the new resource object. Otherwise, when the first identification and the second identification of any configuration file are different, determining that the new resource object is not synchronized into the target service container.
For example, the first md5 values corresponding to all the configuration files in the resource object actually used by the target service container may be obtained, the second md5 values corresponding to all the configuration files in the new resource object may be obtained, the first md5 values and the second md5 values of the configuration files with the same file name are compared, and if the first md5 values and the second md5 values of the configuration files with the same file name are identical, it is determined that the configuration is synchronized, otherwise, the configuration is not synchronized.
In this embodiment, the first identifier of each configuration file included in the resource object currently associated with the target service container is compared with the second identifier of each configuration file included in the new resource object, so as to determine whether the new resource object is synchronized into the target service container according to the comparison result, and obtain synchronization status information of the new resource object, so that the new resource object is conveniently returned to the publishing terminal for display.
Further, after the new resource object has been synchronized into the target service container, the service processes in the target service container of most applications do not support real-time or periodic detection of the configuration change, so that the configuration change cannot be perceived, and the new configuration running program cannot be used, so in an exemplary embodiment, the disclosure further proposes that after step S130, according to the changed configuration information, the historical resource object associated with the target service container is adjusted to be the new resource object, which further includes: generating a business process restarting instruction in the target business container under the condition that the new resource object is determined to be synchronized into the target business container; and restarting the business process of the target business container according to the business process restarting instruction, so that the target business container operates based on the new resource object.
In a specific implementation, a restart instruction input entry (hook) with updated configuration information can be provided at an issue entry of a resource object for a user to fill in, for example, a cold/hot restart instruction of a service process can be filled in at the restart instruction input entry, and further after a new resource object is synchronized to a target service container, the service process of the target service container can be restarted according to the cold/hot restart instruction of the service process, so that the target service container operates based on the new resource object, and a service process operates according to the new configuration.
In this embodiment, a restart instruction input entry (hook) after configuration information update is provided at an issue entry of a resource object is used for filling by a user, so that after a new resource object is synchronized to a target service container, a service process of the target service container can be restarted according to a service process restart instruction, and the perception of the service process on configuration change is realized, so that the target service container can operate based on the new resource object.
In an exemplary embodiment, after creating a new resource object corresponding to the historical resource object according to the changed configuration information in step S110, the method further includes: generating a version identifier of the new resource object; based on the version identification and the configuration information of the new resource object, the version configuration information of the new resource object is obtained, and the version configuration information is recorded.
Where the version identification is an identification characterizing the uniqueness of the new resource object, for example, the version identification may include a resource object name and a version number, e.g., config-V1.
In a specific implementation, after a new resource object corresponding to the historical resource object is created according to the changed configuration information, the version identifier of the new resource object may be generated by combining the version identifiers of the historical resource object, for example, the version identifiers of the historical resource object are config-V1 and config-V2, and then the version identifier of the new resource object may be marked as config-V3, so that the new resource object and the historical resource object have the same resource object name and different version numbers, and a certain regularity may be provided between the version numbers. Further, a mapping relationship between the version identifier of the new resource object and the updated configuration information stored in the new resource object can be established, and the mapping relationship and the version configuration information obtained based on the mapping relationship are recorded.
In this embodiment, by generating the version identifier of the new resource object and recording the version configuration information of the new resource object based on the version identifier and the configuration information of the new resource object, the configuration information of each version can be checked or the difference between the configuration information of each version can be compared, and the version with the problem can be accurately located and configuration rollback processing is facilitated.
In an exemplary embodiment, the method further includes: any two versions of configuration information of the history record are obtained; obtaining difference information between the two version configuration information based on a comparison result between the two version configuration information; and sending the two versions of configuration information and the difference information to the release terminal for display.
In a specific implementation, by recording version configuration information of each version, when a user needs to compare configuration information of any two versions, the comparison instruction of the configuration information of any two versions triggered by the user can be responded, the configuration information of any two versions is obtained and compared, and difference information between the configuration information of the two versions is obtained based on a comparison result, and the difference information can be marked, so that after the configuration information of the two versions and the difference information are sent to a release terminal, the configuration information of the two versions and the marked difference information can be displayed at the release terminal.
In this embodiment, by acquiring any two versions of configuration information of the history record, based on a comparison result between the two versions of configuration information, difference information between the two versions of configuration information is obtained, and the two versions of configuration information and the difference information are sent to the release terminal for display, so that a user can clearly and intuitively check and compare difference points between resource objects of each version.
In another exemplary embodiment, as shown in fig. 3, there is a flowchart of another configuration management method according to an exemplary embodiment, in this embodiment, the method includes the steps of:
step S310, acquiring changed configuration information for a history resource object;
step S320, analyzing the changed configuration information to obtain a configuration identifier of the changed configuration information;
step S330, comparing the configuration identifier with the configuration identifier of the history configuration information stored in the history resource object, if the configuration identifier is different from the configuration identifier of the history configuration information stored in the history resource object, determining that the changed configuration information meets the preset condition, otherwise, determining that the changed configuration information does not meet the preset condition;
step S340, under the condition that the preset condition is met, creating a new resource object corresponding to the historical resource object according to the changed configuration information;
step S350, determining a target service container from a plurality of service containers associated with the historical resource objects;
step S360, according to the changed configuration information, the history resource object associated with the target service container is adjusted to be a new resource object, and the synchronization state information of the new resource object changed to the target service container is monitored;
Step S370, returning corresponding synchronous state information to the release terminal under the condition that the new resource object is monitored to be changed to the target service container, so that the release terminal displays the synchronous state information of the new resource object;
in step S380, when the target service container associated with the new resource object is in the normal operation state, the historical resource objects associated with the service containers except the target service container in the plurality of service containers are adjusted to be the new resource object.
According to the configuration management method provided by the embodiment, the historical resource objects associated with the target service container are adjusted to be new resource objects, and when the target service container is in a normal running state, the historical resource objects associated with the other service containers are adjusted to be new resource objects, so that when the configuration information after being changed is in a problem, the influence range is controlled within a certain range, the risk is reduced, and the defects that all service containers are easy to cause the problem and the risk is high in the traditional one-time full-quantity updating method are overcome.
In an exemplary embodiment, for the convenience of those skilled in the art to understand the embodiments of the present disclosure, the following description will be made with reference to specific examples of the accompanying drawings. Referring to fig. 4, a schematic diagram of a platform architecture of a configuration management system in an edge computing application scenario in an exemplary embodiment is shown. The configuration management system is added with an operation release system based on k8s (kubernetes, open-source container arrangement engine), one of core components of the operation release system is a release component (kes-api) which is used for carrying out some preprocessing and pre-scheduling on requests issued by users, and then issuing the requests to a data center (api-server) of k8 s. While a processing component (kes-sender) is added at the edge node for some processing and data collection of the pods (a set(s) of containers that can be created and managed in Kubernetes, the smallest, deployable computing unit) on that node. The whole scheme is divided into three parts, namely configuration change, configuration release, configuration comparison and viewing.
(1) Configuration change
When the user modifies the configuration information in the resource object (configmap), a new resource object is re-created through the release component (es-api), the naming mode of the new resource object is the configuration name+version number, and after the configuration information is modified, the naming mode of the newly generated resource object is the my-config-v1. Before generating the new configmap, the issuing component (es-api) hashes the changed configuration information to prevent the same configuration from creating multiple versions of resource objects, that is, only when the configuration information in the resource objects changes, the new resource objects are generated.
(2) Configuration release
When a user needs to change the changed configuration information into a service container (pod), gray processing can be performed through an edge computing platform issuing system, a change request is issued in batches according to the version to be changed or a designated target service container, an issuing component (es-api) finds a resource object of the designated version, and the mounting point of the service container (pod) is modified to mount a new resource object into the corresponding service container, and because the resource object can be automatically reloaded by a management component (kubelet), the service container is not required to be rebuilt for updating the resource object.
Meanwhile, although the management component (kubelet) can automatically reload the resource object, because the process from the sending of the resource object change request to the node where the actual update to the target service container is located is asynchronous, after the user sends the change request, the user cannot accurately know whether the change is effective or not, so that the actual synchronous state of the resource object needs to be collected and returned to the edge computing platform release terminal for the user to check; the method for acquiring the synchronization state of the resource object may be:
(1) Acquiring a resource object actually used by a target service container on a node through a processing component (es-sender), and calculating md5 values corresponding to configuration files included in the actually used resource object;
(2) And (3) finding a corresponding directory of the new resource object on the server through a processing component (es-sender), respectively calculating the md5 value (key in the resource object represents the file name) of each configuration file under the directory, comparing with the md5 value calculated in the step (1), and determining that the new resource object is synchronized into the target service container when the md5 values of the configuration files with the same file names are the same, or not synchronizing.
Further, after the new resource object is synchronized to the node where the target service container is located, the service process in the target service container needs to sense the change of the configuration file and perform restarting loading or hot loading, but some services do not currently have the capability, so that the edge computing issuing platform provides a restarting instruction input port (hook) after the configuration file is updated at the entry issued by the resource object and is used for inputting a cold/hot restarting instruction of the service process, and therefore after the new resource object is synchronized to the node, the service process can complete the final update of the service configuration by triggering the configuration hook, and service personnel can complete the configuration change without any intervention.
(3) Configuration contrast and viewing
In order to facilitate the user to check the configuration details and compare the differences among the versions of the configuration, the edge computing and publishing platform can also configure the checking and comparing functions. The user can select any two versions of the configuration, acquire the contents configuring the two versions through a release component (es-api) and display and mark tolerance outliers in the release terminal.
The configuration management method creatively solves the problems that the version management capability of the original resource object is not enough and gray release cannot be achieved, greatly improves the configuration maintenance efficiency of the service, and simultaneously effectively improves the configuration change stability and the platform user experience.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
It should be understood that the same/similar parts of the embodiments of the method described above in this specification may be referred to each other, and each embodiment focuses on differences from other embodiments, and references to descriptions of other method embodiments are only needed.
Based on the same inventive concept, the embodiments of the present disclosure also provide a configuration management apparatus for implementing the above-mentioned related configuration management method.
Fig. 5 is a block diagram illustrating a configuration management apparatus according to an exemplary embodiment. Referring to fig. 5, the apparatus includes: a creation unit 510, a determination unit 520, a first adjustment unit 530, and a second adjustment unit 540, wherein,
a creation unit 510 configured to create a new resource object corresponding to the history resource object according to the changed configuration information if the changed configuration information for the history resource object satisfies a preset condition; the new resource object stores the changed configuration information;
a determining unit 520 configured to perform determining a target service container from a plurality of service containers associated with the history resource object;
a first adjusting unit 530 configured to perform adjustment of the historical resource object associated with the target service container to a new resource object according to the changed configuration information;
The second adjusting unit 540 is configured to perform, when the target service container associated with the new resource object is in a normal operation state, adjustment of the historical resource objects associated with the service containers other than the target service container among the plurality of service containers to the new resource object.
In an exemplary embodiment, the creating unit 510 is further configured to perform obtaining changed configuration information for the historical resource object; analyzing the changed configuration information to obtain a configuration identifier of the changed configuration information; and under the condition that the configuration identifier is different from the configuration identifier of the history configuration information stored in the history resource object, determining that the changed configuration information meets the preset condition.
In an exemplary embodiment, the apparatus further comprises a listening unit configured to perform listening for synchronization status information of a new resource object change to the target service container; returning corresponding synchronous state information to the release terminal under the condition that the new resource object is monitored to be changed to the target service container, so that the release terminal displays the synchronous state information of the new resource object; the distribution terminal is a terminal for distributing the changed configuration information.
In an exemplary embodiment, the changed configuration information is stored in the new resource object in the form of a configuration file, and the apparatus further includes a state determining unit configured to perform obtaining a first identifier of each configuration file included in the resource object currently associated with the target service container and a second identifier of each configuration file included in the new resource object; in the case that the first identity and the second identity of each profile are the same, then it is determined that the new resource object has been synchronized into the target business container.
In an exemplary embodiment, the apparatus further comprises a restart unit configured to execute a business process restart instruction in the target business container in case it is determined that the new resource object has been synchronized into the target business container; and restarting the business process of the target business container according to the business process restarting instruction, so that the target business container operates based on the new resource object.
In an exemplary embodiment, the apparatus further comprises a management unit configured to perform generating a version identification of the new resource object; based on the version identification and the configuration information of the new resource object, the version configuration information of the new resource object is obtained, and the version configuration information is recorded.
In an exemplary embodiment, the management unit is further configured to perform any two versions of configuration information of the acquisition history; obtaining difference information between the two version configuration information based on a comparison result between the two version configuration information; and sending the two versions of configuration information and the difference information to the release terminal for display.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 6 is a block diagram illustrating an electronic device 600 for implementing a configuration management method, according to an example embodiment. For example, the electronic device 600 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 6, an electronic device 600 may include one or more of the following components: a processing component 602, a memory 604, a power component 606, a multimedia component 608, an audio component 610, an input/output (I/O) interface 612, a sensor component 614, and a communication component 616.
The processing component 602 generally controls overall operation of the electronic device 600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.
The memory 604 is configured to store various types of data to support operations at the electronic device 600. Examples of such data include instructions for any application or method operating on the electronic device 600, contact data, phonebook data, messages, pictures, video, and so forth. The memory 604 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, optical disk, or graphene memory.
The power supply component 606 provides power to the various components of the electronic device 600. The power supply components 606 can include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the electronic device 600.
The multimedia component 608 includes a screen between the electronic device 600 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front camera and/or a rear camera. When the electronic device 600 is in an operational mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 610 is configured to output and/or input audio signals. For example, the audio component 610 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 600 is in an operational mode, such as a call mode, a recording mode, and a speech recognition mode. The received audio signals may be further stored in the memory 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.
The I/O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 614 includes one or more sensors for providing status assessment of various aspects of the electronic device 600. For example, the sensor assembly 614 may detect an on/off state of the electronic device 600, a relative positioning of the components, such as a display and keypad of the electronic device 600, the sensor assembly 614 may also detect a change in position of the electronic device 600 or an electronic device 600 component, the presence or absence of a user's contact with the electronic device 600, an orientation or acceleration/deceleration of the device 600, and a change in temperature of the electronic device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 616 is configured to facilitate communication between the electronic device 600 and other devices, either wired or wireless. The electronic device 600 may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 616 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the electronic device 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a computer-readable storage medium is also provided, such as memory 604, including instructions executable by processor 620 of electronic device 600 to perform the above-described method. For example, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product is also provided, comprising instructions executable by the processor 620 of the electronic device 600 to perform the above-described method.
It should be noted that the descriptions of the foregoing apparatus, the electronic device, the computer readable storage medium, the computer program product, and the like according to the method embodiments may further include other implementations, and the specific implementation may refer to the descriptions of the related method embodiments and are not described herein in detail.
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 disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general 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.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (17)

1. A method of configuration management, comprising:
under the condition that the changed configuration information of the historical resource object meets the preset condition, creating a new resource object corresponding to the historical resource object according to the changed configuration information; the new resource object stores the changed configuration information;
determining a target service container from a plurality of service containers associated with the historical resource object;
according to the changed configuration information, the historical resource object associated with the target service container is adjusted to be the new resource object;
under the condition that a target service container associated with the new resource object is in a normal operation state, adjusting historical resource objects associated with service containers except the target service container in the service containers to the new resource object;
the method further comprises the steps of: monitoring the synchronous state information of the new resource object changed to the target service container;
returning corresponding synchronous state information to a release terminal under the condition that the new resource object is monitored to be changed to the target service container, so that the release terminal displays the synchronous state information of the new resource object; the release terminal is a terminal for releasing the changed configuration information.
2. The method according to claim 1, wherein the method further comprises:
acquiring changed configuration information for the historical resource object;
analyzing the changed configuration information to obtain a configuration identifier of the changed configuration information;
and under the condition that the configuration identifier is different from the configuration identifier of the history configuration information stored in the history resource object, determining that the changed configuration information meets the preset condition.
3. The method of claim 1, wherein said determining a target business container from a plurality of business containers associated with said historical resource object comprises:
determining a target service container from the plurality of service containers according to container information of the target service container submitted by a user; or,
and randomly selecting a service container with a corresponding proportion from the plurality of service containers according to a preset proportion, and taking the service container with the corresponding proportion as a target service container.
4. The method of claim 1, wherein the altered configuration information is stored in the new resource object in the form of a configuration file, the method further comprising:
acquiring a first identifier of each configuration file included in a resource object currently associated with the target service container and a second identifier of each configuration file included in the new resource object;
In the case that the first identifier and the second identifier of each configuration file are the same, determining that the new resource object is synchronized into the target service container.
5. The method of claim 1, further comprising, after adjusting the historical resource object associated with the target business container to the new resource object based on the changed configuration information:
generating a business process restart instruction in the target business container if it is determined that the new resource object has been synchronized into the target business container;
restarting the business process of the target business container according to the business process restarting instruction, so that the target business container operates based on the new resource object.
6. The method of claim 1, further comprising, after creating a new resource object corresponding to the historical resource object based on the altered configuration information:
generating a version identifier of the new resource object;
and obtaining the version configuration information of the new resource object based on the version identifier and the configuration information of the new resource object, and recording the version configuration information.
7. The method of claim 6, wherein the method further comprises:
any two versions of configuration information of the history record are obtained;
obtaining difference information between the two version configuration information based on a comparison result between the two version configuration information;
and sending the two versions of configuration information and the difference information to a release terminal for display.
8. A configuration management apparatus, comprising:
a creation unit configured to create a new resource object corresponding to a history resource object according to changed configuration information if the changed configuration information for the history resource object satisfies a preset condition; the new resource object stores the changed configuration information;
a determining unit configured to perform determining a target service container from a plurality of service containers associated with the history resource object;
a first adjustment unit configured to perform adjustment of the history resource object associated with the target service container to the new resource object according to the changed configuration information;
a second adjustment unit configured to perform adjustment of a history resource object associated with a service container other than the target service container among the plurality of service containers to the new resource object in a case where the target service container associated with the new resource object is in a normal operation state;
A monitoring unit configured to perform monitoring of synchronization status information of the new resource object changed to the target service container; returning corresponding synchronous state information to a release terminal under the condition that the new resource object is monitored to be changed to the target service container, so that the release terminal displays the synchronous state information of the new resource object; the release terminal is a terminal for releasing the changed configuration information.
9. The apparatus of claim 8, wherein the creation unit is further configured to perform obtaining changed configuration information for a historical resource object; analyzing the changed configuration information to obtain a configuration identifier of the changed configuration information; and under the condition that the configuration identifier is different from the configuration identifier of the history configuration information stored in the history resource object, determining that the changed configuration information meets the preset condition.
10. The apparatus according to claim 8, wherein the determining unit is further configured to perform determining a target service container from the plurality of service containers according to container information of the target service container submitted by the user; or, according to the preset proportion, randomly selecting the service container with the corresponding proportion from the plurality of service containers as the target service container.
11. The apparatus according to claim 8, wherein the changed configuration information is stored in the new resource object in the form of a configuration file, the apparatus further comprising a state determining unit configured to perform obtaining a first identification of each configuration file included in the resource object currently associated with the target service container, and a second identification of each configuration file included in the new resource object; in the case that the first identifier and the second identifier of each configuration file are the same, determining that the new resource object is synchronized into the target service container.
12. The apparatus according to claim 8, further comprising a restart unit configured to execute a business process restart instruction in the target business container if it is determined that the new resource object has been synchronized into the target business container; restarting the business process of the target business container according to the business process restarting instruction, so that the target business container operates based on the new resource object.
13. The apparatus of claim 8, further comprising a management unit configured to perform generating a version identification of the new resource object; and obtaining the version configuration information of the new resource object based on the version identifier and the configuration information of the new resource object, and recording the version configuration information.
14. The apparatus of claim 13, wherein the management unit is further configured to perform any two versions of the configuration information of the acquisition history; obtaining difference information between the two version configuration information based on a comparison result between the two version configuration information; and sending the two versions of configuration information and the difference information to a release terminal for display.
15. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the configuration management method of any one of claims 1 to 7.
16. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of configuration management according to any one of claims 1 to 7.
17. A computer program product comprising instructions which, when executed by a processor of an electronic device, enable the electronic device to perform the configuration management method of any one of claims 1 to 7.
CN202210532236.4A 2022-05-10 2022-05-10 Configuration management method, device, electronic equipment and storage medium Active CN114936048B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210532236.4A CN114936048B (en) 2022-05-10 2022-05-10 Configuration management method, device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210532236.4A CN114936048B (en) 2022-05-10 2022-05-10 Configuration management method, device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114936048A CN114936048A (en) 2022-08-23
CN114936048B true CN114936048B (en) 2024-03-19

Family

ID=82864733

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210532236.4A Active CN114936048B (en) 2022-05-10 2022-05-10 Configuration management method, device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114936048B (en)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015197564A1 (en) * 2014-06-23 2015-12-30 Getclouder Ltd. Cloud hosting systems featuring scaling and load balancing with containers
CN110007929A (en) * 2018-01-02 2019-07-12 ***通信有限公司研究院 The method and device of resource is obtained under a kind of mixed deployment
CN111651178A (en) * 2020-05-27 2020-09-11 平安普惠企业管理有限公司 Container configuration updating method and device, computer equipment and storage medium
CN111651187A (en) * 2020-06-01 2020-09-11 福建天晴在线互动科技有限公司 Method and system for updating version increment based on H5 micro terminal
CN111737082A (en) * 2020-06-19 2020-10-02 中国建设银行股份有限公司 Container and monitoring method, device, equipment and medium for container application
CN112130889A (en) * 2020-09-15 2020-12-25 北京金山云网络技术有限公司 Resource management method and device, storage medium and electronic device
CN112346926A (en) * 2020-10-16 2021-02-09 北京金山云网络技术有限公司 Resource state monitoring method and device and electronic equipment
CN112417051A (en) * 2020-12-01 2021-02-26 腾讯科技（深圳）有限公司 Container arrangement engine resource management method and device, readable medium and electronic equipment
CN112947965A (en) * 2021-03-01 2021-06-11 北京百度网讯科技有限公司 Containerized service updating method and device
CN113296872A (en) * 2020-04-13 2021-08-24 阿里巴巴集团控股有限公司 Container state query method, device, equipment, storage medium and system
CN113778623A (en) * 2021-08-26 2021-12-10 北京达佳互联信息技术有限公司 Resource processing method and device, electronic equipment and storage medium
CN113949707A (en) * 2021-09-30 2022-01-18 上海浦东发展银行股份有限公司 OpenResty and K8S-based container cloud service discovery and load balancing method
CN114079615A (en) * 2021-11-17 2022-02-22 上海道客网络科技有限公司 Application synchronization method, system, medium and electronic device in multi-cluster environment

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11200081B2 (en) * 2019-10-21 2021-12-14 ForgeRock, Inc. Systems and methods for tuning containers in a high availability environment

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015197564A1 (en) * 2014-06-23 2015-12-30 Getclouder Ltd. Cloud hosting systems featuring scaling and load balancing with containers
CN110007929A (en) * 2018-01-02 2019-07-12 ***通信有限公司研究院 The method and device of resource is obtained under a kind of mixed deployment
CN113296872A (en) * 2020-04-13 2021-08-24 阿里巴巴集团控股有限公司 Container state query method, device, equipment, storage medium and system
CN111651178A (en) * 2020-05-27 2020-09-11 平安普惠企业管理有限公司 Container configuration updating method and device, computer equipment and storage medium
CN111651187A (en) * 2020-06-01 2020-09-11 福建天晴在线互动科技有限公司 Method and system for updating version increment based on H5 micro terminal
CN111737082A (en) * 2020-06-19 2020-10-02 中国建设银行股份有限公司 Container and monitoring method, device, equipment and medium for container application
CN112130889A (en) * 2020-09-15 2020-12-25 北京金山云网络技术有限公司 Resource management method and device, storage medium and electronic device
CN112346926A (en) * 2020-10-16 2021-02-09 北京金山云网络技术有限公司 Resource state monitoring method and device and electronic equipment
CN112417051A (en) * 2020-12-01 2021-02-26 腾讯科技（深圳）有限公司 Container arrangement engine resource management method and device, readable medium and electronic equipment
CN112947965A (en) * 2021-03-01 2021-06-11 北京百度网讯科技有限公司 Containerized service updating method and device
CN113778623A (en) * 2021-08-26 2021-12-10 北京达佳互联信息技术有限公司 Resource processing method and device, electronic equipment and storage medium
CN113949707A (en) * 2021-09-30 2022-01-18 上海浦东发展银行股份有限公司 OpenResty and K8S-based container cloud service discovery and load balancing method
CN114079615A (en) * 2021-11-17 2022-02-22 上海道客网络科技有限公司 Application synchronization method, system, medium and electronic device in multi-cluster environment

Also Published As

Publication number Publication date
CN114936048A (en) 2022-08-23

Similar Documents

Publication Publication Date Title
CN109388625B (en) Method and device for processing configuration file in multi-distributed file system
CN106354571B (en) Message reminding method and device
RU2645282C2 (en) Method and device for calling via cloud-cards
CN110737844B (en) Data recommendation method and device, terminal equipment and storage medium
CN113099262B (en) Information display method and device, electronic equipment and storage medium
CN106095405B (en) Icon updating method and device
CN115185717B (en) Interface calling method and device, electronic equipment and storage medium
US20160026719A1 (en) Methods and devices for sharing resources
CN107395624B (en) Information processing method and device
CN112528185A (en) Comment information display method and device, server and terminal
CN113259226A (en) Information synchronization method and device, electronic equipment and storage medium
CN104951522B (en) Method and device for searching
CN106506808B (en) Method and device for prompting communication message
CN110908814A (en) Message processing method and device, electronic equipment and storage medium
CN114936048B (en) Configuration management method, device, electronic equipment and storage medium
CN114268802B (en) Virtual space display method and device, electronic equipment and storage medium
CN108012258B (en) Data traffic management method and device for virtual SIM card, terminal and server
CN114066370A (en) Inventory service calling method, device, equipment, storage medium and program product
CN114567790A (en) Information display method and device, electronic equipment and storage medium
CN110457084B (en) Loading method and device
CN113868562A (en) Resource acquisition method, device, system, electronic equipment and readable storage medium
CN110807116B (en) Data processing method and device for data processing
CN107257384B (en) Service state monitoring method and device
CN111736890A (en) Data updating method and device, electronic equipment and storage medium
CN113098781A (en) Session list processing method, device, server and storage medium

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
GR01 Patent grant
GR01 Patent grant