Porting virtual images between platforms

• US 8,984,503 B2
• Filed: 12/31/2009
• Issued: 03/17/2015
• Est. Priority Date: 12/31/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Poddar, Indrajit, Gaponenko, Yulia, Miroshkin, Alexey, Sukharev, Igor, Ponomarev, Vladislav Borisovich
• Primary Examiner(s): Jalil, Neveen Abel
• Assistant Examiner(s): ELLIS, MATTHEW J
• Application Number:
  US12/651,277
• Publication Number:
  US 20110161952A1
• Time in Patent Office: 1,902 Days
• Field of Search: 717/168, 717171-173
• US Class Current: 717/173
• CPC Class Codes: G06F 16/583 using metadata automatically derived from the content
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines

Abstract

In an embodiment, an approach is provided that differences a source topology model associated with a source platform and a target topology model associated with a target platform. This differencing is performed by a processor and results in a topology difference. An operation in a workflow model is obtained from an asset library, the operation being associated with the topology difference. At least a portion of the asset library is stored in a persistent storage medium. The operation to deploy a portion of a solution is transmitted for deployment. The deployed portion of the solution includes a target image compatible with the target platform.

Claims

1. An information handling system comprising:

one or more processors;

a memory accessible by at least one of the processors;

a persistent storage medium accessible by at least one of the processors;

a network interface that connects the information handling system to a computer network, wherein the network interface is accessible by at least one of the processors; and

a set of instructions stored in the memory and executed by at least one of the processors in order to perform actions of;

differencing a source topology model associated with a source platform and a target topology model associated with a target platform, wherein the source platform is a first cloud and the target platform is a second cloud, the differencing resulting in a topology difference, wherein the differencing comprises;

comparing a first set of model units corresponding to the source platform and a second set of model units corresponding to the target platform, wherein the comparing results in one or more changed model units and one or more common model units;

retrieving a first set of automation step models from the source topology model that correspond to the common model units, wherein the first set of automation step models describe a first set of automation steps used to deploy the common model units;

searching an asset library for the changed model units, the searching resulting in a second set of automation step models corresponding to the changed model units, wherein the second set of automation step models describe a second set of automation steps used to deploy the changed model units;

obtaining an operation in a workflow model from the asset library, wherein the workflow model includes the first and second sets of automation step models, and wherein the operation is associated with the topology difference and wherein at least a portion of the asset library is stored in the persistent storage medium; and

transmitting the operation to deploy at least a portion of a solution,

wherein the deployed portion of the solution includes a target virtual image compatible with the target platform.

2. The information handling system of claim 1 wherein the actions further comprise:

deploying the portion of the solution at the target platform by executing the operation.

3. The information handling system of claim 1 wherein the actions further comprise:

searching metadata for at least one base virtual image metadata that is associated with the target platform.

4. The information handling system of claim 3 wherein the actions further comprise:

retrieving one or more base virtual image descriptions from the metadata stored in the asset library in response to the searching.

5. The information handling system of claim 1 wherein the actions further comprise:

associating the topology difference to the source topology model and the target topology model; and

storing the topology difference and the associations in the asset library as a patch.

6. The information handling system of claim 5 wherein the actions further comprise:

receiving a second source topology model that is partially common to the source topology model and a second target platform that is partially common to the target platform;

searching one or more patches, including the patch, in the asset library, wherein the search includes the associated source topology model;

retrieving the patch from the asset library in response to the search; and

applying the retrieved patch to the second source topology model resulting in a second target topology model that associated with the second target platform.

7. The information handling system of claim 1 wherein the differencing results in an identification of one or more new units, wherein the new units are found in the target topology model and are not found in the source topology model, and wherein the actions further comprise:

searching the asset library for the new units.

8. The information handling system of claim 1 wherein the source platform is a first hypervisor running on a first set of one or more computer systems, wherein the target platform is a second hypervisor running on a second set of one or more computer systems, and wherein the first and second hypervisors are different types of hypervisors.

9. The information handling system of claim 1 wherein the source and target topology models each include metadata describing one or more software application components, a middleware software application component, and a guest operating system component.

