Systems and methods for java virtual machine management

Abstract

A virtual machine (VM) management utility tool may deploy an object model that may persist one or more virtual machine dependencies and relationships. Through a web front-end interface, for example, the VMs may be started in a specific order or re-booted, and the tool automatically determines the additional VMs that need to be re-booted in order to maintain the integrity of the environment. Through the web interface, for example, the object model may be managed, and start-up orders or VM dependencies may be updated. For VMs that may not start under load, the object model may block access to the VM until the VM is fully initialized.

What is claimed is: 
     
       1. A method for managing virtual machines, the method comprising:
 querying, by a computer, a dependency map associated with a first virtual machine based on a request to perform a first action on the first virtual machine, the dependency map indicating a set of one or more dependent virtual machines that are dependent on the first virtual machine, 
 wherein the dependency map identifies a second virtual machine dependent on the first virtual machine and indicates that the first virtual machine is blocked from receiving requests; and 
 preventing the blocked first virtual machine and the dependent second virtual machine from receiving any requests from a user. 
 
     
     
       2. The method according to  claim 1 , further including identifying, by the computer a sequential ordering of actions including the first action, wherein the sequential ordering is based on a weight assigned to each one of the dependent virtual machines. 
     
     
       3. The method according to  claim 1 , wherein the first action is a type of action selected from a group consisting of: start, bounce, shut down, and reboot. 
     
     
       4. The method according to  claim 1 , further including:
 querying, by the computer, a server hosting the first virtual machine; and 
 determining, by the computer, a status of the first virtual machine upon identifying the server hosting the first virtual machine. 
 
     
     
       5. The method according to  claim 4 , further including querying, by the computer, a cell including a server hosting the dependent second virtual machine to obtain the dependency map. 
     
     
       6. The method according to  claim 1 , further including determining, by the computer, a status of the first virtual machine in response to receiving a request to perform the first action with the first virtual machine. 
     
     
       7. The method according to  claim 1 , further including identifying, by the computer, a sequential ordering of actions including the first action, wherein the sequential ordering is further based on a type of the first action. 
     
     
       8. The method according to  claim 1 , further including identifying, by the computer, the dependent second virtual machine that depends on the first virtual machine according to the dependency map in response to the computer identifying the second virtual machine. 
     
     
       9. The method according to  claim 1 , further including automatically generating, by the computer, a do not start list. 
     
     
       10. The method according to  claim 9 , wherein the do not start list is based upon the dependency map. 
     
     
       11. The method of  claim 10 , wherein do not start list is a machine-readable computer file including a list of dependent virtual machines prohibited from execution by one or more servers hosting each respective dependent virtual machine. 
     
     
       12. The method according to  claim 1 , further including determining, by the computer, an action queue to perform a second action for the dependent second virtual machine prohibited from receiving the request according to the dependency map, wherein the action queue is determined based on a load list including the first virtual machine. 
     
     
       13. The method according to  claim 1 , further including in response to the first virtual machine performing the action issuing, by the computer, the request to perform a second action to the dependent second virtual machine based on the action queue. 
     
     
       14. The method according to  claim 1 , further including determining, by the computer, whether the first virtual machine is listed in a do not start list, wherein the do not start list is a machine-readable computer file including a list of virtual machines prohibited from starting. 
     
     
       15. The method according to  claim 14 , further including automatically updating, by the computer, the do not start list based upon a sequential ordering of actions and the dependency map. 
     
     
       16. A hardware computer readable storage device comprising instructions that, when executed, cause a machine to at least:
 query a dependency map associated with a first virtual machine based on a request to perform a first action on the first virtual machine, the dependency map indicating a set of one or more dependent virtual machines that are dependent on the first virtual machine, 
 wherein the dependency map identifies a second virtual machine dependent on the first virtual machine and indicates that the first virtual machine is blocked from receiving requests; 
 prevent the blocked first virtual machine from receiving any requests from a user; and 
 prevent the dependent second virtual machine from receiving any requests from the user. 
 
     
     
       17. The hardware computer readable storage device system of  claim 16 , wherein the instructions, when executed, further cause the machine to identify a sequential ordering of actions including the first action, wherein the sequential ordering is based on a weight assigned to each one of the dependent virtual machines. 
     
     
       18. The hardware computer readable storage device system of  claim 16 , wherein the first action is a type of action selected from a group consisting of: start, bounce, shut down, and reboot. 
     
     
       19. The hardware computer readable storage device system of  claim 16 , wherein the instructions, when executed, further cause the machine to identify a sequential ordering of actions including the first action, wherein the sequential ordering is based on a type of the first action. 
     
     
       20. The hardware computer readable storage device system of  claim 16 , wherein the action queue is determined based on a load list including the first virtual machine.