Configuration updating method, system and equipment and storage medium
By creating a shared storage mount configuration in the container group and utilizing a file change monitoring system, the synchronization delay and consistency issues of configuration updates in a multi-node environment are resolved, achieving efficient and consistent configuration updates.
Patent Information
- Application Number
- CN202511647150.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-11
- Publication Date
- 2026-02-13
AI Technical Summary
In a multi-node environment, this technology efficiently and consistently updates the configuration management resource objects of container groups, solving the synchronization delay and consistency problems of configuration updates in existing technologies.
By creating a shared storage mount configuration, a file change monitoring system is used to monitor configuration file changes and retrieve updated configuration files from the shared storage, enabling efficient updates of the container group.
It achieves efficient synchronization and consistency of configuration information, reduces update latency, improves configuration update performance, and ensures high availability and consistency of the system.
Smart Images

Figure CN121523722A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of cloud computing, and in particular to a configuration updating method, system, device and storage medium. BACKGROUND
[0002] In modern cloud-native applications, container management platforms provide powerful capabilities for managing and scheduling containerized applications. Configuration management resource objects are a resource type in container management platforms used to store non-confidential configuration data, and are widely used to store configuration parameters, environment variables, and the like of applications.
[0003] In a multi-node environment, when configuration management resource objects need to be frequently updated, how to efficiently and consistently synchronize updates to multiple container groups is one of the difficulties in configuration management of container management platforms. SUMMARY
[0004] The present application provides a configuration updating method, system, device and storage medium, which can efficiently and consistently update configurations in multiple nodes and container groups.
[0005] According to an aspect of the present application, a configuration updating method is provided, applied to a container group, comprising:
[0006] creating a mounting configuration of a shared storage, wherein the shared storage stores a configuration file containing configuration information of a configuration management resource object;
[0007] in response to a configuration file change message initiated by a file change monitoring system, obtaining an updated configuration file from the shared storage based on the mounting configuration;
[0008] wherein the file change monitoring system runs in a node where the current container group is located, and is used to monitor changes in the configuration file in the shared storage;
[0009] updating the current configuration information based on the updated configuration file.
[0010] According to another aspect of the present application, a configuration updating system is provided, comprising a shared storage and a container management cluster, wherein the container management cluster comprises at least one node, each node runs at least one container group and a file change monitoring system;
[0011] the shared storage is used to update a current configuration file currently stored based on an updated configuration management resource object in response to listening to a configuration management resource object update event of the container management cluster;
[0012] the file change monitoring system is used to monitor the configuration file in the shared storage, and send a configuration file change message to the container group in the node when the configuration file in the shared storage changes.
[0013] The container group is used to execute the configuration updating method in any of the embodiments of the application.
[0014] According to another aspect of the application, a configuration updating apparatus is provided, comprising:
[0015] A shared storage mounting module is configured to create a mounting configuration of the shared storage, and the shared storage stores a configuration file containing configuration information in a configuration management resource object;
[0016] An updating configuration obtaining module is configured to, in response to a configuration file change message initiated by a file change monitoring system, obtain an updating configuration file from the shared storage based on the mounting configuration;
[0017] The file change monitoring system is run in a node where the current container group is located, and is configured to monitor changes of the configuration file in the shared storage;
[0018] A configuration information updating module is configured to update the current configuration information based on the updating configuration file.
[0019] According to another aspect of the application, an electronic device is provided, comprising:
[0020] at least one processor; and
[0021] a memory connected to the at least one processor in communication; wherein
[0022] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the configuration updating method in any of the embodiments of the application.
[0023] According to another aspect of the application, a computer readable storage medium is provided, and the computer readable storage medium stores computer instructions for enabling a processor to implement the configuration updating method in any of the embodiments of the application when executed by the processor.
[0024] According to another aspect of the application, a computer program product is provided, comprising a computer program, and the computer program, when executed by a processor, implements the configuration updating method in any of the embodiments of the application.
[0025] The technical scheme of the embodiment of the present application creates a mounting configuration of shared storage, responds to a configuration file change message initiated by a file change monitoring system, obtains an updated configuration file from the shared storage based on the mounting configuration, and updates current configuration information based on the updated configuration file. By monitoring changes in the configuration file in the shared storage and initiating a configuration file change message to the container group in a timely manner when a change occurs, efficient synchronization and consistency of configuration information updates can be achieved.
[0026] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS
[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.
[0028] Figure 1 is a flowchart of a configuration update method according to an embodiment of the present application;
[0029] Figure 2 is a flowchart of a configuration update method according to an embodiment of the present application;
[0030] Figure 3 is an architecture diagram of a configuration update system according to an embodiment of the present application;
[0031] Figure 4 is a structural schematic diagram of a configuration update device according to an embodiment of the present application;
[0032] Figure 5 is a structural schematic diagram of an electronic device implementing the configuration update method of the embodiment of the present application. DETAILED DESCRIPTION
[0033] In order to better understand the present application by those skilled in the art, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should be within the scope of protection of the present application.
[0034] It should be noted that the terms "first", "second", and the like in the description and in the claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to only those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to such a process, method, product or device.
[0035] Embodiment one
[0036] Figure 1 A flowchart of a configuration updating method is provided for the first embodiment of the present application. The present embodiment can be applied to the case of combining the configuration management resource object of the container management cluster with the external shared storage to realize efficient synchronization and consistency guarantee of configuration information. The method can be executed by a configuration updating device, which can be realized in the form of hardware and / or software, and can be configured in various general-purpose computing devices. As shown in the figure, the method comprises: Figure 1
[0037] S110, creating a mounting configuration of the shared storage; the shared storage stores a configuration file containing configuration information in the configuration management resource object.
[0038] The shared storage is an architecture for realizing data sharing of multiple devices or processes through shared storage resources, which can improve the data consistency and reliability of shared objects. For example, the shared storage is a network file system, a reliable autonomous distributed object storage system, or a distributed file system. The shared storage stores a configuration file containing configuration information in the configuration management resource object. Specifically, the content of the configuration management resource object can be written into the shared storage by an external script to form a configuration file.
[0039] In the embodiment of the present application, in order to enable the container group to read the configuration information in the shared storage, the mounting configuration of the shared storage is first created in the container group. Specifically, the content of the initial configuration management resource object is written into the shared storage by initializing the container or an external script, so that the shared storage obtains the initial configuration information. Then, the directory of the shared storage is mounted to the local working path pre-set in the container group, so that the processes in the container group can access the shared storage in the form of directly accessing local files.
[0040] In one specific example, the shared storage is a network file system, and a persistent volume can be created first, then a persistent volume claim is created, and finally the shared storage is mounted to a local working path. Subsequent container groups can access the shared storage by directly accessing the local working path.
[0041] S120, in response to the configuration file change message initiated by the file change monitoring system, obtaining the updated configuration file from the shared storage based on the mounting configuration.
[0042] The file change monitoring system runs in the node where the current container group is located, and is used for change monitoring of the configuration file in the shared storage.
[0043] In the embodiment of the application, the shared storage updates the current configuration file stored in response to listening to the configuration management resource object update event of the container management cluster, and updates the configuration management resource object based on the updated configuration management resource object. In order to realize efficient updating of configuration information in the container group, the file change monitoring system is used for change monitoring of the configuration file in the shared storage. When it is detected that the configuration file in the shared storage is changed, the file change monitoring system sends a configuration file change message to the container group to ensure that the container group can obtain the updated configuration information in time. The container group obtains the updated configuration file from the shared storage based on the mounting configuration in response to the configuration file change message initiated by the file change monitoring system.
[0044] By monitoring the configuration file in the shared storage through the file change monitoring system, it can be ensured that the container group can obtain the latest configuration information in time, and the synchronization delay of the traditional updating method is solved, and the configuration synchronization efficiency is improved. By creating the shared storage mounting configuration, the processes in the container group access the shared storage in the form of directly accessing local files, and based on the efficient access performance of the shared storage, in the scene of frequent configuration updating, the configuration updating performance can be greatly improved.
[0045] By using the strong consistency feature of the shared storage, it is ensured that the container groups in all nodes of the cluster obtain the same configuration information, and the inconsistency problem caused by concurrent access is avoided. Moreover, by using the high-availability design of the shared storage, even if some nodes fail, other nodes can still access the latest configuration information, and the high availability of the system is ensured.
[0046] In one specific example, when the file change monitoring system detects that at least one configuration file in the shared storage is changed, the target container group associated with the changed configuration file is determined according to the mapping relationship table of the configuration file and the container group, and a configuration file change message is sent to the target container group. The target container group obtains the updated configuration file from the shared storage based on the mounting configuration.
[0047] In another specific example, when the file change monitoring system detects a change in at least one configuration file in shared storage, it sends a configuration file change message to the container group on the corresponding node to ensure that the container group can obtain the updated configuration information in a timely manner. In response to the configuration file change message initiated by the file change monitoring system, the container group retrieves the updated configuration file from the shared storage based on the mounted configuration. It can then determine the target updated configuration information associated with the current container group from the retrieved updated configuration information.
[0048] Optionally, before retrieving the updated configuration file from shared storage based on the mount configuration in response to a configuration file change message initiated by the file change monitoring system, the following steps are also included:
[0049] Mount the initial configuration management resource object in the container management cluster to the designated directory; the initial configuration management resource object includes the current configuration information.
[0050] In this optional embodiment, in response to a configuration file change message initiated by the file change monitoring system, before retrieving the updated configuration file from shared storage based on the mounted configuration, the initial configuration management resource object in the container management cluster is mounted to a designated directory to obtain the initial configuration information as the current configuration information in the container group. The initial configuration management resource object includes the current configuration information. Specifically, the initial configuration management resource object is mounted to the designated directory via a volume to obtain the current configuration information, enabling containers to directly access the configuration information within the initial configuration management resource object.
[0051] S130. Update the current configuration information based on the updated configuration file.
[0052] In this embodiment of the invention, containers in a container group can read the updated configuration information in the update configuration file, and then update the current configuration information based on the updated configuration information. Specifically, in the update configuration file, a target update configuration file associated with the current container group is determined, and the current configuration information is updated based on the target update configuration file.
[0053] The technical solution of this invention creates a shared storage mount configuration, responds to a configuration file change message initiated by the file change monitoring system, obtains an updated configuration file from the shared storage based on the mount configuration, and updates the current configuration information based on the updated configuration file. By monitoring changes to the configuration file in the shared storage and promptly initiating a configuration file change message to the container group when changes occur, efficient synchronization and consistency assurance of configuration information updates can be achieved.
[0054] Example 2
[0055] Figure 2A flowchart of a configuration updating method provided for the second embodiment of the present application is further refined on the basis of the above-mentioned embodiments, and provides specific steps of creating a mounting configuration of shared storage, specific steps of obtaining an updated configuration file from the shared storage based on the mounting configuration in response to a configuration file change message initiated by a file change monitoring system, and specific steps of updating current configuration information based on the updated configuration file. As shown in FIG. 10, the method comprises the following steps. Figure 2
[0056] S210, creating a persistent volume and a persistent volume claim pointing to the shared storage.
[0057] In the embodiment of the present application, in order to mount the shared storage to the local working path, a persistent volume and a persistent volume claim pointing to the shared storage are first created.
[0058] S220, mounting the shared storage to the local working path; the shared storage stores a configuration file containing configuration information in the configuration management resource object.
[0059] In the embodiment of the present application, on the basis of creating the persistent volume and the persistent volume claim, the content of the initial configuration management resource object is written into the shared storage through an initialization container or an external script, so that the shared storage obtains the initial configuration information. Further, the shared storage is mounted to the local working path, so that the processes in the container group can access the shared storage in the form of directly accessing local files.
[0060] In addition, the initial configuration management resource object in the container management cluster is mounted to a designated directory in the container group, so that the container group obtains the configuration information in the initial configuration management resource object as the current configuration information.
[0061] Optionally, the shared storage is at least one of a network file system, a reliable autonomous distributed object storage system, and a distributed file system.
[0062] S230, in response to a configuration file change message initiated by a file change monitoring system, obtaining an updated configuration file in the shared storage under the local working path mounted by the shared storage.
[0063] The file change monitoring system runs in the node where the current container group is located, and is used for monitoring changes of the configuration file in the shared storage. Further, the updated configuration information and the current configuration information in the current configuration file are compared to determine the information difference, and finally the current configuration file is incrementally updated based on the information difference.
[0064] The shared storage listens for update events of configuration management resource objects in the container management platform and extracts the updated configuration information from the updated configuration management resource objects. By adopting an incremental update strategy, only the changed configuration parts are updated, rather than a full overwrite of the entire configuration management resource object each time. This significantly reduces network load during updates and improves synchronization efficiency.
[0065] In this embodiment of the invention, the file change monitoring system runs on the node where the current container group resides. It monitors changes to configuration files in shared storage and, upon detecting a change, sends a configuration file change message to the container group on that node. Upon receiving the configuration file change message from the file change monitoring system, the container group retrieves the updated configuration file from the shared storage at its local working path.
[0066] In addition, to ensure system reliability, the shared storage also supports configuration rollback functionality. When configuration management resource object updates fail or encounter problems, the shared storage's version control mechanism can be used to restore to a historical version, ensuring system reliability.
[0067] S240. In the update configuration file, determine the target update configuration file associated with the current container group.
[0068] In this embodiment of the invention, when multiple update configuration files are obtained, it is necessary to determine the target update configuration file associated with the current container group from among the update configuration files.
[0069] S250: Update the current configuration information based on the target update configuration file.
[0070] The technical solution of this invention combines the configuration management resource object of the container management cluster with external shared storage. Leveraging the efficient file access and strong consistency features of shared storage, the content of the configuration management resource object is directly stored in the shared storage. Multiple nodes or container groups can read the configuration file in real time through the shared storage, without relying on the container management cluster's interface for synchronous updates. This eliminates synchronization latency issues and consistency problems between different nodes or container groups. By monitoring file changes in the shared storage, when the configuration management resource is updated, all container groups using that resource can detect the update in real time and read the latest configuration content from the shared storage, reducing update latency and improving resource utilization efficiency.
[0071] Example 3
[0072] Figure 3 This is a schematic diagram of a configuration update system provided in Embodiment 3 of the present invention. Figure 3As shown, the system comprises a shared storage 1 and a container management cluster 2, the container management cluster 2 comprising at least one node 21, at least one container group 211 and a file change monitoring system 212 running in each node 21;
[0073] The shared storage 1 is configured to, in response to listening to a configuration management resource object update event of the container management cluster 2, update a current configuration file currently stored based on an updated configuration management resource object.
[0074] In the embodiment of the application, the shared storage 1 updates the current configuration file currently stored based on the updated configuration management resource object in response to listening to the configuration management resource object update event of the container management cluster 2, so that the container group 211 mounted on the shared storage 1 can obtain the updated configuration file in the shared storage 1 in time.
[0075] Through the high availability and consistency guarantee mechanism of the shared storage 1, it is ensured that the data read by all nodes and container groups 211 is always consistent when the configuration file is updated. When multiple container groups 211 or nodes 21 access the same configuration, the problem of inconsistent data caused by concurrent access is avoided.
[0076] The shared storage 1 is at least one of a network file system, a reliable autonomous distributed object storage system, and a distributed file system.
[0077] The file change monitoring system 212 is configured to monitor the configuration file in the shared storage 1 and send a configuration file change message to the container group 211 in the node 21 when the configuration file in the shared storage 1 changes.
[0078] In the embodiment of the application, the file change monitoring system 212 runs in the node 21 where the current container group 211 is located, and is configured to monitor the configuration file in the shared storage 1. When the configuration file in the shared storage 1 changes, the file change monitoring system 212 sends a configuration file change message to the container group 211 in the node 21, so that the container group 211 can obtain the updated configuration information in time.
[0079] The container group 211 is configured to perform the following operations:
[0080] Create a mounting configuration of the shared storage 1; the shared storage 1 stores a configuration file containing configuration information in the configuration management resource object;
[0081] In response to the configuration file change message initiated by the file change monitoring system 212, obtain an updated configuration file from the shared storage 1 based on the mounting configuration;
[0082] The file change monitoring system 212 is run in the node 21 where the current container group 211 is located, and is used for monitoring changes of the configuration file in the shared storage 1.
[0083] The current configuration information is updated based on the updated configuration file.
[0084] When the container group 211 is mounted on the shared storage 1, the container group 211 acts as a client, and the shared storage 1 adopts a distributed system design, and the consistency of the data written by the container group 211 is ensured according to the design and configuration of the distributed storage.
[0085] The shared storage 1 is specifically used for:
[0086] In response to monitoring a configuration management resource object update event in the container management platform, updated configuration information in the updated configuration management resource object is extracted;
[0087] The updated configuration information is compared with current configuration information in the current configuration file to determine information differences;
[0088] The current configuration file is incrementally updated based on the information differences.
[0089] In the embodiment of the application, the shared storage 1 responds to the monitoring of the configuration management resource object update event in the container management platform, extracts the updated configuration information in the updated configuration management resource object, further compares the updated configuration information with the current configuration information in the current configuration file to determine information differences, and finally incrementally updates the current configuration file based on the information differences. Through the incremental update mechanism, only the changed part of the configuration file is updated, rather than the entire configuration file content being written into the shared storage 1 every time. In this way, the network transmission pressure and storage pressure caused by configuration update can be effectively reduced.
[0090] The shared storage 1 is further used for:
[0091] In response to a configuration management resource object update failure, a version management mechanism is run to roll back the updated configuration file.
[0092] In the embodiment of the application, a version management mechanism of the configuration file is run in the shared storage 1, so that the rollback operation of the configuration can be ensured. For example, in a distributed file system, a file version control function can be enabled. When the configuration update fails, for example, the configuration management resource object update fails, the version management mechanism is run to roll back the configuration file to a previous version to restore the normal operation of the system, thereby enhancing the reliability of the system.
[0093] The configuration information in the configuration management resource object is configured as the configuration source of the shared storage 1, the original configuration information of the program can be recorded, and the shared storage 1 records the configuration information update in the configuration management resource object, so that the version strategy of the background distributed service of the shared storage 1 is used to record the update of the configuration content without restarting the container group 211. The version control and rollback management of the shared storage 1 are key mechanisms to guarantee data consistency, traceability and disaster recovery capability. The background storage system realizes version control through snapshot, versioned object, incremental backup and the like, and supports rollback to a specific historical state, thereby providing a more flexible mechanism for version control of the application program.
[0094] The technical scheme of the embodiment of the application combines the configuration management resource object of the container management cluster and the external shared storage, directly stores the content of the configuration management resource object in the shared storage by using the efficient file access characteristics and the strong consistency features of the shared storage, and multiple nodes or container groups read the configuration file in real time through the shared storage without having to rely on the interface of the container management cluster for synchronous update, thereby solving the problem of synchronization delay and the consistency problem between different nodes or container groups. By monitoring the file change in the shared storage, when the configuration management resource is updated, all container groups using the configuration management resource can perceive the update in real time and read the latest configuration content from the shared storage, thereby reducing the update delay and improving the utilization efficiency of the resource.
[0095] Embodiment four
[0096] Figure 4 A structural schematic diagram of a configuration update device provided by the fourth embodiment of the application is shown in FIG. 4. Figure 4 As shown in the figure, the device comprises:
[0097] A shared storage mounting module 410, configured to create a mounting configuration of the shared storage; the shared storage stores a configuration file containing configuration information in a configuration management resource object;
[0098] An update configuration obtaining module 420, configured to, in response to a configuration file change message initiated by a file change monitoring system, obtain an updated configuration file from the shared storage based on the mounting configuration;
[0099] The file change monitoring system runs in a node where the current container group is located, and is configured to monitor the configuration file in the shared storage for change;
[0100] A configuration information updating module 430, configured to update the current configuration information based on the updated configuration file.
[0101] The technical scheme of the embodiment of the application creates a mounting configuration of shared storage, responds to a configuration file change message initiated by a file change monitoring system, obtains an updated configuration file from the shared storage based on the mounting configuration, and updates current configuration information based on the updated configuration file, thereby realizing efficient synchronization and consistency guarantee of configuration information update by monitoring changes of configuration files in the shared storage and initiating a configuration file change message to a container group in a timely manner when changes occur.
[0102] Optionally, the shared storage mounting module 410 is specifically configured to:
[0103] create a persistent volume and a persistent volume claim pointing to the shared storage;
[0104] mount the shared storage to a local working path;
[0105] The update configuration obtaining module 420 is specifically configured to:
[0106] obtain an updated configuration file in the shared storage under the local working path mounted by the shared storage in response to a configuration file change message initiated by a file change monitoring system.
[0107] Optionally, the configuration information updating module 430 is specifically configured to:
[0108] determine a target updated configuration file associated with the current container group in the updated configuration file;
[0109] update the current configuration information based on the target updated configuration file.
[0110] Optionally, the configuration updating apparatus further comprises:
[0111] An initial configuration mounting module is configured to mount an initial configuration management resource object in the container management cluster to a set directory before obtaining an updated configuration file from the shared storage based on the mounting configuration in response to a configuration file change message initiated by a file change monitoring system; the initial configuration management resource object comprises current configuration information.
[0112] The configuration updating apparatus provided in the embodiment of the application can execute the configuration updating method provided in any embodiment of the application, and has the corresponding function modules and beneficial effects of the execution method.
[0113] In the technical scheme of the application, the collected information is information and data authorized by the user or authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of related data comply with relevant laws, regulations and standards of relevant countries and regions, necessary security measures are taken, public order and good customs are not violated, and corresponding operation portals are provided for the user to select authorization or refusal.
[0114] Embodiment Five
[0115] According to embodiments of the present application, the present application also provides an electronic device, a readable storage medium and a computer program product.
[0116] Figure 5 A structural schematic diagram of an electronic device 10 that can be used to implement embodiments of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices (e.g., headsets, glasses, watches, etc.), and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application described and / or claimed in this document.
[0117] As shown in Figure 5 The electronic device 10 includes at least one processor 11, and a memory, such as a read-only memory 12, a random access memory 13, etc., connected to the at least one processor 11 in communication, where the memory stores computer programs executable by the at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer programs stored in the read-only memory 12 or loaded into the random access memory 13 from the storage unit 18. Various programs and data required for the operation of the electronic device 10 can also be stored in the random access memory 13. The processor 11, the read-only memory 12, and the random access memory 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0118] Various components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunications networks.
[0119] The processor 11 can be various general and / or special purpose processing components having processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, central processing units, graphics processing units, various specialized artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any appropriate processor, controller, microcontroller, etc. The processor 11 performs various methods and processes described above, such as the configuration update method.
[0120] In some embodiments, the configuration update method can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 10 via the read only memory 12 and / or the communication unit 19. One or more steps of the configuration update method described above can be performed when the computer program is loaded onto the random access memory 13 and executed by the processor 11. Alternatively, in other embodiments, the processor 11 can be configured, by way of firmware or otherwise, to execute the configuration update method.
[0121] Various implementations of the systems and techniques described above can be realized in digital electronic circuitry, integrated circuitry, specially designed application specific integrated circuits, application specific standard products, chips, microprocessors, computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
[0122] Computer programs used to implement the methods of the application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the computer program, when executed, implements the functions / acts specified in the flowcharts and / or block diagrams. The computer program can be executed entirely on a machine, partially on a machine and partially on a remote machine or entirely on a remote machine or application.
[0123] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of a machine-readable storage medium will include one or more lines of a program of instructions in a transitory signal, a portable computer diskette, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical fiber, a portable compact disc read-only memory, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0124] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a cathode ray tube or a liquid crystal display monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.
[0125] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data application server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network, a wide area network, a blockchain network, and the Internet.
[0126] A computing system can include a client and an applicator. The client and the applicator are generally remote from each other and typically interact through a communication network. The relationship of client and applicator arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The applicator can be a cloud applicator, also known as a cloud computing applicator or cloud host, which is a host product in the cloud computing application system to solve the defects of large management difficulty and weak business scalability in traditional physical host and virtual private service.
[0127] It should be understood that the various forms of flow shown above can be used to reorder, add or delete steps. For example, the steps described in the present application can be executed in parallel, sequentially or in a different order, as long as the desired results of the technical solutions of the present application can be achieved, which are not limited herein.
[0128] The above detailed description does not constitute a limitation on the scope of protection of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application shall be included in the scope of protection of the present application.
Claims
1. A configuration update method, characterized in that, include: Create a mount configuration for the shared storage; The shared storage contains configuration files that include configuration information from configuration management resource objects. In response to a configuration file change message initiated by the file change monitoring system, the updated configuration file is retrieved from the shared storage based on the mounted configuration. The file change monitoring system runs on the node where the current container group is located and is used to monitor changes to the configuration files in the shared storage. Based on the updated configuration file, the current configuration information is updated.
2. The method according to claim 1, characterized in that, Create a mount configuration for the shared storage, including: Create a persistent volume pointing to the shared storage and a persistent volume declaration; Mount the shared storage to the local working path; In response to a configuration file change message initiated by the file change monitoring system, based on the mounted configuration, the updated configuration file is retrieved from the shared storage, including: In response to a configuration file change message initiated by the file change monitoring system, the updated configuration file in the shared storage is retrieved from the local working path mounted on the shared storage.
3. The method according to claim 1, characterized in that, Based on the updated configuration file, the current configuration information is updated, including: In the update configuration file, specify the target update configuration file associated with the current container group; Based on the target update configuration file, the current configuration information is updated.
4. The method according to claim 1, characterized in that, Before retrieving the updated configuration file from shared storage based on the mounted configuration in response to a configuration file change message initiated by the file change monitoring system, the process also includes: Mount the initial configuration management resource object in the container management cluster to the designated directory; the initial configuration management resource object includes the current configuration information.
5. A configuration update system, characterized in that, It includes shared storage and a container management cluster, wherein the container management cluster includes at least one node, and each node runs at least one container group and a file change monitoring system; The shared storage is used to respond to a configuration management resource object update event detected by the container management cluster, and to update the current configuration file in the current storage based on the updated configuration management resource object. The file change monitoring system is used to monitor the configuration files in the shared storage, and when the configuration files in the shared storage are changed, it sends a configuration file change message to the container group in the node. The container group is used to execute the configuration update method as described in any one of claims 1-4.
6. The system according to claim 5, characterized in that, The shared storage is specifically used for: In response to the detection of an update event of the configuration management resource object in the container management platform, the updated configuration information in the updated configuration management resource object is extracted; The updated configuration information is compared with the current configuration information in the current configuration file to determine the differences. Based on the aforementioned information differences, the current configuration file is incrementally updated.
7. The system according to claim 5, characterized in that, The shared storage is also used for: In response to a failure to update a configuration management resource object, the updated configuration file is rolled back using the version management mechanism.
8. The system according to any one of claims 5-7, characterized in that, The shared storage is at least one of a network file system, a reliable autonomous distributed object storage system, and a distributed file system.
9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the configuration update method according to any one of claims 1-4.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the configuration update method according to any one of claims 1-4.