ASSISTING SERVER MIGRATION

• US 20110107327A1
• Filed: 10/29/2009
• Published: 05/05/2011
• Est. Priority Date: 10/29/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Pfitzmann, Birgit M., Filepp, Robert, Peterson, Brian L., Ramasamy, Harigovind V., Bhattacharya, Kamal, Westerman, David L., Barros, James R. S. II, Cheng, Karen, Barkie, Eric J., Joukov, Nikolai, Young, Christopher C., Malone, Colm V., Galloway, Kevin D., Sun, Kewei, Vogl, Norbert G., Luo, Jing
• Granted Patent: US 8,850,423 B2
• Time in Patent Office: Days
• US Class Current: 717/176
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order

Abstract

The present invention describes a method and system for preparing a migration and consolidation of at least one source application to be migrated to or consolidated in at least one heterogeneous server device. A computing system selects at least one prospective target platform component based on an evaluation of at least one source platform component, a requirement of the at least one source application, and a compatibility and an affinity of the at least one prospective target platform component. The computing system collects first metadata of the at least one source platform component and the at least one prospective target platform component. The computing system collects second metadata associated with the migration and consolidation. The computing system groups the first metadata and the second metadata into a RFM (Request For Migration). The computing system prepares and configures a final target platform in accordance with the RFM.

Claims

1. A computer-implemented method for preparing a migration and consolidation of at least one source application to be migrated to or consolidated in at least one heterogeneous server device, the method comprising:

selecting at least one prospective target platform component based on one or more of;

an evaluation of at least one source platform component and a requirement of the at least one source application, wherein the source platform component referring to an individual dependency that the at least one source application has upon hardware, software or at least one attribute of the hardware and software, the prospective target platform component referring to an individual software, hardware or attributes of the individual software and hardware to be provisioned for the at least one server device;

collecting first metadata of the at least one source platform component and the at least one prospective target platform component;

collecting second metadata associated with the migration and consolidation; and

preparing and configuring a final target platform based on the first metadata and the second metadata, the final target platform referring to a sum of dependencies a final target application has upon hardware or software, the final target application referring to an application that exists after the migration and consolidation.

2. The computer-implemented method according to claim 1 further comprises one or more of:

discovering information of source platform, the source platform referring to a sum of dependencies a source application has upon software or hardware, the source application referring to an application in the at least one server device to be migrated or consolidated; and

packing the first metadata and the second metadata into a RFM (Request For Migration) data structure specifying the at least one selected prospective target platform component, the first metadata and the second metadata.

3. The computer-implemented method according to claim 2 further comprises:

providing an interface for allowing a user to design the RFM data structure.

4. The computer-implemented method according to claim 3, wherein the interface performs steps of:

allowing the user to search the source platform based on a search criterion;

presenting the user a first option to migrate the at least one source platform component to the final target platform without a modification;

presenting the user a second option to modify attributes of the at least one source platform component;

presenting the user a third option to specify at least one final target platform component to be added to at least one final target platform, the at least one final target platform referring to an individual dependency that the final target application has upon; and

intelligently suggesting configuration values of the at least one final target platform component.

5. The computer-implemented method according to claim 1 further comprises:

choosing the at least one prospective target platform component based on a compatibility and an affinity of the at least one prospective target platform component; and

providing a data repository for storing information of one or more of;

at least one source platform and the at least one source platform component, the at least one source platform referring to a sum of dependencies that the at least one source application has upon hardware or software;

an inventory of at least one prospective target platform and the at least one prospective target platform component, the at least one prospective target platform referring to a sum of software and hardware to be provisioned for the at least one server device;

the compatibility and the affinity of the at least one prospective target platform component; and

the final target platform and at least one final target platform component, the at least one final target platform referring to an individual dependency that the final target application has upon.

6. The computer-implemented method according to claim 5, wherein the data repository further comprises:

an interface for enabling an access to the data repository by catching inbound requests received via a protocol and invoking actions against the data repository.

7. The computer-implemented method according to claim 5 further comprises:

providing an asset library for storing the inventory of at least one prospective target platform, the at least one prospective target platform component and the compatibility and the affinity of the at least one prospective target platform component.

8. The computer-implemented method according to claim 7 further comprises:

providing an asset editor for allowing a user to populate or edit the inventory of at least one prospective target platform, the at least one prospective target platform component and the compatibility and the affinity of the at least one prospective target platform component.

9. The computer-implemented method according to claim 8, wherein the asset editor comprises:

a means for adding, changing or deleting information in the asset library associated with the at least one prospective target platform components and attributes of the at prospective target platform components.

10. The computer-implemented method according to claim 9, wherein the added, changed or deleted information in the asset library comprises one or more of:

