Method and system for delegated job control across a network

• US 8,904,003 B2
• Filed: 06/30/2008
• Issued: 12/02/2014
• Est. Priority Date: 06/30/2008
• Status: Active Grant

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Wookey, Michael J.
• Primary Examiner(s): Hoang, Hieu
• Assistant Examiner(s): WIDHALM, ANGELA M
• Application Number:
  US12/165,334
• Publication Number:
  US 20090328065A1
• Time in Patent Office: 2,346 Days
• Field of Search: 709/203, 709/217, 709223-226, 709/235
• US Class Current: 709/226
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]

Abstract

A method for job delegation including receiving a job from a user by a first management object, identifying a target system for the job using a data model in the first management object and a job delegation policy, where the data model comprises an object representing the target system, and determining a first nexthop for the target system, where the first nexthop is a second management object. The method also includes placing the job on a queue corresponding to the second management object, where the queue is located in the first management object, receiving the job by the second management object, locating the target system and a driver corresponding to the target system using the second management object, and executing the job using the driver corresponding to the target system.

Claims

1. A method for job delegation, comprising:

receiving a job from a user by a first management object, wherein the first management object is a satellite management object (SMO) executing on a first managed system;

identifying a target system for the job using a first data model in the first management object and a job delegation policy, wherein the first data model comprises an object representing the target system, wherein the target system is a second managed system;

determining a first nexthop for the target system, wherein the first nexthop is a second management object, wherein the second management object is a proxy management object (PMO) executing on a network device, wherein the network device is one selected from a group consisting of a router and a load balancer, and wherein the PMO is configured to generate a second data model using data directly obtained from the network device and a third data model;

placing the job on a first queue corresponding to the second management object, wherein the first queue is located in the first management object;

receiving the job by the second management object;

making a determination that the PMO cannot process the job;

based on the determination;

identifying the target system and a second nexthop for the target system in the second data model in the second management object, wherein the second nexthop is a third management object and wherein the first data model comprises data obtained from the second data model;

placing the job on a second queue corresponding to the third management object, wherein the second queue is located in the second management object;

receiving the job by the third management object on the target system, wherein the third management object is an agent management object (AMO), wherein the AMO is located in an operating system of the target system, and wherein the AMO is configured to use a driver to obtain data about the target system to generate the third data model;

identifying the driver located in the third management object to execute the job; and

executing the job using the driver;

wherein the SMO is configured to communicate with the PMO and the PMO is configured to communicate with the AMO,

wherein the first managed system and the target system are each operatively connected to the network device, and

wherein the first management object, the second management object, and the third management object execute on one or more processors.

2. The method of claim 1, further comprising:

sending a notification to the first management object that the job has been executed.

3. The method of claim 1, wherein the first management object is configured to perform at least on selected from the group of:

suspend the job, stop the job, resume the job, and rollback the job.

4. A system for job delegation, comprising:

a first management object, wherein the first management object is configured to;

receive a job from a user by the first management object, wherein the first management object is a satellite management object (SMO) executing on a first managed system;

identify a target system for the job using a first data model in the first management object and a job delegation policy, wherein the first data model comprises an object representing the target system, wherein the target system is a second managed system;

determine a first nexthop for the target system, wherein the first nexthop is a second management object, wherein the second management object is a proxy management object (PMO) executing on a network device, wherein the network device is one selected from a group consisting of a router and a load balancer, and wherein the PMO is configured to generate a second data model using data directly obtained from the network device and a third data model;

place the job on a first queue corresponding to the second management object, wherein the first queue is located in the first management object; and

the second management object, wherein the second management object is configured to;

receive the job;

make a determination that the PMO cannot process the job;

based on the determination;

identify the target system and a second nexthop for the target system in the second data model in the second management object, wherein the second nexthop is a third management object and wherein the first data model comprises data obtained from the second data model;

place the job on a second queue corresponding to the third management object, wherein the second queue is located in the second management object;

the third management object, wherein the third management object is configured to;

receive the job, wherein the third management object is an agent management object (AMO), wherein the AMO is located in an operating system of the target system, and wherein the AMO is configured to use a driver to obtain data about the target system to generate the third data model;

identify the driver located in the third management object to execute the job; and

execute the job using the driver,

wherein the SMO is configured to communicate with the PMO and the PMO is configured to communicate with the AMO,

wherein the first managed system and the target system are each operatively connected to the network device, and

wherein the first management object, the second management object, and the third management object execute on one or more processors.

5. The system of claim 4, wherein the job comprises a plurality of tasks, wherein each of the tasks is an atomic operation to be performed on the target system.

6. The system of claim 5, wherein the third management object maintains a last-in first-out (LIFO) queue associated with the job, wherein the LIFO queue comprises a first completed task of the plurality of tasks and wherein the LIFO queue is used by a compensation engine in the third management object to undo the first completed task if a second one of the plurality of tasks fails.

7. The system of claim 4, wherein the second management object is configured to:

send a notification to the first management object that the job has been executed.

8. The system of claim 4, wherein the first management object is further configured to perform at least on selected from the group of:

suspend the job, stop the job, resume the job, and roll back the job.

9. A non-transitory computer readable medium comprising software code for delegating a job, comprising software instructions to:

receive the job from a user by a first management object, wherein the first management object is a satellite management object (SMO) executing on a first managed system;

identify a target system for the job using a first data model in the first management object and a job delegation policy, wherein the first data model comprises an object representing the target system, wherein the target system is a second managed system;

determine a first nexthop for the target system, wherein the first nexthop is a second management object, wherein the second management object is a proxy management object (PMO) executing on a network device, wherein the network device is one selected from a group consisting of a router and a load balancer, and wherein the PMO is configured to generate a second data model using data directly obtained from the network device and a third data model;

place the job on a first queue corresponding to the second management object, wherein the first queue is located in the first management object;

receive the job by the second management object;

make a determination that the PMO cannot process the job;

based on the determination;

identify the target system and a second nexthop for the target system in the second data model in the second management object, wherein the second nexthop is a third management object and wherein the first data model comprises data obtained from the second data model;

place the job on a second queue corresponding to the third management object, wherein the second queue is located in the second management object;

receive the job by the third management object on the target system, wherein the third management object is an agent management object (AMO) wherein the AMO is located in an operating system of the target system, and wherein the AMO is configured to use a driver to obtain data about the target system to generate the third data model;

identify the driver located in the third management object to execute the job; and

execute the job using the driver

wherein the SMO is configured to communicate with the PMO and the PMO is configured to communicate with the AMO,

wherein the first managed system and the target system are each operatively connected to the network device, and

wherein the first management object, the second management object, and the third management object execute on one or more processors.

10. The non-transitory computer readable medium of claim 9, wherein the second management object is configured to:

send a notification to the first management object that the job has been executed.

11. The non-transitory computer readable medium of claim 9, wherein the first management object is further configured to perform at least on selected from the group of:

suspend the job, stop the job, resume the job, and roll back the job.