CN113810513B - Configuration management method and system for elastic public network IP - Google Patents
Configuration management method and system for elastic public network IP Download PDFInfo
- Publication number
- CN113810513B CN113810513B CN202110936151.8A CN202110936151A CN113810513B CN 113810513 B CN113810513 B CN 113810513B CN 202110936151 A CN202110936151 A CN 202110936151A CN 113810513 B CN113810513 B CN 113810513B
- Authority
- CN
- China
- Prior art keywords
- public network
- elastic public
- configuration
- instance
- agent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 34
- 230000008859 change Effects 0.000 claims abstract description 37
- 238000012795 verification Methods 0.000 claims abstract description 14
- 238000000034 method Methods 0.000 claims description 41
- 238000012544 monitoring process Methods 0.000 claims description 20
- 230000004044 response Effects 0.000 claims description 8
- 230000008569 process Effects 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 5
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000012546 transfer Methods 0.000 claims description 2
- 230000005540 biological transmission Effects 0.000 claims 1
- 238000005096 rolling process Methods 0.000 claims 1
- 239000003795 chemical substances by application Substances 0.000 description 96
- 238000010586 diagram Methods 0.000 description 10
- 238000013461 design Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/255—Maintenance or indexing of mapping tables
- H04L61/2553—Binding renewal aspects, e.g. using keep-alive messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a configuration management method and system of an elastic public network IP, comprising the following steps: dividing the equipment deployed with the daemon Agent for executing configuration loading into a plurality of equipment groups, and distributing the elastic public network IP to each equipment group; agents in each equipment group monitor configuration changes of each elastic public network IP in the group; when the change exists, checking main configuration information of the elastic public network IP through an MD5 value of the elastic public network IP; when the verification of the main configuration information of the elastic public network IP is successful, a new configuration file for binding the elastic public network IP to the instance used by the user is generated according to the binding relation between the elastic public network IP and the instance used by the user; all agents of the equipment group where the agents are located execute configuration files for loading all the elastic public network IP of the equipment group, and the elastic public network IP is bound to an instance used by a corresponding user. All the nodes are not subjected to configuration change, so that the node generation efficiency related to each configuration change can be ensured.
Description
Technical Field
The invention relates to the field of elastic public networks, in particular to a configuration management method and system of an elastic public network IP.
Background
When the elastic public network IP service provided by the cloud service manufacturer is configured, a configuration management system based on ETCD (open source distributed key value pair database) is adopted; the configuration management system often stores configuration information in a database in a structured way, exports and synchronizes configuration data in the database to an ETCD cluster when configuration is issued, and a daemon deployed on a server acquires new configuration data through a Watch function of the ETCD so as to achieve the purpose of configuration issuing. In carrying out the present invention, the applicant has found that at least the following problems exist in the prior art: if the nodes involved in each configuration change are not guaranteed to be all effective, when part of nodes succeed, if engineers do not process in time, the service is affected.
Disclosure of Invention
The embodiment of the invention provides a configuration management method and a configuration management system for an elastic public network IP, which do not carry out configuration change on all nodes and can ensure the node generation efficiency related to each configuration change.
In order to achieve the above objective, in one aspect, an embodiment of the present invention provides a method for configuration management of an elastic public network IP, including:
dividing the equipment deployed with the daemon process Agent for executing configuration loading into a plurality of equipment groups, distributing the elastic public network IP to each equipment group, and managing the corresponding elastic public network IP configuration in each equipment group by each equipment group;
The Agent in each equipment group monitors whether the configuration of each elastic public network IP in the equipment group in which the Agent is positioned changes;
when the Agent monitors that the configuration of the elastic public network IP in the equipment group is changed, acquiring the related configuration of the changed elastic public network IP; the relevant configuration of the elastic public network IP includes: the main configuration information of the elastic public network IP and the corresponding MD5 value of the elastic public network IP, wherein the main configuration information of the elastic public network IP comprises: the method comprises the steps that a user requests an ID, an ID of an instance used by the user, an elastic public network IP bound by the instance, and a binding mode of the instance binding elastic public network IP, wherein the binding mode of the instance binding elastic public network IP refers to that the instance binding unique elastic public network IP or the instance binding a plurality of elastic public network IPs; the MD5 value of the elastic public network IP is used for checking the integrity of the main configuration information of the corresponding elastic public network IP;
checking main configuration information of the elastic public network IP through an MD5 value of the elastic public network IP; when the verification of the main configuration information of the elastic public network IP is successful, recording the binding relation between the elastic public network IP and the instance used by the user in a database, and generating a new configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; all agents of the equipment group where the agents are located execute configuration files for loading all the elastic public network IP of the equipment group, and the elastic public network IP is bound to an instance used by a corresponding user.
On the other hand, an embodiment of the present invention provides a configuration management system for an elastic public network IP, including:
the device management unit is used for dividing the device deployed with the daemon Agent for executing configuration loading into a plurality of device groups, distributing the elastic public network IP to each device group, and managing the corresponding elastic public network IP configuration in the device groups by each device group;
the first monitoring unit is used for monitoring whether the configuration of each elastic public network IP in the equipment group where the Agent in each equipment group is located changes or not; when the Agent monitors that the configuration of the elastic public network IP in the equipment group is changed, acquiring the related configuration of the changed elastic public network IP; the relevant configuration of the elastic public network IP includes: the main configuration information of the elastic public network IP and the corresponding MD5 value of the elastic public network IP, wherein the main configuration information of the elastic public network IP comprises: the method comprises the steps that a user requests an ID, an ID of an instance used by the user, an elastic public network IP bound by the instance, and a binding mode of the instance binding elastic public network IP, wherein the binding mode of the instance binding elastic public network IP refers to that the instance binding unique elastic public network IP or the instance binding a plurality of elastic public network IPs; the MD5 value of the elastic public network IP is used for checking the integrity of the main configuration information of the corresponding elastic public network IP;
An example configuration updating unit, configured to verify main configuration information of the elastic public network IP by using an MD5 value of the elastic public network IP; when the verification of the main configuration information of the elastic public network IP is successful, recording the binding relation between the elastic public network IP and the instance used by the user in a database, and generating a new configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; all agents of the equipment group where the agents are located execute configuration files for loading all the elastic public network IP of the equipment group, and the elastic public network IP is bound to an instance used by a corresponding user.
The technical scheme has the following beneficial effects: all the nodes are not subjected to configuration change, so that the node generation efficiency related to each configuration change can be ensured.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a configuration management method of an elastic public network IP according to an embodiment of the present invention;
fig. 2 is a block diagram of a configuration management system of an elastic public network IP according to an embodiment of the present invention;
fig. 3 is a configuration management method architecture diagram of an elastic public network IP according to an embodiment of the present invention;
FIG. 4 is a Jackson diagram of a device group configuration data structure in accordance with an embodiment of the present invention;
FIG. 5 is a Jackson diagram of an EIP related configuration data structure according to an embodiment of the present invention;
FIG. 6 is a flow chart of an Agent performing configuration loading in accordance with an embodiment of the present invention;
FIG. 7 is a Jackson diagram of an Agent request data structure in accordance with an embodiment of the present invention;
FIG. 8 is a Jackson diagram of a task center response data structure in accordance with an embodiment of the present invention;
FIG. 9 is a state machine diagram of task center maintenance of an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
As shown in fig. 1, in combination with an embodiment of the present invention, a configuration management method of an elastic public network IP is provided, including:
s101: dividing the equipment deployed with the daemon process Agent for executing configuration loading into a plurality of equipment groups, distributing the elastic public network IP to each equipment group, and managing the corresponding elastic public network IP configuration in each equipment group by each equipment group;
s102: the Agent in each equipment group monitors whether the configuration of each elastic public network IP in the equipment group in which the Agent is positioned changes;
when the Agent monitors that the configuration of the elastic public network IP in the equipment group is changed, acquiring the related configuration of the changed elastic public network IP; the relevant configuration of the elastic public network IP includes: the main configuration information of the elastic public network IP and the corresponding MD5 value of the elastic public network IP, wherein the main configuration information of the elastic public network IP comprises: the method comprises the steps that a user requests an ID, an ID of an instance used by the user, an elastic public network IP bound by the instance, and a binding mode of the instance binding elastic public network IP, wherein the binding mode of the instance binding elastic public network IP refers to that the instance binding unique elastic public network IP or the instance binding a plurality of elastic public network IPs; the MD5 value of the elastic public network IP is used for checking the integrity of the main configuration information of the corresponding elastic public network IP;
S103: checking main configuration information of the elastic public network IP through an MD5 value of the elastic public network IP; when the verification of the main configuration information of the elastic public network IP is successful, recording the binding relation between the elastic public network IP and the instance used by the user in a database, and generating a new configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; all agents of the equipment group where the agents are located execute configuration files for loading all the elastic public network IP of the equipment group, and the elastic public network IP is bound to an instance used by a corresponding user.
Preferably, the method further comprises:
s104: when a user requests an elastic public network IP for an example used by the user for the first time, the daemon Agent distributes the available elastic public network IP in the equipment group to the user and records the available elastic public network IP distributed to the user to a database; recording the binding relation between the available elastic public network IP and the instance used by the user in a database, and generating a configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; executing a configuration file for loading the available elastic public network IP through the Agent in the equipment group according to the binding relation, and binding the available elastic public network IP to the instance;
Adopting a key value pair to represent a configuration file binding the elastic public network IP for the instance, wherein the key of the key value pair is a path value of an ID of a device group to which the elastic public network IP bound by the instance belongs; the path value comprises equipment in which a key value pair representing a configuration file is located, an ID of an equipment group to which the equipment in which the Agent is located belongs is used as a prefix of the path value, and an elastic public network IP bound by an example is used as a suffix of the path value; the value of the key value pair is the relevant configuration of the elastic public network IP bound by the instance;
in step 102, the Agent in each device group monitors whether the configuration of each elastic public network IP in the device group where the Agent is located changes, and specifically includes:
s1021: the Agent searches the equipment group in which the Agent is located in the database through the main configuration information of the equipment group and the identification of the equipment, and obtains the prefix of the path value of the ID of the equipment group to which the elastic public network IP bound by the example belongs from the key value pair corresponding to the configuration file of the elastic public network IP bound by the example in the searched equipment group;
s1022: the Agent monitors the prefix of the path value of the key of the configuration file of the binding elastic public network IP for the instance in the equipment group, and senses the change of all sub paths of the instance through the change of the prefix of the path value.
Preferably, after executing the loading of the configuration file of all the elastic public network IP of the device group by all the agents of the device group where the agents are located, the method further includes:
s105: all agents in the equipment group report the results of executing and loading the configuration files of all the elastic public network IPs of the equipment group to a task center through a remote procedure call protocol (RPC), and whether the configuration files of all the elastic public network IPs are completely successfully loaded and updated in respective examples is judged by analyzing the response information of the task center to the execution and loading results;
s106: if the configuration file of the part of the elastic public network IP in the equipment group where the Agent is located fails to be loaded and updated in the corresponding instance or is overtime, the configuration file of a version on the part of the instance is pulled from the database to roll back, and the configuration of the part of the elastic public network IP of the instance is rolled back to the configuration before being updated and loaded; and when the loading update fails or the elastic public network IP with the configuration change is included in the timeout, an alarm is sent out, and the configuration file with the elastic public network IP with the change is loaded to the instance used by the corresponding user again to update the configuration of the elastic public network IP with the change.
Preferably, when all the agents of the device group where the agents are located execute loading configuration files of all the elastic public networks IP of the device group, the method further includes:
S107: the method comprises the steps that a task center is responsible for maintaining and recording a state machine of executing the configuration file state of loading all the elastic public network IP of the equipment group by an Agent, the state machine is expressed in a key value pair mode, keys of the key value pair comprise a request ID of a user and the IP of the equipment where the Agent is located, and the value of the key value pair is the loading state of loading and updating the configuration file of the elastic public network IP to a corresponding instance; wherein:
initializing a state machine when each instance used by a user executes loading configuration files, and recording the loading state of the configuration files of the elastic public network IP, which are received for the first time, updated to the corresponding instance as executing;
the method comprises the steps that a returned loading state is received in a state return period agreed by a task center and an Agent, and the number of times of returning the loading state in the return period is set to be not more than the preset highest retry number; updating the loading state in the current state machine to be successful or failed according to the returned loading state;
when the status feedback period appointed by the task center and the Agent is exceeded and the returned loading status is not received, setting the loading status as overtime;
and the task center informs the loading state of the instance loading configuration file to the equipment corresponding to the deployment Agent according to the loading state in the current state machine.
Preferably, further comprising;
s108: the Agent monitors whether the configuration of the equipment group where the Agent is located changes; wherein, the configuration of the device group includes: the device group main configuration information and the MD5 value corresponding to the device group, where the device group main configuration information includes: information of all devices for deploying the Agent, wherein the information of the devices for deploying the Agent comprises the following components: an ID of a device group to which the device belongs, and an IP address of each device in the device group; the MD5 value of the equipment group is used for checking the integrity of the main configuration information of the equipment group;
s109: when the Agent monitors that the configuration of the equipment group is changed, the equipment is removed from the equipment group, or the equipment group is deleted, the Agent automatically ends the operation;
s110: when the Agent monitors that the configuration of the equipment group is changed to a new equipment group, the equipment of the Agent acquires main configuration information of the new equipment group and a corresponding MD5 value of the new equipment group, and the main configuration information of the new equipment group is checked through the MD5 value of the new equipment group;
s111: after the verification of the main configuration information of the new equipment group is successful, the Agent monitors whether the relevant configuration of all the elastic public network IP of the new equipment group is changed; and
s112: after the verification of the main configuration information of the new device group is successful, whether the configuration of the new device group changes or not is monitored.
As shown in fig. 2, in combination with an embodiment of the present invention, there is provided a configuration management system of an elastic public network IP, including:
a device management unit 21, configured to divide a device deployed with daemon Agent for executing configuration loading into a plurality of device groups, and allocate an elastic public network IP to each device group, where each device group manages a corresponding elastic public network IP configuration therein;
a first monitoring unit 22, configured to monitor, by an Agent in each device group, whether the configuration of each elastic public network IP in the device group in which the Agent is located changes; when the Agent monitors that the configuration of the elastic public network IP in the equipment group is changed, acquiring the related configuration of the changed elastic public network IP; the relevant configuration of the elastic public network IP includes: the main configuration information of the elastic public network IP and the corresponding MD5 value of the elastic public network IP, wherein the main configuration information of the elastic public network IP comprises: the method comprises the steps that a user requests an ID, an ID of an instance used by the user, an elastic public network IP bound by the instance, and a binding mode of the instance binding elastic public network IP, wherein the binding mode of the instance binding elastic public network IP refers to that the instance binding unique elastic public network IP or the instance binding a plurality of elastic public network IPs; the MD5 value of the elastic public network IP is used for checking the integrity of the main configuration information of the corresponding elastic public network IP;
An instance configuration updating unit 23, configured to verify the main configuration information of the elastic public network IP by using the MD5 value of the elastic public network IP; when the verification of the main configuration information of the elastic public network IP is successful, recording the binding relation between the elastic public network IP and the instance used by the user in a database, and generating a new configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; all agents of the equipment group where the agents are located execute configuration files for loading all the elastic public network IP of the equipment group, and the elastic public network IP is bound to an instance used by a corresponding user.
Preferably, the method further comprises:
the allocation unit 24 is configured to, when a user first requests application of an elastic public network IP for an instance used by the user, allocate the available elastic public network IP in the device group to the user by using the daemon Agent, and record the available elastic public network IP allocated to the user in the database; the binding relation between the available elastic public network IP and the instance used by the user is recorded in a database;
a first configuration unit 25, configured to generate a configuration file for binding the elastic public network IP to an instance used by the user according to the binding relationship; executing a configuration file for loading the available elastic public network IP through the Agent in the equipment group according to the binding relation, and binding the available elastic public network IP to the instance; the configuration file binding the elastic public network IP for the instance is represented by a key value, and the key of the key value pair is the path value of the ID of the equipment group to which the elastic public network IP bound by the instance belongs; the path value comprises equipment in which a key value pair representing a configuration file is located, an ID of an equipment group to which the equipment in which the Agent is located belongs is used as a prefix of the path value, and an elastic public network IP bound by an example is used as a suffix of the path value; the value of the key value pair is the relevant configuration of the elastic public network IP bound by the instance;
The first monitoring unit 21 includes:
the monitoring information determining subunit 211 is configured to find the device group where the Agent locates in the database through the main configuration information of the device group and the identifier of the device, and obtain, in the found device group, the prefix of the path value of the ID of the device group to which the elastic public network IP bound by the instance belongs from the key value pair corresponding to the configuration file of the elastic public network IP bound by the instance;
the monitor path subunit 212 is configured to monitor, by an Agent, a prefix of a path value of a key of a configuration file of the instance binding elastic public network IP in a device group where the Agent is located, and sense a change of all sub paths of the instance through a change of the prefix of the path value.
Preferably, the instance updating unit 23 includes a result delivering subunit 231 and a result parsing subunit 232, and the configuration management system of the elastic public network IP further includes a processing unit 25, where:
the result transferring subunit 231 is configured to report, after executing the loading of the configuration files of all the elastic public network IPs of the device group by all the agents of the device group where the agents are located, a result of executing the loading of the configuration files of all the elastic public network IPs of the device group to a task center through a remote procedure call protocol RPC;
The result analysis subunit 232 is configured to determine whether all the configuration files of the elastic public network IP are completely successfully loaded and updated in the respective instances by analyzing response information of the task center to the execution loading result;
a handling unit 25, configured to pull, from the database, a configuration file of a version on the part of the instance to roll back, and roll back the configuration of the elastic public network IP of the part of the instance to the configuration before update loading, if the update fails or the time-out of the configuration file of the part of the elastic public network IP in the device group where the Agent is located is performed in the corresponding instance; and when the loading update fails or the elastic public network IP with the configuration change is included in the timeout, an alarm is sent out, and the configuration file with the elastic public network IP with the change is loaded to the instance used by the corresponding user again to update the configuration of the elastic public network IP with the change.
Preferably, the method further comprises:
the task center is used for maintaining and recording a state machine of the state of the Agent for loading the configuration files of the elastic public network IP of the equipment group by the execution of all the agents of the equipment group, and representing the state machine in a key value pair form, wherein keys of the key value pair comprise a request ID of a user and the IP of the equipment of the Agent, and the value of the key value pair is the loading state of loading and updating the configuration files of the elastic public network IP to corresponding examples; wherein:
Initializing a state machine when each instance used by a user executes loading configuration files, and recording the loading state of the configuration files of the elastic public network IP, which are received for the first time, updated to the corresponding instance as executing;
the method comprises the steps that a returned loading state is received in a state return period agreed by a task center and an Agent, and the number of times of returning the loading state in the return period is set to be not more than the preset highest retry number; updating the loading state in the current state machine to be successful or failed according to the returned loading state;
when the status feedback period appointed by the task center and the Agent is exceeded and the returned loading status is not received, setting the loading status as overtime;
and the task center informs the loading state of the instance loading configuration file to the equipment corresponding to the deployment Agent according to the loading state in the current state machine.
Preferably, the method further comprises:
a second monitoring unit 26, configured to monitor whether the configuration of the device group in which the Agent is located changes; wherein, the configuration of the device group includes: the device group main configuration information and the MD5 value corresponding to the device group, where the device group main configuration information includes: information of all devices for deploying the Agent, wherein the information of the devices for deploying the Agent comprises the following components: an ID of a device group to which the device belongs, and an IP address of each device in the device group; the MD5 value of the equipment group is used for checking the integrity of the main configuration information of the equipment group;
A termination unit 27, configured to automatically terminate the operation when the Agent monitors that the configuration of the device group where the Agent is located changes to a state where the device is removed from the device group where the Agent is located, or the device group where the Agent is located is deleted;
the device group updating unit 28 is configured to, when the Agent monitors that the configuration of the device group where the Agent is located changes to a new device group when the device where the Agent is located changes to the new device group, obtain main configuration information of the new device group and an MD5 value corresponding to the new device group, and verify the main configuration information of the new device group through the MD5 value of the new device group;
the first monitoring unit 22 is further configured to monitor, by an Agent, whether relevant configurations of all the elastic public networks IP of the new device group change after verification of the main configuration information of the new device group is successful;
the second monitoring unit 26 is further configured to monitor whether the configuration of the new device group changes after the verification of the master configuration information of the new device group is successful.
The beneficial effects obtained by the embodiment of the invention are as follows:
1. all the nodes are not subjected to configuration change, so that all the nodes involved in each configuration change can be ensured to be effective, the production efficiency is improved, and the influence on the service caused by untimely processing of engineers when part of the nodes are successful is avoided;
2. Management of daemons (agents) on the server may be achieved.
3. Can respond to the user request in real time, and safely and quickly send out new configuration data
4. And the configuration data is issued in each increment, all configurations do not need to be reloaded in a full quantity each time, and the risk of configuration change is reduced.
The foregoing technical solutions of the embodiments of the present invention will be described in detail with reference to specific application examples, and reference may be made to the foregoing related description for details of the implementation process that are not described.
Technical terms or abbreviations related to the present invention are as follows:
the EIP is an elastic public network IP which is arranged on a cloud platform and is different from the common public network IP in that the elastic public network IP is invisible in local.
ECS cloud server
SLB load balancing
Agent daemon deployed on a server to perform configuration loading
The device comprises: server node with Agent deployed
The equipment group: abstracted device set for managing server with Agent
ETCD: open source distributed key value pair database
Redis, key value of open source, database
RPC, remote procedure call protocol
The invention relates to a configuration management method of an elastic public network IP, which is also an elastic public network IP service for balancing network load. Through the design of the data structure configured in the ETCD, the processing logic of the Agent, and the design matters of the state machine, fig. 3 shows the architecture implementation principle of the configuration management method of the elastic public network IP of the present invention.
The method of the invention firstly divides each equipment node deployed with Agent (daemon deployed on a server to execute configuration loading) into a plurality of equipment groups for management, and then distributes limited public network IP resources to each equipment group, thereby facilitating the application and use of the resources by users. The constituent configuration of all device groups is stored in a database and synchronized to an ETCD (open source distributed key value pair database) cluster.
Fig. 4 is a Jackson diagram of a device group configuration data structure in ETCD, which describes the configuration of a cluster to which the elastic public network IP belongs (i.e. the device group to which the elastic public network IP belongs). The device group configuration includes: a primary configuration information encoded as json format string, and an MD5 value for checking the integrity of the configuration. The main configuration information of the device group comprises information of all devices for deploying the agents, and each device information comprises an elastic public network IP address managed by the device and an id of the device group to which the device belongs.
After the user applies for the elastic public network IP, the user can bind with an ECS (cloud server) instance (an instance is a device with a physical structure), an SLB (load balancing) instance, or a NAT gateway, etc. to form configuration information, and the system can synchronize the configuration information to the ETCD database. The configuration of the instance in ETCD is stored in the form of key-value pairs, where the id of the device group to which the instance-bound elastic public network IP belongs is taken as the path value of the key (the path structure of the id of the device group to which the instance-bound elastic public network IP belongs is taken as the key), and the key is terminated with the elastic public network IP address to which the instance is bound. This is a feature of ETCD, where the key is the structure of the path (referring to a structure similar to the file path in the linux operating system), which has the advantage that all changes in its child paths can be perceived by monitoring the prefix of this path, i.e. the parent path. The format of a specific key is as follows: nat/group-a7bGt5 ekutclguyhdxpddvz/172.16.10.1, where nat is the gateway, group-a7bGt5 ekutclguyhdxpddvz is the device group id,172.16.10.1 is the elastic public network IP. The values in the key value pair store configuration information related to EIP (elastic public network IP), and as shown in fig. 5, a Jackson diagram of the configuration information data structure of the elastic public network IP is introduced. Also, binding is the phenomenon that a user sees at the level of this instance (e.g., ECS, SLB, NAT) is binding (i.e., business logic writes this layer of relationships to a relationship-type database), but to actually implement "binding" requires that this configuration representing the binding relationship be pushed by business logic to the etc. then an Agent on the physical machine takes this configuration and takes effect by monitoring the etc.
The elastic public network IP configuration can be seen from fig. 5 to include: a primary configuration information encoded as json format string, and an MD5 value for checking the integrity of the configuration. The main configuration information of the elastic public network IP comprises a request id of a user, all EIPs bound by an instance (a plurality of EIPs can be bound by some instances), an id of the instance and a binding mode of the EIPs (used for distinguishing whether the instance can only bind one EIP or a plurality of EIPs).
The Agent daemon deployed on the device, after obtaining the configuration data, performs a configuration loading action, and the specific execution flow is shown in fig. 6. The Agent will monitor the configuration changes of the device group simultaneously and the changes of the relevant configuration of all EIPs on the device group where it is located. The program will end up running when its device is removed from the device group or the device group is deleted, and the Agent will re-monitor all EIP related configuration changes on the new device group when its device is moved to another device group.
When the Agent monitors EIP related configuration change, firstly, the acquired configuration information is checked through an MD5 value, then a configuration file used by bottom software is generated according to a template and configuration loading is executed, after loading is completed, the Agent reports a loading result to a task center through an RPC remote procedure call protocol, whether all equipment nodes are successfully loaded in the configuration change at this time or not is judged through analyzing task center response information, if the equipment nodes which fail or are overtime exist, the configuration data of the last version is pulled to the ETCD for rollback, and the configuration is rolled back before loading. Jackson diagrams of data communication between agents and task centers are shown in fig. 7 and 8. And the minimum unit of each updating configuration is a device group, and each node in the device group basically ensures the consistency of configuration.
The task center is responsible for maintaining the state machine. The state machine is cached in the Redis cluster, and the key consists of a user request id and a device management ip, such as: cxYH7-Udju7Ui9w8HRCHYUjKTHYn:10.210.10.10, the value is the device load state. The state machine is shown in fig. 9.
The system initializes a state machine for each user request, and when the task center receives the state feedback of the user request for the first time, the corresponding state machine is maintained. The initial state of the device in the state machine is "executing", the task center agrees with the Agent for a state feedback period and a highest retry number, the task center updates the state to be successful or failed when receiving the state feedback in the period, if the state feedback is not acquired in the period exceeding the agreed period, the task center sets the state to be overtime (the state may be set to be overtime even if the device is loaded successfully), the task center informs the device node of the executing state requested by the user according to the current state machine, and the response of the task center is shown in table 1.
TABLE 1 task center status response table
After all the nodes are loaded successfully, the task center waits for a return period again, so that the information is uniformly distributed to all the nodes after the status return of all the nodes is received, and the information is distributed to all the nodes, because the information is communicated with the task center only by the Agent nodes involved in each configuration change.
The beneficial effects obtained by the invention are as follows:
1. all nodes are not subjected to configuration change, so that all the nodes involved in each configuration change can be ensured to be effective, and the influence on service caused by untimely processing of engineers when part of nodes are successful is avoided;
2. management of daemons (agents) on the server may be achieved.
3. Can respond to the user request in real time, and safely and quickly send out new configuration data
4. And the configuration data is issued in each increment, all configurations do not need to be reloaded in a full quantity each time, and the risk of configuration change is reduced.
It should be understood that the specific order or hierarchy of steps in the processes disclosed are examples of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate preferred embodiment of this invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. As will be apparent to those skilled in the art; various modifications to these embodiments will be readily apparent, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing description includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, as used in the specification or claims, the term "comprising" is intended to be inclusive in a manner similar to the term "comprising," as interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean "non-exclusive or".
Those of skill in the art will further appreciate that the various illustrative logical blocks (illustrative logical block), units, and steps described in connection with the embodiments of the invention may be implemented by electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components (illustrative components), elements, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present invention.
The various illustrative logical blocks or units described in the embodiments of the invention may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described. A general purpose processor may be a microprocessor, but in the alternative, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In an example, a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may reside in a user terminal. In the alternative, the processor and the storage medium may reside as distinct components in a user terminal.
In one or more exemplary designs, the above-described functions of embodiments of the present invention may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on a computer-readable medium or transmitted as one or more instructions or code on the computer-readable medium. Computer readable media includes both computer storage media and communication media that facilitate transfer of computer programs from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store program code in the form of instructions or data structures and other data structures that may be read by a general or special purpose computer, or a general or special purpose processor. Further, any connection is properly termed a computer-readable medium, e.g., if the software is transmitted from a website, server, or other remote source via a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless such as infrared, radio, and microwave, and is also included in the definition of computer-readable medium. The disks (disks) and disks (disks) include compact disks, laser disks, optical disks, DVDs, floppy disks, and blu-ray discs where disks usually reproduce data magnetically, while disks usually reproduce data optically with lasers. Combinations of the above may also be included within the computer-readable media.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (10)
1. The configuration management method of the elastic public network IP is characterized by comprising the following steps:
dividing the equipment deployed with the daemon process Agent for executing configuration loading into a plurality of equipment groups, distributing the elastic public network IP to each equipment group, and managing the corresponding elastic public network IP configuration in each equipment group by each equipment group;
the Agent in each equipment group monitors whether the configuration of each elastic public network IP in the equipment group in which the Agent is positioned changes;
when the Agent monitors that the configuration of the elastic public network IP in the equipment group is changed, acquiring the related configuration of the changed elastic public network IP; the relevant configuration of the elastic public network IP includes: the main configuration information of the elastic public network IP and the corresponding MD5 value of the elastic public network IP, wherein the main configuration information of the elastic public network IP comprises: the method comprises the steps that a user requests an ID, an ID of an instance used by the user, an elastic public network IP bound by the instance, and a binding mode of the instance binding elastic public network IP, wherein the binding mode of the instance binding elastic public network IP refers to that the instance binding unique elastic public network IP or the instance binding a plurality of elastic public network IPs; the MD5 value of the elastic public network IP is used for checking the integrity of the main configuration information of the corresponding elastic public network IP;
Checking main configuration information of the elastic public network IP through an MD5 value of the elastic public network IP; when the verification of the main configuration information of the elastic public network IP is successful, recording the binding relation between the elastic public network IP and the instance used by the user in a database, and generating a new configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; all agents of the equipment group where the agents are located execute configuration files for loading all the elastic public network IP of the equipment group, and the elastic public network IP is bound to an instance used by a corresponding user.
2. The method for configuration management of an elastic public network IP according to claim 1, further comprising:
when a user requests an elastic public network IP for an example used by the user for the first time, the daemon Agent distributes the available elastic public network IP in the equipment group to the user and records the available elastic public network IP distributed to the user to a database; recording the binding relation between the available elastic public network IP and the instance used by the user in a database, and generating a configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; executing a configuration file for loading the available elastic public network IP through the Agent in the equipment group according to the binding relation, and binding the available elastic public network IP to the instance;
Adopting a key value pair to represent a configuration file binding the elastic public network IP for the instance, wherein the key of the key value pair is a path value of an ID of a device group to which the elastic public network IP bound by the instance belongs; the path value comprises equipment in which a key value pair representing a configuration file is located, an ID of an equipment group to which the equipment in which the Agent is located belongs is used as a prefix of the path value, and an elastic public network IP bound by an example is used as a suffix of the path value; the value of the key value pair is the relevant configuration of the elastic public network IP bound by the instance;
the Agent in each equipment group monitors whether the configuration of each elastic public network IP in the equipment group where the Agent is located changes or not, and specifically comprises the following steps:
the Agent searches the equipment group in which the Agent is located in the database through the main configuration information of the equipment group and the identification of the equipment, and obtains the prefix of the path value of the ID of the equipment group to which the elastic public network IP bound by the example belongs from the key value pair corresponding to the configuration file of the elastic public network IP bound by the example in the searched equipment group;
the Agent monitors the prefix of the path value of the key of the configuration file of the binding elastic public network IP for the instance in the equipment group, and senses the change of all sub paths of the instance through the change of the prefix of the path value.
3. The method for managing configuration of an elastic public network IP according to claim 1, further comprising, after all agents of the device group in which the agents are located execute loading configuration files of all elastic public network IPs of the device group:
All agents in the equipment group report the results of executing and loading the configuration files of all the elastic public network IPs of the equipment group to a task center through a remote procedure call protocol (RPC), and whether the configuration files of all the elastic public network IPs are completely successfully loaded and updated in respective examples is judged by analyzing the response information of the task center to the execution and loading results;
if the configuration file of the part of the elastic public network IP in the equipment group where the Agent is located fails to be loaded and updated in the corresponding instance or is overtime, the configuration file of a version on the part of the instance is pulled from the database to roll back, and the configuration of the part of the elastic public network IP of the instance is rolled back to the configuration before being updated and loaded; and when the loading update fails or the elastic public network IP with the configuration change is included in the timeout, an alarm is sent out, and the configuration file with the elastic public network IP with the change is loaded to the instance used by the corresponding user again to update the configuration of the elastic public network IP with the change.
4. The method for managing configuration of an elastic public network IP according to claim 3, wherein, while all agents of the device group where the agents are located execute loading configuration files of all elastic public network IPs of the device group, further comprising:
The method comprises the steps that a task center is responsible for maintaining and recording a state machine of executing the configuration file state of loading all the elastic public network IP of the equipment group by an Agent, the state machine is expressed in a key value pair mode, keys of the key value pair comprise a request ID of a user and the IP of the equipment where the Agent is located, and the value of the key value pair is the loading state of loading and updating the configuration file of the elastic public network IP to a corresponding instance; wherein:
initializing a state machine when each instance used by a user executes loading configuration files, and recording the loading state of the configuration files of the elastic public network IP, which are received for the first time, updated to the corresponding instance as executing;
the method comprises the steps that a returned loading state is received in a state return period agreed by a task center and an Agent, and the number of times of returning the loading state in the return period is set to be not more than the preset highest retry number; updating the loading state in the current state machine to be successful or failed according to the returned loading state;
when the status feedback period appointed by the task center and the Agent is exceeded and the returned loading status is not received, setting the loading status as overtime;
and the task center informs the loading state of the instance loading configuration file to the equipment corresponding to the deployment Agent according to the loading state in the current state machine.
5. The method for configuration management of an elastic public network IP according to claim 1, further comprising:
the Agent monitors whether the configuration of the equipment group where the Agent is located changes; wherein, the configuration of the device group includes: the device group main configuration information and the MD5 value corresponding to the device group, where the device group main configuration information includes: information of all devices for deploying the Agent, wherein the information of the devices for deploying the Agent comprises the following components: an ID of a device group to which the device belongs, and an IP address of each device in the device group; the MD5 value of the equipment group is used for checking the integrity of the main configuration information of the equipment group;
when the Agent monitors that the configuration of the equipment group is changed, the equipment is removed from the equipment group, or the equipment group is deleted, the Agent automatically ends the operation;
when the Agent monitors that the configuration of the equipment group is changed to a new equipment group, the equipment of the Agent acquires main configuration information of the new equipment group and a corresponding MD5 value of the new equipment group, and the main configuration information of the new equipment group is checked through the MD5 value of the new equipment group; after the verification of the main configuration information of the new equipment set is successful, the Agent monitors whether the relevant configuration of all the elastic public networks IP of the new equipment set changes or not, and monitors whether the configuration of the new equipment set changes or not.
6. A configuration management system for an elastic public network IP, comprising:
the device management unit is used for dividing the device deployed with the daemon Agent for executing configuration loading into a plurality of device groups, distributing the elastic public network IP to each device group, and managing the corresponding elastic public network IP configuration in the device groups by each device group;
the first monitoring unit is used for monitoring whether the configuration of each elastic public network IP in the equipment group where the Agent in each equipment group is located changes or not; when the Agent monitors that the configuration of the elastic public network IP in the equipment group is changed, acquiring the related configuration of the changed elastic public network IP; the relevant configuration of the elastic public network IP includes: the main configuration information of the elastic public network IP and the corresponding MD5 value of the elastic public network IP, wherein the main configuration information of the elastic public network IP comprises: the method comprises the steps that a user requests an ID, an ID of an instance used by the user, an elastic public network IP bound by the instance, and a binding mode of the instance binding elastic public network IP, wherein the binding mode of the instance binding elastic public network IP refers to that the instance binding unique elastic public network IP or the instance binding a plurality of elastic public network IPs; the MD5 value of the elastic public network IP is used for checking the integrity of the main configuration information of the corresponding elastic public network IP;
An example configuration updating unit, configured to verify main configuration information of the elastic public network IP by using an MD5 value of the elastic public network IP; when the verification of the main configuration information of the elastic public network IP is successful, recording the binding relation between the elastic public network IP and the instance used by the user in a database, and generating a new configuration file for binding the elastic public network IP to the instance used by the user according to the binding relation; all agents of the equipment group where the agents are located execute configuration files for loading all the elastic public network IP of the equipment group, and the elastic public network IP is bound to an instance used by a corresponding user.
7. The configuration management system of an elastic public network IP of claim 6, further comprising:
the distribution unit is used for distributing the available elastic public network IP in the equipment group to the user when the user requests the elastic public network IP for the used example for the first time, and recording the available elastic public network IP distributed to the user to the database by the daemon Agent; the binding relation between the available elastic public network IP and the instance used by the user is recorded in a database;
the first configuration unit is used for generating a configuration file for binding the elastic public network IP to an instance used by the user according to the binding relation; executing a configuration file for loading the available elastic public network IP through the Agent in the equipment group according to the binding relation, and binding the available elastic public network IP to the instance; the configuration file binding the elastic public network IP for the instance is represented by a key value, and the key of the key value pair is the path value of the ID of the equipment group to which the elastic public network IP bound by the instance belongs; the path value comprises equipment in which a key value pair representing a configuration file is located, an ID of an equipment group to which the equipment in which the Agent is located belongs is used as a prefix of the path value, and an elastic public network IP bound by an example is used as a suffix of the path value; the value of the key value pair is the relevant configuration of the elastic public network IP bound by the instance;
The first monitoring unit includes:
the monitoring information determining subunit is used for the Agent to find out the equipment group in which the Agent is located in the database through the main configuration information of the equipment group and the identification of the equipment, and obtain the prefix of the path value of the ID of the equipment group to which the elastic public network IP bound by the example belongs from the key value pair corresponding to the configuration file of the elastic public network IP bound by the example in the found equipment group;
and the monitoring path subunit is used for monitoring the prefixes of the path values of the keys of the configuration files of the instance binding elastic public network IP in the equipment group where the Agent is located, and sensing the changes of all sub paths of the instance through the changes of the prefixes of the path values.
8. The configuration management system of an elastic public network IP according to claim 7, wherein the instance configuration updating unit includes a result transfer subunit and a result parsing subunit, the configuration management system of an elastic public network IP further comprising a handling unit, wherein:
the result transmission subunit is configured to, after executing the loading of the configuration files of all the elastic public network IPs of the device group by all the agents of the device group where the agents are located, report the result of executing the loading of the configuration files of all the elastic public network IPs of the device group to the task center through the remote procedure call protocol RPC;
The result analysis subunit is used for judging whether the loading and updating of the configuration files of all the elastic public network IP in the respective examples are all successful or not through analyzing the response information of the task center to the execution loading result;
the processing unit is used for pulling a version of configuration file of the part of the instance from the database to roll back if the configuration file of the part of the elastic public network IP in the equipment group where the Agent is located fails to be loaded and updated in the corresponding instance or is overtime, and rolling back the configuration of the part of the elastic public network IP of the part of the instance to the configuration before the update and the loading; and when the loading update fails or the elastic public network IP with the configuration change is included in the timeout, an alarm is sent out, and the configuration file with the elastic public network IP with the change is loaded to the instance used by the corresponding user again to update the configuration of the elastic public network IP with the change.
9. The configuration management system of an elastic public network IP of claim 8, further comprising:
the task center is used for maintaining and recording a state machine of the state of the Agent for loading the configuration files of the elastic public network IP of the equipment group by the execution of all the agents of the equipment group, and representing the state machine in a key value pair form, wherein keys of the key value pair comprise a request ID of a user and the IP of the equipment of the Agent, and the value of the key value pair is the loading state of loading and updating the configuration files of the elastic public network IP to corresponding examples; wherein:
Initializing a state machine when each instance used by a user executes loading configuration files, and recording the loading state of the configuration files of the elastic public network IP, which are received for the first time, updated to the corresponding instance as executing;
the method comprises the steps that a returned loading state is received in a state return period agreed by a task center and an Agent, and the number of times of returning the loading state in the return period is set to be not more than the preset highest retry number; updating the loading state in the current state machine to be successful or failed according to the returned loading state;
when the status feedback period appointed by the task center and the Agent is exceeded and the returned loading status is not received, setting the loading status as overtime;
and the task center informs the loading state of the instance loading configuration file to the equipment corresponding to the deployment Agent according to the loading state in the current state machine.
10. The configuration management system of an elastic public network IP of claim 6, further comprising;
the second monitoring unit is used for monitoring whether the configuration of the equipment group where the Agent is located changes or not; wherein, the configuration of the device group includes: the device group main configuration information and the MD5 value corresponding to the device group, where the device group main configuration information includes: information of all devices for deploying the Agent, wherein the information of the devices for deploying the Agent comprises the following components: an ID of a device group to which the device belongs, and an IP address of each device in the device group; the MD5 value of the equipment group is used for checking the integrity of the main configuration information of the equipment group;
The termination unit is used for automatically ending the operation when the Agent monitors that the configuration of the equipment group is changed, the equipment is removed from the equipment group, or the equipment group is deleted;
the device group updating unit is used for acquiring main configuration information of the new device group and a corresponding MD5 value of the new device group by the device where the Agent is located when the Agent monitors that the configuration of the device group where the Agent is located changes to the new device group, and checking the main configuration information of the new device group through the MD5 value of the new device group;
the first monitoring unit is further configured to monitor, by an Agent, whether relevant configurations of all elastic public networks IP of the new device group change after verification of main configuration information of the new device group is successful;
the second monitoring unit is further configured to monitor whether the configuration of the new device group changes after the verification of the master configuration information of the new device group is successful.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110936151.8A CN113810513B (en) | 2021-08-16 | 2021-08-16 | Configuration management method and system for elastic public network IP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110936151.8A CN113810513B (en) | 2021-08-16 | 2021-08-16 | Configuration management method and system for elastic public network IP |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113810513A CN113810513A (en) | 2021-12-17 |
| CN113810513B true CN113810513B (en) | 2023-10-24 |
Family
ID=78943112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110936151.8A Active CN113810513B (en) | 2021-08-16 | 2021-08-16 | Configuration management method and system for elastic public network IP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113810513B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115174524B (en) * | 2022-05-18 | 2024-01-02 | 天翼云科技有限公司 | Floating IP distribution method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102394901A (en) * | 2011-06-23 | 2012-03-28 | 北京新媒传信科技有限公司 | Server cluster system and updating method of monitoring policies in same |
| CN110198221A (en) * | 2018-02-27 | 2019-09-03 | ***通信集团有限公司 | A kind of implementation method of load balancing, apparatus and system |
| US10630566B1 (en) * | 2012-06-20 | 2020-04-21 | Amazon Technologies, Inc. | Tightly-coupled external cluster monitoring |
| CN111708834A (en) * | 2020-05-25 | 2020-09-25 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for synchronizing service configuration data |
-
2021
- 2021-08-16 CN CN202110936151.8A patent/CN113810513B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102394901A (en) * | 2011-06-23 | 2012-03-28 | 北京新媒传信科技有限公司 | Server cluster system and updating method of monitoring policies in same |
| US10630566B1 (en) * | 2012-06-20 | 2020-04-21 | Amazon Technologies, Inc. | Tightly-coupled external cluster monitoring |
| CN110198221A (en) * | 2018-02-27 | 2019-09-03 | ***通信集团有限公司 | A kind of implementation method of load balancing, apparatus and system |
| CN111708834A (en) * | 2020-05-25 | 2020-09-25 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for synchronizing service configuration data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113810513A (en) | 2021-12-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9984140B1 (en) | Lease based leader election system | |
| US10585691B2 (en) | Distribution system, computer, and arrangement method for virtual machine | |
| US8055735B2 (en) | Method and system for forming a cluster of networked nodes | |
| CN107179879B (en) | Method and apparatus for data migration of storage device | |
| CN104598459B (en) | database processing, data access method and system | |
| CN111737230B (en) | Data verification method, device, electronic equipment and readable storage medium | |
| CN109218100A (en) | Distributed objects storage cluster and its request responding method, system and storage medium | |
| CN111262726B (en) | Configuration information updating method and device and computer readable storage medium | |
| CN109150608A (en) | Interface service upgrade method and system for voice dialogue platform | |
| KR20150110688A (en) | Instance host configuration | |
| CN113810513B (en) | Configuration management method and system for elastic public network IP | |
| CN103369038A (en) | PaaS (platform as a service) management platform and method | |
| CN110365524B (en) | Mirror image upgrading method and system for server node firmware | |
| CN112148206A (en) | Data reading and writing method and device, electronic equipment and medium | |
| CN110798358B (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| CN107623705B (en) | Storage mode upgrading method, device and system based on video cloud storage system | |
| CN107547622B (en) | Resource adjusting method and device | |
| CN113810463B (en) | Method and system for configuring delivery CDN server | |
| US11290318B2 (en) | Disaster recovery of cloud resources | |
| CN114610545A (en) | Method, system, device and medium for reducing single point of failure of private cloud computing | |
| CN114564530A (en) | Database access method, device, equipment and storage medium | |
| US10911307B2 (en) | System and method for out of the box solution-level configuration and diagnostic logging and reporting | |
| CN112463305A (en) | Management method, system and related device of cloud virtualization GPU | |
| CN110502460B (en) | Data processing method and node | |
| CN114296909B (en) | Automatic capacity expansion and contraction method and system for nodes according to kubernetes events |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230420 Address after: Room 501-502, 5/F, Sina Headquarters Scientific Research Building, Block N-1 and N-2, Zhongguancun Software Park, Dongbei Wangxi Road, Haidian District, Beijing, 100193 Applicant after: Sina Technology (China) Co.,Ltd. Address before: 100193 7th floor, scientific research building, Sina headquarters, plot n-1, n-2, Zhongguancun Software Park, Dongbei Wangxi Road, Haidian District, Beijing, 100193 Applicant before: Sina.com Technology (China) Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |