Cascading failover of blade servers in a data center

• US 9,122,652 B2
• Filed: 12/17/2012
• Issued: 09/01/2015
• Est. Priority Date: 12/17/2012
• Status: Active Grant

• Current Assignee: Lenovo International Limited (Lenovo Group Ltd.)
• Original Assignee: Lenovo Enterprise Solutions (Singapore) Pte., Ltd. (Lenovo Group Ltd.)
• Inventors: Bennah, Albert D., Rodriguez, Adrian X.
• Primary Examiner(s): Riad, Amine
• Application Number:
  US13/717,031
• Publication Number:
  US 20140173336A1
• Time in Patent Office: 988 Days
• Field of Search: 714/4.1, 714/4.11
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2041 with more than one idle spare processing component
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: G06F 11/3433 for load management allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029
• CPC Class Codes: G06F 2201/81 Threshold

Abstract

Cascading failover of blade servers in a data center that includes transferring by a system management server a data processing workload from a failing blade server to an initial replacement blade server, with the data processing workload characterized by data processing resource requirements and the initial replacement blade server having data processing resources that do not match the data processing resource requirements; and transferring the data processing workload from the initial replacement blade server to a subsequent replacement blade server, where the subsequent replacement blade server has data processing resources that better match the data processing resource requirements than do the data processing resources of the initial replacement blade server, including transferring the workload to the subsequent replacement blade server only if the data processing cost of the transfer of the workload to the subsequent replacement blade is less than the value of a transfer cost threshold.

Claims

1. A method comprising:

transferring a data processing workload from a failing blade server to an initial replacement blade server, the data processing workload characterized by data processing resource requirements, the initial replacement blade server having data processing resources that do not match the data processing resource requirements; and

transferring the data processing workload from the initial replacement blade server to a subsequent replacement blade server, the subsequent replacement blade server having data processing resources that better match the data processing resource requirements than do the data processing resources of the initial replacement blade server, including transferring the workload to the subsequent replacement blade server only if the data processing cost of the transfer of the workload to the subsequent replacement blade is less than the value of a transfer cost threshold;

wherein the data processing workload is executed on a virtual machine on the failing blade server; and

the data processing resource requirements are implemented as virtual machine metadata describing the data processing resource requirements of the virtual machine.

2. The method of claim 1 further comprising determining the value of the transfer cost threshold based upon a cost of an inefficiency of executing the workload on the initial replacement blade server while the initial replacement blade server provides data processing resources that do not match the data processing resource requirements of the workload.

3. The method of claim 1 further comprising determining the cost of the transfer of the workload to the subsequent replacement blade based upon a cost of workload downtime during the transfer, a cost of powering down the initial replacement blade server, a cost of starting execution of the workload on the subsequent replacement blade server.

4. The method of claim 1 further comprising maintaining records indicating which blade servers in the data center are candidates for workload transfer to a subsequent replacement blade server, a candidate being a blade server whose data processing resources do not match the data processing resource requirements of a data processing workload executing on that blade server.

5. The method of claim 1 further comprising monitoring a pool of standby blade servers for availability of replacement blade servers that better match the data processing resource requirements of a data processing workload executing on a candidate.

6. The method of claim 1 further comprising selecting the subsequent replacement blade server from a pool of standby blade servers, the subsequent replacement blade server providing, as among the standby blade servers, the best available match between the data processing resource requirements and the data processing resources of the subsequent replacement blade server.

7. A system management server comprising a computer processor and a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that when executed by the processor cause the system management server to carry out the steps of:

transferring a data processing workload from a failing blade server to an initial replacement blade server, the data processing workload characterized by data processing resource requirements, the initial replacement blade server having data processing resources that do not match the data processing resource requirements; and

transferring the data processing workload from the initial replacement blade server to a subsequent replacement blade server, the subsequent replacement blade server having data processing resources that better match the data processing resource requirements than do the data processing resources of the initial replacement blade server, including transferring the workload to the subsequent replacement blade server only if the data processing cost of the transfer of the workload to the subsequent replacement blade is less than the value of a transfer cost threshold;

