CN112988335A - High-availability virtualization management system, method and related equipment - Google Patents
High-availability virtualization management system, method and related equipment Download PDFInfo
- Publication number
- CN112988335A CN112988335A CN202110520907.0A CN202110520907A CN112988335A CN 112988335 A CN112988335 A CN 112988335A CN 202110520907 A CN202110520907 A CN 202110520907A CN 112988335 A CN112988335 A CN 112988335A
- Authority
- CN
- China
- Prior art keywords
- node
- physical host
- virtualization management
- master node
- load balancing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention is suitable for the technical field of cloud computing, and provides a high-availability virtualization management system, a high-availability virtualization management method and related equipment, wherein the high-availability virtualization management system comprises a plurality of scattered physical host nodes; each physical host node includes: the load balancing module is used for providing a virtual access address and receiving an access request of a user; the virtualization management platform provides services through an open port; the database module is used for providing data for the virtualization management platform; the load balancing module comprises: the node state monitoring unit is used for dynamically monitoring the heartbeat state of each physical host node to acquire the state information of each physical host node; and the master node selecting unit is used for selecting one active physical host node as a new master node based on a preset selection rule under the condition that the master node in the plurality of physical host nodes fails. The invention realizes the operability of the management platform through the binding of the front-end virtual IP address, the application of the management platform and a 3-layer high-availability system of the distributed database system.
Description
Technical Field
The invention belongs to the technical field of cloud computing, and particularly relates to a high-availability virtualization management system, method and related equipment.
Background
Virtualization is an artificially created virtual computing environment, rather than a physical environment, and typically includes computer-generated versions of hardware, operating systems, and storage devices, etc., by which a single physical computer device or server device may be divided into multiple virtual machines and services provided on the virtual machines. With the development of multi-node virtualization platforms, the requirement of high availability of multiple nodes is gradually increased, and a virtualization management platform running on a multi-node host needs to support a high availability environment, that is, under the condition that a single node fails, the running virtualization management platform can run uninterruptedly.
In the prior art, because a management platform is usually a single-point application or a system only supporting front-end load balancing, due to the particularity of a multi-node virtualization platform, when a single node fails, the load balancing system may still distribute different requests to the failed node, that is, the node failure state cannot be timely fed back to the load balancing system; meanwhile, the load balancing node itself may have a single point of failure.
Disclosure of Invention
The embodiment of the invention provides a high-availability virtualization management system, and aims to solve the problems that in the prior art, due to the failure of a single node of a virtualization cluster, system fault feedback is slow, and load balancing cannot be used.
In a first aspect, an embodiment of the present invention provides a high availability virtualization management system, including a plurality of distributed physical host nodes; each of the physical host nodes includes:
the load balancing module is used for providing a virtual access address and receiving an access request of a user based on the virtual access address;
the virtualization management platform provides services through an open port;
the database module is used for providing data for the virtualization management platform;
the load balancing module comprises:
a node state monitoring unit, configured to dynamically monitor a heartbeat state of each physical host node to obtain state information of each physical host node;
and the master node selecting unit is used for selecting one other active physical host node as a new master node based on a preset selection rule under the condition that the master node in the physical host nodes fails.
Further, the highly available virtualization management system is characterized in that a plurality of the physical host nodes are in the same local area network, a virtual machine is installed on the plurality of the physical host nodes, and the load balancing module is implemented based on LVS and Keepalived and is deployed in the virtual machine.
Further, the high availability virtualization management system is characterized in that the virtualization management platform provides services based on Nginx, the Nginx is deployed in the virtual machine, the virtualization management platform provides web services to the outside through a port and an API opened by the Nginx, and the web services provide services to the outside through the virtual access address.
Further, the high-availability virtualization management system is characterized in that the database module is implemented based on a mariad db database, the database module is deployed in the virtual machine, and a database access address of the virtualization management platform is a logical address of the database module installed in the virtual machine.
Further, the high availability virtualization management system is characterized in that the master node selecting unit includes:
the priority data acquisition subunit is used for acquiring the priority data of all other active physical host nodes under the condition that the main node fails;
and the new main node selection subunit is used for selecting other active physical host nodes with the highest priority as new main nodes under the condition that the main nodes fail.
In a second aspect, an embodiment of the present invention provides a method for handling a failure of a master node of a high-availability virtualization management system, including the following steps:
dynamically monitoring the heartbeat state of each physical host node to acquire the state information of each physical host node;
and if the master node state is the failure state, selecting another active physical host node as a new master node based on a preset selection rule.
Further, the dynamically monitoring the heartbeat status of each physical host node to obtain the status information of each physical host node includes the following steps:
and the load balancing module monitors and detects the network address and the port number of the virtualization management platform through the node state monitoring unit.
Further, the selecting one of the active physical host nodes as a new host node based on a preset selection rule includes the following steps:
the load balancing module acquires the priorities of all other active physical host nodes through a priority data acquisition subunit;
and the new main node selection subunit of the load balancing module selects the active physical host node with the highest priority as a new main node.
In a third aspect, an embodiment of the present invention provides a computer device, including: the system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the computer program to realize the steps of the master node failure processing method of the high availability virtualization management system in any one of the above embodiments.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored, and the computer program, when executed by a processor, implements the steps in the master node failure processing method of the high availability virtualization management system according to any one of the above embodiments.
The invention has the advantages that the operability of the virtualization management platform is realized under the condition that the main node is inactivated, namely the virtualization node is inactivated and/or the database node is inactivated, because the 3-layer high-availability system of the front-end virtual IP address binding load balancing module, the virtualization management platform application and the distributed database module is adopted.
Drawings
FIG. 1 is a block diagram of a highly available virtualization management system according to an embodiment of the present invention;
FIG. 2 is a block diagram of a load balancing module of a highly available virtualization management system according to an embodiment of the present invention;
FIG. 3 is a high availability virtualization management system topology diagram provided by embodiments of the present invention;
FIG. 4 is a network address diagram of a highly available virtualization management system according to an embodiment of the present invention;
fig. 5 is a flowchart of a method for handling a failure of a network master node of a high-availability virtualization management system according to an embodiment of the present invention;
fig. 6 is a flowchart for acquiring status information of each physical host node according to the embodiment of the present invention;
fig. 7 is a flowchart illustrating selecting another active physical host node as a new host node based on a preset selection rule according to an embodiment of the present invention;
fig. 8 is another flowchart of selecting another active physical host node as a new host node based on a preset selection rule in the embodiment of the present invention;
fig. 9 is a schematic computer device diagram illustrating a master node failure handling method of a high availability virtualization management system according to an embodiment of the present invention.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The technical solutions in the embodiments of the present invention will be clearly and completely described with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
Referring to fig. 1, fig. 1 is a structural diagram of a high-availability virtualization management system according to an embodiment of the present invention, as shown in fig. 1, the high-availability virtualization management system includes a load balancing module 101, a virtualization management platform 102, and a database module 103, the high-availability virtualization management system is deployed in a separate physical computer device, the physical computer device has a processor and a memory, and is capable of running a virtual machine software 100, the virtual machine software 100 may be an operating system-based KVM and VMWare work, the computer device is capable of accessing a local area network and obtaining a network address in the local area network through a set or network protocol, and other computer devices are capable of performing network transmission with the computer device through the network address. In the embodiment of the present invention, there are multiple scattered physical computer devices in the highly available virtualization management system, where each physical computer device is referred to as a node, and the load balancing module 101, the virtualization management platform 102, and the database module 103 in the node can independently provide services independent of the modules in other nodes.
In the embodiment of the present invention, the LVS is installed in the virtual machine software 100, and has an independent network address and a hardware address according to the parameters allocated by the virtual machine, and when the LVS is running, the LVS is regarded as an independent service host in a network structure, and the running condition of the LVS is not affected by other modules in the highly available virtualization management system.
Referring to fig. 2, fig. 2 is a diagram of a load balancing module of a high-availability virtualization management system according to an embodiment of the present invention, as shown in fig. 2, the load balancing module is composed of a node state monitoring unit 201 and a master node selecting unit 202, where the master node selecting unit further includes a priority data obtaining subunit 202a and a new master node selecting unit 202 b.
Specifically, the load balancing module may be implemented based on LVS + Keepalived, where Keepalived is software capable of running in an operating system, and is mainly used for implementing connectivity detection and hot standby switching of each part in a network structure through a VRRP network protocol. Specifically, the node status monitoring unit 201 utilizes keepalive connectivity detection feedback mechanism to monitor the active status of the virtualization service platform and the database module, where the detected object includes a network address and a port. Referring to fig. 1, keepalive sends a detection data packet with verification data to the load balancing module 101 of the virtualization management platform 102, the database module 103 and other nodes of the same node within a set time, and if the data returned by the virtualization management platform 102 and the database module 103 do not pass preset verification or do not return a data packet within a preset time, it is determined that the virtualization management platform 102 and the database module 103 are disconnected.
The master node selecting unit 202 may ensure that the standby node can continue to provide the service under the condition that the master node is deactivated based on a keepalive hot standby switching mechanism, where the master node is a node that preferentially provides the service when the high-availability virtualization management system is set. When the node status monitoring unit 201 detects that the virtualization management platform 102 and the database module 103 are disconnected, the priority data obtaining subunit 202a obtains the priority set by keepalive of the load balancing module 101 in the master node, and then the new master node selecting unit 202b selects the node with the highest priority from the other nodes except the master node as a new master node, so that the new master node takes over the function of the master node and continues to provide external services.
In an embodiment of the present invention, the virtualization management platform 102 is installed in the virtual machine software 100, specifically, the virtualization management platform 102 provides a web service to the outside, the web service provides a service to the outside based on Nginx, the Nginx is installed in the virtual machine software 100, a web service address of the Nginx is a logical address where the virtualization management platform 102 is located in the virtual machine, and a port and an API for providing the service are opened to the outside, and the virtualization management platform 102 provides the service through an open port by accessing the API of the Nginx. The virtualization management platform 102 is used in embodiments of the present invention to invoke operations such as virtualization, clustering, and storing data.
The database module 103 may be specifically a database software having an interface, which is executable on an operating system, where the database content is set in an actual demand, specifically, the database is a maria db database, the maria db database is installed in the virtual machine software 100, and the virtualization management platform 102 performs data writing and reading on the maria db database from the virtualization management platform 102 by configuring a database address as a logical address of the maria db database in the virtual machine and by a database operation method.
Referring to fig. 3, fig. 3 is a topology diagram of a high availability virtualization management system according to an embodiment of the present invention, and as shown in fig. 3, an embodiment of the present invention provides a high availability virtualization management system 300 including three nodes, where the three nodes include a main node and two standby nodes, including a main node 301, a first standby node 302, and a second standby node 303, the main node 301 includes a first load balancing module 301a, a first virtualization management platform 301b, and a first database module 301c, the first standby node 302 includes a second load balancing module 302a, a second virtualization management platform 302b, and a second database module 302c, and the main node 301 and the standby nodes are set by parameters of LVS and keepalive. Specifically, the connection conditions of the modules in the main node 301 and the standby node are the same, that is, the load balancing module 301a of the main node 301 and the load balancing module 302a and the load balancing module 303a in the standby node are connected to each other, the load balancing module 101, the virtualization management platform 102 and the database module 103 in each node have independent functions, but are connected to each other through a network address and a port number, and finally, an interaction sequence is a logical sequence relationship of the load balancing module, the virtualization management platform and the database module.
Example two
Referring to fig. 4, fig. 4 is a network address diagram of a high-availability virtualization management system according to an embodiment of the present invention, where a network address of the first load balancing module 301a of the main node 301 is 192.168.100.101, a network address of the second load balancing module 302a of the first standby node 302 is 192.168.100.102, a network address of the third load balancing module 303a of the second standby node 303 is 192.168.100.103, network addresses owned by the virtualization management platforms in the three nodes are 192.168.100.201, 192.168.100.202, and 192.168.100.203, respectively, when LVS and Keepalived parameters of the three nodes are configured, the network address is set to be a virtual network address 304 for external access to a web service, the virtual network address is 192.168.100.100, when the main node 301 configures Keepalived, the state type is master, the priority is 200, and the state types of the first standby node 302 and the second standby node 303 are backup, the priorities are 150 and 100, respectively.
In the state of the highly available virtualized management system network address map as shown in fig. 4, the virtualized management platform can be accessed from the outside through the virtual network address 192.168.100.100 for data management and query, at this time, the first load balancing module 301a of the master node 301 designates the first virtualized management platform 301b as a response object, that is, the first virtualized management platform 301b with the real network address 192.168.100.201 responds to the connection request, and the first database 301c of the master node 301 is a database providing services.
EXAMPLE III
Referring to fig. 4 and fig. 5, fig. 5 is a flowchart of a method for handling a failure of a network master node of a high-availability virtualization management system according to an embodiment of the present invention, where the method includes the following steps:
s401, dynamically monitoring the heartbeat state of each physical host node to acquire the state information of each physical host node;
specifically, referring to fig. 6, fig. 6 is a flowchart of a process for acquiring status information of each physical host node according to an embodiment of the present invention, where the process includes the following steps:
s401a, the load balancing module monitors and detects the network address and port number of the virtualization management platform through the node state monitoring unit.
The node state monitoring unit in each load balancing module continuously sends a check data packet to the virtualization management platform and the database module which are located in the same node, a preset check value exists in each module, each module generates a return data packet based on the preset check value after receiving the check data packet, and the node state monitoring unit updates the overall state information of each physical host node after receiving the return data packet and judges that the node state monitoring unit is in an active state or an inactive state.
S401b, the load balancing module forwards the external request to the virtualization management platform of the real address of the main node for processing.
In the above steps, if the node state monitoring unit determines that the host node 301 is in an active state, according to a normal operation flow, the load balancing module of the host node 301 forwards the external request to the virtualization management platform for processing at the real address of the host node, that is, the first load balancing module 301a in the host node forwards the external request to the first virtualization management platform 301b with a real network address of 192.168.100.202.
On the other hand, if the check value of the returned data packet is in error, or the node status monitoring unit does not receive the returned data packet of one of the modules in one of the host nodes 301, the node status monitoring unit determines that the host node is in an inactive state (failure state).
S402, if the master node state is the failure state, selecting another active physical host node as a new master node based on a preset selection rule.
Specifically, referring to fig. 7, fig. 7 is a flowchart of selecting another active physical host node as a new host node based on a preset selection rule according to an embodiment of the present invention, where the flowchart includes the following steps:
s402a, the main node stops forwarding data to the virtualization management platform.
After the first virtualization management platform 301b and the first database module 301c of the master node 301 are deactivated, the first load balancing module 301a of the master node 301 stops forwarding the request data to the first virtualization management platform 301b, and at this time, the external access request is not rejected.
S402b, the load balancing module obtains the priority of all other active physical host nodes through the priority data obtaining subunit.
The priority data acquiring subunit in each of the physical host nodes acquires the priority of the other physical hosts, and at this time, each of the priority data acquiring subunits has priority data of all the physical host nodes.
S402c, the new master node selecting subunit of the load balancing module selects the active physical host node with the highest priority as the new master node.
The new master node selecting units in the load balancing modules of the three nodes arbitrate among themselves, the active physical host node with the highest priority among all the physical host nodes except the inactivated master node 301 is selected as the new master node, in the priority value setting of the first standby node 302 and the second standby node 303, the value of the first standby node 302 is high, in the current state, the new master node selection subunit will decide that the first standby node 302 assumes the function of the master node 301, respond to the request for the virtual network address, and forwards the access request to the virtualization management platform in the first standby node 302 for processing, that is, the second virtualization management platform 302b with the actual network address of 192.168.100.202 responds to the connection request, and the corresponding second database 302c is the database providing services.
Similarly, the second load balancing module 303a of the second standby node 303 sets the lowest priority value of the three nodes during setting, and when a module in the first master node 301 and the first standby node 302 is inactive in the embodiment of the present invention, the second standby node 303 will become an active node in the same manner, which is similar to the active manner of the first standby node 302 in the embodiment of the present invention and is not described herein again.
Example four
Referring to fig. 4, fig. 5, and fig. 8, fig. 8 is a flowchart illustrating another process of selecting an active physical host node as a new host node based on a preset selection rule according to an embodiment of the present invention, where the process includes the following steps:
s501, integrally inactivating the main node.
Under the above circumstances, the load balancing module in the main node 301 that bears the forwarding function is deactivated, or the main node 301 is wholly deactivated, so that the priority data acquiring subunit and the new main node selecting subunit in the main node 301 cannot work normally, and at this time, the deactivated state of the main node 301 is detected by the node state monitoring unit in the other physical host nodes.
S502, the load balancing module acquires the priorities of all other active physical host nodes through the priority data acquisition subunit.
The priority data acquiring subunit in each of the physical host nodes except the master node 301 acquires the priority of the other physical host nodes except the master node 301, and at this time, each of the priority data acquiring subunits has the priority data of the currently active physical host node.
And S503, the new main node selection subunit of the load balancing module selects the active physical host node with the highest priority as a new main node.
Under the embodiment of the present invention, the new master node selecting sub-unit in the load balancing module of the first standby node 302 and the second standby node 303 arbitrates between the new master node selecting sub-units, selects the active physical host node with the highest priority from all physical host nodes except the inactivated master node 301 as the new master node, in the setting of the priority values of the first standby node 302 and the second standby node 303, the value of the first standby node 302 is higher, in the current state, the new master node selecting sub-unit determines that the first standby node 302 will assume the function of the master node 301, responds to the request of the virtual network address, and forwards the access request to the virtualization management platform in the first standby node 302 for processing, that is, the second virtualization management platform 302b with the actual network address of 192.168.100.202 responds to the connection request, the corresponding second database 302c is a database providing services.
Similarly, the second load balancing module 303a of the second standby node 303 sets the lowest priority value of the three nodes during setting, and in the case that the first master node 301 and the first standby node 302 are wholly inactivated in the embodiment of the present invention, the second standby node 303 will become an active node in the same manner, and the specific manner is similar to the active manner of the first standby node 302 in the embodiment of the present invention, and details thereof are not repeated here.
EXAMPLE five
Referring to fig. 9, fig. 9 is a schematic diagram of a computer device of a method for handling a failure of a master node of a high availability virtualization management system according to an embodiment of the present invention, where the electronic device 600 includes: a memory 602, a processor 601 and a computer program stored on the memory 602 and executable on the processor 601.
The processor 601 calls the computer program stored in the memory 602 to execute the following steps:
dynamically monitoring the heartbeat state of each physical host node to acquire the state information of each physical host node;
and if the master node state in the plurality of physical host nodes is a failure state, selecting one active physical host node as a new master node based on a preset selection rule.
Specifically, the dynamic monitoring of the heartbeat state of each physical host node is implemented by LVS + keepalive, and the function of the node state monitoring unit of the load balancing module in the above embodiment is executed, the preset selection rule is based on the priority level when keepalive is set, and the function of the new host node selection subunit of the load balancing module in the above embodiment is executed, and the specific operation modes of the node state monitoring unit and the new host node selection subunit are the same as those in the above embodiment, and are not described herein again.
It should be noted that, in the foregoing embodiment, parameters such as the actual network address of each part, the port number of the virtualized management platform providing the service, the virtual network address of the load balancing module, and priorities (priorities) of the LVS and the keepalived are not limited to the present invention, and may be selected according to needs when actually used.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.
Claims (10)
1. A highly available virtualization management system comprising a plurality of decentralized physical host nodes; each of the physical host nodes includes:
the load balancing module is used for providing a virtual access address and receiving an access request of a user based on the virtual access address;
the virtualization management platform provides services through an open port;
the database module is used for providing data for the virtualization management platform;
the load balancing module comprises:
a node state monitoring unit, configured to dynamically monitor a heartbeat state of each physical host node to obtain state information of each physical host node;
and the master node selecting unit is used for selecting one other active physical host node as a new master node based on a preset selection rule under the condition that the master node in the physical host nodes fails.
2. The high availability virtualization management system according to claim 1, wherein a plurality of the physical host nodes are in the same local area network, a virtual machine is installed in the plurality of the physical host nodes, and the load balancing module is implemented based on LVS and Keepalived and is deployed in the virtual machine.
3. The highly available virtualization management system of claim 2, wherein the virtualization management platform provides services based on Nginx, the Nginx being deployed in the virtual machine, the virtualization management platform providing web services to the outside through ports and APIs opened by the Nginx, the web services providing services to the outside through the virtual access addresses.
4. The high availability virtualization management system of claim 2 wherein the database module is implemented based on a MariaDB database, the database module being deployed in the virtual machine, the database access address of the virtualization management platform being a logical address of the database module installed in the virtual machine.
5. The highly available virtualization management system of claim 1, wherein the master node selection unit comprises:
the priority data acquisition subunit is used for acquiring the priority data of all other active physical host nodes under the condition that the main node fails;
and the new main node selection subunit is used for selecting other active physical host nodes with the highest priority as new main nodes under the condition that the main nodes fail.
6. A master node failure handling method of a high availability virtualization management system according to claim 1, comprising the steps of:
dynamically monitoring the heartbeat state of each physical host node to acquire the state information of each physical host node;
and if the master node state is the failure state, selecting another active physical host node as a new master node based on a preset selection rule.
7. The master node failure handling method of claim 6, wherein the dynamically monitoring the heartbeat status of each physical host node to obtain status information for each of the physical host nodes comprises the steps of:
and the load balancing module monitors and detects the network address and the port number of the virtualization management platform through the node state monitoring unit.
8. The master node failure handling method of claim 6, wherein the selecting one of the active physical host nodes as a new master node based on a preset selection rule comprises the steps of:
the load balancing module acquires the priorities of all other active physical host nodes through a priority data acquisition subunit;
and the new main node selection subunit of the load balancing module selects the active physical host node with the highest priority as a new main node.
9. A computer device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps in the master node failure handling method of the high availability virtualization management system according to any of claims 6 to 8 when executing the computer program.
10. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the master node failure handling method of the high availability virtualization management system according to any one of claims 6 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110520907.0A CN112988335A (en) | 2021-05-13 | 2021-05-13 | High-availability virtualization management system, method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110520907.0A CN112988335A (en) | 2021-05-13 | 2021-05-13 | High-availability virtualization management system, method and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112988335A true CN112988335A (en) | 2021-06-18 |
Family
ID=76337653
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110520907.0A Pending CN112988335A (en) | 2021-05-13 | 2021-05-13 | High-availability virtualization management system, method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112988335A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114785671A (en) * | 2022-05-18 | 2022-07-22 | 江苏安超云软件有限公司 | Method, system and electronic device for realizing high availability of virtual load balancer |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6061600A (en) * | 1997-05-09 | 2000-05-09 | I/O Control Corporation | Backup control mechanism in a distributed control network |
| CN104539055A (en) * | 2015-01-07 | 2015-04-22 | 山东鲁能智能技术有限公司 | Electric system key equipment actualizing-one-prepared method and system based on network |
| CN104679604A (en) * | 2015-02-12 | 2015-06-03 | 大唐移动通信设备有限公司 | Method and device for switching between master node and standby node |
| CN105224637A (en) * | 2015-09-24 | 2016-01-06 | 珠海许继芝电网自动化有限公司 | A kind of based on PostgreSQL database active and standby/the comprehensive method of cluster application |
| CN107707393A (en) * | 2017-09-26 | 2018-02-16 | 赛尔网络有限公司 | More live systems based on Openstack O version characteristics |
| CN111813620A (en) * | 2020-06-18 | 2020-10-23 | 麒麟软件有限公司 | Cluster monitoring system and cluster state monitoring method |
| CN108200124B (en) * | 2017-12-12 | 2021-02-12 | 武汉烽火众智数字技术有限责任公司 | High-availability application program architecture and construction method |
| CN112596911A (en) * | 2020-12-29 | 2021-04-02 | 恩亿科(北京)数据科技有限公司 | Automatic operation and maintenance method and system for high-availability distributed system |
-
2021
- 2021-05-13 CN CN202110520907.0A patent/CN112988335A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6061600A (en) * | 1997-05-09 | 2000-05-09 | I/O Control Corporation | Backup control mechanism in a distributed control network |
| CN104539055A (en) * | 2015-01-07 | 2015-04-22 | 山东鲁能智能技术有限公司 | Electric system key equipment actualizing-one-prepared method and system based on network |
| CN104679604A (en) * | 2015-02-12 | 2015-06-03 | 大唐移动通信设备有限公司 | Method and device for switching between master node and standby node |
| CN105224637A (en) * | 2015-09-24 | 2016-01-06 | 珠海许继芝电网自动化有限公司 | A kind of based on PostgreSQL database active and standby/the comprehensive method of cluster application |
| CN107707393A (en) * | 2017-09-26 | 2018-02-16 | 赛尔网络有限公司 | More live systems based on Openstack O version characteristics |
| CN108200124B (en) * | 2017-12-12 | 2021-02-12 | 武汉烽火众智数字技术有限责任公司 | High-availability application program architecture and construction method |
| CN111813620A (en) * | 2020-06-18 | 2020-10-23 | 麒麟软件有限公司 | Cluster monitoring system and cluster state monitoring method |
| CN112596911A (en) * | 2020-12-29 | 2021-04-02 | 恩亿科(北京)数据科技有限公司 | Automatic operation and maintenance method and system for high-availability distributed system |
Non-Patent Citations (1)
| Title |
|---|
| 沈平 等: "一例基于LVS+Keepalived架构的服务器访问故障分析", 《电脑知识与技术》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114785671A (en) * | 2022-05-18 | 2022-07-22 | 江苏安超云软件有限公司 | Method, system and electronic device for realizing high availability of virtual load balancer |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11226753B2 (en) | Adaptive namespaces for multipath redundancy in cluster based computing systems | |
| US9760455B2 (en) | PCIe network system with fail-over capability and operation method thereof | |
| US8612561B2 (en) | Virtual network storage system, network storage device and virtual method | |
| US8055933B2 (en) | Dynamic updating of failover policies for increased application availability | |
| CN102355369B (en) | Virtual clustered system as well as processing method and processing device thereof | |
| US7225356B2 (en) | System for managing operational failure occurrences in processing devices | |
| US7925817B2 (en) | Computer system and method for monitoring an access path | |
| US7937617B1 (en) | Automatic clusterwide fail-back | |
| US11206173B2 (en) | High availability on a distributed networking platform | |
| US11669360B2 (en) | Seamless virtual standard switch to virtual distributed switch migration for hyper-converged infrastructure | |
| JP2017084406A (en) | Scheduling for fabric distributed resource | |
| US20050108593A1 (en) | Cluster failover from physical node to virtual node | |
| CN102594861A (en) | Cloud storage system with balanced multi-server load | |
| US11349706B2 (en) | Two-channel-based high-availability | |
| WO2014174594A1 (en) | Storage system and storage system fault administration method | |
| US20120144006A1 (en) | Computer system, control method of computer system, and storage medium on which program is stored | |
| US20190334990A1 (en) | Distributed State Machine for High Availability of Non-Volatile Memory in Cluster Based Computing Systems | |
| JP2008107896A (en) | Physical resource control management system, physical resource control management method and physical resource control management program | |
| EP2740255A1 (en) | Hardware failure mitigation | |
| US11409621B2 (en) | High availability for a shared-memory-based firewall service virtual machine | |
| CN112988335A (en) | High-availability virtualization management system, method and related equipment | |
| US8918670B2 (en) | Active link verification for failover operations in a storage network | |
| US11418382B2 (en) | Method of cooperative active-standby failover between logical routers based on health of attached services | |
| JP2009294828A (en) | Pci switch, virtual tree switching method and pci switch system | |
| US10367711B2 (en) | Protecting virtual computing instances from network failures |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210618 |