High availability method and system for improving the utility of physical servers in cloud computing resource pool

• US 9,760,454 B2
• Filed: 08/27/2013
• Issued: 09/12/2017
• Est. Priority Date: 12/14/2012
• Status: Active Grant

• Current Assignee: ZTE Corporation
• Original Assignee: ZTE Corporation
• Inventors: Bu, Jixian
• Primary Examiner(s): Leibovich, Yair
• Application Number:
  US14/442,787
• Publication Number:
  US 20150293823A1
• Time in Patent Office: 1,477 Days
• Field of Search: 714 411
• CPC Class Codes: G06F 11/2033 switching over of hardware resources
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A high availability method and system for improving utilization of physical servers in a cloud computing resource pool, wherein the method includes: when the physical servers in the cloud computing resource pool fail, judging whether idle memory on the normally-running physical servers can support running of virtual machines on all the failed physical servers; when the idle memory on the normally-running physical servers can support the running of the virtual machines on all the failed physical servers, restarting the virtual machines on all the failed physical servers on the normally-running physical servers. The embodiments of the present document improve the utilization of memory resource of physical servers.

Claims

1. A high availability (HA) method for improving utilization of physical servers in a cloud computing resource pool, wherein the method comprises:

when the physical servers in the cloud computing resource pool fail, judging whether idle memory of the normally-running physical servers can support running of virtual machines on all the failed physical servers;

when the idle memory of the normally-running physical servers can support the running of the virtual machines on all the failed physical servers, restarting the virtual machines on all the failed physical servers on the normally-running physical servers;

wherein the method further comprises;

when the physical servers in the cloud computing resource pool fail, judging whether the idle memory of the normally-running physical servers can support the running of the virtual machines on all the failed physical servers with reserved memory, and when the idle memory of the normally-running physical servers can support the running of the virtual machines on all the failed physical servers with the reserved memory, restarting the virtual machines on all the failed physical servers on the normally running physical servers with the reserved memory;

when the idle memory of the normally-running physical servers can not support the running of the virtual machines on all the failed physical servers, decreasing the memory occupied by the virtual machines on the normally-running physical servers, and sequentially using the decrease of the memory as the idle memory.

2. The method as claimed in claim 1, wherein said decreasing the memory occupied by the virtual machines on the normally-running physical servers comprises:

decreasing the memory occupied by the virtual machines with a memory retention rate being 0 configured on the normally-running physical servers, and/or, decreasing the memory occupied by the virtual machines with the memory retention rate being less than 1 and greater than 0 configured on the normally-running physical servers.

3. The method as claimed in claim 2, wherein,

said decreasing the memory occupied by the virtual machines with a memory retention rate being 0 configured on the normally-running physical servers comprises:

closing the virtual machines with the memory retention rate being 0 configured on the normally-running physical servers;

said decreasing the memory occupied by the virtual machines with the memory retention rate being less than 1 and greater than 0 configured on the normally-running physical servers comprises;

changing the virtual machines with the memory retention rate being less than 1 and greater than 0 configured on the normally-running physical servers from running with occupying configured memory to running with occupying reserved memory.

4. The method as claimed in claim 3, wherein, the method further comprises:

when the failed physical servers return to normal, running, with the configured memory, the virtual machines not running and configured with the reserved memory being 0 on the physical servers returning to normal; and

/or, transferring the virtual machines running with the reserved memory with the memory retention rate being less than 1 to the physical servers returning to normal, and running the transferred virtual machines with the configured memory.

5. The method as claimed in claim 2, wherein, the method further comprises:

when the failed physical servers return to normal, running, with the configured memory, the virtual machines not running and configured with the reserved memory being 0 on the physical servers returning to normal; and

/or, transferring the virtual machines running with the reserved memory with the memory retention rate being less than 1 to the physical servers returning to normal, and running the transferred virtual machines with the configured memory.

6. A high availability (HA) system for improving utilization of physical servers in a cloud computing resource pool, wherein the system comprises hardware performing instructions stored in a non-transitory computer readable medium which executes steps in following modules:

a judgment module and a virtual machine restarting module, wherein,

the judgment module is configured to;

when the physical servers in the cloud computing resource pool fail, judge whether idle memory of the normally-running physical servers can support running of virtual machines on all the failed physical servers, and inform the virtual machine restarting module of a judgment result;

the virtual machine restarting module is configured to;

when acquiring from the judgment module that the judgment result is that the idle memory of the normally-running physical servers can support the running of the virtual machines on all the failed physical servers, restart the virtual machines on all the failed physical servers on the normally-running physical servers;

wherein, the system further comprises;

the judgment module is configured to;

when the physical servers in the cloud computing resource pool fail, judge whether the idle memory of the normally-running physical servers can support the running of the virtual machines on all the failed physical servers with reserved memory;

the virtual machine restarting module is configured to;

when acquiring from the judgment module that the judgment result is that the idle memory of the normally-running physical servers can support the running of the virtual machines on all the failed physical servers with the reserved memory, restart the virtual machines on all the failed physical servers on the normally-running physical servers with the reserved memory;

the virtual machine restarting module is further configured to;

when acquiring from the judgment module that the judgment result is that the idle memory of the normally-running physical servers can not support the running of the virtual machines on all the failed physical servers, decrease the memory occupied by the virtual machines on the normally-running physical servers, and sequentially use the decrease of the memory as the idle memory.

7. The system as claimed in claim 6, wherein, the virtual machine restarting module being configured to decrease the memory occupied by the virtual machines on the normally-running physical servers, comprises:

the virtual machine restarting module decreasing the memory occupied by the virtual machines with a memory retention rate being 0 configured on the normally-running physical servers, and/or, decreasing the memory occupied by the virtual machines with the memory retention rate being less than 1 and greater than 0 configured on the normally-running physical servers.

8. The system as claimed in claim 7, wherein,

the virtual machine restarting module being configured to decrease the memory occupied by the virtual machines with a memory retention rate being 0 configured on the normally-running physical servers, comprises:

the virtual machine restarting module closing the virtual machines with the memory retention rate being 0 configured on the normally-running physical servers;

the virtual machine restarting module being configured to decrease the memory occupied by the virtual machines with the memory retention rate being less than 1 and greater than 0 configured on the normally-running physical servers, comprises;

the virtual machine restarting module changing the virtual machines with the memory retention rate being less than 1 and greater than 0 configured on the normally-running physical servers from running with occupying configured memory to running with occupying reserved memory.

9. The system as claimed in claim 8, wherein:

the virtual machine restarting module is further configured to;

when the failed physical servers return to normal, run, with the configured memory, the virtual machines not running and configured with the reserved memory being 0 on the physical servers returning to normal; and

/or, transfer the virtual machines running with the reserved memory with the memory retention rate being less than 1 to the physical servers returning to normal, and run the transferred virtual machines with the configured memory.

10. The system as claimed in claim 7, wherein:

the virtual machine restarting module is further configured to;

when the failed physical servers return to normal, run, with the configured memory, the virtual machines not running and configured with the reserved memory being 0 on the physical servers returning to normal; and

/or, transfer the virtual machines running with the reserved memory with the memory retention rate being less than 1 to the physical servers returning to normal, and run the transferred virtual machines with the configured memory.