wherein the data processing workload is executed on a virtual machine on the failing blade server; and

the data processing resource requirements are implemented as virtual machine metadata describing the data processing resource requirements of the virtual machine.

8. The system management server of claim 7 further comprising computer program instructions that cause the system management server to determine the value of the transfer cost threshold based upon a cost of an inefficiency of executing the workload on the initial replacement blade server while the initial replacement blade server provides data processing resources that do not match the data processing resource requirements of the workload.

9. The system management server of claim 7 further comprising computer program instructions that cause the system management server to determine the cost of the transfer of the workload to the subsequent replacement blade based upon a cost of workload downtime during the transfer, a cost of powering down the initial replacement blade server, a cost of starting execution of the workload on the subsequent replacement blade server.

10. The system management server of claim 7 further comprising computer program instructions that cause the system management server to maintain records indicating which blade servers in the data center are candidates for workload transfer to a subsequent replacement blade server, a candidate being a blade server whose data processing resources do not match the data processing resource requirements of a data processing workload executing on that blade server.

11. The system management server of claim 7 further comprising computer program instructions that cause the system management server to monitor a pool of standby blade servers for availability of replacement blade servers that better match the data processing resource requirements of a data processing workload executing on a candidate.

12. The system management server of claim 7 further comprising computer program instructions that cause the system management server to select the subsequent replacement blade server from a pool of standby blade servers, the subsequent replacement blade server providing, as among the standby blade servers, the best available match between the data processing resource requirements and the data processing resources of the subsequent replacement blade server.

13. A computer program product including a non-transitory computer readable storage recordable medium, the computer program product comprising computer program instructions when executed by a computer processor cause a system management server of the data center to carry out the steps of:

transferring a data processing workload from a failing blade server to an initial replacement blade server, the data processing workload characterized by data processing resource requirements, the initial replacement blade server having data processing resources that do not match the data processing resource requirements; and

transferring the data processing workload from the initial replacement blade server to a subsequent replacement blade server, the subsequent replacement blade server having data processing resources that better match the data processing resource requirements than do the data processing resources of the initial replacement blade server, including transferring the workload to the subsequent replacement blade server only if the data processing cost of the transfer of the workload to the subsequent replacement blade is less than the value of a transfer cost threshold;

the data processing workload is executed on a virtual machine on the failing blade server; and

the data processing resource requirements are implemented as virtual machine metadata describing the data processing resource requirements of the virtual machine.

14. The computer program product of claim 13 further comprising computer program instructions that cause the system management server to determine the value of the transfer cost threshold based upon a cost of an inefficiency of executing the workload on the initial replacement blade server while the initial replacement blade server provides data processing resources that do not match the data processing resource requirements of the workload.

15. The computer program product of claim 13 further comprising computer program instructions that cause the system management server to determine the cost of the transfer of the workload to the subsequent replacement blade based upon a cost of workload downtime during the transfer, a cost of powering down the initial replacement blade server, a cost of starting execution of the workload on the subsequent replacement blade server.

16. The computer program product of claim 13 further comprising computer program instructions that cause the system management server to maintain records indicating which blade servers in the data center are candidates for workload transfer to a subsequent replacement blade server, a candidate being a blade server whose data processing resources do not match the data processing resource requirements of a data processing workload executing on that blade server.

17. The computer program product of claim 13 further comprising computer program instructions that cause the system management server to monitor a pool of standby blade servers for availability of replacement blade servers that better match the data processing resource requirements of a data processing workload executing on a candidate.

18. The computer program product of claim 13 further comprising computer program instructions that cause the system management server to select the subsequent replacement blade server from a pool of standby blade servers, the subsequent replacement blade server providing, as among the standby blade servers, the best available match between the data processing resource requirements and the data processing resources of the subsequent replacement blade server.