Methods and apparatus for managing dependencies in distributed systems

• US 6,847,970 B2
• Filed: 09/11/2002
• Issued: 01/25/2005
• Est. Priority Date: 09/11/2002
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Keller, Alexander, Kar, Gautam, Blumenthal, Uri
• Primary Examiner(s): Jung, David
• Application Number:
  US10/241,162
• Publication Number:
  US 20040049509A1
• Time in Patent Office: 867 Days
• Field of Search: 707200-206, 707 1- 10, 707100-104, 717100-103
• US Class Current: 1/1
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Techniques for managing information in a computing environment. Information associated with components of the computing environment is obtained. Then, from at least a portion of the obtained information, a determination is made as to the existence of one or more relationships associated with at least a portion of the components of the computing environment. The determination of the existence of one or more relationships is capable of accounting for a full lifecycle (e.g., including deployment, installation and runtime) associated with at least one component of the computing environment. Thus, techniques for managing runtime dependencies between the various components of computing systems are disclosed which provide a level of abstraction from individual systems and allow the computation of service/component (wherein the component may, for example, be an application, middleware, hardware, a device driver, an operating system and a system associated with the computing environment) dependencies that are related to end-to-end services, as perceived by a customer. By way of example, the inventive techniques may be applied to a distributed computing environment. The computing environment may also be an autonomic computing environment.

Claims

1. A computer-based method of managing information in a computing environment, the method comprising the steps of:

obtaining information associated with components of the computing environment; and

determining, from at least a portion of the obtained information, an existence of one or more relationships associated with at least a portion of the components of the computing environment, wherein the step of determining the existence of one or more relationships is capable of accounting for a full lifecycle associated with at least one component of the computing environment.

2. The method of claim 1, wherein the computing environment comprises a distributed computing environment.

3. The method of claim 1, wherein the computing environment comprises an autonomic computing environment.

4. The method of claim 1, wherein the step of determining the existence of one or more relationships associated with at least a portion of the components of the computing environment is further capable of accounting for a heterogeneity associated with at least two components of the computing environment.

5. The method of claim 1, wherein the step of determining the existence of one or more relationships associated with at least a portion of the components of the computing environment is further capable of accounting for one or more components which span one or more domains associated with the computing environment.

6. The method of claim 1, wherein the step of determining the existence of one or more relationships associated with at least a portion of the components of the computing environment further comprises computing component dependencies in a form comprising a functional categorization, a structural categorization and an operational categorization.

7. The method of claim 6, wherein the functional categorization of the component dependencies comprises functional elements modeled as a graph of nodes, wherein one or more first nodes are linked to one or more second nodes from which the one or more first nodes depend and to one or more third nodes which depend on the one or more first nodes.

8. The method of claim 7, wherein the nodes are representative of components in the computing environment.

9. The method of claim 8, wherein the components are defined as at least one of dependents and antecedents.

10. The method of claim 9, wherein the graph of nodes contains links between nodes, the links representing dependencies.

11. The method of claim 10, wherein the dependencies are one to one relationships comprising a dependent and an antecedent.

12. The method of claim 7, wherein the functional elements are one of linked and cross-referenced with structural elements in the structural categorization.

13. The method of claim 6, wherein the structural categorization of the component dependencies comprises structural elements modeled as a graph of nodes, wherein one or more first nodes are linked to one or more second nodes from which the one or more first nodes depend and to one or more third nodes which depend on the one or more first nodes.

14. The method of claim 13, wherein the structural elements provide information which defines deployment aspects of the components of the computing environment.

15. The method of claim 14, wherein information on the structural elements of the structural categorization is stored in one or more repositories during deployment actions by at least one of system administrators and operators.

16. The method of claim 15, wherein the information on the structural elements is made available from the one or more system repositories by one or more application programming interfaces.

17. The method of claim 6, wherein the operational categorization of the component dependencies comprises operational elements modeled as a graph of nodes, wherein one or more first nodes are linked to one or more second nodes from which the one or more first nodes depend and to one or more third nodes which depend on the one or more first nodes.

18. The method of claim 17, wherein the operational elements are one of linked and cross-referenced with structural elements in the structural categorization.

19. The method of claim 6, wherein the operational categorization is computed from at least one of the structural categorization and the functional categorization.

20. The method of claim 6, wherein the categorizations of the component dependencies are represented as graphical representations.

21. The method of claim 20, wherein at least a portion of edges of the graphical representations are annotated with additional qualifying information.

22. The method of claim 20, wherein the graphical representations are one of unidirectional and bidirectional.

23. The method of claim 20, wherein the graphical representations are one of directed acyclic graphs and directed cyclic graphs.

24. The method of claim 20, wherein a graphical representation is at least one of upward, downward and laterally traversible.

25. The method of claim 20, wherein the dependency information represented by a graphical representation is accessible in accordance with one or more application programming interfaces.

26. The method of claim 6, wherein one or more of the categorizations are persistently stored after being computed.

27. The method of claim 6, wherein one or more of the categorizations are not persistently stored after being computed.

28. The method of claim 1, wherein a component is one of a service, an application, middleware, hardware, a device driver, an operating system and a system associated with the computing environment.

29. The method of claim 1, wherein the information obtaining step further comprises getting information through at least one of one or more directly involved systems and one or more proxy systems.

30. The method of claim 1, further comprising the step of maintaining a history of changes associated with at least a portion of the one or more relationships.

31. Apparatus for managing information in a computing environment, comprising:

at least one processor operative to;

(i) obtain information associated with components of the computing environment; and

(ii) determine, from at least a portion of the obtained information, an existence of one or more relationships associated with at least a portion of the components of the computing environment, wherein the step of determining the existence of one or more relationships is capable of accounting for a full lifecycle associated with at least one component of the computing environment; and

memory, coupled to the at least one processor, operative to store information associated with the one or more determined relationships.

32. The apparatus of claim 31, wherein the computing environment comprises a distributed computing environment.

33. The apparatus of claim 31, wherein the computing environment comprises an autonomic computing environment.

34. The apparatus of claim 31, wherein the at least one processor is further operative to retrieve at least a portion of the stored information.

35. The apparatus of claim 31, wherein the operation of determining the existence of one or more relationships associated with at least a portion of the components of the computing environment is further capable of accounting for a heterogeneity associated with at least two components of the computing environment.

36. The apparatus of claim 31, wherein the operation of determining the existence of one or more relationships associated with at least a portion of the components of the computing environment is further capable of accounting for one or more components which span one or more domains associated with the computing environment.

37. The apparatus of claim 31, wherein the operation of determining the existence of one or more relationships associated with at least a portion of the components of the computing environment further comprises computing component dependencies in a form comprising a functional categorization, a structural categorization and an operational categorization.

38. The apparatus of claim 31, wherein a component is one of a service, an application, middleware, hardware, a device driver, an operating system and a system associated with the computing environment.

39. The apparatus of claim 31, wherein the information obtaining operation further comprises getting information through at least one of one or more directly involved systems and one or more proxy systems.

40. The apparatus of claim 31, wherein the at least one processor is further operative to maintain a history of changes associated with at least a portion of the one or more relationships.

41. An article of manufacture for managing information in a computing environment, comprising a machine readable medium containing one or more programs which when executed implement the steps of:

obtaining information associated with components of the computing environment; and

determining, from at least a portion of the obtained information, an existence of one or more relationships associated with at least a portion of the components of the computing environment, wherein the step of determining the existence of one or more relationships is capable of accounting for a full lifecycle associated with at least one component of the computing environment.