Cluster management of distributed applications

1. A method comprising:

performing at a lifecycle manager a first process, the first process comprising:

determining nodes in a cluster to run an application;

determining a difference between a cluster goal state and a cluster actual state for the application;

determining goal state for each node; and

sending respective goal state to agents;

performing at each agent a second process, the second process comprising:

determining a difference between the goal state of the node and an actual state of the node;

determining actions to be performed based on the difference between the goal state of the node and the actual state of the node; and

sending actions to resource managers to perform based on the difference between the goal state of the node and the actual state of the node.

2. The method of claim 1 , wherein the lifecycle manager comprises:

a first web service to handle application interface (API) requests;

a cluster goal state driver to perform the first process;

a cluster goal state;

a first event library configured to generate cluster level events;

a cluster actual state formed from actual states of each agent; and

a persistence component comprising key/value store for a cluster state.

3. The method of claim 2 , wherein each agent comprises:

a second web service to handle application interface (API) requests;

a goal state driver to perform the second process;

goal states for applications running on the physical host the agent is running on;

a second event library configured to generate host level events;

an actual state as reported by the resource managers;

the resource managers; and

a local storage.

4. The method of claim 3 , further comprising triggering the second process periodically.

5. The method of claim 3 , further comprising triggering the second process after every event.

6. An apparatus, comprising:

electronic hardware circuitry configured to:

perform at a lifecycle manager a first process, the first process comprising:

determining nodes in a cluster to run an application;

determining a difference between a cluster goal state and a cluster actual state for the application;

determining goal state for each node; and

sending respective goal state to agents;

perform at each agent a second process, the second process comprising:

determining a difference between the goal state of the node and an actual state of the node;

determining actions to be performed based on the difference between the goal state of the node and the actual state of the node; and

sending actions to resource managers to perform based on the difference between the goal state of the node and the actual state of the node.

7. The apparatus of claim 6 , wherein the circuitry comprises at least one of a processor, a memory, a programmable logic device or a logic gate.

8. The apparatus of claim 6 , wherein the lifecycle manager comprises:

a first web service to handle application interface (API) requests;

a cluster goal state driver to perform the first process;

a cluster goal state;

a first event library configured to generate cluster level events;

a cluster actual state formed from actual states of each agent; and

a persistence component comprising key/value store for a cluster state.

9. The apparatus of claim 8 , wherein each agent comprises:

a second web service to handle application interface (API) requests;

a goal state driver to perform the second process;

goal states for applications running on the physical host the agent is running on;

a second event library configured to generate host level events;

an actual state as reported by the resource managers;

the resource managers; and

a local storage.

10. The apparatus of claim 9 , wherein the circuitry is further configured to trigger the second process periodically.

11. The apparatus of claim 9 , wherein the circuitry is further configured to trigger the second process after every event.

12. An article comprising:

a non-transitory computer-readable medium that stores computer-executable instructions, the instructions causing a machine to:

perform at a lifecycle manager a first process, the first process comprising:

determining nodes in a cluster to run an application;

determining differences between a cluster goal state and a cluster actual state for the application;

determining goal state for each node; and

sending respective goal state to agents;

perform at each agent a second process, the second process comprising:

determining difference between the goal state of the node and an actual state of the node;

determining actions to be performed based on the differences between the goal state of the node and the actual state of the node; and

sending actions to resource managers to perform based on the differences between the goal state of the node and the actual state of the node.

13. The article of claim 12 , wherein the lifecycle manager comprises:

a first web service to handle application interface (API) requests;

a cluster goal state driver to perform the first process;

a cluster goal state;

a first event library configured to generate cluster level events;

a cluster actual state formed from actual states of each agent; and

a persistence component comprising key/value store for a cluster state.

14. The article of claim 13 , wherein each agent comprises:

a second web service to handle application interface (API) requests;

a goal state driver to perform the second process;

goal states for applications running on the physical host the agent is running on;

a second event library configured to generate host level events;

an actual state as reported by the resource managers;

the resource managers; and

a local storage.

15. The article of claim 14 , wherein the instructions causing a machine to trigger the second process periodically.

16. The article of claim 14 , wherein the instructions causing a machine to trigger the second process after every event.