10. The information handling system of claim 9 wherein the metadata included with the source and target topology models each further include one or more virtual image deployment parameters, wherein the source topology model includes source topology model units of source configuration parameters corresponding to the source cloud and source credentials and source service endpoints, wherein the target topology model includes target topology model units of target configuration parameters corresponding to the target cloud and target credentials and target service endpoints.

11. The information handling system of claim 10 wherein the actions further comprise:

associating each of the source topology model units with a source automation step model that details one or more of the operations used to deploy the associated source topology model unit;

associating each of the target topology model units with a target automation step model that details one or more of the operations used to deploy the associated target topology model unit; and

storing each of the target automation step models in the workflow model.

12. A computer program product stored in a computer readable storage device, comprising functional descriptive material that, when executed by an information handling system, causes the information handling system to perform actions comprising:

differencing a source topology model associated with a source platform and a target topology model associated with a target platform, the differencing resulting in a topology difference, wherein the source platform is a first cloud and the target platform is a second cloud, and wherein the differencing comprises;

comparing a first set of model units corresponding to the source platform and a second set of model units corresponding to the target platform,

wherein the comparing results in one or more changed model units and one or more common model units;

retrieving a first set of automation step models from the source topology model that correspond to the common model units, wherein the first set of automation step models describe a first set of automation steps used to deploy the common model units;

searching an asset library for the changed model units, the searching resulting in a second set of automation step models corresponding to the changed model units, wherein the second set of automation step models describe a second set of automation steps used to deploy the changed model units;

obtaining an operation in a workflow model from the asset library, wherein the workflow model includes the first and second sets of automation step models, and wherein the operation is associated with the topology difference, and wherein at least a portion of the asset library is stored in a persistent storage medium; and

transmitting the operation to deploy at least a portion of a solution, wherein the deployed portion of the solution includes a target virtual image compatible with the target platform.

13. The computer program product of claim 12 wherein the actions further comprise:

deploying the portion of the solution at the target platform by executing the operation.

14. The computer program product of claim 12 wherein the actions further comprise:

searching metadata for at least one base virtual image metadata that is associated with the target platform.

15. The computer program product of claim 14 wherein the actions further comprise:

retrieving one or more base virtual image descriptions from the metadata stored in the asset library in response to the searching.

16. The computer program product of claim 12 wherein the actions further comprise:

associating the topology difference to the source topology model and the target topology model; and

storing the topology difference and the associations in the asset library as a patch.

17. The computer program product of claim 16 wherein the actions further comprise:

receiving a second source topology model that is partially common to the source topology model and a second target platform that is partially common to the target platform;

searching one or more patches, including the patch, in the asset library, wherein the search includes the associated source topology model;

retrieving the patch from the asset library in response to the search; and

applying the retrieved patch to the second source topology model resulting in a second target topology model that associated with the second target platform.

18. The computer program product of claim 12 wherein the differencing results in an identification of one or more new units, wherein the new units are found in the target topology model and are not found in the source topology model, and wherein the actions further comprise:

searching the asset library for the new units.

19. The computer program product of claim 12 wherein the source platform is a first hypervisor running on a first set of one or more computer systems, wherein the target platform is a second hypervisor running on a second set of one or more computer systems, and wherein the first and second hypervisors are different types of hypervisors.

20. The computer program product of claim 12 wherein the source and target topology models each include metadata describing one or more software application components, a middleware software application component, and a guest operating system component.

21. The computer program product of claim 20 wherein the metadata included with the source and target topology models each further include one or more virtual image deployment parameters, wherein the source topology model includes source topology model units of source configuration parameters corresponding to the source cloud and source credentials and source service endpoints, wherein the target topology model includes target topology model units of target configuration parameters corresponding to the target cloud and target credentials and target service endpoints.

22. The computer program product of claim 21 wherein the actions further comprise:

associating each of the source topology model units with a source automation step model that details one or more of the operations used to deploy the associated source topology model unit;

associating each of the target topology model units with a target automation step model that details one or more of the operations used to deploy the associated target topology model unit; and

storing each of the target automation step models in the workflow model.