METHOD AND SYSTEM FOR PERFORMING DEPLOYMENT MANAGEMENT

• US 20120005646A1
• Filed: 06/30/2010
• Published: 01/05/2012
• Est. Priority Date: 06/30/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: MANGLIK, Gaurav, SRIRAM, Vijay Nichinbati, GANGULY, Shamik, SAH, Rohit, MUKHERJEE, Sourav
• Granted Patent: US 9,292,343 B2
• Time in Patent Office: Days
• US Class Current: 717/105
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence

Abstract

A system, method, computer program product are shown for automatically performing deployment activities that can handle deployments for any-sized organization, even for deployments at the enterprise level. According to some approaches, modeling is performed to generate a model of the components in the computing environment. Dependency graphs can be generated for the deployment, and used to then automatically perform the deployment.

Claims

1. A computer implemented method for performing deployment with a processor, comprising:

identifying a model corresponding to a topology, where the model corresponds to an inventory of components in the topology and dependency relationships for the components;

using the model to identify dependencies for a deployment;

based at least in part on the identified dependencies, determining a deployment procedure; and

implementing the deployment procedure to perform the deployment in the topology.

2. The method of claim 1 in which the model comprises a dependency graph for the components.

3. The method of claim 1 in which the model comprises operational steps to perform the deployment.

4. The method of claim 3 in which the operational steps comprise optimizations based at least in part upon the existence of other components that are subject to the deployment.

5. The method of claim 4 in which the optimizations are used to minimize downtime for the components.

6. The method of claim 1 in which the model is generic to a class of the components or is specific to an individual component.

7. The method of claim 1 in which the identified dependencies is based at least in part upon a dependency tree having one or more root nodes and zero or more leaf nodes.

8. The method of claim 7 in which one path from root node to leaf node is handled in a single downtime window.

9. The method of claim 7 in which there are multiple paths root node to leaf node, and where the components are patched to ensure at least one patch is available from the root node to the leaf node.

10. The method of claim 1 in which the deployment comprises provisioning, patching, configuration, or reconfiguration.

11. A computer program product embodied on a computer usable medium, the computer readable medium having stored thereon a sequence of instructions which, when executed by a processor causes the processor to execute a method for performing deployment with, the method comprising:

identifying a model corresponding to a topology, where the model corresponds to an inventory of components in the topology and dependency relationships for the components;

using the model to identify dependencies for a deployment;

based at least in part on the identified dependencies, determining a deployment procedure; and

implementing the deployment procedure to perform the deployment in the topology.

12. The computer program product of claim 11 in which the model comprises a dependency graph for the components.

13. The computer program product of claim 11 in which the model comprises operational steps to perform the deployment.

14. The computer program product of claim 13 in which the operational steps comprise optimizations based at least in part upon the existence of other components that are subject to the deployment.

15. The computer program product of claim 14 in which the optimizations are used to minimize downtime for the components.

16. The computer program product of claim 11 in which the model is generic to a class of the components or is specific to an individual component.

17. The computer program product of claim 11 in which the identified dependencies is based at least in part upon a dependency tree having one or more root nodes and zero or more leaf nodes.

18. The computer program product of claim 17 in which one path from root node to leaf node is handled in a single downtime window.

19. The computer program product of claim 17 in which there are multiple paths root node to leaf node, and where the components are patched to ensure at least one patch is available from the root node to the leaf node.

20. The computer program product of claim 11 in which the deployment comprises provisioning, patching, configuration, or reconfiguration.

21. A computer-based system for performing deployment, comprising:

a computer processor to execute a set of program code instructions;

a memory to hold the program code instructions, in which the program code instructions comprises program code to identify a model corresponding to a topology, where the model corresponds to an inventory of components in the topology and dependency relationships for the components, use the model to identify dependencies for a deployment, determine a deployment procedure based at least in part on the identified dependencies, and to implement the deployment procedure to perform the deployment in the topology.

22. The system of claim 21 in which the model comprises a dependency graph for the components.

23. The system of claim 21 in which the model comprises operational steps to perform the deployment.

24. The system of claim 23 in which the operational steps comprise optimizations based at least in part upon the existence of other components that are subject to the deployment.

25. The system of claim 24 in which the optimizations are used to minimize downtime for the components.

26. The system of claim 21 in which the model is generic to a class of the components or is specific to an individual component.

27. The system of claim 21 in which the identified dependencies is based at least in part upon a dependency tree having one or more root nodes and zero or more leaf nodes.

28. The system of claim 27 in which one path from root node to leaf node is handled in a single downtime window.

29. The system of claim 27 in which there are multiple paths root node to leaf node, and where the components are patched to ensure at least one patch is available from the root node to the leaf node.

30. The system of claim 21 in which the deployment comprises provisioning, patching, configuration, or reconfiguration.