Scaling systems management using a stateless proxy

• US 7,899,898 B2
• Filed: 06/30/2008
• Issued: 03/01/2011
• Est. Priority Date: 06/30/2008
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Wookey, Michael J.
• Primary Examiner(s): Follansbee; John
• Assistant Examiner(s): MADAMBA, GLENFORD J
• Application Number:
  US12/165,227
• Publication Number:
  US 20090327470A1
• Time in Patent Office: 974 Days
• Field of Search: 709/223, 709/224, 707/741
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]

Abstract

A system for managing system devices including a first managed system, which includes hardware, an operating system executing on the hardware, and an agent management object (AMO) executing on the operating system and configured to obtain first management information about the operating system and the hardware. The system also includes a second managed system, including a first proxy management object (PMO) configured to receive the first management information from the AMO, request second management information about the hardware from the first managed system, receive the second management information from the first managed system, normalize the first management information and the second management information to obtain first normalized management information, and populate a first proxy data model associated with the PMO using the first normalized management information, where the first normalized management information is used to manage the first managed system.

Claims

1. A system for managing system devices, comprising:

a first managed system, comprising;

hardware,

an operating system executing on the hardware, and

an agent management object (AMO) executing on the operating system and configured to obtain first management information about the operating system and the hardware; and

a second managed system comprising a first proxy management object (PMO) configured to;

receive the first management information from the AMO,

send a request for second management information about the hardware from the hardware, wherein the request is configured to bypass the AMO,

receive, in response to the request, the second management information from the hardware,

normalize the first management information and the second management information to obtain first normalized management information, and

populate a first proxy data model associated with the PMO using the first normalized management information, wherein the first normalized management information is used to manage the first managed system.

2. The system of claim 1, further comprising:

a satellite management object (SMO) operatively connected to the first PMO and a second PMO, wherein the SMO is configured to;

receive the first proxy data model from the first PMO,

receive a second proxy data model from the second PMO,

normalize the first proxy data model and the second proxy data model to obtain second normalized management information, and

populate a satellite data model associated with the SMO using the second normalized management information, wherein the second normalized management information is used to manage the first PMO, the second PMO, and the AMO.

3. The system of claim 1, wherein the AMO comprises a driver and wherein the AMO is configured to use the driver to obtain management information associated with hardware, and wherein the first management information comprises the management information associated with the hardware.

4. The system of claim 1, wherein the AMO comprises an agent data model, wherein the agent data model includes a management object for each of the entities managed by the AMO, wherein each of the entities is one selected from a group consisting of a hardware component of the hardware, the operating system, and an application executing on the operating system.

5. The system of claim 4, wherein the first proxy data model includes a management object for each of the entities managed by the PMO, wherein each of the entities is one selected from a group consisting of a hardware component of hardware on which the PMO is executing, a hardware component of the hardware, the operating system, and the application executing on the operating system.

6. The system of claim 4, wherein the AMO communicates updates in the agent data model to the PMO.

7. A method for managing system devices, comprising a first proxy management object (PMO), comprising:

receiving, directly from a target hardware, a first set of data about the target hardware;

receiving, from an agent management object (AMO) operatively connected to the target hardware, a second set of data about the target hardware, wherein the AMO is bypassed when receiving the first set of data;

normalizing the first set of data and the second set of data to obtain normalized data;

populating a proxy data model using the normalized data; and

managing the target hardware using the proxy data model.

8. The method of claim 7, further comprising:

sending the proxy data model to a satellite management object (SMO), wherein the SMO is operatively connected to a proxy management object (PMO) and wherein the SMO is configured to;

populate a satellite data model using the proxy data model; and

manage the target hardware using the satellite data model.

9. The method of claim 7, wherein the second set of data about the target hardware is received from an agent data model.

10. The method of claim 7, wherein normalizing the first set of data and the second set of data comprises using a normalizing policy.

11. The method of claim 10, wherein the normalization policy specifies which of the first data set and the second data set to use when the first data set and the second data set include management information about the target hardware.

12. The method of claim 8, wherein the PMO is removed and a second PMO is instantiated, wherein a second proxy data model in the second PMO is populated from data received from the SMO and requested from the AMO.

13. The method of claim 8, wherein the PMO receives an management update from the AMO and sends the management update to the SMO.

14. A non-transitory computer readable medium comprising software code for managing system devices, comprising software instructions to:

receive, directly from a target hardware, a first set of data about the target hardware;

receive, from an agent management object (AMO) operatively connected to the target hardware, a second set of data about the target hardware, wherein the AMO is bypassed when receiving the first set of data;

normalize the first set of data and the second set of data to obtain normalized data;

populate a proxy data model using the normalized data; and

manage the target hardware using the proxy data model.

15. The computer readable medium of claim 14, further comprising software instructions to:

send the proxy data model to a satellite management object (SMO), wherein the SMO is operatively connected to a proxy management object (PMO) and wherein the SMO is configured to;

populate a satellite data model using the proxy data model; and

manage the target hardware using the satellite data model.

16. The non-transitory computer readable medium of claim 14, wherein the second set of data about the target hardware is received from an agent data model.

17. The non-transitory computer readable medium of claim 14, wherein normalizing the first set of data and the second set of data comprises using a normalizing policy.

18. The non-transitory computer readable medium of claim 14, wherein the normalization policy specifies which of the first data set and the second data set to use when the first data set and the second data set include management information about the target hardware.

19. The non-transitory computer readable medium of claim 15, wherein the PMO is removed and a second PMO is instantiated, wherein a second proxy data model in the second PMO is populated from data received from the SMO and requested from the AMO.

20. The non-transitory computer readable medium of claim 15, wherein the PMO receives an management update from the AMO and sends the management update to the SMO.