CN113900728A - Method, system, electronic device and storage medium for synchronous configuration - Google Patents
Method, system, electronic device and storage medium for synchronous configuration Download PDFInfo
- Publication number
- CN113900728A CN113900728A CN202111097262.0A CN202111097262A CN113900728A CN 113900728 A CN113900728 A CN 113900728A CN 202111097262 A CN202111097262 A CN 202111097262A CN 113900728 A CN113900728 A CN 113900728A
- Authority
- CN
- China
- Prior art keywords
- agent
- configuration
- neutron
- server
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 65
- 230000001360 synchronised effect Effects 0.000 title claims abstract description 21
- 230000008859 change Effects 0.000 claims abstract description 23
- 230000008569 process Effects 0.000 claims abstract description 23
- 230000006870 function Effects 0.000 claims description 40
- 230000004048 modification Effects 0.000 claims description 14
- 238000012986 modification Methods 0.000 claims description 14
- 238000012545 processing Methods 0.000 claims description 13
- 238000005096 rolling process Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
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
Abstract
The invention discloses a method, a system, electronic equipment and a storage medium for synchronous configuration, belongs to the technical field of cloud computing, and aims to solve the technical problem of realizing the synchronization of configuration information of a plurality of computing nodes and avoiding restarting all agents, wherein the technical scheme is as follows: the method comprises the following specific steps: modifying the configuration file of the neutron agent of the designated node and reloading the agent service; the neutron agent reloads the configuration file and sends the current configuration to a neutron-server; the neutron-server receives the configuration content sent by the agent end, takes out the previous cooperation, and stores the new configuration in the database to cover the previous configuration; the neutron-server compares the contents of the configuration files of the previous and subsequent times to determine whether the contents of the configuration files are consistent or not: if not, triggering a hook function and triggering an event of configuration change; the module for registering the callback function receives and processes the event of the configuration change; wherein events of configuration changes that need to be handled separately will be notified to the agent service in the form of RPC.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a method, a system, electronic equipment and a storage medium for synchronous configuration.
Background
OpenStack is an open-source cloud operating system with the capability of managing large computing, storage, and network resources in a data center. Through a uniform user interface, an administrator can manage resources such as virtual machines, virtual storage, virtual networks and the like in the data center; the tenant through the network console can create the resources it needs.
Neutron is a sub-item in Openstack for managing virtual network resources, and provides network service for virtual network interfaces created by nova and other applications. Different types of virtual networks such as vlan and vxlan can be created according to the needs of users; creating a virtual three-layer router of a vrouter and a floating IP; provide network QoS functionality, and the like. In deployment, neutron supports the use of linux bridge, Open vSwitch, and other backend-provided bottom-layer SDN implementations.
Because of the particularity of the neutron network agent, the agent is often required to run on all computer nodes, and in the case of large-scale deployment, often thousands of computing nodes provide services of virtual machines and virtual storage in one data center, so that under the condition of modifying the default special configuration, such as a vxlan port, rolling upgrade is required to be realized, and the occurrence of jitter of the flow on the control plane is prevented.
The current neutron-ovs-agent cannot support automatic distribution of agent configuration modifications, synchronization of ovs-agent configuration requires restarting all agents, the process of restarting in a multi-node environment can take a long time, if the IP or port of the tunnel network is changed, the virtual machine can not communicate with the virtual machines of other nodes for a while, which means that the configuration of the node is not possible to be updated by rolling, but the failure to update the configuration by rolling implies another problem, that is, in order to ensure that the tunnel communication between the nodes is normal, it is necessary to restart the node service as many times as possible, which is not practical, for a large data center, thousands of computing nodes may be deployed, and restarting at the same time inevitably causes unnecessary stress on the control nodes, and in extreme cases, may cause users to fail to use the service normally.
The current configuration for updating the neutron agent has the following problems:
firstly, some key configurations cannot support heterogeneous configurations, such as vlxna tunnel port;
updating the key configuration can not support rolling updating, and the network data communication is influenced by a high probability in the updating process;
thirdly, a large number of computing nodes need to be restarted at the same time, and the configuration updating method is complicated;
and fourthly, due to the large operation range, the updating speed is slow, and the influence time on the user is long.
Disclosure of Invention
The technical task of the invention is to provide a method, a system, an electronic device and a storage medium for synchronous configuration, so as to solve the problem of how to realize the synchronization of configuration information of a plurality of computing nodes and avoid restarting all agents.
The technical task of the invention is realized in the following way, and the method for synchronous configuration specifically comprises the following steps:
modifying the configuration file of the neutron agent of the designated node and reloading the agent service;
the neutron agent reloads the configuration file and sends the current configuration to a neutron-server;
the neutron-server receives the configuration content sent by the agent end, takes out the previous cooperation, and stores the new configuration in the database to cover the previous configuration;
the neutron-server compares the contents of the configuration files of the previous and subsequent times to determine whether the contents of the configuration files are consistent or not:
if not, triggering a hook function and triggering an event of configuration change;
the module for registering the callback function receives and processes the event of the configuration change; wherein events of configuration changes that need to be handled separately will be notified to the agent service in the form of RPC.
Preferably, the modifications to the configuration file of the neutron agent of the specified node include modifications to the neutron-server and modifications to the neutron agent;
the neutron-server is modified specifically as follows:
the neutron-server provides an RPC interface for receiving the current configuration file content sent by the client of the neutron agent.
Preferably, the data structure of the interface layer of the RPC interface includes a timestamp when the neutron agent updates the configuration file, a host name of a node where the neutron agent is located, a type of a process of the neutron agent, configuration information uploaded by the neutron agent, and a hash value of the agent configuration information;
meanwhile, the neutron agent sends a globally unique ID for identifying the uniqueness of the neutron agent service, and the ID is uniformly issued through a neutron-server without making more assumptions;
the service layer and the data layer of the RPC interface are specifically as follows:
the neutron-server receives the current configuration information of the agent sent by the agent;
acquiring the current configuration information of the agent according to the ID of the agent, the node where the agent is located and the information of the service type of the agent,
the neutron-server compares the current configuration information of the agent with the configuration information transmitted by the agent, and judges whether the processing conditions are met:
firstly, the time stamp of the transmitted configuration information is larger than the currently stored time stamp;
the transmitted configuration information is different from the currently recorded configuration information;
if the processing condition is met, the neutron-server performs the following operations:
firstly, storing a new configuration item into a database;
secondly, after the storage is successful, the neutron-server side triggers the agent configuration updating call back, and hook functions of all subscription time are called in sequence.
Preferably, the hook function and the subscription are implemented as follows:
defining a global event trigger, wherein the event trigger defines a register method and a publish method; the register method is used for registering events, triggering opportunities and call-back functions when the events occur, the entry parameters of the call-back functions are event objects, and the event objects are used for configuring information;
the registration of the hook function occurs in the initialization process of each service component;
after the database is updated, the neutron-server side calls generation of a publish method trigger event;
the publishing method receives three entries, namely the type of the event, the time of the event and a data structure related to the event; wherein, the data structure related to the event stores the previous configuration file, the updated configuration file and the node information submitted to update;
and the event center object traverses the callback functions meeting the conditions and triggers once.
Preferably, the callback function adopts a 12pop component to subscribe the change of the configuration information and processes the event of the change of the tunnel port of the node; after receiving the fact that the port is changed, the 12pop component acquires the information of the changed agent of the node, wherein the information of the agent of the node comprises an ID and a host name;
if the port monitored by the tunnel changes, the 12pop component acquires the information of all the nodes establishing tunnel links with the node from the database, and calls back the information of the nodes establishing tunnel links to the agent end.
Preferably, the neutron agent is specifically as follows:
the neutron agent detects that the configuration file changes, and the change is sensed in the following two ways:
firstly, reloading agent service after the administrator updates the configuration file;
secondly, the agent monitors events on the file by an interface provided by an operating system;
after sensing that the configuration file changes, the agent collects the current configuration, calculates the hash value, constructs a data structure of the interface layer, sends the data structure to the neutron-server, and informs aerver to process the data structure.
Preferably, the agent side will receive the call back from the neutron-server side, which is as follows:
in the agent end, receiving instruction information from a neutron-server end for a related service plug-in expansion interface;
when a tunnel port in the agent end is changed, the agent end is added with an interface and participates in a changed agent structure, and the agent structure at least comprises a node domain name, an agent globally unique identifier, a node address and agent structure information of the tunnel port;
after the Agent acquires the Agent structure information, the Agent modifies the definition of the related vxlan tunnel, and the process realizes automation and does not need human intervention of an administrator.
A system for synchronous configuration, the system comprising,
the modification module is used for modifying the configuration file of the neutron agent of the specified node and reloading the agent service;
the reloading module is used for reloading the configuration file by the neutron agent and sending the current configuration to the neutron-server;
the overlay module is used for receiving the configuration content sent by the agent end by the neutron-server end, taking out the previous cooperation, storing the new configuration into the database and overlaying the previous configuration;
the judging module is used for judging whether the content of the configuration file of the neutron-server is consistent with the content of the configuration file of the previous configuration file and the content of the configuration file of the next configuration file: if not, triggering a hook function and triggering an event of configuration change;
the processing module is used for receiving and processing the configuration change event by the module for registering the callback function; wherein events of configuration changes that need to be handled separately will be notified to the agent service in the form of RPC.
An electronic device, comprising: a memory and at least one processor;
wherein the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the method of synchronizing the configurations as described above.
A computer-readable storage medium having stored thereon computer-executable instructions, which when executed by a processor implement a method of synchronizing a configuration as described above.
The method, the system, the electronic equipment and the storage medium for synchronous configuration have the following advantages that:
the invention promotes the flexibility of configuration, realizes the synchronization of configuration contents among the agent nodes, conveniently realizes the difference configuration of the nodes, and ensures that the heat change of the cluster configuration does not influence the availability of the whole cluster any more;
the method comprises the following steps that (II) configuration information is synchronized in a mode that a neutron-server automatically distributes agent configuration, and the neutron-server sends updated data to a node subscribed with the data after sensing the change of user data, so that all agents are prevented from being restarted;
thirdly, the invention provides a simple and practical available scheme to support the update and propagation of the configuration of the neutron agent and simultaneously realize the rolling upgrade of the neutron agent;
by realizing the function of dynamically updating and configuring ovs-agent, the invention updates key characteristics without restarting ovs-agent of all nodes, thereby reducing the influence range of restarting; the updating configuration can be independently executed on each node at will, so that the speed of configuration synchronization is improved, and the time of link interruption is shortened; the gray level release of the configuration is supported, the configuration is allowed to be different at each node, and the verification of the configuration items is facilitated; the rolling update of the configuration file is supported, and meanwhile, the quick rollback is facilitated when problems occur; the event is subscribed in a registration mode, the interface is flexible, and the expansion is convenient according to the actual condition of the service.
Drawings
The invention is further described below with reference to the accompanying drawings.
FIG. 1 is a logical block diagram of a method of synchronous configuration;
FIG. 2 is a block diagram of a process for agent updating a configuration file;
FIG. 3 is a block diagram of a server process flow.
Detailed Description
The method, system, electronic device, and storage medium for synchronization configuration of the present invention are described in detail below with reference to the accompanying drawings and specific embodiments.
Example 1:
as shown in fig. 1, 2 and 3, the method of the present invention for synchronous configuration specifically comprises the following steps:
s1, modifying the configuration file of the neutron agent of the designated node and reloading the agent service;
s2, reloading the configuration file by the neutron agent, and sending the current configuration to a neutron-server;
s3, the neutron-server receives the configuration content sent by the agent end, takes out the previous cooperation, and stores the new configuration in the database to cover the previous configuration;
s4, the neutron-server compares the contents of the configuration files of the previous and next two times to see whether the contents are consistent:
if not, triggering a hook function and triggering an event of configuration change;
s5, the module of registering the callback function receives the event of the configuration change and processes the event; wherein events of configuration changes that need to be handled separately will be notified to the agent service in the form of RPC.
The modification of the configuration file of the neutron agent of the designated node in step S1 of this embodiment includes modification of neutron-server and modification of neutron agent;
the neutron-server is modified specifically as follows:
the neutron-server provides an RPC interface for receiving the current configuration file content sent by the client of the neutron agent.
The data structure of the interface layer of the RPC interface in this embodiment includes a timestamp when the neutron agent updates the configuration file, a host name of a node where the neutron agent is located, a type of a process of the neutron agent, configuration information uploaded by the neutron agent, and a hash value of the agent configuration information;
meanwhile, the neutron agent sends a globally unique ID for identifying the uniqueness of the neutron agent service, and the ID is uniformly issued through a neutron-server without making more assumptions;
the service layer and the data layer of the RPC interface are specifically as follows:
(1) the neutron-server receives the current configuration information of the agent sent by the agent;
(2) the current configuration information of the agent is obtained through the ID of the agent, the node where the agent is located, and the information of the service type of the agent, and it is noted that the current configuration information of the agent is not necessarily obtained here, because the node may be registered for the first time. If it is the first registration, the old configuration information may be considered as None for simplicity, and the hook function needs to correctly process the None in the future processing callback, so that it will not be clearly distinguished in the following.
(3) And comparing the current configuration information of the agent with the configuration information transmitted by the agent by the neutron-server, and judging whether the processing conditions are met:
firstly, the time stamp of the transmitted configuration information is larger than the currently stored time stamp;
the transmitted configuration information is different from the currently recorded configuration information;
the way of comparing the incoming configuration information with the currently recorded configuration information is not limited here, and generally, we can traverse the dictionaries of the two configuration information in a recursive manner. In addition, since the client terminal transmits the hash value, in order to speed up comparison, whether the hash values of the current configuration item and the transmitted configuration item are the same or not can be directly compared. Of course, only possible implementations are exemplified here, and how to implement them can be performed according to a specific service scenario.
(4) If the processing condition is met, the neutron-server performs the following operations:
firstly, storing a new configuration item into a database;
secondly, after the storage is successful, the neutron-server side triggers the agent configuration updating call back, and hook functions of all subscription time are called in sequence.
The hook function and subscription in step S4 of this embodiment are specifically implemented as follows:
s401, defining a global event trigger, wherein the event trigger defines a register method and a publish method; the register method is used for registering events, triggering opportunities and call-back functions when the events occur, the entry parameters of the call-back functions are event objects, and the event objects are used for configuring information;
s402, registering the hook function in the initialization process of each service component; this requires the global event registry to initialize before the hook function registers.
S403, after the database is updated, the neutron-server side calls generation of a publish method trigger event; wherein, the publish method receives three entries, which are the type of the event, the time of the event and the data structure related to the event; wherein, the data structure related to the event stores the previous configuration file, the updated configuration file and the node information submitted to update;
s404, the event center object traverses the callback functions meeting the conditions and triggers once.
In this embodiment, the callback function in step S404 uses a 12pop component to subscribe to the change of the configuration information, and processes the event of the change of the tunnel port of the node; after receiving the fact that the port is changed, the 12pop component acquires the information of the changed agent of the node, wherein the information of the agent of the node comprises an ID and a host name;
if the port monitored by the tunnel changes, the 12pop component acquires the information of all the nodes establishing tunnel links with the node from the database, and calls back the information of the nodes establishing tunnel links to the agent end.
The neutron agent in this embodiment is specifically as follows:
the neutron agent detects that the configuration file changes, and the change is sensed in the following two ways:
firstly, reloading agent service after the administrator updates the configuration file;
secondly, the agent monitors events on the file by an interface provided by an operating system;
after sensing that the configuration file changes, the agent collects the current configuration, calculates the hash value, constructs a data structure of the interface layer, sends the data structure to the neutron-server, and informs aerver to process the data structure.
The agent end in this embodiment will receive a callback from the neutron-server, which is specifically as follows:
in the agent end, receiving instruction information from a neutron-server end for a related service plug-in expansion interface;
when a tunnel port in the agent end is changed, the agent end is added with an interface and participates in a changed agent structure, and the agent structure at least comprises a node domain name, an agent globally unique identifier, a node address and agent structure information of the tunnel port;
after the Agent acquires the Agent structure information, the Agent modifies the definition of the related vxlan tunnel, and the process realizes automation and does not need human intervention of an administrator.
Example 2:
the system of synchronous configuration in this embodiment, the system comprising,
the modification module is used for modifying the configuration file of the neutron agent of the specified node and reloading the agent service;
the reloading module is used for reloading the configuration file by the neutron agent and sending the current configuration to the neutron-server;
the overlay module is used for receiving the configuration content sent by the agent end by the neutron-server end, taking out the previous cooperation, storing the new configuration into the database and overlaying the previous configuration;
the judging module is used for judging whether the content of the configuration file of the neutron-server is consistent with the content of the configuration file of the previous configuration file and the content of the configuration file of the next configuration file: if not, triggering a hook function and triggering an event of configuration change;
the processing module is used for receiving and processing the configuration change event by the module for registering the callback function; wherein events of configuration changes that need to be handled separately will be notified to the agent service in the form of RPC.
Example 3:
an embodiment of the present invention further provides an electronic device, including: a memory and a processor;
wherein the memory stores computer-executable instructions;
the one processor executes the computer-executable instructions stored in the memory, so that the one processor executes the method for synchronous configuration according to any one of the invention.
Example 4:
embodiments of the present invention further provide a computer-readable storage medium, in which a plurality of instructions are stored, where the instructions are loaded by a processor, and cause the processor to execute the method for synchronous configuration in any of the embodiments of the present invention. Specifically, a system or an apparatus equipped with a storage medium on which software program codes that realize the functions of any of the above-described embodiments are stored may be provided, and a computer (or a CPU or MPU) of the system or the apparatus is caused to read out and execute the program codes stored in the storage medium.
In this case, the program code itself read from the storage medium can realize the functions of any of the above-described embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.
Examples of the storage medium for supplying the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (e.g., CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD + RW), a magnetic tape, a nonvolatile memory card, and a ROM. Alternatively, the program code may be downloaded from a server computer via a communications network.
Further, it should be clear that the functions of any one of the above-described embodiments may be implemented not only by executing the program code read out by the computer, but also by causing an operating system or the like operating on the computer to perform a part or all of the actual operations based on instructions of the program code.
Further, it is to be understood that the program code read out from the storage medium is written to a memory provided in an expansion board inserted into the computer or to a memory provided in an expansion unit connected to the computer, and then causes a CPU or the like mounted on the expansion board or the expansion unit to perform part or all of the actual operations based on instructions of the program code, thereby realizing the functions of any of the above-described embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A method for synchronous configuration is characterized in that the method specifically comprises the following steps:
modifying the configuration file of the neutron agent of the designated node and reloading the agent service;
the neutron agent reloads the configuration file and sends the current configuration to a neutron-server;
the neutron-server receives the configuration content sent by the agent end, takes out the previous cooperation, and stores the new configuration in the database to cover the previous configuration;
the neutron-server compares the contents of the configuration files of the previous and subsequent times to determine whether the contents of the configuration files are consistent or not:
if not, triggering a hook function and triggering an event of configuration change;
the module for registering the callback function receives and processes the event of the configuration change; wherein events of configuration changes that need to be handled separately will be notified to the agent service in the form of RPC.
2. The method of synchronous configuration of claim 1, wherein the modifications to the configuration file of the neutron agent of the specified node include modifications to neutron-server and modifications to neutron agent;
the neutron-server is modified specifically as follows:
the neutron-server provides an RPC interface for receiving the current configuration file content sent by the client of the neutron agent.
3. The method for synchronous configuration according to claim 2, wherein the data structure of the interface layer of the RPC interface includes a timestamp when the neutron agent updates the configuration file, a host name of a node where the neutron agent is located, a type of a process of the neutron agent, configuration information uploaded by the neutron agent, and a hash value of the agent configuration information;
meanwhile, the neutron agent sends a globally unique ID for identifying the uniqueness of the neutron agent service, and the ID is uniformly issued through a neutron-server;
the service layer and the data layer of the RPC interface are specifically as follows:
the neutron-server receives the current configuration information of the agent sent by the agent;
acquiring the current configuration information of the agent according to the ID of the agent, the node where the agent is located and the information of the service type of the agent,
the neutron-server compares the current configuration information of the agent with the configuration information transmitted by the agent, and judges whether the processing conditions are met:
firstly, the time stamp of the transmitted configuration information is larger than the currently stored time stamp;
the transmitted configuration information is different from the currently recorded configuration information;
if the processing condition is met, the neutron-server performs the following operations:
firstly, storing a new configuration item into a database;
secondly, after the storage is successful, the neutron-server side triggers the agent configuration updating call back, and hook functions of all subscription time are called in sequence.
4. The method of claim 1, wherein hook functions and subscriptions are implemented as follows:
defining a global event trigger, wherein the event trigger defines a register method and a publish method; the register method is used for registering events, triggering opportunities and call-back functions when the events occur, the entry parameters of the call-back functions are event objects, and the event objects are used for configuring information;
the registration of the hook function occurs in the initialization process of each service component;
after the database is updated, the neutron-server side calls generation of a publish method trigger event;
the publishing method receives three entries, namely the type of the event, the time of the event and a data structure related to the event; wherein, the data structure related to the event stores the previous configuration file, the updated configuration file and the node information submitted to update;
and the event center object traverses the callback functions meeting the conditions and triggers once.
5. The method for synchronous configuration according to claim 1, wherein the callback function employs a 12pop component to subscribe to changes of configuration information and to process events of tunnel port changes of the node; after receiving the fact that the port is changed, the 12pop component acquires the information of the changed agent of the node, wherein the information of the agent of the node comprises an ID and a host name;
if the port monitored by the tunnel changes, the 12pop component acquires the information of all the nodes establishing tunnel links with the node from the database, and calls back the information of the nodes establishing tunnel links to the agent end.
6. The method for synchronous configuration according to claim 1, wherein the neutron agent is specified as follows:
the neutron agent detects that the configuration file changes, and the change is sensed in the following two ways:
firstly, reloading agent service after the administrator updates the configuration file;
secondly, the agent monitors events on the file by an interface provided by an operating system;
after sensing that the configuration file changes, the agent collects the current configuration, calculates the hash value, constructs a data structure of the interface layer, sends the data structure to the neutron-server, and informs aerver to process the data structure.
7. The method for synchronous configuration according to claim 5, wherein the agent end receives the call back from the neutron-server end, specifically as follows:
in the agent end, receiving instruction information from a neutron-server end for a related service plug-in expansion interface;
when a tunnel port in the agent end is changed, the agent end is added with an interface and participates in a changed agent structure, and the agent structure at least comprises a node domain name, an agent globally unique identifier, a node address and agent structure information of the tunnel port;
the Agent will modify the definition of the relevant vxlan tunnel after it has acquired Agent structure information.
8. A system for synchronous deployment, the system comprising,
the modification module is used for modifying the configuration file of the neutron agent of the specified node and reloading the agent service;
the reloading module is used for reloading the configuration file by the neutron agent and sending the current configuration to the neutron-server;
the overlay module is used for receiving the configuration content sent by the agent end by the neutron-server end, taking out the previous cooperation, storing the new configuration into the database and overlaying the previous configuration;
the judging module is used for judging whether the content of the configuration file of the neutron-server is consistent with the content of the configuration file of the previous configuration file and the content of the configuration file of the next configuration file: if not, triggering a hook function and triggering an event of configuration change;
the processing module is used for receiving and processing the configuration change event by the module for registering the callback function; wherein events of configuration changes that need to be handled separately will be notified to the agent service in the form of RPC.
9. An electronic device, comprising: a memory and at least one processor;
wherein the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the method of synchronizing a configuration as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium having computer-executable instructions stored thereon which, when executed by a processor, implement the method of synchronization configuration of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111097262.0A CN113900728A (en) | 2021-09-18 | 2021-09-18 | Method, system, electronic device and storage medium for synchronous configuration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111097262.0A CN113900728A (en) | 2021-09-18 | 2021-09-18 | Method, system, electronic device and storage medium for synchronous configuration |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113900728A true CN113900728A (en) | 2022-01-07 |
Family
ID=79028716
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111097262.0A Pending CN113900728A (en) | 2021-09-18 | 2021-09-18 | Method, system, electronic device and storage medium for synchronous configuration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113900728A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116756737A (en) * | 2023-08-24 | 2023-09-15 | 深圳红途科技有限公司 | Interface abnormal behavior analysis method and device, computer equipment and storage medium |
-
2021
- 2021-09-18 CN CN202111097262.0A patent/CN113900728A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116756737A (en) * | 2023-08-24 | 2023-09-15 | 深圳红途科技有限公司 | Interface abnormal behavior analysis method and device, computer equipment and storage medium |
| CN116756737B (en) * | 2023-08-24 | 2024-03-26 | 深圳红途科技有限公司 | Interface abnormal behavior analysis method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109639572B (en) | Route management method and device and micro-service system | |
| US10140112B2 (en) | Update management system and update management method | |
| US6332198B1 (en) | Network device for supporting multiple redundancy schemes | |
| US7225240B1 (en) | Decoupling processes from hardware with logical identifiers | |
| CN105743692B (en) | Policy-based framework for application management | |
| US6694450B1 (en) | Distributed process redundancy | |
| US7062642B1 (en) | Policy based provisioning of network device resources | |
| US6601186B1 (en) | Independent restoration of control plane and data plane functions | |
| US6708291B1 (en) | Hierarchical fault descriptors in computer systems | |
| US6983362B1 (en) | Configurable fault recovery policy for a computer system | |
| US8375001B2 (en) | Master monitoring mechanism for a geographical distributed database | |
| US8719386B2 (en) | System and method for providing configuration synchronicity | |
| US7051097B1 (en) | Embedded database for computer system management | |
| CN107590072B (en) | Application development and test method and device | |
| US6715097B1 (en) | Hierarchical fault management in computer systems | |
| US11432137B2 (en) | Service notification method for mobile edge host and apparatus | |
| CN112035216B (en) | Communication method for Kubernetes cluster network and OpenStack network | |
| CN111404628B (en) | Time synchronization method and device | |
| CN113067850A (en) | Cluster arrangement system under multi-cloud scene | |
| US20220326940A1 (en) | Service Upgrade Method, Apparatus, and System | |
| CN112042170A (en) | On-node DHCP implementation for virtual machines | |
| CN116566984B (en) | Routing information creation method and device of k8s container cluster and electronic equipment | |
| CN114448895B (en) | Application access method, device, equipment and medium | |
| CN112882738A (en) | Configuration information updating method and device under micro-service architecture and electronic equipment | |
| CN106850724B (en) | Data pushing method and device |
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 |