System management infrastructure for corrective actions to servers with shared resources

• US 7,529,981 B2
• Filed: 04/17/2003
• Issued: 05/05/2009
• Est. Priority Date: 04/17/2003
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Childress, Rhonda L., Laney, Mark Anthony, Minyen, Reid Douglas, Pennell, Neil Raymond
• Primary Examiner(s): Maskulinski; Michael C
• Application Number:
  US10/418,565
• Publication Number:
  US 20040210889A1
• Time in Patent Office: 2,210 Days
• Field of Search: 714/26, 714/48
• US Class Current: 714/48
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0727 in a storage system, e.g. in a DASD or network based storage system drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; 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], H04L67/1097
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/34 Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment

Abstract

A corrective action method or subsystem for providing corrective actions in a for a computing domain shared among multiple customers wherein different domain resources are shared by different customers, and each customer'"'"'s corrective action preferences are accommodated differently according a repository of customer preferences. A database may be queried when a fault event or out-of-limits condition is detected for a given shared resource to determine which customers share the resource, determine each affected customer'"'"'s response preferences, and to perform corrective actions according to those response preferences. For example, three customers may share a particular hard drive in a shared computing system. One customer may prefer to receive an email notice when the drive is nearly full, another may prefer to receive additional allocation of disk space elsewhere, and the third may prefer to receive a written report of space utilization.

Claims

1. A method comprising the steps of:

providing a customer requirements repository containing corrective action preferences for each of a plurality customers sharing a first computing system to execute one or more application programs on behalf of each of said customers, wherein said corrective action preferences differ among said customers; and

responsive to receipt of a fault event or out-of-limits condition for a shared resource of said first computing system domain;

querying said customer requirements repository;

determining two or more affected application programs for two or more customers sharing said shared resource;

determining affected customers on behalf of which said affected application programs are being executed;

extracting from said repository corrective action preferences for each of said affected application programs; and

performing two or more corrective actions according to said extracted preferences, wherein said corrective actions comprise at least two different actions, and wherein at least one corrective action comprises moving execution of an application program from said first computing system to a second computing system.

2. The method as set forth in claim 1 wherein said customer requirements repository comprises a database.

3. The method as set forth in claim 1 wherein said corrective action preferences comprise a set of rules disposed for evaluation during extracting corrective action preferences.

4. The method as set forth in claim 1 wherein said corrective actions comprise sending an electronic mail message.

5. The method as set forth in claim 1 wherein said corrective actions comprise sending a pager message.

6. The method as set forth in claim 1 wherein said corrective actions comprise opening a problem ticket.

7. The method as set forth in claim 1 wherein said corrective actions comprise generating a trouble report.

8. The method as set forth in claim 1 wherein said corrective actions comprise scheduling an upgrade to a computing platform resource.

9. The method as set forth in claim 1 wherein said corrective actions comprise scheduling a repair to a computing platform resource.

10. The method as set forth in claim 1 wherein said corrective actions comprise scheduling an upgrade to a computing platform software component.

11. The method as set forth in claim 1 wherein said receipt of a fault event or out-of limits condition for a shared resource comprises an event associated with a processor bandwidth utilization maximum limit.

12. The method as set forth in claim 1 wherein said receipt of a fault event or out-of limits condition for a shared resource comprises an event associated with a memory utilization maximum limit.

13. The method as set forth in claim 1 wherein said receipt of a fault event or out-of limits condition for a shared resource comprises an event associated with a communication link bandwidth utilization maximum limit.

14. The method as set forth in claim 1 wherein said receipt of a fault event or out-of limits condition for a shared resource comprises an event associated with a persistent storage utilization maximum limit.

15. The method as set forth in claim 1 wherein said receipt of a fault event or out-of limits condition for a shared resource comprises an event associated with a delay of service maximum limit.