METHOD AND SYSTEM FOR COMPUTER SYSTEM DIAGNOSTIC SCHEDULING USING SERVICE LEVEL OBJECTIVES

• US 20100043004A1
• Filed: 09/24/2008
• Published: 02/18/2010
• Est. Priority Date: 08/12/2008
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Jagadish, Archana, Tambi, Ashwini Kumar
• Application Number:
  US12/236,514
• Publication Number:
  US 20100043004A1
• Time in Patent Office: Days
• US Class Current: 718/103
• 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 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence

Abstract

A system and method for automatically scheduling health diagnostics within a computer system is disclosed. In one embodiment, a method for automatically scheduling health diagnostics within a computer system using service level objectives (SLOs) includes reviewing the SLOs associated with each managed server, invoking each managed server for diagnosing computer system based on the associated SLOs, receiving diagnostic status data and computer system health data from each managed server, and analyzing the received diagnostic status data and computer system health data and implementing any needed one or more corrective actions based on the analysis and a predetermined configuration corrective action criteria.

Claims

1. A method for automatically scheduling health diagnostics within a computer system using service level objectives (SLOs) and wherein the computer system includes a plurality of managed servers communicatively coupled to a management server, comprising:

creating the SLOs by an information technology (IT) administrator using the management server for each managed server;

reviewing service level objectives (SLOs) associated with each managed server by the management server; and

invoking each managed server for diagnosing the computer system based on the associated SLOs by the management server.

2. The method of claim 1, further comprising:

receiving diagnostic status data and computer system health data from each managed server;

analyzing the received diagnostic status data and computer system health data by the management server; and

implementing one or more corrective actions based on the analysis and a predetermined configuration corrective action criteria.

3. The method of claim 2, further comprising:

determining resource utilization information associated with each managed server;

analyzing the determined resource utilization information for each managed server; and

determining a priority workload and a non-priority workload for each managed server based on the analysis.

4. The method of claim 3, further comprising:

determining whether the determined resource utilization exceeds a predetermined resource utilization value for each managed server;

if so, suspending any applications associated with the non-priority workload running on each managed server that is determined to have exceeded the predetermined resource utilization value; and

if not, executing any scheduled hardware diagnostic tools and continuing receiving the diagnostic status data and computer system health data and determining the resource utilization information for each managed server after a predetermined time interval.

5. The method of claim 4, further comprising:

determining whether the resource utilization exceeds the predetermined resource utilization value after suspending any of the applications associated with the non-priority workload for each managed server;

if so, deferring the diagnosing computer system for each managed server based on the associated SLOs; and

if not, executing any scheduled hardware diagnostic tools and continuing receiving the diagnostic status data and computer system health data and determining resource utilization information for each managed server after a predetermined time interval.

6. The method of claim 1, further comprising:

modifying one or more of the SLOs by the IT administrator using the management server; and

invoking each managed server for diagnosing computer system based on the associated modified SLOs by the management server.

7. An article, comprising:

a storage medium having instructions, that when executed by a computing platform, results in execution of a method for automatically scheduling health diagnostics within a computer system using service level objectives (SLOs) and wherein the computer system includes a plurality of managed servers communicatively coupled to a management server, the method comprising;

reviewing service level objectives (SLOS) associated with each managed server by the management server;

invoking each managed server for diagnosing computer system based on the associated SLOs by the management server; and

receiving diagnostic status data and computer system health data from each managed server.

8. The article of claim 7, further comprising:

determining resource utilization information associated with each managed server;

analyzing the determined resource utilization information for each managed server;

determining a priority workload and a non-priority workload for each managed server based on the analysis;

determining whether the determined resource utilization exceeds a predetermined resource utilization value for each managed server;

if, so suspending any applications associated with the non-priority workload running on each managed server that is determined to have exceeded the predetermined resource utilization value; and

if not, executing any scheduled hardware diagnostic tools and continuing receiving the diagnostic status data and computer system data and determining the resource utilization information for each managed server after a predetermined time interval.

9. The article of claim 8, further comprising:

determining whether the resource utilization exceeds the predetermined resource utilization value after suspending any of the applications associated with the non-priority workload for each managed server;

if so, deferring the diagnosing computer system for each managed server based on the associated SLOs; and

if not, executing any scheduled hardware diagnostic tools and continuing receiving the diagnostic status data and computer system health data and determining resource utilization information for each managed server after a predetermined time interval.

10. A computer system comprising:

a plurality of managed servers; and

a management server communicatively coupled to the plurality of managed servers, wherein the management server includes a policy engine and a diagnostic controller and wherein each managed server comprises;

a resource automation and utilization manager;

a hardware diagnostic subsystem; and

a diagnostic manager, wherein the policy engine comprises a policy repository including service level objectives (SLOs), wherein the diagnostic manager reviews the SLOs associated with each managed server, and wherein the diagnostic controller invokes each managed server for diagnosing computer system based on the reviewed associated SLOs, wherein the diagnostic manager receives diagnostic status data and computer system health data from each managed server.

11. The computer system of claim 10, wherein the policy engine further comprises:

a policy editor, wherein the policy editor is coupled to the policy repository, and wherein the IT administrator creates the SLOs for each managed server using the policy editor.

12. The computer system of claim 11, wherein the resource automation and utilization manager comprises:

a workload manager to determine resource utilization information associated with each managed server; and

a utilization agent coupled to the workload manager and the diagnostic controller and wherein the utilization agent analyzes the determined resource utilization information of each managed server and determines a priority workload and a non-priority workload of each managed server.

13. The system of claim 12, wherein the diagnostic manager determines whether the determined resource utilization exceeds a predetermined resource utilization value for each managed server, wherein the diagnostic controller using the diagnostic manager suspends any applications that are associated with the non-priority workload running on each managed server that is determined as exceeding the predetermined resource utilization value, wherein the diagnostic manager continues receiving the diagnostic status data and computer system health data and determining the resource utilization information for each managed server that is determined as not exceeding the predetermined resource utilization value after a predetermined time interval.

14. The computer system of claim 13, wherein each managed server comprises:

a plurality of hardware monitoring agents and associated plurality of hardware diagnostic tools and wherein the diagnostic controller invokes the diagnostic manager via the associated plurality of hardware diagnostic tools for diagnosing computer system based on the associated SLOs.

15. The computer system of claim 14, wherein the managed server further comprises:

a latest diagnostic run log that is communicatively coupled to the diagnostic manager and wherein the latest diagnostic run log is an extensible markup language (XML) based log file including event associated with each invoking of the hardware diagnostic tools for diagnosing computer system that is updated by the diagnostic manager.

16. The computer system of claim 15, wherein the management server further comprises an event repository that is coupled to the diagnostic manager to receive and store the diagnostic status data and computer system health data associated with each managed server via each associated hardware monitoring agent, and wherein the IT administrator modifies the one or more SLOs residing in the policy repository using the policy editor.