CN107071069B - Method and device for transparently switching data traffic to user, storage medium and electronic equipment - Google Patents
Method and device for transparently switching data traffic to user, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN107071069B CN107071069B CN201710447792.0A CN201710447792A CN107071069B CN 107071069 B CN107071069 B CN 107071069B CN 201710447792 A CN201710447792 A CN 201710447792A CN 107071069 B CN107071069 B CN 107071069B
- Authority
- CN
- China
- Prior art keywords
- configuration file
- server
- equalizer
- updated
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000003860 storage Methods 0.000 title claims abstract description 28
- 238000012795 verification Methods 0.000 claims description 16
- 238000012986 modification Methods 0.000 claims description 7
- 230000004048 modification Effects 0.000 claims description 7
- 238000009826 distribution Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 10
- 238000004590 computer program Methods 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 7
- 230000002159 abnormal effect Effects 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method, a device, a storage medium and electronic equipment for transparently switching data traffic to a user, wherein the method comprises the following steps: receiving update information, wherein the update information comprises node information of a server to be updated; remotely logging in the load balancer and acquiring a configuration file currently logged in the balancer according to the balancer IP and the configuration file storage position recorded in a prestored load balancer list; if the node information of the server to be updated is recorded in the configuration file of the currently logged balancer, modifying the configuration file according to the balancer type of the currently logged balancer recorded in the load balancer list; and sending a reloading instruction to enable the current login equalizer to execute the modified configuration file. According to the method, the server can be automatically removed from the distribution object of the load balancer in the process of updating the program of the server, and the updating efficiency and the user experience of the server are improved.
Description
Technical Field
The invention relates to the field of network communication, in particular to a method and a device for transparently switching data traffic to a user, a storage medium and electronic equipment.
Background
At present, most companies provide the same network service for users through a plurality of servers, the plurality of servers form a server cluster, and a load balancer is responsible for distributing data traffic requested by the users among the servers, so that the loads among the servers are balanced.
When a server in a server cluster needs to update a program, in order to avoid stopping network service, a corresponding load balancer is usually searched according to an IP of the server to be updated and a program running port, a configuration file in the load balancer is manually modified, one or more servers are removed from a distribution object of the load balancer, and the remaining servers continue to provide network service. And then, carrying out program updating on the removed server, adding the removed server into the distribution object of the load balancer by modifying the configuration file of the load balancer after the updating is finished, and repeating the steps until all the servers finish the program updating. By the above manner of manually removing the added server, an operator is required to check whether each step in the process is successful, so that the updating efficiency is low, and the use experience of the user is influenced. If the method is to be implemented, a database is also needed to be established for storing the corresponding relationship between the load balancer and the server IP and the program running port, so that after the IP and the program running port of the server to be updated are known, the corresponding load balancer is searched. In order to ensure that the corresponding relation in the database is consistent with the actual situation, when a certain server is added or removed, an operator needs to synchronize the server into the database, manual synchronization operation is easy to miss, and therefore inconvenience is brought to subsequent program updating.
Disclosure of Invention
The invention provides a method, a device, a storage medium and electronic equipment for transparently switching data streams to a user, and aims to solve the problem that when a server in a server cluster updates a program, the data flow of the server can be switched only in a mode of manually removing the server.
In order to solve the above problem, the present invention provides a method for transparently switching data streams to a user, comprising:
receiving update information, wherein the update information comprises node information of a server to be updated;
the method comprises the steps of remote login, namely sequentially remotely logging in the load balancer and acquiring a configuration file currently logged in the balancer according to a balancer IP and a configuration file storage position recorded in a prestored load balancer list, wherein the configuration file records node information of all servers corresponding to the currently logged in balancer;
modifying a configuration file, namely if node information of the server to be updated is recorded in the configuration file in the current login equalizer, modifying the configuration file according to the equalizer type of the current login equalizer recorded in the load equalizer list, and shielding at least one server to be updated in the modified configuration file;
and sending a reloading instruction to enable the current login equalizer to execute the modified configuration file and switch the shielded traffic borne by the server to be updated to other servers.
Optionally, in the step of modifying the configuration file, the method for transparently switching data traffic to a user further includes:
and backing up the configuration file and storing the backed-up configuration file in a specified directory.
Optionally, the method for transparently switching data traffic to a user, between the step of modifying the configuration file and the step of sending the reload instruction, further includes:
a step of sending a check instruction, so that the current login equalizer identifies the modified configuration file;
and receiving verification result information, and if the current login equalizer successfully identifies the modified configuration file, executing the step of sending the overloading instruction.
Optionally, in the method for transparently switching data traffic to a user, in the step of receiving the verification result information:
and if the current login equalizer cannot identify the modified configuration file, acquiring the backup configuration file to replace the modified configuration file, and then executing the step of sending the reloading instruction.
Optionally, in the method for transparently switching data traffic to a user, in the step of receiving the verification result information:
and if the current login equalizer cannot identify the modified configuration file, executing the configuration file modification step.
Optionally, the method for transparently switching data traffic to a user further includes:
inquiring the running state information of the current login equalizer, wherein the running state information comprises node information of all servers bearing data flow currently;
and an alarming step, namely if the running state information contains shielded node information of the server to be updated, sending out a shielding failure warning.
Optionally, the method for transparently switching data traffic to a user further includes:
and a shielding information sending step of sending shielding information including the shielded node information of the server to be updated if the running state information does not include the shielded node information of the server.
Optionally, the method for transparently switching data traffic to a user further includes:
receiving program state information, wherein the program state information comprises the program updating progress;
a configuration file replacing step, namely, if the program state information represents that the program updating is finished, acquiring the backup configuration file to replace the modified configuration file;
a step of executing a configuration file, which is to send a heavy load instruction to enable the current login equalizer to execute the backed-up configuration file;
and a prompting step, namely inquiring whether the running state information of the current login equalizer contains shielded node information of the server to be updated, and displaying prompt information representing successful updating of a program if the running state information of the current login equalizer contains shielded node information of the server to be updated.
Based on the same inventive concept, the invention also provides a device for transparently switching data traffic to users, which comprises:
the receiving unit is used for receiving the updating information, and the updating information comprises the node information of the server to be updated;
the login unit is used for sequentially and remotely logging in the load balancer and acquiring the configuration file currently logged in the balancer according to the balancer IP and the configuration file storage position recorded in the pre-stored load balancer list, wherein the configuration file records the node information of all servers corresponding to the currently logged balancer;
the configuration unit is used for modifying the configuration file according to the equalizer type of the current login equalizer recorded in the load equalizer list if the node information of the server to be updated is recorded in the configuration file of the current login equalizer, and shielding at least one server to be updated in the modified configuration file;
and the sending unit is used for sending a reloading instruction to enable the current login equalizer to execute the modified configuration file and switch the shielded flow borne by the server to be updated to other servers.
Based on the same inventive concept, the present invention also provides a readable storage medium storing computer instructions for executing any one of the above methods for transparently switching data traffic to a user when the computer executes the computer instructions.
Based on the same inventive concept, the invention also provides an electronic device for transparently switching data traffic to a user, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the one processor to cause the at least one processor to:
receiving update information, wherein the update information comprises node information of a server to be updated;
according to the balancer IP and the configuration file storage position recorded in a prestored load balancer list, sequentially and remotely logging in the load balancer and acquiring the configuration file currently logged in the balancer, wherein the configuration file records node information of all servers corresponding to the currently logged balancer;
modifying a configuration file, namely if node information of the server to be updated is recorded in the configuration file in the current login equalizer, modifying the configuration file according to the equalizer type of the current login equalizer recorded in the load equalizer list, and shielding at least one server to be updated in the modified configuration file;
and sending a reloading instruction to enable the current login equalizer to execute the modified configuration file, and switching the shielded traffic borne by the server to be updated to other servers.
Optionally, in the electronic device for transparently switching data traffic to a user, the at least one processor may further be configured to:
and backing up the configuration file and storing the backed-up configuration file in a specified directory.
Optionally, in the electronic device for transparently switching data traffic to a user, the at least one processor may further be configured to:
sending a checking instruction to enable the current login equalizer to identify the modified configuration file;
and receiving verification result information, and if the current login equalizer successfully identifies the modified configuration file, executing to send a heavy load instruction.
Optionally, in the electronic device for transparently switching data traffic to a user, the at least one processor may further be configured to:
and if the current login equalizer cannot identify the modified configuration file, acquiring the backup configuration file to replace the modified configuration file, and then executing and sending a reloading instruction.
Optionally, in the electronic device for transparently switching data traffic to a user, the at least one processor may further be configured to:
and if the current login equalizer cannot identify the modified configuration file, executing the configuration file modification step.
Optionally, in the electronic device for transparently switching data traffic to a user, the at least one processor may further be configured to:
inquiring the running state information of the current login equalizer, wherein the running state information comprises node information of all servers bearing data flow at present;
and if the running state information contains shielded node information of the server to be updated, sending out a shielding failure warning.
Optionally, in the electronic device for transparently switching data traffic to a user, the at least one processor may further be configured to:
and if the operation state information does not contain the shielded node information of the server, transmitting shielded information comprising the shielded node information of the server to be updated.
Optionally, in the electronic device for transparently switching data traffic to a user, the at least one processor may further be configured to:
receiving program state information, wherein the program state information comprises the program updating progress;
if the program state information represents that the program updating is finished, the backup configuration file is obtained to replace the modified configuration file;
sending a reloading instruction to enable the current login equalizer to execute the backed-up configuration file;
and inquiring whether the running state information of the current login equalizer contains shielded node information of the server to be updated, and if the running state information of the current login equalizer contains shielded node information of the server to be updated, displaying prompt information representing successful updating of a program.
The invention provides a method, a device, a storage medium and electronic equipment for transparently switching data flow to a user, wherein the method for transparently switching data flow to the user comprises the steps of sequentially logging in load balancers recorded in a load balancer list in a remote login mode after receiving update information, acquiring configuration files of the load balancers, judging whether the current login balancers correspond to servers to be updated or not by comparing the configuration files with node information in the update information, modifying the configuration files of the current login balancers if the current login balancers correspond to the servers to be updated, shielding at least one server to be updated in the modified configuration files, and then sending a overloading instruction to switch flow borne by the shielded servers to be updated to other servers. By the method, the server can be automatically removed from the distribution object of the load balancer in the process of updating the program of the server, workers do not need to check each step, data traffic of any user cannot be lost, and the updating efficiency and the user experience of the server are improved.
Drawings
Fig. 1 is a flowchart of a method for transparently switching data traffic to a user according to embodiment 1 of the present invention.
Fig. 2 is a flowchart of a method for transparently switching data traffic to a user according to embodiment 2 of the present invention.
Fig. 3 is a schematic structural diagram of an apparatus for transparently switching data traffic to a user according to embodiment 3 of the present invention.
Fig. 4 is a schematic block diagram of an electronic device for transparently switching data traffic to a user according to embodiment 6 of the present invention.
Detailed Description
The embodiments of the present invention will be further described with reference to the accompanying drawings.
Example 1
The embodiment provides a method for transparently switching data traffic to a user, which can be applied to a computer device, where the computer and a balancing server are in the same network, as shown in fig. 1, the method includes the following steps:
s101, receiving update information, wherein the update information comprises node information of a server to be updated. The updating information is from updating equipment which is responsible for updating the server program, the updating equipment acquires program information such as the name of the program to be updated and operation port information recorded in the program to be updated after receiving the program to be updated, the server node information to be updated corresponding to the program to be updated is determined according to the corresponding relation between the program information stored in the updating equipment and the server node information, and the node information is the IP address of the server and the program operation port information.
S102, sequentially and remotely logging in the load balancer and acquiring the configuration file currently logged in the balancer according to the balancer IP and the configuration file storage position recorded in the pre-stored load balancer list, wherein the configuration file records node information of all servers corresponding to the currently logged balancer.
The locally pre-stored list of the load balancers includes the balancer IP of each load balancer and the storage location of the configuration file, where the balancer IP represents the location of the load balancer in the network, and according to the balancer IP, the corresponding load balancer can be remotely logged in, for example, by configuring SSH (Secure Shell) channel, and according to the storage location of the configuration file, the configuration file of the currently logged balancer is obtained. In this step, according to the sequence of the load balancers in the load balancer list, the load balancers are remotely logged in sequence and the configuration files currently logged in the balancers are obtained, whether the node information of the server to be updated exists in the configuration files is inquired, if the node information of the server to be updated is recorded in the configuration files currently logged in the balancers, the inquiry is stopped, and the next step is executed. And if the acquired configuration files do not find the node information of the server to be updated, the server can directly exit and display the prompt information which is not found.
In the step, whether the current login equalizer is the load equalizer corresponding to the server to be updated is judged by logging in the corresponding load equalizer through the equalizer IP and matching whether the server node information recorded in the configuration file of the current login equalizer is consistent with the node of the server to be updated, so that a database is not required to be established to maintain the corresponding relation between the load equalizer and the server node information, the condition that the update is not timely due to the fact that the database is maintained manually is avoided, and better guarantee is provided for the subsequent program update.
And S103, if the node information of the server to be updated is recorded in the configuration file of the currently logged balancer, modifying the configuration file according to the balancer type of the currently logged balancer recorded in the load balancer list, and shielding at least one server to be updated in the modified configuration file.
The load balancer list further comprises a balancer type of each load balancing server, and the balancer type is related to the model of the load balancer and a manufacturer for producing the load balancer. The formats and syntaxes of the configuration files of the load balancers of different balancer types are different, so that when the configuration files are modified, the load balancers cannot identify the load balancers according to the balancer types. In this step, if the node information of the server to be updated is recorded in the configuration file of the currently logged balancer, it is indicated that the server to be updated corresponds to the currently logged load balancer, the configuration file is modified according to the balancer type of the currently logged load balancer recorded in the load balancer list, at least one server to be updated is shielded in the modified configuration file, and the shielding can be performed in a manner of deleting a code containing the node information of the server to be updated or not executing a code containing the node information of the server to be updated, i.e., the server to be updated is shielded, i.e., the server to be updated is removed from the currently logged balancer. The order of shielding the servers to be updated can be determined according to the IP size of each server to be updated, for example, the servers to be updated with a smaller priority update IP address can also be determined according to the capacity of each server to be updated, for example, the servers to be updated with a smaller priority update capacity can be determined. Meanwhile, the number of the shielded servers to be updated can also be determined more than the current data flow, for example, when the data flow is larger, only one server is updated at a time.
And S104, sending a reloading instruction to enable the current login equalizer to execute the modified configuration file, and switching the shielded traffic borne by the server to be updated to other servers.
Specifically, the configuration file is read once by the load balancer only after the load balancer is restarted or receives a reload instruction, so that the modified configuration file is not immediately executed by the load balancer after the configuration file is modified. In this step, a reload instruction is sent to enable the load balancer to execute the modified configuration file, the shielded traffic borne by the server to be updated is switched to other servers, and data traffic is not distributed to the server to be updated any more.
In the method for transparently switching data traffic to a user described in this embodiment, after update information is received, load balancers recorded in a load balancer list are sequentially logged in a remote login manner, a configuration file of the load balancers is obtained, whether a currently logged balancer corresponds to a server to be updated is determined by comparing node information in the configuration file and the update information, if the currently logged balancer corresponds to the server to be updated, the configuration file of the currently logged balancer is modified, at least one server to be updated is shielded in the modified configuration file, and then a reload instruction is sent, and traffic carried by the shielded server to be updated is switched to other servers. By the method, the server can be automatically removed from the distribution object of the load balancer in the process of updating the program of the server, workers do not need to check each step, data traffic of any user cannot be lost, and the updating efficiency and the user experience of the server are improved.
Example 2
The present embodiment provides another method for transparently switching data traffic to a user, as shown in fig. 2, including the following steps:
s201, receiving update information, wherein the update information comprises node information of a server to be updated.
S202, according to the balancer IP and the configuration file storage position recorded in the pre-stored load balancer list, logging in the balancer remotely in sequence and acquiring the configuration file currently logged in the balancer, wherein the configuration file records node information of all servers corresponding to the currently logged balancer.
S203, if the node information of the server to be updated is recorded in the configuration file in the current login equalizer, backing up the configuration file, storing the backed-up configuration file in an appointed directory, modifying the configuration file according to the equalizer type of the current login equalizer recorded in the loader list, and shielding at least one server to be updated in the modified configuration file.
In this step, before modifying the configuration file, the configuration file is backed up for standby, so as to prevent the modified configuration file from generating problems.
S204, sending a checking instruction to enable the current login equalizer to identify the modified configuration file.
Specifically, because the equalizer types of each load equalizer are different, during the process of modifying the configuration file, errors are easy to occur, for example, syntax problems occur, and the IP which should be written in the upper case is written into the lower case IP, so that the load equalizer cannot identify the configuration file. If the load balancer directly executes the configuration file which cannot be identified, the load balancer cannot work normally, and the problem can be effectively avoided by sending the verification instruction in the step. After the modified configuration file is verified, the load balancer sends verification result information, and whether the modified configuration file is successfully identified by the load balancer can be judged through the information.
S205, receiving the verification result information, judging whether the current login equalizer can identify the modified configuration file, and if not, executing the step S206; if the current logged equalizer successfully identifies the modified configuration file, step S207 is executed.
S206, the backed-up configuration file is acquired to replace the modified configuration file, and then step S207 is executed. In this step, if the current logged equalizer cannot identify the modified configuration file, the backup configuration file is obtained to replace the modified configuration file, so as to avoid the abnormality of the current logged equalizer. This step may also return to execution S203 to retry modifying the configuration file.
S207, sending a reloading instruction to enable the current login equalizer to execute a configuration file once. The configuration file in this step may be a modified configuration file or a backup configuration file.
And S208, inquiring the running state information of the current login equalizer, wherein the running state information comprises the node information of all current servers bearing data traffic.
Specifically, when the load balancer is distributing data traffic, it generates an operation status message, which includes node information of the server currently carrying the data traffic, and if a server is successfully masked by modifying the configuration file, the operation status message will not appear. In addition, if some servers corresponding to the load balancer have abnormality, the abnormality will not appear in the running state information.
S209, judging whether the operation state information contains shielded node information of the server to be updated, and if so, executing a step S210; if not, step S211 is executed.
In this step, if the backed-up configuration file is executed in step S207 and the shielded server to be updated has an abnormality, the node information of the server to be updated that is not shielded in the operation state information is not included in the operation state information when the operation state information is queried, so that the server to be updated is still successfully shielded.
S210, a shielding failure warning is sent out. In this step, when the running state information includes the shielded node information of the server to be updated, it indicates that the shielded server to be updated fails to shield, so that a shielding failure warning is sent to prompt an operator that the server to be updated fails to be removed, and the later program updating is correspondingly stopped.
S211, sending the shielded information including the shielded node information of the server to be updated. In this step, the shielding information is sent to the updating device, so that the updating device finds the corresponding server according to the node information in the shielding information and updates the program of the corresponding server.
S212, receiving program state information, wherein the program state information comprises the program updating progress. In this step, whether the program update is finished is judged by obtaining the program update progress, and then the time for adding the shielded server to be updated is determined.
And S213, if the program state information represents that the program updating is finished, acquiring the backup configuration file to replace the modified configuration file. In this step, the shielded server to be updated may also be added by modifying the modified configuration file.
S214, sending a reloading instruction to enable the current login equalizer to execute the backed-up configuration file.
S215, inquiring whether the running state information of the current login equalizer contains the shielded node information of the server to be updated, and if so, displaying prompt information representing successful program updating. In this step, whether the shielded server to be updated is successfully added is further confirmed by querying the running state of the currently logged-in equalizer, and if the program update fails or the shielded server to be updated is unsuccessfully added, node information of the server to be updated, which is not shielded, in the running state information of the currently logged-in equalizer can be displayed, and prompt information representing the program update failure can be displayed at this time.
In this embodiment, before the configuration file is modified, the configuration file is backed up to prevent the modified configuration file from being problematic, and before the reload instruction is sent, the check instruction is sent to enable the current login equalizer to identify the modified configuration file, and if the current login equalizer can successfully identify the modified configuration file, the reload instruction is sent again, so that the problem of abnormal work caused by the fact that the load equalizer directly executes the configuration file which cannot be identified can be avoided. And after the load balancer re-executes the configuration file, inquiring the running state information of the load balancer, further confirming whether the shielding of the service area to be updated is successful, and when the shielding is successful, sending the shielding information out, and updating the program in the shielded server to be updated. And after the updating is finished, the shielded servers to be updated are added again by using the backup configuration files, and whether the shielded servers to be updated are successfully added is further confirmed through the running state information of the load balancer. Through the scheme, the servers to be updated are automatically removed and added, the manual maintenance amount and the manual misoperation are reduced, and the safety requirement is improved.
Example 3
The present embodiment provides an apparatus for transparently switching data traffic to a user, as shown in fig. 3, including:
the receiving unit 301 receives update information, where the update information includes node information of a server to be updated. And the node information is the IP address of the server and the program operation port information.
The login unit 302 sequentially and remotely logs in the load balancer and obtains the configuration file currently logged in the load balancer according to the balancer IP and the configuration file storage location recorded in the pre-stored load balancer list, where the configuration file records node information of all servers corresponding to the currently logged in balancer. In the unit, according to the sequence of the load balancers in the load balancer list, the load balancers are remotely logged in sequence, configuration files in the current logged balancers are obtained, whether node information of a server to be updated exists in the configuration files is inquired, if the node information of the server to be updated is recorded in the configuration files in the current logged balancers, the inquiry is stopped, and the next step is executed. By means of the remote login query method, a database does not need to be established to maintain the corresponding relation between the load balancer and the server borrowing point information, manual maintenance amount is reduced, meanwhile, the server does not need to be synchronized to the database when being removed and added, and labor cost and maintenance cost are greatly reduced.
The configuration unit 303, if the node information of the server to be updated is recorded in the configuration file currently logged in the load balancer, modifies the configuration file according to the balancer type of the currently logged in load balancer recorded in the load balancer list, and shields at least one server to be updated in the modified configuration file. The load balancer list further comprises a balancer type of each load balancing server, and the balancer type is related to the model of the load balancer and a manufacturer for producing the load balancer. In this unit, if the node information of the server to be updated is recorded in the configuration file of the currently logged balancer, it is indicated that the server to be updated corresponds to the currently logged load balancer, the configuration file is modified according to the balancer type of the currently logged load balancer recorded in the load balancer list, at least one server to be updated is shielded in the modified configuration file, and the shielding can be performed in a manner of deleting a code containing the node information of the server to be updated or not executing a code containing the node information of the server to be updated, i.e., the server to be updated is shielded, i.e., the server to be updated is removed from the currently logged balancer.
A sending unit 304, configured to send a reload instruction, so that the current login equalizer executes the modified configuration file, and switches the traffic carried by the shielded server to be updated to another server. In this unit, a reload instruction is sent to enable the load balancer to execute the modified configuration file, the shielded traffic borne by the server to be updated is switched to other servers, and data traffic is not distributed to the server to be updated any more.
The apparatus for transparently switching data traffic to a user in this embodiment includes a receiving unit 301, a logging unit 302, a configuration unit 303, and a sending unit 304. The receiving unit 301 receives node information of a server to be updated, the logging unit 302 remotely logs in the load balancer to obtain a configuration file in the load balancer according to a balancer IP recorded in a pre-stored load balancer list, if borrowing point information of the server to be updated is stored in the configuration file of the currently logged balancer, the configuration unit 303 modifies the configuration file of the currently logged balancer according to the balancer type, so that the modified configuration file shields at least one server to be updated, and finally the sending unit 304 sends a reload instruction, so that the currently logged balancer executes the modified configuration file. By the aid of the device, the servers to be updated are automatically removed and added, manual maintenance and manual misoperation are reduced, and safety requirements are improved.
Example 4
This embodiment provides another apparatus for transparently switching data traffic to a user, including:
and the receiving unit is used for receiving the updating information, and the updating information comprises the node information of the server to be updated. And the node information is the IP address of the server and the program operation port information.
And the login unit is used for sequentially and remotely logging in the load balancer and acquiring the configuration file currently logged in the load balancer according to the balancer IP and the configuration file storage position recorded in the pre-stored load balancer list, wherein the configuration file records the node information of all servers corresponding to the currently logged balancer. In the unit, according to the sequence of the load balancers in the load balancer list, the load balancers are remotely logged in sequence, configuration files in the current logged balancers are obtained, whether node information of a server to be updated exists in the configuration files is inquired, and if the node information of the server to be updated is recorded in the configuration files in the current logged balancers, the inquiry is stopped, and the next unit is started. By means of the remote login query method, a database does not need to be established to maintain the corresponding relation between the load balancer and the server borrowing point information, manual maintenance amount is reduced, meanwhile, the server does not need to be synchronized to the database when being removed and added, and labor cost and maintenance cost are greatly reduced.
And the configuration unit is used for backing up the configuration file if the node information of the server to be updated is recorded in the configuration file currently logged in the equalizer, storing the backed-up configuration file in an appointed directory, modifying the configuration file according to the equalizer type of the currently logged equalizer recorded in the loader list, and shielding at least one server to be updated in the modified configuration file. The load balancer list further comprises a balancer type of each load balancing server, and the balancer type is related to the model of the load balancer and a manufacturer for producing the load balancer. In this unit, if the node information of the server to be updated is recorded in the configuration file of the currently logged balancer, it is indicated that the server to be updated corresponds to the currently logged load balancer, the configuration file is modified according to the balancer type of the currently logged load balancer recorded in the load balancer list, at least one server to be updated is shielded in the modified configuration file, and the shielding can be performed in a manner of deleting a code containing the node information of the server to be updated or not executing a code containing the node information of the server to be updated, i.e., the server to be updated is shielded, i.e., the server to be updated is removed from the currently logged balancer.
And the sending unit is used for sending a check instruction to enable the current login equalizer to identify the modified configuration file. Specifically, because the equalizer types of each load equalizer are different, during the process of modifying the configuration file, errors are easy to occur, for example, syntax problems occur, and the IP which should be written in the upper case is written into the lower case IP, so that the load equalizer cannot identify the configuration file. If the load balancer directly executes the configuration file which cannot be identified, the load balancer cannot work normally, and the unit sends the verification instruction to effectively avoid the problems.
And the receiving unit is used for receiving the verification result information, acquiring the backup configuration file to replace the modified configuration file if the current login equalizer cannot identify the modified configuration file, and then entering the next unit. If the current login equalizer cannot identify the modified configuration file, the receiving unit may also return to the configuration unit to execute the configuration file modification. And the receiving unit enters the next unit if the current login equalizer successfully identifies the modified configuration file.
And the sending unit is used for sending a heavy-load instruction to enable the current login equalizer to execute the modified configuration file and switch the flow borne by the shielded server to be updated to other servers. In this unit, a reload instruction is sent to enable the load balancer to execute the modified configuration file, the shielded traffic borne by the server to be updated is switched to other servers, and data traffic is not distributed to the server to be updated any more.
And the query unit is used for querying the running state information of the current login equalizer, wherein the running state information comprises the node information of all servers bearing data flow currently. Specifically, when the load balancer is distributing data traffic, it generates an operation status message, which includes node information of the server currently carrying the data traffic, and if a server is successfully masked by modifying the configuration file, the operation status message will not appear.
And the alarm unit is used for sending out a shielding failure warning if the running state information contains shielded node information of the server to be updated. In this unit, when the operation status information includes the node information of the shielded server to be updated, it indicates that the shielded server to be updated fails to be shielded, so that a shielding failure warning is sent to prompt an operator that the server to be updated fails to be removed, and the later program update is correspondingly stopped.
And an information sending unit, configured to send shielding information including the shielded node information of the server to be updated if the running state information does not include the shielded node information of the server to be updated. In the unit, the shielding information is sent to the updating device, so that the updating device finds the corresponding server according to the node information in the shielding information and updates the program of the corresponding server.
The receiving unit receives program status information, wherein the program status information comprises the program updating progress. In the present unit, it is determined whether the program update is completed by acquiring the program update progress, and then the timing of adding the masked server to be updated is determined.
And the file replacing unit is used for acquiring the backup configuration file to replace the modified configuration file if the program state information represents that the program updating is finished.
And the instruction sending unit is used for sending a heavy-load instruction to enable the current login equalizer to execute the backed-up configuration file.
And the result query unit is used for querying whether the running state information of the current login equalizer contains the shielded node information of the server to be updated or not, and displaying prompt information representing successful program updating if the running state information of the current login equalizer contains the shielded node information of the server to be updated. In the unit, whether the shielded server to be updated is successfully added is further confirmed by inquiring the running state of the currently logged balancer, and if the program updating fails or the shielded server to be updated is unsuccessfully added, the running state information of the currently logged balancer does not contain the shielded node information of the server to be updated.
In this embodiment, before modifying the configuration file, the configuration unit backs up the configuration file to prevent the modified configuration file from causing a problem, and the sending unit sends the verification instruction before sending the reload instruction, so that the current login equalizer identifies the modified configuration file, the receiving unit receives the verification result information, and when the current login equalizer can successfully identify the modified configuration file, the sending unit sends the reload instruction again, so that the problem of abnormal work caused by the fact that the load equalizer directly executes the configuration file which cannot be identified can be avoided. And after the load balancer re-executes the configuration file, the query unit queries the running state information of the load balancer and further confirms whether the shielding of the service area to be updated is successful, and when the shielding is successful, the information sending unit sends out the shielding information and updates the programs in the shielded server to be updated. After the updating is completed, the file replacing unit adds the shielded servers to be updated again by using the backup configuration files, and the result inquiring unit inquires the running state information of the load balancer to further confirm whether the shielded servers to be updated are successfully added. Through the scheme, the servers to be updated are automatically removed and added, the manual maintenance amount and the manual misoperation are reduced, and the safety requirement is improved.
Example 5
The present embodiment provides a readable storage medium, which may be a non-volatile computer storage medium, and the storage medium stores computer-executable instructions, which may execute the method for transparently switching data traffic to a user in any of the above method embodiments.
Example 6
The present embodiment provides an electronic device for transparently switching data traffic to a user, as shown in fig. 4, including: at least one processor 401; and a memory 402 communicatively coupled to the at least one processor; wherein,
the memory 402 stores instructions executable by the one processor 401 to cause the at least one processor 402 to:
the updating information comprises node information of the server to be updated;
according to the storage positions of the balancer IP and the configuration files recorded in a prestored load balancer list, sequentially and remotely logging in a load list balancer and acquiring the configuration files currently logged in the load balancer, wherein the configuration files record node information of all servers corresponding to the currently logged balancer;
modifying a configuration file, namely modifying the configuration file according to the equalizer type of the current login load equalizer recorded in the load equalizer list if the node information of the server to be updated is recorded in the configuration file of the current login load equalizer, and shielding at least one server to be updated in the modified configuration file;
and enabling the current login equalizer to execute the modified configuration file, and switching the flow borne by the shielded server to be updated to other servers.
In the scheme, the corresponding load balancer is found out in a remote login mode, a database is not required to be established to maintain the corresponding relation between the load balancer and the server node information, the condition that the database is artificially maintained and update is not timely is avoided, and better guarantee is provided for subsequent program update. Meanwhile, the server is automatically removed from the distribution object of the load balancer in the process of updating the program of the server, workers do not need to check each step, data traffic of any user cannot be lost, and the updating efficiency and the user experience of the server are improved.
Further, in the electronic device for transparently switching data traffic to a user according to the embodiment, the at least one processor 402 further includes:
and backing up the configuration file and storing the backed-up configuration file in a specified directory.
Before the configuration file is modified, the configuration file is backed up for standby so as to prevent the problem of the modified configuration file.
The at least one processor 402 is further capable of:
sending a checking instruction to enable the current login equalizer to identify the modified configuration file;
and receiving verification result information, and if the current login equalizer successfully identifies the modified configuration file, executing to send a heavy load instruction.
By sending the check instruction, the configuration file which is not identified and is modified and executed by the current login equalizer can be avoided, and the abnormal work of the current login equalizer caused by the configuration file can be avoided.
When the load balancer cannot identify the modified configuration file, the at least one processor 402 is further capable of:
and if the current login equalizer cannot identify the modified configuration file, acquiring the backup configuration file to replace the modified configuration file, and then executing and sending a reloading instruction.
Namely, the backup configuration file is adopted to replace the modified configuration file, so that the abnormal working of the current login equalizer is avoided.
The at least one processor 402 is further capable of: and if the current login equalizer cannot identify the modified configuration file, executing the configuration file modification step.
The at least one processor 402 is further capable of:
inquiring the running state information of the current login equalizer, wherein the running state information comprises node information of all servers bearing data flow at present;
and if the running state information contains shielded node information of the server to be updated, sending out a shielding failure warning.
When the load balancer distributes the data traffic, it will generate an operation status message, which includes the node information of the server currently carrying the data traffic, and if a certain server is successfully shielded by modifying the configuration file, it will not appear in the operation status message. And when the running state information contains the shielded node information of the server to be updated, the shielded server to be updated is failed to shield, so that a shielding failure warning is sent to prompt an operator that the server to be updated fails to be removed, and the later program updating is correspondingly stopped.
The at least one processor 402 is further capable of:
and if the operation state information does not contain the shielded node information of the server, transmitting shielded information comprising the shielded node information of the server to be updated. And sending the shielding information to the updating equipment, so that the updating equipment finds the corresponding server according to the node information in the shielding information and updates the program of the server.
The at least one processor 402 is further capable of:
receiving program state information, wherein the program state information comprises the program updating progress;
if the program state information represents that the program updating is finished, the backup configuration file is obtained to replace the modified configuration file;
sending a reloading instruction to enable the current login equalizer to execute the backed-up configuration file;
and inquiring whether the running state information of the current login equalizer contains shielded node information of the server to be updated, and if the running state information of the current login equalizer contains shielded node information of the server to be updated, displaying prompt information representing successful updating of a program.
And judging whether the program updating is finished or not by acquiring the program updating progress, and then determining the time for adding the shielded server to be updated. And further confirming whether the shielded server to be updated is successfully added or not by inquiring the running state of the current login equalizer, wherein if the program updating fails or the shielded server to be updated is unsuccessfully added, the node information of the server to be updated, which is not shielded, in the running state information of the current login equalizer can display prompt information representing the program updating failure.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (8)
1. A method for transparently switching data traffic to a user, comprising the steps of:
receiving update information, wherein the update information comprises node information of a server to be updated;
the method comprises the steps of remote login, namely sequentially remotely logging in the load balancer and acquiring a configuration file currently logged in the balancer according to a balancer IP and a configuration file storage position recorded in a prestored load balancer list, wherein the configuration file records node information of all servers corresponding to the currently logged in balancer;
modifying a configuration file, namely if node information of the server to be updated is recorded in the configuration file in the current login equalizer, modifying the configuration file according to the equalizer type of the current login equalizer recorded in the load equalizer list, and shielding at least one server to be updated in the modified configuration file;
a step of sending a reload instruction, which enables the current login equalizer to execute the modified configuration file and switches the shielded traffic borne by the server to be updated to other servers;
in the step of modifying the configuration file, the method further comprises the following steps:
backing up the configuration file and storing the backed-up configuration file in a specified directory;
between the step of modifying the configuration file and the step of sending the reloading instruction, the method further comprises the following steps:
a step of sending a check instruction, so that the current login equalizer identifies the modified configuration file;
receiving verification result information, and if the current login equalizer successfully identifies the modified configuration file, executing the step of sending a heavy load instruction;
in the step of receiving the verification result information:
if the current login equalizer cannot identify the modified configuration file, acquiring the backup configuration file to replace the modified configuration file, and then executing a step of sending a reloading instruction;
inquiring the running state information of the current login equalizer, wherein the running state information comprises node information of all servers bearing data flow currently;
an alarm step, namely if the running state information contains shielded node information of the server to be updated, sending out a shielding failure alarm;
and a shielding information sending step of sending shielding information including the shielded node information of the server to be updated if the running state information does not include the shielded node information of the server.
2. The method of claim 1, wherein in the step of receiving the verification result information:
and if the current login equalizer cannot identify the modified configuration file, executing the configuration file modification step.
3. The method of transparently switching data traffic according to claim 1, further comprising:
receiving program state information, wherein the program state information comprises the program updating progress;
a configuration file replacing step, namely, if the program state information represents that the program updating is finished, acquiring the backup configuration file to replace the modified configuration file;
a step of executing a configuration file, which is to send a heavy load instruction to enable the current login equalizer to execute the backed-up configuration file;
and a prompting step, namely inquiring whether the running state information of the current login equalizer contains shielded node information of the server to be updated, and displaying prompt information representing successful updating of a program if the running state information of the current login equalizer contains shielded node information of the server to be updated.
4. An apparatus for transparently switching data traffic to a user, comprising:
the receiving unit is used for receiving the updating information, and the updating information comprises the node information of the server to be updated;
the login unit is used for sequentially and remotely logging in the load balancer and acquiring the configuration file currently logged in the balancer according to the balancer IP and the configuration file storage position recorded in the pre-stored load balancer list, wherein the configuration file records the node information of all servers corresponding to the currently logged balancer;
the configuration unit is used for modifying the configuration file according to the equalizer type of the current login equalizer recorded in the load equalizer list if the node information of the server to be updated is recorded in the configuration file of the current login equalizer, and shielding at least one server to be updated in the modified configuration file;
the sending unit is used for sending a heavy-load instruction to enable the current login equalizer to execute the modified configuration file and switch the shielded flow borne by the server to be updated to other servers;
further comprising:
backing up the configuration file and storing the backed-up configuration file in a specified directory;
further comprising:
a step of sending a check instruction, so that the current login equalizer identifies the modified configuration file;
if the current login equalizer successfully identifies the modified configuration file, executing and sending a heavy load instruction;
if the current login equalizer cannot identify the modified configuration file, acquiring the backup configuration file to replace the modified configuration file, and then executing a step of sending a reloading instruction;
inquiring the running state information of the current login equalizer, wherein the running state information comprises node information of all servers bearing data flow currently;
an alarm step, namely if the running state information contains shielded node information of the server to be updated, sending out a shielding failure alarm;
and a shielding information sending step of sending shielding information including the shielded node information of the server to be updated if the running state information does not include the shielded node information of the server.
5. A computer-readable storage medium storing computer instructions for performing the method for transparently switching data traffic to a user of any one of claims 1-3 when the computer instructions are executed by a computer.
6. An electronic device for transparently switching data traffic to a user, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to:
receiving update information, wherein the update information comprises node information of a server to be updated;
according to the balancer IP and the configuration file storage position recorded in a prestored load balancer list, sequentially and remotely logging in the load balancer and acquiring the configuration file currently logged in the balancer, wherein the configuration file records node information of all servers corresponding to the currently logged balancer;
modifying a configuration file, namely if node information of the server to be updated is recorded in the configuration file in the current login equalizer, modifying the configuration file according to the equalizer type of the current login equalizer recorded in the load equalizer list, and shielding at least one server to be updated in the modified configuration file;
sending a reloading instruction to enable the current login equalizer to execute the modified configuration file, and switching the shielded traffic borne by the server to be updated to other servers; the at least one processor is further capable of:
backing up the configuration file and storing the backed-up configuration file in a specified directory;
the at least one processor is further capable of:
sending a checking instruction to enable the current login equalizer to identify the modified configuration file;
receiving verification result information, and if the current login equalizer successfully identifies the modified configuration file, executing to send a heavy load instruction;
the at least one processor is further capable of:
if the current login equalizer cannot identify the modified configuration file, the backup configuration file is obtained to replace the modified configuration file, and then a heavy load instruction is sent;
inquiring the running state information of the current login equalizer, wherein the running state information comprises node information of all servers bearing data flow at present;
if the running state information contains shielded node information of the server to be updated, a shielding failure warning is sent out;
and if the operation state information does not contain the shielded node information of the server, transmitting shielded information comprising the shielded node information of the server to be updated.
7. The electronic device of claim 6, wherein the at least one processor is further capable of:
and if the current login equalizer cannot identify the modified configuration file, executing the configuration file modification step.
8. The electronic device of claim 6, wherein the at least one processor is further capable of:
receiving program state information, wherein the program state information comprises the program updating progress;
if the program state information represents that the program updating is finished, the backup configuration file is obtained to replace the modified configuration file;
sending a reloading instruction to enable the current login equalizer to execute the backed-up configuration file;
and inquiring whether the running state information of the current login equalizer contains shielded node information of the server to be updated, and if the running state information of the current login equalizer contains shielded node information of the server to be updated, displaying prompt information representing successful updating of a program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710447792.0A CN107071069B (en) | 2017-06-14 | 2017-06-14 | Method and device for transparently switching data traffic to user, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710447792.0A CN107071069B (en) | 2017-06-14 | 2017-06-14 | Method and device for transparently switching data traffic to user, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107071069A CN107071069A (en) | 2017-08-18 |
| CN107071069B true CN107071069B (en) | 2020-08-25 |
Family
ID=59595255
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710447792.0A Expired - Fee Related CN107071069B (en) | 2017-06-14 | 2017-06-14 | Method and device for transparently switching data traffic to user, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107071069B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110572284B (en) * | 2019-08-30 | 2022-05-13 | 华为云计算技术有限公司 | A method, device and system for upgrading virtual network element |
| CN112394960B (en) * | 2020-11-23 | 2024-06-07 | 中国农业银行股份有限公司 | Control method and device for service flow, electronic equipment and computer storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468735A (en) * | 2014-11-19 | 2015-03-25 | 山东中创软件工程股份有限公司 | Load balancer management method and device based on graphical user interface |
| CN105005487A (en) * | 2015-06-29 | 2015-10-28 | 清华大学 | Continuous-service high-performance cluster operating system online upgrading method |
| CN106201561A (en) * | 2015-04-30 | 2016-12-07 | 阿里巴巴集团控股有限公司 | The upgrade method of distributed caching cluster and equipment |
| CN106550014A (en) * | 2016-10-09 | 2017-03-29 | 华为数字技术（成都）有限公司 | Node upgrade method and device in server cluster |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9026655B2 (en) * | 2007-01-31 | 2015-05-05 | Oracle America, Inc. | Method and system for load balancing |
-
2017
- 2017-06-14 CN CN201710447792.0A patent/CN107071069B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468735A (en) * | 2014-11-19 | 2015-03-25 | 山东中创软件工程股份有限公司 | Load balancer management method and device based on graphical user interface |
| CN106201561A (en) * | 2015-04-30 | 2016-12-07 | 阿里巴巴集团控股有限公司 | The upgrade method of distributed caching cluster and equipment |
| CN105005487A (en) * | 2015-06-29 | 2015-10-28 | 清华大学 | Continuous-service high-performance cluster operating system online upgrading method |
| CN106550014A (en) * | 2016-10-09 | 2017-03-29 | 华为数字技术（成都）有限公司 | Node upgrade method and device in server cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107071069A (en) | 2017-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108683516B (en) | Application instance upgrading method, device and system | |
| US9405630B2 (en) | Methods and apparatus to perform site recovery of a virtual data center | |
| CN103595807B (en) | A kind of data synchronization updating method and device | |
| CN113778623A (en) | Resource processing method and device, electronic equipment and storage medium | |
| CN110162334B (en) | Code management method, device and storage medium | |
| CN112434008A (en) | Distributed database upgrading method, device and medium | |
| CN103488590A (en) | Programmable display | |
| EP4162649B1 (en) | Stable references for network function life cycle management automation | |
| CN111464603A (en) | Server capacity expansion method and system | |
| CN105607968B (en) | A kind of incremental backup method and equipment | |
| CN104793981A (en) | Online snapshot managing method and device for virtual machine cluster | |
| CN107071069B (en) | Method and device for transparently switching data traffic to user, storage medium and electronic equipment | |
| CN102833101A (en) | Software upgrading method and equipment of distributed network system | |
| CN113242147B (en) | Automatic operation and maintenance deployment method, device, equipment and storage medium of multi-cloud environment | |
| CN109274734B (en) | Service process calling method and device based on Internet of things cloud platform | |
| CN113347037A (en) | Data center access method and device | |
| CN108804129B (en) | Software upgrading method and device | |
| CN113746676B (en) | Network card management method, device, equipment, medium and product based on container cluster | |
| CN113760608B (en) | Data recovery method and device, electronic equipment and storage medium | |
| CN112667711B (en) | MySQL read-only instance management method, system and computer readable medium | |
| CN113220506A (en) | Data processing method and device for terminal equipment | |
| CN111385613A (en) | Television system repairing method, storage medium and application server | |
| CN105338058A (en) | Application updating method and device | |
| CN103914339A (en) | Server management system and server management method | |
| CN106453455A (en) | Audio file synchronization method and audio file synchronization 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20200825 Termination date: 20210614 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |