System and method for generating a response plan for a hypothetical event

• US 8,793,344 B2
• Filed: 02/17/2012
• Issued: 07/29/2014
• Est. Priority Date: 02/17/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Manivel, Vinay, Gusev, Andrey, Creighton, Jonathan
• Primary Examiner(s): BAROT, BHARAT
• Application Number:
  US13/399,951
• Publication Number:
  US 20130219022A1
• Time in Patent Office: 893 Days
• Field of Search: 709202-203, 709217-219, 719/318
• US Class Current: 709/219
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals

Abstract

A cluster management system can facilitate determining a response to a hypothetical event by a computer cluster. During operation, the system can receive a request for a policy outcome from a user, such that the request can indicate a hypothetical event within a computer cluster. Next, the system determines a cluster state that includes state information from a plurality of server nodes in the cluster. The system then generates a response plan to the hypothetical event based on the cluster state, without executing the response plan in the cluster. The response plan indicates actions that are to be performed by server nodes in the cluster in response to the hypothetical event. The system then provides the response plan to the user.

Claims

1. A computer-implemented method, comprising:

receiving, at a computing device, a request for a policy outcome from a user, wherein the request indicates a hypothetical event within a computer cluster;

determining a cluster state, which includes state information from a plurality of server nodes in the cluster;

generating a response plan for the hypothetical event based on the cluster state, without executing the response plan in the cluster, which involves;

generating a hypothetical state by modifying the cluster state to account for the hypothetical event;

determining an initial cluster configuration that results from the hypothetical event, indicates a plurality of resources deployed in server nodes of the cluster, and includes a plurality of resource dependencies among the resources;

determining, based on the hypothetical state and the initial cluster configuration, a target cluster configuration that satisfies application policies for one or more applications deployed in the cluster; and

determining an ordered sequence of actions performed by the server nodes in the cluster to realize the policies in response to the hypothetical event, wherein the sequence of actions map the cluster'"'"'s initial configuration at the hypothetical state to the target configuration that satisfies the application policies; and

providing the response plan to the user.

2. The method of claim 1, wherein the request indicates a set of critical entities in the cluster that are marked as being critical to a service.

3. The method of claim 2, wherein the response plan indicates a set of critical entities whose state would change in response to executing the response plan.

4. The method of claim 1, wherein the actions in the response plan include the ordered sequence of actions, and wherein the actions in the response plan are identical to actions that would be performed by the server nodes in response to an actual event that matches the hypothetical event.

5. The method of claim 1, wherein the response plan also indicates the target configuration of the cluster that would result from executing the response plan.

6. The method of claim 1, wherein the hypothetical event includes at least one of:

an addition of a server node to the cluster;

a removal of a server node from the cluster;

a failure of a server node in the cluster;

an addition of a server pool to the cluster;

a removal of a server pool from the cluster;

an addition of a server node to a server pool;

a removal of a server node from a server pool;

a modification of an active policy;

a modification of a server category;

an addition of a resource to a server node;

a modification of a resource at a server node;

a start of a resource at a server node;

a stop of a resource at a server node;

a failure of a resource at a server node; and

a relocation of a resource within the cluster.

7. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method, the method comprising:

receiving a request for a policy outcome from a user, wherein the request indicates a hypothetical event within a computer cluster;

determining a cluster state, which includes state information from a plurality of server nodes in the cluster;

generating a response plan for the hypothetical event based on the cluster state, without executing the response plan in the cluster, which involves;

generating a hypothetical state by modifying the cluster state to account for the hypothetical event;

determining an initial cluster configuration that results from the hypothetical event, indicates a plurality of resources deployed in server nodes of the cluster, and includes a plurality of resource dependencies among the resources;

determining, based on the hypothetical state and the initial cluster configuration, a target cluster configuration that satisfies application policies for one or more applications deployed in the cluster; and

determining an ordered sequence of actions performed by the server nodes in the cluster to realize the policies in response to the hypothetical event, wherein the sequence of actions map the cluster'"'"'s initial configuration at the hypothetical state to the target configuration that satisfies the application policies; and

providing the response plan to the user.

8. The storage medium of claim 7, wherein the request indicates a set of critical entities in the cluster that are marked as being critical to a service.

9. The storage medium of claim 8, wherein the response plan indicates a set of critical entities whose state would change in response to executing the response plan.

10. The storage medium of claim 7, wherein the actions in the response plan include the ordered sequence of actions, and wherein the actions in the response plan are identical to actions that would be performed by the server nodes in response to an actual event that matches the hypothetical event.

11. The storage medium of claim 7, wherein the response plan also indicates the target configuration of the cluster that would result from executing the response plan.

12. The storage medium of claim 7, wherein the hypothetical event includes at least one of:

an addition of a server node to the cluster;

a removal of a server node from the cluster;

a failure of a server node in the cluster;

an addition of a server pool to the cluster;

a removal of a server pool from the cluster;

an addition of a server node to a server pool;

a removal of a server node from a server pool;

a modification of an active policy;

a modification of a server category;

an addition of a resource to a server node;

a modification of a resource at a server node;

a start of a resource at a server node;

a stop of a resource at a server node;

a failure of a resource at a server node; and

a relocation of a resource within the cluster.

13. An apparatus comprising:

a communication module to receive a request for a policy outcome from a user, wherein the request indicates a hypothetical event within a cluster;

a configuration-determining module to determine a cluster state, wherein the cluster state includes state information from a plurality of server nodes in the cluster; and

a response-generating module to generate a response plan for the hypothetical event based on the cluster state, without executing the response plan in the cluster, wherein generating the response plan involves;

generating a hypothetical state by modifying the cluster state to account for the hypothetical event;

determining an initial cluster configuration that results from the hypothetical event, indicates a plurality of resources deployed in server nodes of the cluster, and includes a plurality of resource dependencies among the resources;

determining, based on the hypothetical state and the initial cluster configuration, a target cluster configuration that satisfies application policies for one or more applications deployed in the cluster; and

determining an ordered sequence of actions performed by the server nodes in the cluster to realize the policies in response to the hypothetical event, wherein the sequence of actions map the cluster'"'"'s initial configuration at the hypothetical state to the target configuration that satisfies the application policies;

wherein the communication module is further configured to provide the response plan to the user.

14. The apparatus of claim 13, wherein the request indicates a set of critical entities in the cluster that are marked as being critical to a service.

15. The apparatus of claim 14, wherein the response plan indicates a set of critical entities whose state would change in response to executing the response plan.

16. The apparatus of claim 13, wherein the actions in the response plan include the ordered sequence of actions, and wherein the actions in the response plan are identical to actions that would be performed by the server nodes in response to an actual event that matches the hypothetical event.

17. The apparatus of claim 13, wherein the response plan also indicates the target configuration of the cluster that would result from executing the response plan.

18. The apparatus of claim 13, wherein the hypothetical event includes at least one of:

an addition of a server node to the cluster;

a removal of a server node from the cluster;

a failure of a server node in the cluster;

an addition of a server pool to the cluster;

a removal of a server pool from the cluster;

an addition of a server node to a server pool;

a removal of a server node from a server pool;

a modification of an active policy;

a modification of a server category;

an addition of a resource to a server node;

a modification of a resource at a server node;

a start of a resource at a server node;

a stop of a resource at a server node;

a failure of a resource at a server node; and

a relocation of a resource within the cluster.