US10841270B2 - Methods and devices for switching a virtual internet protocol address - Google Patents
Methods and devices for switching a virtual internet protocol address Download PDFInfo
- Publication number
- US10841270B2 US10841270B2 US15/855,938 US201715855938A US10841270B2 US 10841270 B2 US10841270 B2 US 10841270B2 US 201715855938 A US201715855938 A US 201715855938A US 10841270 B2 US10841270 B2 US 10841270B2
- Authority
- US
- United States
- Prior art keywords
- address
- vip address
- master
- vip
- control center
- 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, expires
Links
Images
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
-
- 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/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H04L61/15—
-
- 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/45—Network directories; Name-to-address mapping
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
Definitions
- a floating Internet Protocol (IP) address is a shared virtual IP address used for server switching in a dual-host server backup circumstance.
- IP Internet Protocol
- an application end may not detect the switch of the IP address of the local host server.
- the physical server may declare the floating IP address as using the Address Resolution Protocol (ARP), and provide services via the floating IP address.
- ARP Address Resolution Protocol
- the range the floating IP address may reach is limited by the number of ports of the physical servers, and typically does not go beyond one hundred physical servers.
- a virtual internet protocol (VIP) address used by a physical server is allocated and managed by a virtualization platform.
- VIP virtual internet protocol
- the virtualization platform does not allow for IP floating among Virtual Machines (VMs).
- Cloud network applications or software such as Keepalived and Heartbeat, may only run normally when the host servers have the ability to switch using a floating IP. Therefore, to run these applications or software in a cloud network, their software codes would need to be modified.
- the embodiments of present application provide methods and devices for switching a VIP address.
- the methods and devices may advantageously solve the problem of IP address floating among Virtual Machines (VMs) that cannot be achieved in the existing cloud network, thereby allowing for the running of high availability applications or software in the existing cloud network.
- VMs Virtual Machines
- the present disclosure provides a method for switching a virtual internet protocol (VIP) address.
- the method may include sending to a control center of a VIP address system a first address resolution protocol (ARP) mapping message for mapping a VIP address to a VM address of a virtual machine (VM) of the VIP address system.
- the control center is configured to determine the VM corresponding to the VM address as the master VM using the VIP address.
- the VIP address system may include one or more VMs connected to one or more virtual switches, the one or more VMs and one or more virtual switches being located in one or more hosts that are connected to the control center via a cloud network.
- the method may further include sending a notification message to a VM in the VIP address system. The notification message is from the control center determining the master VM.
- the present disclosure provides a method for switching a virtual internet protocol (VIP) address.
- the method may include receiving, from a virtual switch, a first ARP mapping message for mapping a VIP address to a virtual machine (VM) of a VIP address system using the VIP address.
- the VIP address system may include one or more VMs connected to one or more virtual switches, the one or more VMs and one or more virtual switches being located in one or more hosts.
- the method may further include determining the VM as the master VM based on the first ARP mapping message; and sending a notification message of determining the master VM to a VM in the VIP address system via the virtual switch connected to the VM.
- the present disclosure provides a non-transitory computer readable medium that stores a set of instructions that is executable by at least one processor of a server to cause the server to perform a method for switching a virtual internet protocol (VIP) address.
- the method may include providing for sending to a control center of a VIP address system a first address resolution protocol (ARP) mapping message for mapping a VIP address to a VM address of a virtual machine (VM) of the VIP address system.
- ARP address resolution protocol
- the control center is configured to determine the VM corresponding to the VM address as the master VM using the VIP address.
- the VIP address system may include one or more VMs connected to one or more virtual switches, the one or more VMs and one or more virtual switches being located in one or more hosts connected to the control center via a cloud network.
- the method may further include providing for sending a notification message from the control center determining the master VM to a VM in the VIP address system.
- the present disclosure provides a non-transitory computer readable medium that stores a set of instructions that is executable by at least one processor of a server to cause the server to perform a method for switching a virtual internet protocol (VIP) address.
- the method may include acquiring, from a virtual switch, a first ARP mapping message for mapping a VIP address to a virtual machine (VM) of a VIP address system using the VIP address.
- the VIP address system may include one or more VMs connected to one or more virtual switches, the one or more VMs and one or more virtual switches being located in one or more hosts.
- the method may further include determining, based on the first ARP mapping message, the VM as the master VM; and providing for sending, via the virtual switch, a notification message of determining the master VM to a VM in the VIP address system.
- the present disclosure provides a virtual internet protocol (VIP) address switching apparatus.
- the apparatus may include a first sending unit configured to send to a control center of a VIP address system a first address resolution protocol (ARP) mapping message for mapping a VIP address to a VM address of a virtual machine (VM) of the VIP address system.
- the VIP address system may include one or more VMs connected to one or more virtual switches, the one or more VMs and one or more virtual switches being located in one or more hosts that are connected to the control center via a cloud network.
- VIP address may be used by the control center to determine the VM corresponding to the VM address as the master VM.
- the apparatus may further include a second sending unit configured to send a notification message to a VM in the VIP address system. The notification message is from the control center determining the master VM.
- the present disclosure provides a virtual internet protocol (VIP) address system.
- the system may include a control center, and at least one host connected to the control center via a cloud network, the at least one host being provided with a virtual machine (VM) and a virtual switch connected to the VM.
- the virtual switch is configured to send to the control center an ARP mapping message for mapping a VIP address to a VM address of a VM.
- the control center is configured to receive the ARP mapping message from the virtual switch, determine, based on the ARP mapping message, the VM as the master VM, and send, via the virtual switch, the notification message of determining the master VM to a VM in the VIP address system.
- a virtual switch sends to a control center a first ARP mapping message for mapping a VIP address to a VM address of a VM of a VIP address system.
- This allows the control center to determine a VM corresponding to the VM address as the master VM using the VIP address and the other VMs as backup VMs.
- the control center may return, via a virtual switch, an identifier of the master VM by carrying the identifier in a notification message to a VM connected to the virtual switch, thereby facilitating the forwarding of data associated with the VIP address to the master VM.
- an ARP request can be processed in the VIP address system based on a cloud network, the VIP address floating in the cloud network can be achieved, and VRRR (Virtual Router Redundancy Protocol)-based software with high availability, such as Keepalived and Heartbeat, can be used.
- VRRR Virtual Router Redundancy Protocol
- FIG. 1 is a schematic diagram illustrating an exemplary architecture for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- FIG. 2 is a flow chart of an exemplary method for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- FIG. 3 is a flow chart of an exemplary method for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- FIG. 4 is a schematic diagram illustrating the hardware structure of an exemplary device for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- FIG. 5 is a schematic diagram illustrating the hardware structure of an exemplary device for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- FIG. 6 is a schematic block diagram of an exemplary apparatus for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- FIG. 7 is a schematic block diagram of an exemplary apparatus for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- an IP address in a virtual network can appear unchanged to the outside using a Software Load Balancer scheme.
- VM 1 first virtual machine
- VM 2 second virtual machine
- the Software Load Balancer uses a mapping relationship between a VIP and the IP 1 .
- the Software Load Balancer thus currently presents to the outside that the VIP is the serving IP address.
- API Application Programming Interface
- the mapping relationship can be modified as a mapping relationship between the VIP and the IP 2 such that the standby VM 2 at the back end is switched to be the master VM while the IP address presented to the outside remains the VIP address, unchanged.
- the Software Load Balancer does not perform IP address floating.
- the Software Load Balancer needs to modify the mapping relationship between the VIP and the IP address of a VM so that the IP address presented to the outside can remain unchanged.
- the Software Load Balancer is designed based on a four-layer Transmission Control Protocol (TCP) or User Datagram Protocol (UDP), it is not suitable for two-layer or three-layer network architecture, which limits the use of the Software Load Balancer.
- TCP Transmission Control Protocol
- UDP User Datagram Protocol
- the embodiments of the present disclosure provide methods and devices for switching a VIP address in a cloud network system.
- the methods and devices allow for the connection of a control center with one more host servers associated with one or more VMs and virtual switches via a message transmission channel of the cloud network, thereby constructing a cloud network-based VIP address system.
- a virtual switch sends to the control center a first ARP mapping message received by the VM for mapping a VIP address to a VM address. This allows the control center to determine the VM corresponding to the VM address as the master VM using the VIP address and to determine other VMs as backup VMs.
- the control center returns an identifier of the master VM by carrying the identifier in a notification message sent to each VM in the VIP address system via the virtual switch. This in turn facilitates the forwarding of data associated with the VIP address to the master VM.
- an ARP request can be processed and the IP address floating in the cloud network can be achieved without conducting any control over or amending the relationship between the master and backup VMs.
- the present disclosure solve the problems of existing techniques, such as not performing IP address floating in a cloud network, being only applicable to four- or more-layer network protocols, etc.
- the exemplary server can be a physical or logical server.
- Various functions of the exemplary can also be achieved by cooperation between two or more physical or logical servers that take on different responsibilities.
- Any suitable type of server, and any suitable type and protocol of the communication network between servers, etc., may be used by embodiments of the present disclosure.
- FIG. 1 a schematic diagram illustrating an exemplary architecture for switching a VIP address, consistent with embodiments of the present disclosure.
- the architecture is herein referred to as a VIP address system 100 , which may include: a control center 102 , a message transmission channel 104 based on a cloud network connected to control center 102 , and several hosts or host servers 105 - 107 connected to message transmission channel 104 , wherein each host is provided with a virtual switch (e.g., virtual switch 110 of host 105 ) and a VM (e.g., virtual machine 112 of host 105 ) connected to the virtual switch.
- a virtual switch e.g., virtual switch 110 of host 105
- VM e.g., virtual machine 112 of host 105
- Control center 102 can be a server, and there may be, for example, hundreds of thousands of hosts connected to the message transmission channel.
- FIG. 2 is a flow chart of an exemplary method 200 for switching a VIP address, consistent with embodiments of the present disclosure.
- Method 200 can be performed by a virtual switch, such as virtual switch 110 of FIG. 1 .
- method 200 may include steps 201 and 202 .
- the virtual switch receives a first ARP mapping message for mapping a VIP address to a VM address and sends the first ARP mapping message to a control center (e.g., control center 102 of FIG. 1 ).
- the control center determines a VM corresponding to the VM address as the master VM using the VIP address.
- a certain VM can send, when using a VIP address, an ARP request to a virtual switch connected to the VM.
- the virtual switch receives the ARP request, and sends to a control center an ARP mapping message for mapping the VIP address to the VM.
- the ARP mapping message may carry an identifier of a host where the VM is located, such as an IP address of the host.
- the ARP mapping message may also carry the IP address of the VM, and may further carry the VIP address currently used by the VM.
- the control center determines the VM currently using the VIP address as the master VM for processing the ARP request. Then, the control center records an identifier of the VM currently using the VIP address, such as the IP address of the VM and the IP address of the host where the VM is located.
- one or more virtual switches send a notification message from the control center determining the master VM to their corresponding VMs in the VIP address system such that data associated with the VIP address is forwarded to the master VM.
- the virtual switches each can send to their corresponding VMs a notification message from the control center for indicating an identifier of the master VM currently using the VIP address. Accordingly, after receiving the notification message, each VM may determine whether the identifier in the notification message is consistent with its own identifier. If the identifier in the notification message is consistent with its own identifier, the VM determines that it is the master VM, and thus can use the VIP address for communication, and may process the received data associated with the VIP address, such as the ARP request.
- the VM determines that it is not the master VM, but a backup VM, and thus can release network resources occupied thereby and may not use the VIP address for communication. In such instances, the network resources can be allocated to and used by the master VM, thereby improving the running efficiency of the master VM and/or increasing the availability of the cloud network.
- the control center does not deliver the notification message after recording an identifier of a VM currently using the VIP address.
- Each VM autonomously sends, when needed or at a set time interval, a message acquisition request to the control center to request to obtain an identifier of the VM currently using the VIP address, thereby pulling the information about the master VM.
- a virtual switch corresponding to a VM may send to the control center a request message sent by the VM for acquiring the identifier of the master VM. Subsequently, the virtual switch can receive a response message returned by the control center and carrying the identifier of the master VM.
- the virtual switch then may send the response message to the VM, so that the VM determines whether it is the master VM itself based on the master VM identifier. Accordingly, the consumption of network resources can be reduced. The use of network resources caused by the control center delivering the notification message while the VM runs abnormally and cannot receive the notification message can be reduced or avoided.
- only the VM that is determined by the control center as the master VM is responsible for using the VIP address for communication with an external device, such as receiving data associated with the VIP address, and responding to the ARP request. All data associated with the VIP address can be forwarded to the master VM for processing.
- a VM When a VM determines that it is not the master VM itself, it can acquire an association relationship between its identifier and a priority level to become the master VM, and thus can determine its priority for becoming the master VM.
- a backup VM with the highest priority can monitor the health condition of the master VM, and switch its address to the VIP address when the master VM is detected to be abnormal, so as to facilitate or maintain normal communication.
- a backup VM having a lower priority level can stay in an idle or substantially idle state, and can release network resources occupied for the master VM to use, thereby improving and/or maintaining the running efficiency of the master VM.
- each VM has a priority level that indicates the order of each VM, when serving as a backup VM, to become the master VM.
- the priority level can be determined based on various factors, such as the configuration of a VM and the configuration of a host where the VM is located.
- the association relationship between the identifier of a VM and its priority level can be stored in the control center, or in the corresponding host.
- the process for acquiring a priority level may include: the virtual switch sending to the control center a request message sent by a backup VM for acquiring the association relationship; the virtual switch receiving the association relationship returned by the control center; and the virtual switch sending the association relationship to the backup VM such that the backup VM can determine its own priority level and/or order to become the master VM based on the association relationship.
- the backup VM that determines its priority level to be the highest may detect the health condition of the master VM at a set time interval. For example, the backup VM with the highest priority level can detect whether the master VM is abnormal, and can switch its IP address to the VIP address to maintain normal communication when the master VM is detected to be abnormal, such as when the master VM fails, when the host where the master VM is located fails, and at time of network failure.
- the backup VM with the highest priority when the master VM is determined to be abnormal, sends a second ARP request to the virtual switch after executing the VIP address switch.
- packet loss may occur such that the virtual switch may not receive the second ARP request, and thus does not know that the backup VM has switched to the VIP address. Therefore, the virtual switch cannot second the second ARP request to the control center, and the control center cannot update in time the recorded information of the master VM currently using the VIP address, which may in turn affect the real-time performance of the IP address floating.
- the virtual switch can regularly inspect the condition of a VM using the VIP address.
- the virtual switch can determine that an IP address switching has occurred, and that the VM has switched to the VIP address. If the last inspection result is that the VIP address was being used, while the present inspection result is that the VIP address is not being used, the virtual switch can determine that an IP address switch occurred, and the VIP address has been switched to another VM. In both circumstances, the virtual switch may send a message regarding the switch to the control center in the form of an ARP mapping message so that the control center can update in time the stored identifier of the master VM, i.e., the IP address of the host where the master VM is located and the IP address of the master VM. The virtual switch can also receive a heartbeat message sent by a VM to determine whether a VIP address switch has occurred, and to determine whether to send an ARP mapping message to the control center.
- a second ARP request is sent by the backup VM to the virtual switch connected thereto.
- the virtual switch sends to the control center a second ARP mapping message for mapping the VIP address to the backup VM, the second ARP mapping message carrying the IP address of the host where the backup VM is located, the IP address of the VM, and the VIP address.
- the control center receives the second ARP mapping message, determines the corresponding backup VM as the master VM, and records an identifier of the new master VM.
- the virtual switch may each send to its corresponding VM a notification message from the control center that indicates the identifier of the master VM currently using the VIP address.
- the original master VM that was abnormal can become a backup VM as well because it does not use the VIP address any more. Therefore, the control center determines the VM currently using the VIP address as the master VM.
- the virtual switch sends to the control center a first ARP mapping message received by a VM for mapping a VIP address to a VM address.
- This allows the control center to determine the VM corresponding to the VM address as the master VM using the VIP address and to determine other VMs as backup VMs.
- the control center returns an identifier of the master VM by carrying the identifier in a notification message sent to each VM in the VIP address system via the virtual switch. This in turn facilitates the forwarding of data associated with the VIP address to the master VM.
- an ARP request can be processed and IP-address floating in the cloud network can be achieved without conducting any control over or amending the relationship between the master and backup VMs, thereby allowing for the convenient use of software with high availability, such as Keepalived and Heartbeat.
- the message transmission channel based on a cloud network can be connected to hundreds of thousands of hosts, which advantageously expands the range the floating VIP address can reach, comparing to about one hundred hosts connected in a physical network due to the limited number of ports.
- FIG. 3 is a flow chart of an exemplary method 300 for switching a virtual internet protocol address, consistent with embodiments of the present disclosure.
- Method 300 can be performed by a control center, such as control center 102 of FIG. 1 .
- Method 300 may include steps 301 - 303 .
- step 301 the control center receives from a virtual switch a first ARP mapping message for mapping a VIP address to a VM using the VIP address.
- the VM using the VIP address may send to a control center a first ARP mapping message via a virtual switch connected thereto, the first ARP mapping message carrying the IP address of a host where the VM is located, the IP address of the VM, and the VIP address.
- step 302 the control center determines the VM as the master VM based on the first ARP mapping message.
- a VM corresponding to the first ARP mapping message received by the control center is the VM currently using the VIP address.
- the control center records the IP address of the host and the IP address of the VM in the first ARP mapping message, and determines the VM currently using the VIP address as the master VM. Accordingly, other VMs in the VIP address system, i.e., VMs currently not using the VIP address, are backup VMs.
- step 303 the control center sends a notification message determining the master VM to one or more VMs in the VIP address system via one or more virtual switches connected thereto such that data associated with the VIP address is forwarded to the master VM.
- the control center may deliver to each VM a notification message for identifying an identifier of the master VM currently using the VIP address, and each VM may also actively acquire the identifier of the master VM from the control center.
- control center can also determine the priority level of each VM to become the master VM based on the configuration of each VM, and may store an association relationship between the priority level and the identifier of each VM. In this way, a VM, such as a backup VM, can acquire the association relationship from the control center, and thus acquire its own priority level and determine whether to monitor the health condition of the master VM.
- the control center when the master VM is determined to be abnormal, the control center allows the VIP address to remain unchanged during a disaster recovery switch process by determining a new master VM, achieving IP address floating in the cloud network, thereby improving the high availability of the VIP address system, and allowing for convenient use of common high availability software, such as Keepalived and Heartbeat, without the need to modify codes of such software.
- the use of an ARP protocol in embodiments of the present disclosure is applicable to two- and more-layer network architectures.
- the embodiments of the present disclosure also provide exemplary apparatuses and devices for switching a VIP address.
- the exemplary apparatuses and devices may implement the exemplary methods described above.
- the structures of the exemplary apparatuses and devices are described and illustrated below with reference to FIGS. 4-7 .
- a control center may implement VIP address switching methods or apparatuses consistent with the present disclosure.
- Apparatus embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware.
- an apparatus may be a logical module of computer program instructions stored in a non-volatile computer-readable storage medium, read into a memory, and executed by a processor of a device.
- FIG. 4 is a schematic diagram illustrating the hardware structure of an exemplary device 400 for switching a VIP address, consistent with embodiments of the present disclosure.
- device 400 for switching a VIP address may include a processor 410 , a memory 420 , a network interface 430 , and a non-volatile computer-readable storage medium 450 .
- An exemplary VIP address switching apparatus 440 implemented by a control center may be a logical module of computer program instructions that are stored in non-volatile computer-readable storage medium 450 , read into memory 420 , and executed by processor 410 of device 400 .
- Device 400 where the apparatus 440 is located can further include other hardware components that perform other functions of device 400 not shown in FIG. 4 .
- a server may implement VIP address switching methods or apparatuses consistent with the present disclosure.
- Apparatus embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware.
- an apparatus may be a logical module of computer program instructions stored in a non-volatile computer-readable storage medium, read into a memory, and executed by a processor of a device.
- FIG. 5 is a schematic diagram illustrating the hardware structure of an exemplary device 500 for switching a VIP address, consistent with embodiments of the present disclosure.
- device 500 for switching a VIP address may include a processor 510 , a memory 520 , a network interface 530 , and a non-volatile computer-readable storage medium 540 .
- An exemplary VIP address switching apparatus 540 implemented by a server may be a logical module of computer program instructions that are stored in non-volatile computer-readable storage medium 550 , read into memory 520 , and executed by processor 510 of device 500 .
- Device 500 where the apparatus 540 is located can further include other hardware components that perform other functions of device 500 not shown in FIG. 5 .
- FIG. 6 is a schematic block diagram of an exemplary apparatus 600 for switching a VIP address, consistent with embodiments of the present disclosure.
- the exemplary apparatus can be implemented in a VIP address system.
- the VIP address system may include a control center and several hosts connected to the control center via a cloud network. Each host can be provided with a VM and a virtual switch connected to the VM.
- Apparatus 600 can be implemented using one or more modules/units (and any corresponding sub-modules/sub-units), which can be a packaged functional hardware unit designed for use with other components (e.g., portions of an integrated circuit) and/or a part of a program (stored on a computer readable medium, e.g.
- the one or more modules can have entry and exit points and can be written in a programming language, such as, for example, Java, Lua, C, or C++.
- a software module can be compiled and linked into an executable program, installed in a dynamic link library, or written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules can be callable from other modules or from themselves, and/or can be invoked in response to detected events or interrupts.
- Software modules configured for execution on computing devices can be provided on a non-transitory computer readable medium, such as a compact disc, digital video disc, RAM, ROM, flash drive, or any other non-transitory medium, or as a digital download (and can be originally stored in a compressed or installable format that requires installation, decompression, or decryption prior to execution).
- Software code can be stored, partially or fully, on a memory device of the executing computing device, for execution by apparatus 600 .
- Software instructions can be embedded in firmware, such as an EPROM.
- hardware modules can be comprised of connected logic units, such as gates and flip-flops, and/or can be comprised of programmable units, such as programmable gate arrays or processors.
- apparatus 600 may include a first sending unit 610 and a second sending unit 620 .
- the first sending unit 610 is configured to send to the control center a first ARP mapping message received from a VM for mapping a VIP address to a VM address. This allows the control center to determine the VM corresponding to the VM address as the master VM using the VIP address.
- the second sending unit 620 is configured to send a notification message from the control center determining the master VM to a VM in the VIP address system such that data associated with the VIP address is forwarded to the master VM.
- the second sending unit 620 may include a first receiving sub-unit.
- the first receiving sub-unit is configured to receive a notification message, sent by the control center, for indicating an identifier of the master VM currently using the VIP address.
- the second sending unit 620 may further include a first sending sub-unit configured to send the notification message to a VM in the VIP address system such that data associated with the VIP address can be forwarded to the master VM.
- apparatus 600 may further include a first receiving unit.
- the first receiving unit is configured to receive, when the master VM is determined to be abnormal, a second ARP mapping message for mapping the VIP address to the address of one backup VM (different from the master VM) sent by the backup VM after the backup VM switches its IF address to the VIP address.
- apparatus 600 may further include a third sending unit configured to send the second ARP mapping message to the control center such that the control center can determine that the backup VM as the new master VM.
- apparatus 600 may further include a fourth sending unit configured to send to the control center a request message, sent by a VM, for acquiring the master VM identifier, a second receiving unit configured to receive a response message returned by the control center, carrying the master VM identifier, and a first replying unit configured to send the response message to the VM such that the VM determines whether itself is the master VM based on the master VM identifier.
- a fourth sending unit configured to send to the control center a request message, sent by a VM, for acquiring the master VM identifier
- a second receiving unit configured to receive a response message returned by the control center, carrying the master VM identifier
- a first replying unit configured to send the response message to the VM such that the VM determines whether itself is the master VM based on the master VM identifier.
- apparatus 600 may further include a fifth sending unit configured to send to the control center a request message, sent by a backup VM, for acquiring an association relationship; a third receiving unit configured to receive the association relationship returned by the control center, indicating the priority level of the backup VM to become the master VM and the identifier of the backup VM; and a sixth sending unit configured to send the association relationship to the backup VM for the backup VM determines its own priority level to become the master VM.
- a fifth sending unit configured to send to the control center a request message, sent by a backup VM, for acquiring an association relationship
- a third receiving unit configured to receive the association relationship returned by the control center, indicating the priority level of the backup VM to become the master VM and the identifier of the backup VM
- a sixth sending unit configured to send the association relationship to the backup VM for the backup VM determines its own priority level to become the master VM.
- sixth sending unit is further configured to: detect, at a set time interval, whether the master VM is abnormal when the priority level of the backup VM to become the master VM is the highest; and release occupied network resources when the priority level of the backup VM to become the master VM is not the highest.
- apparatus 600 may further include a fourth receiving unit configured to receive a heartbeat message sent by a VM; and a first determining unit configured to determine, based on the heartbeat message, whether the VIP address has switched and whether to send a second ARP mapping message to the control center.
- FIG. 7 is a schematic block diagram of an exemplary apparatus 700 for switching a VIP address, consistent with embodiments of the present disclosure.
- the exemplary apparatus can be implemented in a VIP address system.
- the VIP address system may include a control center and several hosts connected to the control center via a cloud network, with each host being provided with a VM and a virtual switch connected to the VM.
- Apparatus 700 may include one or more components of apparatus 600 as described above with reference to FIG. 6 .
- Apparatus may 700 also include a fifth receiving unit 710 , a second determining unit 720 , and a seventh sending unit 740 .
- Fifth receiving unit 710 is configured to receive, from a virtual switch, an ARP mapping message for mapping a VIP address to a VM using the VIP address.
- Second determining unit 720 is configured to determine, based on the ARP mapping message, the VM as the master VM.
- Seventh sending unit 740 is configured to send, via the virtual switch, a notification message determining the master VM to a VM in the VIP address system such that data associated with the VIP address is forwarded to the master VM.
- apparatus 700 may further include a sixth receiving unit configured to receive a request message from a VM, sent via the virtual switch, for acquiring the master VM identifier, and a second replying unit configured to send to the VM, via the virtual switch, a response message carrying the identifier of the master VM currently using the VIP address based on the request message.
- a sixth receiving unit configured to receive a request message from a VM, sent via the virtual switch, for acquiring the master VM identifier
- a second replying unit configured to send to the VM, via the virtual switch, a response message carrying the identifier of the master VM currently using the VIP address based on the request message.
- apparatus 700 may further include a third determining unit configured to determine the priority level of each VM to become the master VM based on the configuration of each VM in the VIP address; and a storing unit configured to store an association relationship between a priority level and an identifier of each VM.
- apparatus 700 may further include a seventh receiving unit configured to receive a request message for acquiring the association relationship from a backup VM sent via the virtual switch, and a third replying unit configured to send the association relationship to the backup VM via the virtual switch.
- an exemplary VIP address system 100 may implement the exemplary methods described above.
- an exemplary VIP address system 100 consistent with the present application includes a control center 102 , at least one host (e.g., hosts 105 - 107 ) connected to the control center via a cloud network, with the host being provided with a VM (e.g., VM 112 ) and a virtual switch (e.g., virtual switch 110 ) connected to the VM.
- the virtual switch is configured to send to control center 102 an ARP mapping message for mapping a VIP address to a VM address received from the VM such that control center 102 can determine a VM corresponding to the VM address as the master VM using the VIP address.
- the virtual switch is further configured to send a notification message determining the master VM from control center 102 to a VM in the VIP address system such that data associated with the VIP address is forwarded to the master VM.
- Control center is configured to receive the ARP mapping message from the virtual switch. Based on the ARP mapping message, control center 102 is further configured to determine the VM as the master. VM and send the notification message of determining the master VM to a VM via the virtual switch.
- modules or units are described as separated components may or may not be physically separated from each other.
- the exemplary units may or may not be physical units, and may be positioned at one location or may be distributed over multiple networks.
- One or more of the modules or units may be selected according to practical requirements to achieve the objectives of the solutions of the present disclosure. Similar solutions implemented consistent with embodiments of the present disclosure can also be used.
- a control center determines, based on an ARP mapping message sent by a VM via a cloud network, a VM currently using a VIP address as the master VM; and a backup VM automatically switches to the VIP address when the master VM is detected to be abnormal.
- the VIP address floating in the cloud network can be achieved, and VRRR-based software with high availability, such as Keepalived and Heartbeat, can be used.
- the message transmission channel based on a cloud network can be connected to hundreds of thousands of hosts, which expands the range of the VIP address floating. This is advantageous over a physical network where about one hundred hosts can be connected in the physical network due to the limited number of ports.
- the present disclosure may be described in a general context of computer-executable commands or operations, such as a program module, stored on a computer readable medium and executed by a computing device or a computing system, including at least one of a microprocessor, a processor, a central processing unit (CPU), a graphical processing unit (GPU), etc.
- the program module may include routines, procedures, objects, components, data structures, processors, memories, and the like for performing specific tasks or implementing a sequence of steps or operations.
- the present disclosure may also be implemented in a distributed computing environment, and in these distributed computing environments, tasks or operations may be executed by a remote processing device connected through a communication network, e.g., the Internet.
- the program module may be located in a local or a remote non-transitory computer-readable storage medium, including a flash disk or other forms of flash memory, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, a cache, a register, etc.
- Embodiments of the present disclosure may be embodied as a method, a system, a computer program product, etc. Accordingly, embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware for allowing a specialized device having the described specialized components to perform the functions described above. Furthermore, embodiments of the present disclosure may take the form of a computer program product embodied in one or more computer-readable storage media that may be used for storing computer-readable program codes.
- Embodiments of the present disclosure are described with reference to flow charts and/or block diagrams of methods, devices (systems), and computer program products. It will be understood that each flow chart and/or block diagram can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a special-purpose computer, an embedded processor, or other programmable data processing devices or systems to produce a machine or a platform, such that the instructions, when executed via the processor of the computer or other programmable data processing devices, implement the functions and/or steps specified in one or more flow charts and/or one or more block diagrams.
- the computer-readable storage medium may refer to any type of non-transitory memory on which information or data readable by a processor may be stored.
- a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein.
- the computer-readable medium includes non-volatile and volatile media, removable and non-removable media.
- the information and/or data storage can be implemented with any method or technology.
- Information and/or data may be modules of computer-readable instructions, data structures, and programs, or other types of data.
- Examples of a computer-readable storage medium include, but are not limited to, a phase-change random access memory (PRAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), other types of random access memories (RAMs), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory or other memory technologies, a cache, a register, a compact disc read-only memory (CD-ROM), a digital versatile disc (DVD) or other optical storage, a cassette tape, tape or disk storage, or other magnetic storage devices, or any other non-transitory media that may be used to store information capable of being accessed by a computer device.
- PRAM phase-change random access memory
- SRAM static random access memory
- DRAM dynamic random access memory
- RAMs random access memories
- ROM read-only memory
- EEPROM electrically erasable programmable read-only memory
- flash memory or other memory technologies
- a cache a register
- CD-ROM compact
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (34)
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611238096.0 | 2016-12-28 | ||
| CN201611238096 | 2016-12-28 | ||
| CN201611238096.0A CN108259629B (en) | 2016-12-28 | 2016-12-28 | Method and device for switching virtual Internet protocol addresses |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| US20180183750A1 US20180183750A1 (en) | 2018-06-28 |
| US10841270B2 true US10841270B2 (en) | 2020-11-17 |
Family
ID=62630333
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US15/855,938 Active 2038-07-03 US10841270B2 (en) | 2016-12-28 | 2017-12-27 | Methods and devices for switching a virtual internet protocol address |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US10841270B2 (en) |
| EP (1) | EP3563525A1 (en) |
| CN (1) | CN108259629B (en) |
| TW (1) | TWI736657B (en) |
| WO (1) | WO2018125924A1 (en) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108259629B (en) | 2016-12-28 | 2021-07-23 | 阿里巴巴集团控股有限公司 | Method and device for switching virtual Internet protocol addresses |
| US10866824B2 (en) * | 2017-01-13 | 2020-12-15 | Citrix Systems, Inc. | Continuous uptime of guest virtual machines during upgrade of a virtualization host device |
| CN110913028B (en) * | 2018-09-14 | 2022-06-14 | 阿里巴巴集团控股有限公司 | Method, device and system for processing virtual address |
| CN112913196B (en) * | 2018-10-30 | 2023-06-06 | 慧与发展有限责任合伙企业 | Software-defined wide area network uplink selection with virtual IP addresses for cloud services |
| CN109446178A (en) * | 2018-11-13 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of Hadoop object storage high availability method, system, device and readable storage medium storing program for executing |
| CN110062057A (en) * | 2018-12-18 | 2019-07-26 | 华为技术有限公司 | The proxy gateway and communication means of message are handled for hot-backup system |
| US10833981B1 (en) * | 2019-06-24 | 2020-11-10 | Allot Ltd. | Method, device, and system for providing hot reservation for in-line deployed network functions with multiple network interfaces |
| US11323310B2 (en) | 2019-06-24 | 2022-05-03 | Allot Ltd. | Method, device, and system for providing hot reservation for in-line deployed network functions with multiple network interfaces |
| CN112527323A (en) * | 2019-09-17 | 2021-03-19 | 北京国双科技有限公司 | Method and device for installing Ambari and Ambari framework |
| CN111092876B (en) * | 2019-12-12 | 2021-10-01 | 北京首都在线科技股份有限公司 | Multi-host system, electronic device, storage medium, information processing method and apparatus for multi-host system |
| CN111934909B (en) * | 2020-07-13 | 2023-06-13 | 深圳栅格信息技术有限公司 | Main-standby machine IP resource switching method, device, computer equipment and storage medium |
| CN112688917A (en) * | 2020-12-10 | 2021-04-20 | 龙芯中科技术股份有限公司 | Network access method, device, electronic equipment and storage medium |
| US11755433B2 (en) * | 2020-12-22 | 2023-09-12 | EMC IP Holding Company LLC | Method and system for health rank based virtual machine restoration using a conformal framework |
| CN114629816B (en) * | 2022-03-14 | 2023-11-03 | 京东科技信息技术有限公司 | Public network IP network state detection method and system |
| CN115145684B (en) * | 2022-06-22 | 2025-09-12 | 国网山东省电力公司电力科学研究院 | A data measurement and control device, method and computer equipment for an integrated energy system |
| CN116346713B (en) * | 2023-02-20 | 2025-12-05 | 阿里巴巴(中国)有限公司 | Cross-AZ device switching systems, methods, storage media, and software products |
| CN117857315A (en) * | 2023-12-22 | 2024-04-09 | 曙光云计算集团股份有限公司 | Node switching method, device, computer equipment, storage medium and product |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050265230A1 (en) | 2004-06-01 | 2005-12-01 | Samsung Electronics Co., Ltd. | Apparatus and method for performing state transition of backup router in router redundancy system |
| CN1855916A (en) | 2005-04-20 | 2006-11-01 | 大唐移动通信设备有限公司 | Method and system for realizing virtual IP protocol |
| CN101635648A (en) | 2009-08-05 | 2010-01-27 | 中兴通讯股份有限公司 | Method for managing and rapidly switching virtual redundant route protocol group |
| US7881208B1 (en) | 2001-06-18 | 2011-02-01 | Cisco Technology, Inc. | Gateway load balancing protocol |
| US20130159487A1 (en) * | 2011-12-14 | 2013-06-20 | Microsoft Corporation | Migration of Virtual IP Addresses in a Failover Cluster |
| US20130195487A1 (en) | 2012-01-27 | 2013-08-01 | Takeshi Yamashita | Color image forming apparatus |
| US20130198352A1 (en) * | 2012-01-31 | 2013-08-01 | International Business Machines Corporation | Interconnecting data centers for migration of virtual machines |
| US20130297596A1 (en) | 2012-05-01 | 2013-11-07 | Everbridge, Inc. | Systems and methods for distance and performance based load balancing |
| US20140344424A1 (en) * | 2013-05-16 | 2014-11-20 | Fujitsu Limited | System, method and computer-readable medium |
| CN104320282A (en) | 2014-10-31 | 2015-01-28 | 杭州华三通信技术有限公司 | Method for switching of main and standby virtual machines in virtual edge port aggregation system and physical mainframes |
| US8958420B1 (en) * | 2012-03-30 | 2015-02-17 | Juniper Networks, Inc. | Methods and apparatus for virtualizing switch control plane engine |
| US20150195137A1 (en) * | 2014-01-06 | 2015-07-09 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Virtual group policy based filtering within an overlay network |
| US9325602B2 (en) | 2013-06-24 | 2016-04-26 | Disney Enterprises, Inc. | Low-risk deployment of web services |
| US20160323427A1 (en) * | 2014-01-22 | 2016-11-03 | Shanghai Jiao Tong University | A dual-machine hot standby disaster tolerance system and method for network services in virtualilzed environment |
| US20170054654A1 (en) * | 2015-08-18 | 2017-02-23 | Microsoft Technology Licensing, Llc | Data Center Resource Tracking |
| WO2018125924A1 (en) | 2016-12-28 | 2018-07-05 | Alibaba Group Holding Linited | Methods and devices for switching a virtual internet protocol address |
| US10205701B1 (en) * | 2014-12-16 | 2019-02-12 | Infoblox Inc. | Cloud network automation for IP address and DNS record management |
| US10341233B2 (en) * | 2014-09-30 | 2019-07-02 | Nicira, Inc. | Dynamically adjusting a data compute node group |
| US20190273683A1 (en) * | 2018-03-01 | 2019-09-05 | Nicira, Inc. | Generic communication channel for information exchange between a hypervisor and a virtual machine |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102710457B (en) * | 2012-05-07 | 2015-11-25 | 浙江宇视科技有限公司 | A kind of N+1 backup method of cross-network segment and device |
| CN103647849B (en) * | 2013-12-24 | 2017-02-08 | 华为技术有限公司 | Method and device for migrating businesses and disaster recovery system |
| CN105721630A (en) * | 2016-03-24 | 2016-06-29 | 国云科技股份有限公司 | A method for virtual machines to share host machine IP to provide external network services |
-
2016
- 2016-12-28 CN CN201611238096.0A patent/CN108259629B/en active Active
-
2017
- 2017-08-01 TW TW106125915A patent/TWI736657B/en not_active IP Right Cessation
- 2017-12-27 US US15/855,938 patent/US10841270B2/en active Active
- 2017-12-27 EP EP17886283.5A patent/EP3563525A1/en not_active Withdrawn
- 2017-12-27 WO PCT/US2017/068555 patent/WO2018125924A1/en not_active Ceased
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7881208B1 (en) | 2001-06-18 | 2011-02-01 | Cisco Technology, Inc. | Gateway load balancing protocol |
| US20050265230A1 (en) | 2004-06-01 | 2005-12-01 | Samsung Electronics Co., Ltd. | Apparatus and method for performing state transition of backup router in router redundancy system |
| CN1855916A (en) | 2005-04-20 | 2006-11-01 | 大唐移动通信设备有限公司 | Method and system for realizing virtual IP protocol |
| CN101635648A (en) | 2009-08-05 | 2010-01-27 | 中兴通讯股份有限公司 | Method for managing and rapidly switching virtual redundant route protocol group |
| US20130159487A1 (en) * | 2011-12-14 | 2013-06-20 | Microsoft Corporation | Migration of Virtual IP Addresses in a Failover Cluster |
| US20130195487A1 (en) | 2012-01-27 | 2013-08-01 | Takeshi Yamashita | Color image forming apparatus |
| US20130198352A1 (en) * | 2012-01-31 | 2013-08-01 | International Business Machines Corporation | Interconnecting data centers for migration of virtual machines |
| US8958420B1 (en) * | 2012-03-30 | 2015-02-17 | Juniper Networks, Inc. | Methods and apparatus for virtualizing switch control plane engine |
| US20130297596A1 (en) | 2012-05-01 | 2013-11-07 | Everbridge, Inc. | Systems and methods for distance and performance based load balancing |
| US20140344424A1 (en) * | 2013-05-16 | 2014-11-20 | Fujitsu Limited | System, method and computer-readable medium |
| US9325602B2 (en) | 2013-06-24 | 2016-04-26 | Disney Enterprises, Inc. | Low-risk deployment of web services |
| US20150195137A1 (en) * | 2014-01-06 | 2015-07-09 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Virtual group policy based filtering within an overlay network |
| US20160323427A1 (en) * | 2014-01-22 | 2016-11-03 | Shanghai Jiao Tong University | A dual-machine hot standby disaster tolerance system and method for network services in virtualilzed environment |
| US10341233B2 (en) * | 2014-09-30 | 2019-07-02 | Nicira, Inc. | Dynamically adjusting a data compute node group |
| CN104320282A (en) | 2014-10-31 | 2015-01-28 | 杭州华三通信技术有限公司 | Method for switching of main and standby virtual machines in virtual edge port aggregation system and physical mainframes |
| US10205701B1 (en) * | 2014-12-16 | 2019-02-12 | Infoblox Inc. | Cloud network automation for IP address and DNS record management |
| US20170054654A1 (en) * | 2015-08-18 | 2017-02-23 | Microsoft Technology Licensing, Llc | Data Center Resource Tracking |
| WO2018125924A1 (en) | 2016-12-28 | 2018-07-05 | Alibaba Group Holding Linited | Methods and devices for switching a virtual internet protocol address |
| US20190273683A1 (en) * | 2018-03-01 | 2019-09-05 | Nicira, Inc. | Generic communication channel for information exchange between a hypervisor and a virtual machine |
Non-Patent Citations (5)
| Title |
|---|
| Extended European Search Report dated Sep. 25, 2019, issued in EP Application No. 17886283.5 (9 pages). |
| First Chinese Office Action issued in Chinese Application No. 201611238096.0 dated Aug. 27, 2020, 10 pages. |
| Liran Sidki et al., "Fault Tolerant Mechanisms for SDN Controllers," 2016 IEEE Conference on Network Function Virtualization and Software Defined Networks (NFV-SDN), Palo Alto, CA, 2016, pp. 173-178. doi: 10.1109/NFV-SDN.2016.7919494. |
| PCT International Search Report and Written Opinion issued in International Application No. PCT/US17/68555, dated Mar. 19, 2018 (17 pages). |
| Qian, Hangwei et al., "Mega Data Center for Elastic Internet Applications," 2014 IEEE International Parallel & Distributed Processing Symposium Workshops, Phoenix, AZ, 2014, pp. 868-874. doi: 10.1109/IPDPSW.2014.99. |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108259629B (en) | 2021-07-23 |
| TW201824823A (en) | 2018-07-01 |
| CN108259629A (en) | 2018-07-06 |
| TWI736657B (en) | 2021-08-21 |
| WO2018125924A1 (en) | 2018-07-05 |
| US20180183750A1 (en) | 2018-06-28 |
| EP3563525A4 (en) | 2019-11-06 |
| EP3563525A1 (en) | 2019-11-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10841270B2 (en) | Methods and devices for switching a virtual internet protocol address | |
| US11216220B2 (en) | Resolving failed or hanging mount points in a clustered storage solution for containers | |
| US10860367B2 (en) | Opportunistic virtual machine migration | |
| US10826812B2 (en) | Multiple quorum witness | |
| US9575785B2 (en) | Cluster system and method for providing service availability in cluster system | |
| CN109788068B (en) | Heartbeat state information reporting method, device and equipment and computer storage medium | |
| US10860375B1 (en) | Singleton coordination in an actor-based system | |
| US9367414B2 (en) | Persisting high availability protection state for virtual machines stored on distributed object-based storage | |
| US10402100B2 (en) | Techniques for path optimization in storage networks | |
| US10120779B1 (en) | Debugging of hosted computer programs | |
| CN106656580B (en) | Service state migration method and device | |
| US8990608B1 (en) | Failover of applications between isolated user space instances on a single instance of an operating system | |
| CN112052230A (en) | Multi-machine room data synchronization method, computing equipment and storage medium | |
| US11544148B2 (en) | Preserving error context during a reboot of a computing device | |
| US10645163B2 (en) | Site-aware cluster management | |
| JP2016513309A (en) | Control of error propagation due to faults in computing nodes of distributed computing systems | |
| CN108810183B (en) | Method and device for processing conflicting MAC addresses and machine-readable storage medium | |
| US9935836B2 (en) | Exclusive IP zone support systems and method | |
| WO2017197982A1 (en) | Packet processing method, device and system, and computer storage medium | |
| US9348672B1 (en) | Singleton coordination in an actor-based system | |
| US12204931B1 (en) | Systems and methods for process restoration subsequent to an operating system crash | |
| CN114928654A (en) | Node state monitoring method, device, equipment, storage medium and program product | |
| CN118193280A (en) | Data recovery method, device, storage device and storage medium | |
| US12348589B1 (en) | Zero downtime servicing of datapath services in software defined networks | |
| JP7707640B2 (en) | Cluster system, monitoring system, monitoring method, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
| AS | Assignment |
Owner name: ALIBABA GROUP HOLDING LIMITED, CAYMAN ISLANDS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WANG, YINGBIN;GANG, CHENG;SIGNING DATES FROM 20200317 TO 20200603;REEL/FRAME:053298/0379 |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
| STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
| MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |