Method, system and program products for managing a clustered computing environment

• US 7,185,076 B1
• Filed: 05/31/2000
• Issued: 02/27/2007
• Est. Priority Date: 05/31/2000
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Badovinatz, Peter R., Novaes, Marcos N., Schmidt, Michael A., Lucash, Jeffrey S., Laib, Gregory D., Goering, Ronald T.
• Primary Examiner(s): Najjar; Saleh
• Assistant Examiner(s): WON, MICHAEL YOUNG
• Application Number:
  US09/583,677
• Time in Patent Office: 2,463 Days
• Field of Search: 709/100, 709/220, 709/223, 709/106, 709/248
• US Class Current: 709/223
• CPC Class Codes: G06F 2209/505 Clust
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information

Abstract

Various components are provided to manage a clustered environment. These components include a System Registry that provides a global data storage; a Configuration manager that stores data locally on nodes of the clustered environment and globally within the System Registry; a Liveness component to provide status of communications paths of the cluster; a Group Services component that provides services to one or more other components of the clustered environment; and a Resource Management component that communicates with one or more resource controllers of the clustered environment. Each of the components of the clustered environment has one or more data and/or functional dependencies on one or more other components of the environment. However, relationships between the components are created such that the data and functional dependencies form an acyclic graph (i.e., a cycle of dependency relationships is avoided).

Claims

1. A system of managing clusters of a computing environment, said system comprising:

a registry component to provide global data storage for global data of a cluster of said computing environment, said cluster including a plurality of nodes of said computing environment and said global data comprising configuration data of multiple nodes of the plurality of nodes;

a configuration component to maintain data locally on at least one node of said plurality of nodes, and to store global data in said registry component;

a liveness component to provide status of one or more communications paths of said cluster, said liveness component being dependent upon said registry component and said configuration component;

a group services component to provide one or more services to one or more other components of said cluster, said group services component being dependent on said registry component, said configuration component and said liveness component;

a resource management component to provide communications to one or more resource controllers of said cluster, said resource management component being dependent on said registry component, said configuration component and said group services component;

wherein said configuration component is responsible for starting one or more components of said registry component, said liveness component, said group services component and said resource management component, and

wherein said one or more components are started by the configuration component in a defined order comprising starting the registry component, and then the liveness component, the group services component and the resource management component.

2. The system of claim 1, wherein said registry component is dependent on said group services component for at least one type of operation.

3. The system of claim 2, wherein said at least one type of operation comprises a write operation.

4. The system of claim 2, wherein said registry component is functionally dependent on said group services component.

5. The system of claim 1, wherein said being dependent comprises being functionally dependent.

6. The system of claim 5, wherein said registry component lacks a data dependency on said configuration component, said liveness component, said group services component and said resource management component.

7. The system of claim 5, wherein said configuration component has a data dependency on said registry component.

8. The system of claim 5, wherein said liveness component has a data dependency on said registry component.

9. The system of claim 5, wherein said group services component has a data dependency on said registry component.

10. The system of claim 5, wherein said resource management component has a data dependency on said registry component.

11. The system of claim 5, wherein said liveness component has a data dependency on said configuration component.

12. The system of claim 5, wherein said group services component has a data dependency on said configuration component.

13. The system of claim 5, wherein said resource management component has a data dependency on said configuration component.

14. The system of claim 1, wherein said cluster includes a plurality of nodes, and wherein said registry component is included on less than all nodes of said plurality of nodes.

15. The system of claim 1, wherein said configuration component is started by at least one operating system of at least one node of said one or more nodes of said computing environment.

16. The system of claim 1, wherein the starting of one or more components satisfies at least one of one or more functional dependencies between the one or more components and one or more data dependencies between the one or more components.

17. The system of claim 1, wherein said registry component begins a first phase of its initialization, in response to being started, said first phase of initialization comprising determining at least one copy of a global configuration database to be used in the starting.

18. The system of claim 17, wherein said configuration component utilizes a copy of said at least one copy of the global configuration database to verify data, and then continue with starting the liveness component, the group services component and the resource management component.

19. The system of claim 18, wherein said group services component completes its initialization, in response to the liveness component becoming available.

20. The system of claim 19, wherein said registry component begins a second phase of its initialization, in response to the group services component completing initialization, said second phase of initialization comprising updating zero or more copies of the global configuration database to allow write operations against the global configuration database.

21. The system of claim 20, wherein said resource management component performs its initialization using said system registry component and said group services component.

64. The system of claim 1, wherein the configuration data comprises multiple node definitions for the multiple nodes.

65. The system of claim 1, wherein said computing environment is a shared nothing environment.

22. A method of managing clusters of a computing environment, said method comprising:

providing, via a registry component, global data storage for global data of a cluster of said computing environment, said cluster including a plurality of nodes of said computing environment and said global data comprising configuration data of multiple nodes of the plurality of nodes;

maintaining, via a configuration component, data locally on at least one node of said plurality of nodes, and to store global data in said registry component;

providing, via a liveness component, status of one or more communications paths of said cluster, said liveness component being dependent upon said registry component and said configuration component;

providing, via a group services component, one or more services to one or more other components of said cluster, said group services component being dependent on said registry component, said configuration component and said liveness component;

providing, via a resource management component, communications to one or more resource controllers of said cluster, said resource management component being dependent on said registry component, said configuration component and said group services component; and

starting, via said configuration component, one or more components of said registry component, said liveness component, said group services component and said resource management component, wherein said one or more components are started by the configuration component in a defined order comprising starting the registry component, and then the liveness component, the group services component and the resource management component.

23. The method of claim 22, wherein said registry component is dependent on said group services component for at least one type of operation.

24. The method of claim 23, wherein said at least one type of operation comprises a write operation.

25. The method of claim 23, wherein said registry component is functionally dependent on said group services component.

26. The method of claim 22, wherein said being dependent comprises being functionally dependent.

27. The method of claim 26, wherein said registry component lacks a data dependency on said configuration component, said liveness component, said group services component and said resource management component.

28. The method of claim 26, wherein said configuration component has a data dependency on said registry component.

29. The method of claim 26, wherein said liveness component has a data dependency on said registry component.

30. The method of claim 26, wherein said group services component has a data dependency on said registry component.

31. The method of claim 26, wherein said resource management component has a data dependency on said registry component.

32. The method of claim 26, wherein said liveness component has a data dependency on said configuration component.

33. The method of claim 26, wherein said group services component has a data dependency on said configuration component.

34. The method of claim 26, wherein said resource management component has a data dependency on said configuration component.

35. The method of claim 22, wherein said cluster includes a plurality of nodes, and wherein said registry component is included on less than all nodes of said plurality of nodes.

36. The method of claim 22, wherein said configuration component is started by at least one operating system of at least one node of said one or more nodes of said computing environment.

37. The method of claims 22, wherein the starting of one or more components satisfies at least one of one or more functional dependencies between the one or more components and one or more data dependencies between the one or more components.

38. The method of claim 22, further comprising beginning, by said registry component, a first phase of its initialization, in response to being started, said first phase of initialization comprising determining at least one copy of a global configuration database to be used in the starting.

39. The method of claim 38, further comprising utilizing, by said configuration component, a copy of said at least one copy of the global configuration database to verify data, and then continue with starting the liveness component, the group services component and the resource management component.

40. The method of claim 39, further comprising completing, by said group services component, its initialization, in response to the liveness component becoming available.

41. The method of claim 40, further comprising beginning, by said registry component, a second phase of its initialization, in response to the group services component completing initialization, said second phase of initialization comprising updating zero or more copies of the global configuration database to allow write operations against the global configuration database.

42. The method of claim 41, further comprising performing, by said resource management component, its initialization using said system registry component and said group services component.

43. At least one program storage device readable by a machine tangibly embodying at least one program of instructions executable by the machine to perform a method of managing clusters of a computing environment, said method comprising:

providing, via a registry component, global data storage for global data of a cluster of said computing environment, said cluster including a plurality of nodes of said computing environment and said global data comprising configuration data of multiple nodes of the plurality of nodes;

maintaining, via a configuration component, data locally on at least one node of said plurality of nodes, and to store global data in said registry component;

providing, via a liveness component, status of one or more communications paths of said cluster, said liveness component being dependent upon said registry component and said configuration component;

providing, via a group services component, one or more services to one or more other components of said cluster, said group services component being dependent on said registry component, said configuration component and said liveness component;

providing, via a resource management component, communications to one or more resource controllers of said cluster, said resource management component being dependent on said registry component, said configuration component and said group services component; and

starting, via said configuration component, one or more components of said registry component, said liveness component, said group services component and said resource management component, wherein said one or more components are started by the configuration component in a defined order comprising starting the registry component, and then the liveness component, the group services component and the resource management component.

44. The at least one program storage device of claim 43, wherein said registry component is dependent on said group services component for at least one type of operation.

45. The at least one program storage device of claim 44, wherein said at least one type of operation comprises a write operation.

46. The at least one program storage device of claim 44, wherein said registry component is functionally dependent on said group services component.

47. The at least one program storage device of claim 43, wherein said being dependent comprises being functionally dependent.

48. The at least one program storage device of claim 47, wherein said registry component lacks a data dependency on said configuration component, said liveness component, said group services component and said resource management component.

49. The at least one program storage device of claim 47, wherein said configuration component has a data dependency on said registry component.

50. The at least one program storage device of claim 47, wherein said liveness component has a data dependency on said registry component.

51. The at least one program storage device of claim 47, wherein said group services component has a data dependency on said registry component.

52. The at least one program storage device of claim 47, wherein said resource management component has a data dependency on said registry component.

53. The at least one program storage device of claim 47, wherein said liveness component has a data dependency on said configuration component.

54. The at least one program storage device of claim 47, wherein said group services component has a data dependency on said configuration component.

55. The at least one program storage device of claim 47, wherein said resource management component has a data dependency on said configuration component.

56. The at least one program storage device of claim 43, wherein said cluster includes a plurality of nodes, and wherein said registry component is included on less than all nodes of said plurality of nodes.

57. The at least one program storage device of claim 43, wherein said configuration component is started by at least one operating system of at least one node of said one or more nodes of said computing environment.

58. The at least one program storage device of claim 43, wherein the starting of one or more components satisfies at least one of one or more functional dependencies between the one or more components and one or more data dependencies between the one or more components.

59. The at least one program storage device of claim 43, wherein said method further comprises beginning, by said registry component, a first phase of its initialization, in response to being started, said first phase of initialization comprising determining at least one copy of a global configuration database to be used in the starting.

60. The at least one program storage device of claim 59, wherein said method further comprises utilizing, by said configuration component, a copy of said at least one copy of the global configuration database to verify data, and then continue with starting the liveness component, the group services component and the resource management component.

61. The at least one program storage device of claim 60, wherein said method further comprises completing, by said group services component, its initialization, in response to the liveness component becoming available.

62. The at least one program storage device of claim 61, wherein said method further comprises beginning, by said registry component, a second phase of its initialization, in response to the group services component completing initialization, said second phase of initialization comprising updating zero or more copies of the global configuration database to allow write operations against the global configuration database.

63. The at least one program storage device of claim 62, wherein said method further comprises performing, by said resource management component, its initialization using said system registry component and said group services component.