a virtual machine and network components virtualized as a separate machine, a network implementation, an operating system, a file system, a file system type, middleware, a software product, an installing method of the software product, a processor, hardware architecture, a physical data center location, a functional classification of the data center, a security classification of the data center, a user of the final target platform.

11. The computer-implemented method according to claim 2, wherein the preparing and configuring comprises steps of:

ensuring the at least one selected prospective target platform component specified by the RFM data structure is installed and equipped on the final target platform.

12. The computer-implemented method according to claim 2, wherein the preparing and configuring supports a submission of the RPM data structure thorough steps of:

provisioning at least one operating system, at least one file system, at least one user, at least one user group, at least one network configuration as defined for the final target platform by the RFM data structure; and

installing middleware and software for the final target platform according to at least one instruction in the RFM data structure.

22. A computer readable medium embodying computer program instructions being run by a processor for causing a computer to perform method steps for preparing a migration and consolidation of at least one source application to be migrated to or consolidated in at least one heterogeneous server device, said method steps comprising the steps of claim 1.

23. A method of deploying a computer program product including programs of instructions in a computer readable medium for preparing a migration and consolidation of at least one source application to be migrated to or consolidated in at least one heterogeneous server device, wherein, when the programs of instructions are run by at least one processor, the computer program product performs the steps of claim 1.

13. A computer-implemented system for preparing a migration and consolidation of at least one source application to be migrated to or consolidated in at least one heterogeneous server device, the system comprising:

a memory device; and

a processor unit in communication with the memory device, the processor unit performs steps of;

selecting at least one prospective target platform component based on one or more of;

an evaluation of at least one source platform component and a requirement of the at least one source application, wherein the source platform component referring to an individual dependency that the at least one source application has upon hardware, software or at least one attribute of the hardware and software, the prospective target platform component referring to an individual software, hardware or attributes of the individual software and hardware to be provisioned for the at least one server device;

collecting first metadata of the at least one source platform component and the at least one prospective target platform component;

collecting second metadata associated with the migration and consolidation; and

preparing and configuring a final target platform data structure based on the first metadata and the second metadata, the final target platform referring to a sum of dependencies a final target application has upon hardware or software, the final target application referring to an application that exists after the migration and consolidation.

14. The computer-implemented system according to claim 13 wherein the processor unit further performs:

discovering information of source platform, the source platform referring to a sum of dependencies a source application has upon software or hardware, the source application referring to an application in the at least one server device to be migrated or consolidated; and

packing the first metadata and the second metadata into a RFM (Request For Migration) data structure specifying the at least one selected prospective target platform component, the first metadata and the second metadata

15. The computer-implemented system according to claim 14 wherein the processor unit further performs:

providing an interface for allowing a user to design the RFM data structure.

16. The computer-implemented system according to claim 15, wherein the interface performs steps of:

allowing the user to search the source platform based on a search criterion;

presenting the user a first option to migrate the at least one source platform component to the final target platform without a modification;

presenting the user a second option to modify attributes of the at least one source platform component;

presenting the user a third option to specify at least one final target platform component to be added to at least one final target platform, the at least one final target platform referring to an individual dependency that the final target application has upon; and

intelligently suggesting configuration values of the at least one final target platform component.

17. The computer-implemented system according to claim 13, wherein the processor unit further performs:

choosing the at least one prospective target platform component based on a compatibility and an affinity of the at least one prospective target platform component; and

providing a data repository for storing information of one or more of;

at least one source platform and the at least one source platform component, the at least one source platform referring to a sum of dependencies that the at least one source application has upon hardware or software;

an inventory of at least one prospective target platform and the at least one prospective target platform component, the at least one prospective target platform referring to a sum of software and hardware to be provisioned for the at least one server device;

the compatibility and the affinity of the at least one prospective target platform component; and

the final target platform and at least one final target platform component, the at least one final target platform referring to an individual dependency that the final target application has upon.

18. The computer-implemented system according to claim 17, wherein the data repository further comprises:

an interface for enabling an access to the data repository by catching inbound requests received via a protocol and invoking actions against the data repository.

19. The computer-implemented system according to claim 17, wherein the processor unit further performs:

providing an asset library for storing the inventory of at least one prospective target platform, the at least one prospective target platform component and the compatibility and the affinity of the at least one prospective target platform component.

20. The computer-implemented system according to claim 19, wherein the processor unit further performs:

providing an asset editor for allowing a user to populate or edit the inventory of at least one prospective target platform, the at least one prospective target platform component and the compatibility and the affinity of the at least one prospective target platform component.

21. The computer-implemented system according to claim 20, wherein the asset editor comprises:

a means for adding, changing or deleting information in the asset library associated with the at least one prospective target platform components and attributes of the at prospective target platform components.