System and method for scenario generation in a distributed system

• US 20040260982A1
• Filed: 06/19/2003
• Published: 12/23/2004
• Est. Priority Date: 06/19/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Bhowmik, Sushrut, Sumar, Shubhankar
• Granted Patent: US 7,401,259 B2
• Time in Patent Office: Days
• US Class Current: 714/43
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A system and method may emulate scenarios for testing a distributed system. The distributed system may include a plurality of nodes, each having one or more resources. The system may include a resource driver for each type of the one or more resources in the distributed system, as well as one or more agents configured to access each resource through the corresponding resource driver. At least one node in the distributed system may be configured to run on a different platform than another node in the distributed system. The system may further include a central controller configured to communicate with each agent. The central controller may further execute a test scenario script containing one or more test scenarios for the distributed system.

Claims

1. A system, comprising:

a distributed system comprising a plurality of nodes, wherein each one of the plurality of nodes comprises;

one or more resources of the distributed system;

a resource driver for each type of the one or more resources; and

an agent configured to access each of the one or more resources through the corresponding resource driver;

a central controller configured to communicate with the agent on each of the plurality of nodes, wherein the central controller is configured to execute a test scenario script comprising one or more test scenarios for the distributed system, wherein the central controller is configured to send commands to the agents to implement the one or more test scenarios; and

wherein each agent is configured to receive commands from the central controller and perform corresponding actions on the one or more resources residing on the agent'"'"'s node, and wherein each agent is configured to return results from performing the corresponding actions to the central controller.

2. The system of claim 1 wherein at least one node is configured to run on a different platform than another node in the plurality of nodes;

wherein the at least one node configured to run on a different platform than another node in the plurality of nodes runs on a different operating system than the another node in the plurality of nodes.

3. The system of claim 1 wherein the central controller comprises:

a core controller configured to communicate with the agent on each of the plurality of nodes to execute the test scenario script, and

an interpreter operable to read the test scenario script and translate the test scenario script into central controller actions and unit operations for the core controller to send to the agents.

4. The system of claim 1 wherein the central controller further comprises a result analyzer operable to determine if the distributed system has passed or failed a test scenario in the test scenario script.

5. The system of claim 1, comprising a load generator accessible by the central controller and configured to direct a plurality of requests at the distributed system, as indicated by the test script.

6. The system of claim 1 wherein the central controller comprises a user interface to specify the test scenario script.

7. The system of claim 1 wherein one of the resources of the distributed system is a database.

8. The system of claim 1 wherein one of the resources of the distributed system is an application server.

9. The system of claim 1 wherein the central controller is configured to read a configuration file prior to executing the test scenario script, wherein the configuration file comprises:

information on the resources of the distributed system;

agent identification numbers or agent network addresses or port numbers; and

information on which agents correspond to which resources.

10. The system of claim 9, wherein the central controller is configured to communicate information about the location and type of the resources of the distributed system to the agents upon reading the configuration file.

11. The system of claim 1, wherein each of the plurality of nodes in the distributed system is configured to accept additional resource types, and wherein each corresponding agent is configured to interact with additional resource drivers corresponding to the additional resource types.

12. The system of claim 1, wherein each resource driver comprises:

a generic resource driver interface to the agent;

a resource-specific driver configured to access one or more functions of a specific resource type by translating one or more commands received from the central controller into resource-specific communications to carry out the commands.

13. The system of claim 1, wherein each resource driver comprises an event watcher configured to detect resource-specific events.

14. The system of claim 1, wherein each resource driver comprises a logging system configured to log resource-specific events or communications sent to and received from the central controller.

15. The system of claim 1, wherein the core controller comprises an event listener, wherein the event listener waits for notification from an agent that a resource event has occurred, and wherein in response to notification from an agent that a resource event has occurred, the core controller is configured to execute one or more central controller actions, or send one or more unit operations to the agents, as specified by the test scenario script.

16. The system of claim 1, wherein the test scenario script registers certain times or time periods with the central controller, and wherein in response to a certain time or time period elapsing, the central controller is configured to execute one or more central controller actions, or send one or more unit operations to the agents, as specified by the test scenario script.

17. A method, comprising:

executing a test scenario script from a central controller, wherein the test scenario script comprises one or more test scenarios to test a distributed system;

communicating commands according to the test scenario script between the central controller and a plurality of agents on each of a plurality of nodes within the distributed system;

wherein each one of the plurality of nodes comprises one or more resources of the distributed system and a resource driver for each type of the one or more resources; and

in response to each agent within the distributed system receiving commands from the central controller, each agent;

accessing each of the one or more resources through the corresponding resource driver;

performing corresponding actions on the one or more resources residing on the agent'"'"'s node; and

returning results from performing the corresponding actions to the central controller.

18. The method of claim 17 wherein at least one node may be configured to run on a different platform than another node in the plurality of nodes, wherein the at least one of the plurality of nodes running on a different platform than another node in the plurality of nodes runs on a different operating system than another node in the plurality of nodes.

19. The method of claim 17, wherein said executing comprises:

translating the test scenario script into central controller actions and unit operations for the core controller to send to the agents.

20. The method of claim 17, further comprising analyzing the results from a central location to determine if the distributed system has passed or failed a test scenario in the test scenario script.

21. The method of claim 17, wherein said executing script comprises accessing a load generator to direct a plurality of transaction requests at the distributed system.

22. The method of claim 17 further comprising specifying the test scenario through a user interface included in the central controller.

23. The method of claim 17 further comprising reading a configuration file prior to said executing the test scenario script, wherein the configuration file comprises:

information on the resources of the distributed system;

agent identification numbers or agent network addresses or port numbers; and

information on which agents correspond to which resources.

24. The method of claim 23, wherein upon reading the configuration file the central controller communicates information about the location and type of the resources of the distributed system to the agents.

25. The method of claim 23, further comprising:

adding a new resource to an agent in the distributed system;

adding a resource driver corresponding to a type for the new resource to the agent in the distributed system;

modifying the configuration file to indicate where the new resource is located in the distributed system.

26. The method of claim 17, further comprising:

detecting notification from an agent that a resource event has occurred with an event listener included in the core controller; and

executing one or more central controller actions, or sending one or more unit operations to the agents, in response to detecting notification from an agent that a resource event has occurred, as specified by the test scenario script.

27. The method of claim 17, further comprising:

registering certain times or time periods with the central controller; and

executing one or more central controller actions, or sending one or more unit operations to the agents, in response to detecting that certain times or time periods have elapsed, as specified by the test scenario script.